Originally Posted by
DozyWannabe
The first warning was not. This is not coming from me, this is coming from the TRE on the sim day, who was well-versed in the event.
Confiture
The first warning was real and should have been longer, dixit the BEA.
DozyWannabe
Are we talking about the same warning? I'm talking about the single "blip" on the traces at about 02:10:08 - that was a single "G"-induced warning, and the aircraft was not about to stall at that point. The first non-transient warning (where the aircraft was actually approaching stall) began at approx. 02:10:48 according to the traces.
DozyWannabe, why do you still reference your statements to outside sources like your TRE from the sim, when it is all written in the BEA final report?
BEA Final report 1.16.3.2 Analysis of the operation of the stall warning
The activations of the warning picked up by the CVR were identified as occurring at between 2 h 10 min 10.4 and 11.3 and between 2 h 10 min 13 and 13.4. The short duration of activation did not make it possible to detect it from the “Stall warning” parameter, but the FWC 1’s “Master warning” parameters were triggered on one point at this time. However, this warning should have continued until about 2 h 10 min 15.5, and then have been triggered again between 2 h 10 min 17 and 19. The disabling of this warning was probably due to the fact that, between 13.4 and 15.5 and then between 17 and 19, and possibly at other times, the three Mach values were abnormally low (three Pitot probes iced up). The warning triggering threshold then suddenly increased to values of about 10°, much greater than the recorded angles of attack, which led to the warning stopping.