- Joined
- Apr 23, 2013
- Messages
- 6,529
- Display Name
Display name:
3G
United has the AOA DISAGREE warning as well.
Didn’t know that about UA.
SWA, AA, and DL use the HUD for CAT II/III approaches and all have the AOA displays (at least in the HUD). UAL uses autoland for CAT II/III and does not have the AOA display.
It’s not about the HUD, it’s about the PFD.
The AOA DISAGREE checklist in the QRH tells you that the left and right AOA vanes disagree and that you may have airspeed and altimeter errors along with their associated "IAS DISAGREE" and "ALT DISAGREE" alerts. There are no pilot actions in the checklist. I don't see how that would be helpful to pilots who are facing a stabilizer runaway. It would be one more thing distracting them from the real threat.
Considering at the time of Lion Air, no one knew about MCAS, and even after, not all was known, any additional information to help diagnose what was occurring may have been helpful but, like computing MCAS saves, its an unknown.
I’m also not convinced it’s the AOA vane either, but potentially the data from the sensor may be getting corrupted or mis-processed somewhere along the way. Or there’s literally wires getting crossed somewhere along the way.
If there had been any additional MCAS activations recorded by FOQA, or reported via ASAP, we'd know about them by now.
I would hope so, but I can’t speak to how information from foreign airlines would make its way to the US reporting systems.
All of this is to say we’re probably closer to agreement than it appears; I happen to be of the opinion Boeing probably did not fully understand the failure mode(s) and/or probably did a poor job of understanding the human reaction to those failure modes.