I was reading about Air France 447 and came across the line:

The stall warnings stopped, as all airspeed indications were now considered invalid by the aircraft's computer due to the high angle of attack.

In short, due to pilot error, the aircraft (A330) reached a 40 degree angle of attack while under Alternative Law (due to icing conditions) and stalled at 52 kts. Further confusion came from the stall warning suppressing itself after some period of time.

Roughly 20 seconds later, at 02:12 UTC, the pilot decreased the aircraft's pitch slightly, airspeed indications became valid and the stall warning sounded again and sounded intermittently for the remaining duration of the flight, but stopped when the pilot increased the aircraft's nose-up pitch.

It would seem, if the aircraft was stalled, and the computers knew the angle of attack was still far greater than normal, that it's most reasonable to assume the aircraft would still be in a stall even after other sensor data became unreliable. Also, if no airspeed sensors are reading valid data... seems it's most reasonable to assume the aircraft is in a stall... or on the ground (but wheel load sensors can corroborate when that's the case) - not just give up and assume everything is fine.

It seems to me, that perhaps this stall warning is at least partly at fault for this accident.

Why did Airbus design the stall warning system to suppress warnings in this situation?

  • $\begingroup$ AF447 didn't stall at 52 KIAS - the 52-KIAS reading was erroneous, due to the blocked pitot tubes (as evidenced by the fact that, 29 seconds later, the airspeed reading jumped back up to 223 KIAS, while the aircraft was still climbing). It stalled later, after the airspeed indications had become valid again. $\endgroup$
    – Vikki
    Jan 27, 2019 at 1:59

2 Answers 2


Stall warning was inhibited below 60 knots airspeed, in order to eliminate nuisance warnings during taxi and other situations. It is well below the stall speed of an A330 in cruise configuration:

  • landing speed with flaps extended is in order of 135 knots;
  • stall speed in landing configuration would be in order of magnitude of 120 knots;
  • stall speed in cruise configuration way above that.

It was indeed a very tragic circumstance, one of the factors preventing the flight crew from recovering from their situation. The solution however, perhaps in addition to enabling stall warnings for very low speeds in cruise configuration, is to train flight crews in recovering from a fully developed stall. During recovery, the load factor must remain under 2.5 g, the structural limit for an airliner.

This is now mandated by regulation authorities, and the first systems have been certified for training use at airlines. FAA has published 14 CFR part 60 Change 2 for upset recovery training. Alaska Airlines had the first Part 121 simulator certified for Full Stall Training under Part 60 Change 2, in April 2016. The simulator is a B737-800.

  • 2
    $\begingroup$ Is this official/authoritative reasoning? I ask, because it doesn't make much sense. If it's a nuisance, why not have a button to silence it, so pilot knows the stall didn't go away on it's own. Or simply have wheel loading sensors to determine if the aircraft is on the ground or not (inhibiting the warning when on the ground only). The flight crew didn't realize they were developing a full stall partly because the stall indicator silenced itself when nosing up (the opposite of what was expected). A full stall will be at low airspeed, which is precisely when you need the warning. $\endgroup$
    – SnakeDoc
    Jul 7, 2017 at 20:32
  • 3
    $\begingroup$ @SnakeDoc because encouraging the pilots to cancel frequent warnings/alerts can cause them to miss something important. $\endgroup$
    – fooot
    Jul 7, 2017 at 20:35
  • 1
    $\begingroup$ @fooot I would hope stall warnings aren't frequent when at cruise (at least when the computers think the aircraft is at cruise). $\endgroup$
    – SnakeDoc
    Jul 7, 2017 at 20:37
  • 1
    $\begingroup$ The backup speed tape now provides direct AoA indication. In a fully developed stall from cruise altitude at speeds lower than 60 knots, you need way more than a beeping horn. But yeah you do have a point for the cruise configuration. $\endgroup$
    – Koyovis
    Jul 7, 2017 at 20:38
  • 2
    $\begingroup$ @Snakedoc yes agreed on the stall warning and the tragic circumstances. There is a question about adding the stick inputs on this site. $\endgroup$
    – Koyovis
    Jul 7, 2017 at 21:34

The stall warning needs to be an immediate attention-getting alarm that you react to promptly and accurately. If you routinely hear it on landing roll-out or during taxi, and 9,999 times out of 10,000 your reaction has been to cancel it, then on that one time (or less) in a career that you're hearing it for real, there would be a real risk of cancelling it instead of reacting to it. Thus, the need to inhibit nuisance alarms.

The problem on AF447 was two-fold: the defective pitot tube heating setup, and the gross mishandling of the aircraft by the FO. If the pitot tube heat hadn't failed, no accident. If the FO hadn't made control inputs that run counter to every training, every instinct, every habit of flying pilots throughout the world for the last 100+ years, no accident. What that pilot did was so far outside of what's expected that no amount of "normal" systems or procedures was going to do very well dealing with it. You simply don't train for what to do or what to look for in a case where the other pilot does something utterly irrational that defies all common sense and training.

There are things that Airbus aircraft could do differently so that the other pilot knows what sorts of inputs his partner is making, and there are always things that can be done differently in fly-by-wire and warning systems. But at some point, you have to make assumptions that the pilots have been trained and that they won't do things entirely opposite to that training -- especially when you're already in a degraded state without full protections and full air data inputs available.

Enabling nuisance stall warnings & building a habit pattern of cancelling them isn't going to make things better.


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .