upvote
> unclear how speed didn't increase

How can you comment as if you are knowledgeable enough about aviation to speak on this with authority, but you aren't aware that turbofan engines don't have instant throttle response and need time (up to 8 seconds) to spool up? I think a little more restraint is warranted in something like this if you don't know something that basic.

You can actually do the math to work backwards and approximate how much thrust the engines were producing during that time, which was about 15,000 lbf (vs ~120,000 lbf max thrust for a 767-300er) which reduced how quickly they were decelerating by... Maybe a few % or so. But they didn't start accelerating yet. They would have in another second or two, however.

I'll agree that they should have gone around far earlier; getting non-spurious GPWS callouts on final because you're trying to dive and find the glideslope is... Crazy, and configuring landing flaps over the numbers is also crazy, and so is landing 10-20kts faster than the highest possible Vref value for the type, and everything else. But that's fairly obvious...

reply
> How can you comment as if you are knowledgeable enough about aviation to speak on this with authority, but you aren't aware that ...

This is par for the course for HN; smart people applying first-principle thinking on unfamiliar domains for about a minute, which confirms the biases of other outsiders who vote the plausible, but not-quite-right comments to the top.

reply
This is par for the course for HN; smart people failing to interpret a comment in a charitable light, preferring instead to author a condescending reply in an apparent effort to score imaginary points at the expense of intellectually stimulating conversation.
reply
Turbofans being slow to spool up is jets 101.
reply
So presumably OP never took jets 101. Neither have I. So what? The condescension remains unjustified and contrary to fruitful interaction. (See also the "lucky 10000" xkcd.)
reply
This sounds about right to me, so I upvoted.
reply
Lots of armchair experts incorrecting each other
reply
HN is particularly notorious for armchair aviation experts. I am an aerospace engineer having worked in airworthiness & certification as well as maintenance/repair/overhaul on multiple different aircraft types both fixed and rotary. I mention this only to establish my bona fides as someone who knows their shit:

The comments here during the 737 MAX MCAS thing were fucking wild. So many randoms spitting out confidently incorrect nonsense.

reply
> The comments here during the 737 MAX MCAS thing were fucking wild. So many randoms spitting out confidently incorrect nonsense.

Maybe that helps explain some of the fraction of HN that loves LLMs: they found their soulmates.

reply
The most ridiculous one was a poster who claimed that MCAS would run the trim at double the rate of the trim switches.

The trim motors only have 2 speeds - on and off.

reply
HN is notorious for armchair <insert-topic> experts for <insert-topic> you actually know, outside of software, computing/computing-adjacent electronic hardware and startups. “Fucking wild” “confidently incorrect nonsense” is likely the norm on most fringe topics, judging by the few I know about.
reply
That’s all forums in a nut shell. Any time you read about something you’re not personally familiar with it’s “look at all these people who know what they’re talking about… “, as soon as it’s something you are personally familiar with it’s “wtf are these people on about?!”
reply
“Gell-Mann Amnesia“ - usually applied to media when experts scoff at stories they know to be sometimes woefully inaccurate but still accept all the other pages as gospel.

Coined by Michael Crichton (the famous author).

reply
HN = A bunch of weirdly aggressive nerds who fail to explore nuance living in the same prison cell.
reply
Not having handles where they should be at 1000 callout should have been an instant toga party.
reply
That they passed their minimums and still weren't set up correctly is shocking, yes. How can you commit to landing instead of going around when you're not configured for landing?

The more egregious thing to me though is ignoring the GPWS callouts on approach because they were chasing the glideslope. If you can't maintain a stable approach, you need to go around, it's the first thing you learn.

You expect this behaviour from a first-timer in the sim, not a commercial cargo pilot.

reply
> You expect this behaviour from a first-timer in the sim, not a commercial cargo pilot.

I'm curious - are commercial pilots reprimanded for doing a go-round after messing up the approach?

reply
No. They might have to say why they went around but they can't be punished for it (that's a great way to open yourself up to liability even stripping away all of the human elements). And I can't imagine any reason that an airline would truly care since they don't want their planes crashing so they don't want to discourage pilots from going around if they need to do so. The delay incurred is usually fairly small anyways, maybe 20-30 minutes.

However I will say that the majority of unstable approaches (97%!!) do continue to landing: https://flightsafety.org/wp-content/uploads/2017/03/Go-aroun...

...but I think that most of these unstable approaches are likely marginally unstable and only in one dimension. This landing was so far outside the realm of normal it's actually mind boggling that it actually happened. Pilots are trained to immediately go around without questioning it if many of the things that happened on this flight occur (such as not being in landing configuration well before touching down!)

