|
|
|
|
|
by asynchronous13
2651 days ago
|
|
> But it's crazy how many, when they're actually faced with catastrophic failure, forget how to fly the damn plane. Your comment makes me sad. Especially since there will be many other people who come to a similar conclusion without adequate information. The runaway trim problem and the new MCAS problem are superficially similar, but the symptoms are distinctly different. The runaway trim manifests itself with a continuous deflection of the trim. Pilots are trained to recognize this symptom and compensate. The new MCAS also affects the trim, but it is engaged in repeated nose-down commands. It has fundamentally different symptoms compared to the older and more widely known runaway condition. There is no absolute reference on the position of the stabilizer. It is a wheel that turns, so a pilot must watch that wheel continuously to know if it keeps turning or if it turns periodically. The controls column has force feedback. The pilot was pulling back with ~50 lbs of force to fight the angle of the trim. Imagine holding a 50 lb dog while simultaneously trying to review emergency procedures to find the source of the problem. The pilot was flying the damn plane, and the symptoms of this problem were different. |
|
There’s an indicator right next to the wheel:
https://qph.fs.quoracdn.net/main-qimg-1dc99dbe662c71d7c470cf...
And the pilots must have recognized it was a trim issue because they countered it multiple times. Why they didn’t flip the stab trim cut off switch is a mystery.
An earlier crew was able to fly the plane. I agree the pilots should have been made aware of MCAS (though either the Ethiopian pilot was shockingly not aware of it or being aware didn’t help him). But at the end of the day the pilots are there to fly the plane, not manage automation:
https://vimeo.com/159496346