That's even more true if getting it wrong means you could die.
That's even more true if getting it wrong means you could die.
Ejecting could save you but send the plane crashing into a city, and that's just one of many scenarios.
If he was flying with instruments in bad weather and felt that he could not trust those instruments that seems like a good reason to eject since you can easily end up in the ground or a mountain. I don't know if switching modes like he did was standard procedure and if the resulting failure was unusual or not. Maybe he wasn't familiar enough with the airplane's systems. That said, there was a real failure that seems to have happened at the worst possible times.
At the end of the day, the bar is set really high for someone in this position.
It seems that a highly qualified marine test pilot is unlikely to be unfamiliar with the airplane's systems
Those 50 hours can be misleading as to his experience with the aircraft.
Pilot switched mode back to normal flight because it was the switch to landing mode is what caused his HUD and PFD to turn off in the first place.
But I served three years in the Swedish army and wasn’t taught to obediently follow command when it makes no sense. I was taught to disobey illegal orders.
I can’t imagine a fighter pilot has so little authority over their actions like you describe.
Aviators are not expected to be checklist-executing drones who "follow protocol." They are expected to have an encyclopedic knowledge of their aircraft's systems so that they know when to follow procedure, what the procedures are designed to do, and what to do when they have a situation where the existing procedures don't apply or conflict with each other.
In my old community, it was a commonplace occurrence when requalifying in the simulator for instructors to deliberately insert situations involving multiple malfunctions whose emergency procedures conflicted with each other, such that blindly "following protocol" would cause you to die.