reply
> How can you comment as if you are knowledgeable enough about aviation to speak on this with authority, but you aren't aware that turbofan engines don't have instant throttle response and need time (up to 8 seconds) to spool up? I think a little more restraint is warranted in something like this if you don't know something that basic.

I'm a pilot, and I don't fly turbofans/jets. Not claiming any "authority", but qualified to comment... It's not "something that basic" unless you fly in that category, there's a lot more to aviation experience than knowing a fact about an engine you don't use. (But hey, congrats to you that you know it!)

> I think a little more restraint is warranted in something like this..

More restraint than saying "unclear <i.e. to me> why ...", an exact statement about what I didn't know, which harms no one and led to several informative explanations by people who know (most of them in good spirit)?

This is what good conversation is about.

...

Anyway, the point I was making holds and is this:

Orthogonal to whether they could/should have gone around at that point, and given that they stayed on the ground after all, it may turn out that that 4 seconds of indecision (instead of pure deceleration) may have directly contributed to the fatalities at the end of the crash.

reply
> While they were still late in calling a go-around (they should have done it before being anywhere close to touching down due to their unstable approach)

Barring a massive tailwind, they had enough groundspeed to go around at touchdown (158 kts).

I think we'll find throttling to G-A and then aborting the G-A caused the crash. If they'd committed to landing they at least wouldn't have overshot with that much energy. If they'd decided to G-A even at 00:15, they may have been well within margin to take back off.

reply
They didn't have much runway left at 00:15 and were far slower than 158 at that point. They came in far too fast, descending too rapidly; first touch was >50% down the runway, and they didn't get the left gear down, so the spoilers and brakes didn't apply until even later.

Should have had a better approach; should have gone around before they even touched the ground; conditional on the bad approach and first touch, they should have gone around after the initial touch 50% down the runway. But they made the wrong choices at all of those points.

reply
Yea, they couldn’t get the left gear down because they they had enough airspeed to execute a go-around!

Literally 5 consecutive minutes of making 100s of wrong decisions snatching defeat from the jaws of victory.

According to news reports, a magistrate judge at OSHA has been sandbagging an investigation into retaliatory firings by this airline (of pilots who reported unsafe practices with maintenance, CRM, training, scheduling, everything). I wonder if the NTSB will include that judge in the investigation. It seems like he or she has a lot to answer for.

https://www.cbsnews.com/news/miami-plane-crash-21-air-safety...

reply
Do we have a name for the judge?
reply
> But they made the wrong choices at all of those points.

This tends to be something we see in most incidents, because the cases where someone makes the right choice at one of the points tend to not become incidents.

An interesting thought is that the more obviously bad/incompetent/terrible decisions or (in)actions were involved in an incident, the better it is, because it means more things had to go wrong for a disaster to occur (more slices of cheese in the Swiss Cheese model).

reply
Yeah, to some extent. But you see a lot more of this in GA (or Part 135) than in Part 121 airline operations. This was exceedingly bad judgement by real professional pilots in a 767.
reply
> They didn't have much runway left at 00:15 and were far slower than 158 at that point

You're correct. When they first annunciate G-A, they've missed the chance. (They almost certainly had enough airspeed to G-A even after touching down, though.)

