|
|
|
|
|
by cmurf
2447 days ago
|
|
The flight data publicly available for the three flights, shows rather different MCAS upset behavior in all three cases. They're remarkably similar compared to what you'd expect for a normal flight. But the oscillations in the JT 34 case were not nearly as aggressive as the other flights, no evidence mistrim happened, and in fact the JT 34 pilots didn't recognize it as mistrim, it was the jump pilot who reportedly recognized something (we don't know anything about his thought process so far publicly) and apparently made a recommendation to set stabilizer trim to cutoff. Is there training for getting out of mistrim at low altitude without the benefit of electric trim? Is there training even for MCAS upset as distinguished from runaway trim? We already know there isn't a way to simulate angle of attack sensor failure induced MCAS upset, in MAX simulators. Exactly how was it demonstrated that MCAS upset looks like runaway trim? And how much faster it commands nose down compared to the typical runaway trim case? |
|
No.
>Is there training even for MCAS upset as distinguished from runaway trim?
No.
Remember, MCAS was dropped from the manual, and not included in the end training pilot's would be exposed to prior to being handed a MAX. It was nowhere in that presentation. That was covered in the 60 minutes expose.
https://youtu.be/QytfYyHmxtc
>Exactly how was it demonstrated that MCAS upset looks like runaway trim?
It wasn't. Take a look at the ET302 preliminary crash report. You'll see attached to it the documentation pages from Boeing even remotely related to MCAS. In fact...
https://flightsafety.org/wp-content/uploads/2019/04/Prelimin...
Check Page 30 for the memory item as written. The AD from Lion Air is in there too I think.
Note the condition description explicitly mentions a condition where uncommanded trim is running continuously.
Before the AD issued after the Lion Air crash, no one even knew MCAS was a thing.