Second in Command - Not just a seat warmer
Flight International 16-22 September letter to The Editor:
"Following the fatal crash of the Garuda Boeing 737 in Indonesia last year, the company announced several changes to its basic operating procedures. It now specifies the first officer must seize control from the captain if he believes the aircraft is not being flown correctly.
One can imagine the resulting chaos as the copilot attempts to wrest control from the captain on final approach. Realistically, no captain will meekly hand over control without a fight.
One solution is for the copilot to demand the captain go around while he (the copilot) simultaneously selects the landing gear up. It is doubtful any captain would then ignore the copilot's advice and deliberately land wheels up just to make a point. The captain can then blame the copilot for the go around and thus save face."
First officers should always remember they are second in command and not just an occupant in the copilot's seat. As second in command you have certain responsibilities for the safety of the flight. If the captain is engaged in an unstable approach with a good likelihood of landing fast and long, especially on a wet runway, or landing short with high sink rate and idle thrust, then if the captain is intent on pressing on regardless of the consequences and risk of a crash, you as second in command must act quickly and decisively and ask questions later. Don't just sit there transfixed and wondering what to do.
The suggestion in Flight International that in dire circumstances the copilot should demand the captain go-around and to force the go-around by reaching over and selecting the gear lever to up, is one that should be considered. It may be the only option left to prevent a crash.
The CVR will record your actions and prove that you acted decisively and correctly. The old saying of " sometimes you have to cause a crisis to fix a crisis" is very true.