Comment by octaane

1 day ago

This is probably the worst way a plane could go down in terms of damage caused. Maximum effect in term of damage. Cargo plane apparently reached V1 (go/no go speed) on the runway, and suffered a catastrophic engine failure. They passed V1, so they knew they were going down. Engine was shedding large debris, including the housing (!!!) which is a shrapnel shield.

They were on fire just as they reached V1.

Plane was fully loaded with 38,000 LB of fuel for 12 hour flight to hawaii. Worst case scenario.

Pilots did the heroic thing - they tried to take off instead at 160 MPH to minimize collateral damage (highway and warehouses at the end of the runway) and crash and die somewhere else, instead of go beyond the runway at that speed. Accelerating a fully loaded jet plane at ground level beyond the runway has obvious consequences. They had one choice.

Instead, they clipped the UPS factory because they were so low, they tried to clear it but did not. Plane then hit the ground port wing down, shearing it off entirely, smearing a fireball of jet fuel across half a mile (not an exaggeration) before the plane flipped. Crew were likely dead by before this, footage shows the cockpit being slammed into the ground like a mousetrap by the flip once the port wing was gone and gravity took the starboard wing over.

Physics took over. Plane flipped and rolled upon loss of port wing, smearing a rolling fireball of the remaining fuel load from the starboard wing for another half a mile.

Louisville is now a firestorm as a result.

Respect to the flight crew; rest in peace, they made the best they could out of a really shitty scenario. They flew it all the way down.

Footage:

https://x.com/osinttechnical/status/1985845987684855969?s=46

https://x.com/faytuksnetwork/status/1985849267152699741?s=46

https://x.com/faytuksnetwork/status/1985848132500885995?s=46

https://x.com/faytuksnetwork/status/1985843126934614297?s=46

Standard procedure at V1 is commit to the takeoff and diagnose the problem in-air. Much of your comment is pure speculation until flight data recorders come back, we have no idea what the crew was thinking or what issues they were even aware of.

  • You're 100% right, and that's exactly what I'm getting at - they hit V1 and were aware they had a serious problem, but couldn't abort.

    As far as the rest of my comment - watch the videos that I linked.

> Louisville is now a firestorm as a result.

Let's leave that word to mean what it actually means. Louisville experienced a serious fire.

  • It's a few blocks of fire. I was on Tanker 4565 standing by as a backfill for units on scene. It's no where near "All of Louisville", that's a ridiculous thing to say.

Not a UPS Factory (whatever that means).

Grade A Auto Parts on Melton Ave was the initial damaged building. I don't have the name of the chemical place handy.

Med Command setup at River City Metals.

It was around 250k gallons of fuel. Our CAD notes on the initial dispatch said 250k, one press briefing said 280k, and then it was changed to 220k which I think is the actual number.

> they tried to take off instead of accelerate past the runway at ground level

