23 ms·
I seem to remember reading about an incident recently where pilots noticed divergent sensor reading and aborted take-off. It would seem that AoA disagreement w
by matt4077 8y ago
I seem to remember reading about an incident recently where pilots noticed divergent sensor reading and aborted take-off.
It would seem that AoA disagreement would be the very first symptom of the failure that lead to these crashes. Since pilots are likely not to immediately notice this (hence the indicator), this feature may well have given them additional time to sort out a response. Depending on how this failure progressed, it may have even been discovered on previous flights or before take-off.
- Someone1234 8y agoThat's a really good point. The AoA disagree could go off as soon as the nose is lifted, which still may give pilots just enough time to abort take-off or immediately request landing.
- VBprogrammer 8y ago> which still may give pilots just enough time to abort take-off Airliners are committed to takeoff by the point of rotation. Typical ops manuals would abort for any warning before 80kts, at a speed known as V1 they are committed (even in case of engine failure) this typically occurs 10-20kts before rotation speed where the pilot initiates lifting the nose.
- stanski 8y agoGiven that the warning is optional, it would suggest that the AoA sensors are not components that are critical to a safe flight. Well... or so they thought anyway. It's questionable if most pilots would abort a take off because of an AoA sensor discrepancy, especially if they didn't know it controls MCAS or that MCAS exists in the first place. But yeah - good point about it potentially triggering further diagnostics prior to the flight altogether.