DE version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
61% Positive
Analyzed from 1580 words in the discussion.
Trending Topics
#around#pilots#down#pilot#air#runway#pressure#speed#https#avoid
Discussion (49 Comments)Read Original on HackerNews
https://www.youtube.com/watch?v=Ccq30minme8
Airlines in the US do not pressure pilots to avoid go arounds. Pilots in the US do not delegate life or death decisions to ops, especially since the FAA legally holds them accountable for that. All pilots are aware that they are responsible for the decision to go around or not.
Any airline found to be pressuring pilots to avoid go arounds would be in a world of pain with the FAA.
On cargo flights in particular timing and fuel usage are less critical than passenger flights, and a go around doesn't affect either much.
Pressure to avoid go arounds would also be incredibly counter productive since go arounds exist to preserve life and property. Pilots do go arounds to avoid costly incidents.
You are correct that the question is why they didn't do a go around, but I would bet a large sum of money that airline pressure to avoid go arounds was not a factor.
> The Amazon Prime Air Boeing 767 cargo plane that crashed off a Miami runway on Sunday, killing five people, was operated by a North Carolina company that has been accused by past employees of violating safety regulations, legal documents reveal.
There's a lot in the article, but this allegation is worth highlighting:
> Seuring's attorney, Michael Anello, told the judge that another 21 Air pilot, Johnny Salmonson, "was being pressured to fly in periods of time that were too short to comply with the proper amounts of rest, and that implicated safety. The layovers were too short."
Construction companies in the US do not pressure employees to get shit done. Construction workers do not delegate the decisions to work in sketchy circumstances, especially since OSHA holds them accountable for all that.
See how silly that sounds?
They cook up the rules to be all compliant and whatnot and then everyone breaks them a little pretty often and in tasteful ways in order to actually get the job done. If you get caught or screw up, it's on you.
I assume this sort of pressure happens a lot less with pilots because of the cost of screw ups but there's still probably some implied pressure there.
The thing that amazes me about this is the timeline here:
00:30 The nose and right main gear touched down at a groundspeed of 158 knots.
...
00:19 The left main gear touched down at a groundspeed of 134 knots.
00:15 A pilot called for a go-around.
11 seconds and 24 knots after the nose touched down and then the left main finally also touched down? Wow. Then 4 seconds after all that the go-around. It is one thing to hold the nose off for that long, but a main mount?!
If people die in the process, that's regrettable but its a sacrifice he is willing to make.
It'll be interesting to see the outcome of the NTSB investigation, they're usually quite thorough.
From the reporting and commenting on this incident, that is not the impression I'm getting. This wasn't one bad call after getting half way down the runway, this was a continuous stream of bad decision making for the entire approach, with the copilot suggesting the pilot go around too.
Also: this kind of incident is very rare, so obviously, the vast majority of pilots don't make this mistake.
Don’t get me wrong - if I had to land that plane, I’d likely have overrun the runway too. I’m not saying it’s easy, only that it appears to me that they were operating well outside the documented parameters that are the pilot’s responsibility to know.
I just looked it up, and a 767’s Vref is 122-165kts, with Vref at max weight at 144kts. They touched down at 158kts, nose down. The approach was ~35kts over speed, they were above the glide slope, and not bleeding speed fast enough to sink - so they dropped the nose.
From what I can see, they were screwed the moment they touched down - the last moment they had a reasonable opportunity to abort was when they decided to drop the nose and commit instead.
The interaction here is eerily similar to the pilot interactions preceding the 1997 Korean Air Flight 801 (B747) disaster in Guam [1]. It's not clear based on the NTSB update if the Captain was ignoring the First Officer or the other way around.
[1]: https://en.wikisource.org/wiki/Korean_Air_Flight_801_-_Aircr...
I don't know anything about flying. Is this normal? Doesn't sound like it, but I don't know why the pilots would not have used these things that sound useful.
Really that's all that needs to be said at the moment. They had way too much energy[1], which anyone with flight sim or RC experience will recognize as a routine mistake when hand-flying.
The question is why all (all!) the layers of checklists and warnings and process and ATC direction somehow failed in combination to prevent. Yeah, they should have aborted for sure, but they didn't, and we won't know why for a good while yet.
[1] Which can just as easily mean "too high" as "too fast", c.f. the sink rate warnings in the logs which would be consistent with trying to squeeze the airplane down onto the runway. But again we won't know without more data.
Every single thing they could do wrong at, they did.
There are just too many ways to screw up for that ever to be the case.
For instance, they could also have been lined up to land on something other than the runway they were cleared to land on -- see Air Canada Flight 759, https://en.wikipedia.org/wiki/Air_Canada_Flight_759, which came within 14 feet of colliding with an aircraft on the taxiway they mistook for the runway..
What I don't understand from his analysis though was early on he said the tail wind increased a minute before landing which is too quick to have communicated. If that's true, we need to get better about this. A minute to send a message is ages. It should be automatic between the airport and the aircraft.
Prime Air crash: 10+ mandatory go-around triggers were ignored [video] - https://news.ycombinator.com/item?id=49650689 - September 2026
https://www.youtube.com/watch?v=Xm6G7EOP5Qc