Do runways have some sort of barrier between them and the next "important" thing. It seems like that would be prudent both for cases like this, and breaking failures following landings.

  • > Do runways have some sort of barrier between them and the next "important" thing. It seems like that would be prudent both for cases like this

    Ha, Jeju Air Flight 2216 smashed into a barrier on the second landing attempt in Muan last year [0], and people commented "How could there be a barrier at the end of the runway, so obviously stupid, irresponsible", etc.

    Now a plane does not smash into a barrier at the end of the runway and people suggest putting barriers at the end of the runway.

    Don't mean to attack parent post, but may I suggest that

    a) hordes of experts have thought long and hard about these issues, and it is unlikely that you can encounter this for the first time as a lay person and come up with a solution that has eluded the best engineers for decades ("why don't they attach a parachute to the plane?"), and

    b) we are very close to an optimum in commercial aviation, and there are few if any unambiguous ("Pareto") improvements, but rather just tradeoffs. For example: You leave cockpit doors open, terrorists come in and commandeer the plane to turn it into a weapon. You lock the cockpit doors closed, and suicidal pilots lock out the rest of the crew and commandeer the plane to turn it into a weapon of mass-murder-suicide.

    There are no easy answers.

    [0] https://en.wikipedia.org/wiki/Jeju_Air_Flight_2216

    ETA: In 2007 an A320 overran a runway in Brazil and crashed into a gas station, killing 187 pax & crew + 12 on the ground. https://en.wikipedia.org/wiki/TAM_Airlines_Flight_3054

    • After 9/11, unlock the pilot doors. The passengers will revolt against any attempted aircraft hijackings.

      We need members of the public ready to help in a situation where a pilot goes crazy, and they can’t help with a locked door making it impossible for them to enter.

      1 reply →

    • The solution is to "free" the perimeter of takeoff/landing. Bonus: People don't have to chose to work/live in these noisy areas. I understand some areas have challenges to come up with space but the US has tons of space and maybe the sea should be used to host these airports.

      1 reply →

  • > Do runways have some sort of barrier between them and the next "important" thing.

    Some do. Here is what it looks like when an overshooting plane utilizes such a barrier: https://www.youtube.com/watch?v=zW71FrX8t_g

    179 dead.

    Consider the possibility that gigantic flying aluminum tubes filled with tons of flammable fuel hurtling around at hundreds of kilometers per hour comprise a dilemma that has no trivial answers. Even defining what "important thing" means at any given instant is not straightforward.

    • There is a spectrum between "no barrier" and "immovable barrier".

      Arrestor beds exist, and given enough space a fully loaded plane at take-off velocity can be stopped in a controlled and safe way.

      Cost and space are often the reason why this does not happen.

  • Unless you have a berm several dozen meters high with a 100 meter base, you ain't stopping something like this from a physics standpoint unfortunately.

    Many airports have this problem. The recent korean air disaster which echos this is another example. BTW, this is why most airports, if possible, point out to sea...

    • There is a dead zone between rejection and successful take-off speeds. We see it hit too often.

      I think pilot training is playing a factor. A normal rotation kills too much energy. One engine can climb when you have some airspeed and get clean, but if you lose too much energy on rotation, the inefficiency of the AoA for the rest of the short flight means that engine can no longer buy you any up. I've seen too many single-engine planes going down while trying to pitch up the whole way down.

      So, less aggressive single-engine rotations and energy absorbers at the ends of runways that can't get longer. This seems like the kind of thing where we do it because it removes a significant cause of people dying.

      Just watched this angle a few more times: https://x.com/BNONews/status/1985845907191889930

      Another crash video shows the aircraft clearly descending before colliding with anything. It manages to go up a bit, so it's fast enough to get airborne. The normal looking rotation kills too much energy. The plane is then too inefficient to maintain speed. AoA goes up while energy goes down. Power available goes negative and then it's over.

      8 replies →

  • Some runways have been extended with ‘engineered materials’ surfaces, often a form of porous concrete into which an airliner’s wheels will sink, absorbing a lot of energy and arresting the airplane without causing it to break up. It is very effective for landing overruns, but I don’t know about last-seconds aborted takeoffs.

    • It's designed for the much lower speeds of landing overruns (70 knots and below), whereas takeoff speeds are higher (in this case, like 185 knots).

  • Security/debris fencing yes, but that's like, orders of magnitude short of what would stop the amount of energy we're talking about here.

    You also don't particularly want it to be catastrophically effective as there are real world cases where planes have clipped the fence and then NOT gone on to crash, or at least to crash in a fairly controlled manner with the majority onboard surviving. Hitting a brick wall at 180mph is going to have a 0% survival rate.

    • Yet a reinforced concrete wall of e.g. triangular section and anchored with "long enough" piles would be about the only not-that-expensive way to turn a short strip of "airport land" past the EMAS into a V1 stopping supermarket.

