What would you do if windshear is occuring and the captain decides to land anyway?
I'd tell them we need to go-around (if we do). Where I work it is split into windshear caution and windshear warning. If it's a warning you cannot land. If they still insist on flying then things are going to get ugly because I'll be sharing the controls with them without fighting for them, but they'll have a lot of explaining to do later, and not just to me.
I'd never want to have to take the controls from someone or fight over the controls, but if it really looked like there could be a good chance the windshear would result in us fighting for controls at full power sinking into the earth short of the runway, you had better believe I prefer to get the "my airplane" part done at a higher altitude.
WWYD if there's a cell at the end of the runway and the captan decides to land?
Mostly the same as above if the thing is a legitimate nasty looking CB, visually or on radar or as advised from ATC.
WWYD if the captain flies an unstabilized approach?
I'd wonder why I didn't say anything to them along the way down. I haven't personally experience the two questions above but I think anyone who's been at the airlines for more than a few months will eventually face this one. The first time, I was a bit timid since I had probably 1700TT and the captain had maybe 5,000 to 10,000 hours? Whatever the amount, much more than me was the point. Because of that I felt like I ought to wait a little and see how the approach went...I was so new to the game and maybe I didn't realize what the plane could do in a given amount of time. Passing 1000 feet we were fast and high but configured. At 500 we were still about a dot high but still at idle as we were about 30 knots above our desired speed. I called out "we're pretty fast" and he said "correcting." In hindsight: how?? I was just about to say "go around" when he did it for me.
The next few times it happened I wasn't as hesitant to be more specific and I think that's what important in this situation. Saying "we're pretty fast" does make it obvious that you're not exactly content with the approach that's being flown, but it's a lot better if you say, "30 knots fast and we're at 500 feet now...I think we need to come around and try this again, go-around." There's not much they can say to that other than, "going around!"
WWYD if someone told you they saw your captain in the bar 7 hours before the flight?
I'd want to talk to that person separately. If they were telling the truth (i.e. able to answer specific questions such as, how long were YOU there, what time, what were they wearing, were they with anyone else, etc.) then it's time to ask the captain and if they deny it, I think a request for them to go do an alcohol test at the airport clinic is in order. This would probably result in getting a new captain if it's a hub, which is a good idea, as whisper down the lane would probably be in progress in the cabin.
Someone saying "that pilot seems drunk!" at a security checkpoint at 5:00AM when the crew had a 9 hour layover after a 16 hour duty period is one thing.
Someone saying, at 7AM, "Hey, co-pilot...I saw your co-worker at my hotel's bar last night at midnight..." is a different story.
WWYD if you're a new FO and the captain told you not to read the checklists or follow company procedures?
Easiest one, because it sounds like this one takes place at the gate on the first flight with the goofball.
I'd politely tell them that's not how it's going to be and if they can't deal with me doing things the standard way right NOW then we're simply going back to the terminal and I'm packing my bags and getting off the plane. If they change their mind, good. I hope they mean it. If they don't, I'll wish them good luck explaining the gate return to their chief pilot.
