Conversation

JESUS ATE YOUR FILESYSTEM πŸ‡ΊπŸ‡¦πŸ‡¨πŸ‡Ώ

✈️: *shriek* *shriek*
πŸ‘”: CFLAGS="-Wno-all -Wno-error"

2
1
1
@lkundrak triggering GPWS and not aborting is some hardcore stuff
1
0
0

JESUS ATE YOUR FILESYSTEM πŸ‡ΊπŸ‡¦πŸ‡¨πŸ‡Ώ

@katka i honestly don't understand those, thought gpws is inhibited when landing because terrain is sort of supposed to be close?

1
0
0
@lkundrak it still triggers if the descent rate is too high
1
0
0

JESUS ATE YOUR FILESYSTEM πŸ‡ΊπŸ‡¦πŸ‡¨πŸ‡Ώ

@katka oh ok

sweet jesus

1
0
0
@lkundrak Well, if you are going to ignore all warnings, at least _ignore all warnings_. When copilot (probably) tells you to go around, and you are already on the ground with few hundred meters of runway remaining, ignore him! And do max reverse and spoilers too. You'll likely still overrun and damage the plane, but hopefully those cars will have chance to escape.

Seriously, those planes should have systems telling them "long landing, can't stop" and possibly "no go" when remaining runway no longer allows go around.

youtube: blancolirio/ NTSB CVR Data Released MIA 21Air 767 Crash [dcf7n0T3D9c]
1
0
1

JESUS ATE YOUR FILESYSTEM πŸ‡ΊπŸ‡¦πŸ‡¨πŸ‡Ώ

Edited yesterday

@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

1
0
0

@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:

  • "SINK RATE": Mode 1, "Excessive Descent Rate"
  • "TOO LOW TERRAIN": Mode 4, "Unsafe Terrain Clearance"

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?

0
0
0
@lkundrak That's not my understanding.

I don't believe pilots were used to doing this in the simulator. In the simulator, they would go around at 1000ft, by the books. They likely knew they were violating the rules, but likely did not want to explain the go-around or something.

My guess would be that on their own, one pilot would land and overrun slightly.

The other one wanted to go around, and would probably do that if he was flying.
0
0
0