Sorry for ignorance but why is the right thing to continue to take off with an engine on fire?

  • It depends on whether or not, at the point in which you realize you have an engine on fire, you have room on the runway left to stop.

    As I understand it, there is a low speed regime, under 80 knots, where are you stop for basically anything.

    Then there is a high speed regime, where you only stop for serious issues, because you now have so much kinetic energy that stopping the plane, while still possible, will involve risk. (i.e. fire from overheated brakes.)

    At a certain point, called V1, there’s no longer enough room to stop, no matter what your problem is. You’re either getting airborne or you’re crashing into whatever is ant the end of the runway. In general, getting airborne is the safer option, while obviously still not risk free.

    However, this calculation also assumes that the engine fails in an isolated fashion, and its failure did not affect the other engines. If the failure of the left engine threw off debris that damaged the middle engine then we are now talking about a double engine failure. I’m sure the pilots knew there was a problem with the engine when they made the decision to continue, but it’s possible that problems with the middle engine weren’t apparent yet and that it only started to fail once they were committed.

    Obviously, this is just speculation, and we will have to wait for the preliminary report at least.

    RIP

    • Being untrained but spending a little bit of time in a full motion 737 simulator that’s used to train and certify commercial pilots, I was amazed at how quickly things happen even in a scenario with no faults.

      This situation (single engine failure at V1) is something that commercial pilots are certified in at every recurrent certification since it’s one of the most difficult you can be in. The crew now need to climb and go around for a landing on one engine while simultaneously running through the engine failure (and also likely fire) checklist. I don’t know if a double engine failure at V1 on a fully loaded 3 engine aircraft is technically survivable or if it’s something that’s trained on. They were put in an incredibly difficult situation just based on what reports we’ve already seen.

      2 replies →

  • V1 is the speed at which you can still stop the plane before the end of the runway. (It is computed for each takeoff based on runway length, aircraft mass, takeoff engine power setting, flaps, wind, runway condition, etc.)

    When the plane reaches V1, pilots take the hand off the throttle: they're committed to takeoff, even if an engine fails. It is better to take off and fix the problem or land again, than to smash into whatever is beyond the end of the runway.

    • Isn't there any margin? Does it calculate stopping before end of runway or before causing damage?

      Surely uncertainty about the situation contributes to defaulting to committing, but what if it's a passenger plane and at V1 pilots know they've lost power? Wouldn't veering into highway at 30 mph be weighted against certain, big loss of life?

      Edit: I now see that this has been partially answered by uncle comment

      25 replies →

  • It was at a point where they were going to fast to stop or land safely. At that point you're just trying to pick the best place to crash.

  • To avoid mass casualties at the end of the runway - on the road, or the buildings that the runway points to. Check the layout on google maps.

    More specifically, V1 is the max speed at which you're about to take off, but you can still abort from. They hit that max speed and realized there was a major problem that hypothetically, they could have slowed down from, but realistically was not possible. They had no choice.

Makes me think of the song "огромное небо" https://youtu.be/0EQNv8L49cs?si=2LTHtiKNvpZVDWVy

Work place related accidents always have a certain tragedy to them. Still remember when in the industrial park, my employer is located in, tanks belonging to a trash incinerator for special chemical waste exploded, taking several people with it.

>> highway and warehouses at the end of the runway

It's astonishing that this is a thing. Why aren't we building airports with enough space for a plane to remain on the ground and have plenty of room to decelerate in this situation? I can understand why it can't be retro fitted to existing airports but is it a scenario that's considered at new airports? Just seems like such an absolutely basic safety step.

  • > Why aren't we building airports with enough space for a plane to remain on the ground and have plenty of room to decelerate in this situation?

    But that's exactly what a runway is? They're extremely long, have ample safety margins, and have "protected areas" extending out on either end, and outside of that there are regulations about what can and can't be built along the extendend runway centerlines. But jetliners are huge, heavy, fast, and designed to go long distances - the stopping distance of a fully loaded jet at full takeoff speed is measured in miles.

  • Louisville is a major cargo hub. The airport likely was not built by the warehouses, the warehouses were likely built by the airport.

  • Yes, new major airports (rare as they are) do try to acquire large areas of land, larger even than they think they need now, in anticipation of future expansion. However, for scenarios like this, there's limited utility to making the runway longer "just in case." They already pick runway sizes "big enough and then some" as the minimum to even bring planes of each size to an airport. So there is margin.

    But no matter the margin, a plane can always crash on the wrong side of any fence. And people will always build right up to wherever you put the fence as closer to the airport is more convenient for everything airport related.

  • Airports are usually built (originally) out in the boonies away from the major metro area. As time goes by and that land gets more valuable developers grease palms of politicians in land use commissions to allow developments closer and closer to the airports.

    Airports also grow themselves. Some municipal airports sited for small aircraft extend their runways to handle larger planes.