βοΈ: *shriek* *shriek*
π: CFLAGS="-Wno-all -Wno-error"
@katka i honestly don't understand those, thought gpws is inhibited when landing because terrain is sort of supposed to be close?
@pavel lol juan calling into question the pairing of the pilots is actually about the only way i can wrap my head around this
both of the pilots likely went through basically the same situation many times in the simulator. if they trained right their automatic `look ma no brain' reaction should've been to go around.
maybe each pilot indeed would've gone around alone, but through the magic of team work stupidity was made more efficient
@lkundrak @katka
I have no clue but this here is documentation of some random EGPWS implementation with nice explanation:
https://skybrary.aero/sites/default/files/bookshelf/3365.pdf
GPWS has multiple "modes" that are active depending on some criteria; several modes can be active at the same time, and some modes (like mode 1) are always active.
That document categorizes these warnings as:
It looks like there are several ways "TOO LOW TERRAIN" can trigger through modes 4A/4B/4C, but notably any "TOO LOW FLAPS" (4B) or "TOO LOW GEAR" (4A) gets turned into "TOO LOW TERRAIN" (4A/4B) if the plane is going so fast that the pilots are probably not trying to land, which, uh, yeah...
Mode 4C can also generate "TOO LOW TERRAIN" but that is only for "after takeoff" or "during a low altitude go-around".
https://www.ntsb.gov/news/press-releases/Pages/NR20260909.aspx suggests that they had the landing gear extended and flaps at 15 degrees when the callouts came, so I guess this is probably Mode 4B, the flaps warning?