My question is whether throttling up for G-A at 00:15 is what caused the overshoot to extend out of the airport (versus if they'd committed to braking). This will come down to runway conditions, braking performance and the throttle responsse of their engines.

reply
> This will come down to runway conditions, braking performance and the throttle responsse of their engines.

Well also, at what time point did all the tires finally make simultaneous firm contact with the ground? Ie were they going slow enough for braking performance to even matter?

reply
> I think we'll find throttling to G-A and then aborting the G-A caused the crash.

Not even a chance.

reply
> (unclear how speed didn't increase)

Large high-bypass turbofan engines take several seconds to spool up from idle (as they would be on landing) to full thrust. The 4 seconds that the thrust levers spent in the full thrust position in this accident was not long enough.

reply
The go-around decision was far too late. Remember the engines need significant time to spool up. The decision to cancel the go-around was correct (conditional on the preceding series of terrible decisions).
reply
They were over takeoff velocity at that point and could have bounced up in the air and waited for the thrust to come. Would have been sketchy but better than what did happen.
reply
They were not over takeoff velocity at that point. They were at 120 knots when they initiated GA and slowed to 117 knots before aborting (again, the engines take time to spool up despite full thrust configuration and no braking over those seconds). Takeoff is at least 130 knots, I don't know for their exact configuration. (At max takeoff weight it's something like 153 knots, but at the end of their flight they aren't carrying a full fuel load.)
reply
deleted
reply
mind you those numbers are seconds until the cvr stopped recording. they were a few hundred feet from the end of the runway when they initiated the go around and like the other poster said the turbines do take time to spool up from idle. they were so far out of normal spec for landing that it was absolutely pilot fault but not at the far end of the runway. they were not stabilized on approach way further back about 5 min or so. (if you're not stabilized on approach you are required to go around). they even called for flaps 30 halfway down the runway which is also not allowed for a stabilized approach.
reply
Spool up time is 8-10s on high-bypass turbofan engines. They tried to go around maybe 1000ft from the end of the runway? It was far far too late to even try it at that point.

Sadly if they had made the call earlier they were going so fast they were basically at rotation speed when they touched down so could have just pulled back and gotten into the air.

They landed flat (and the left wing refused to come down) because they tried to force the plane onto the runway. That just doesn't work. The wings are creating too much lift when you're that fast.

Disclosure: Pilot but not ATP or Jet rated.

reply
Isn’t there a regulation for idle to full go-around thrust in a maximum of 8 seconds?

If so, it’s tight… but i feel like they should have made it if they had stuck to that plan. They commanded full power 15 seconds before the crash, and were pretty close to (if not slightly above) their stall speed (depends on load). I suspect they just needed another 10-20 knots and enough energy to climb.

reply
> They commanded full power 15 seconds before the crash

Not 15 seconds before the crash, 15 seconds before the end of the recording. Then overran the runway 10 seconds before the end of the recording, then started crashing into objects 7 seconds before the end of the recording.

Thrust was reduced back to idle 11 seconds before the end of the recording, so just before departing the runway.

reply
Ah, those timings make a lot more sense.

They aborted the go-around attempt because they were literally at the end of the runway; Probably because they thought it would be "safer" to run off the end without the engines rapidly reaching full thrust.

reply
You’re imagining a last minute perfectly executed response after what appears to be a series of gross errors of judgement. Rarely works that way.
reply
> Rarely works that way.

How sure are you? Could it actually happen that way 95% of the time, which means they don’t crash and we never hear about it? Likely a pilot gets disciplined for the other errors and nobody else cares? This exact thing could happen 20 times with everything turning up relatively ok and we only heard about it because they didn’t make that final call correctly either.

To be clear I’m not an aviator, just an armchair statistician with an interest in aviation

reply
This was a discussion in the aviation subreddit too. I am also not an aviator, but just someone with an interest.

What the outcome of the discussion was that it depends on the culture and training of the organisation. It could be possible that it does happen like this 95% of the time with no crash in that specific organisation.

reply
The fact they were even in that situation is only worth philosophizing about to a point. Because they were only in that situation due to what appears to be a series of totally unacceptable decisions that got them there. Based on everything that's come out, I'm comfortable saying as a former military aviator that in my opinion, this crash happened due to a complete failure of airmanship on the part of both crew members.

- a) Flying an unacceptably sloppy approach that put them on short final going that fast, high, and overpowered. Professionalism is being on airspeed and/or angle of attack and on glidepath . . . no excuses.

- b) Responding to a) by trying to force the jet onto the runway, when any aircrew member with half a brain should understand how badly you're going to float in ground effect when you're that fast and that overpowered. And what that's going to in turn do to your spoilers and thrust reversers that depend on weight-on-wheels before activating. Professionalism is recognizing a botched approach, swallowing your ego, and taking it the hell around.

- c) The pilot not flying sitting there like a coward and not taking the controls from the pilot flying. If someone hits a go-around criterion and isn't going around, YOU TAKE THE CONTROLS AND EXECUTE ONE. Professionalism is proper crew coordination and proper assertiveness in the cockpit.

This whole thing seems to just boil down to a complete failure of airmanship and a complete failure of professionalism all around. If I'd done that or allowed my pilot to do that, I'd expect to have had my wings pulled. If the investigation reveals more, I'll change my mind. But it ain't looking good.

reply
At 100,000ft the pilot is just another Amazon delivery driver.

And the other pilot is another Amazon driver riding shotgun as required by law.

“As required by law” is a synonym for “as bad as is still legal.”

reply
> no excuses

Airplanes don't pay any attention to excuses. The only way to fly is do it perfectly, every time.

reply