An engine fire by itself shouldn’t have that result.There is a video on Facebook .. looks like engine on fire during take off and crashed?
A big fireball at one point, bigger than the plane.
I saw one pic from overhead that showed engine and/or cowl parts next to the runway, so quite possibly catastrophic failure vs “just” a fire.That’s one helluva engine fire. Engine grenaded, cowl couldn’t contain blast, loss of flight controls? I mean, engine loss on departure after V1 procedures should be pretty well ingrained at this point.
Number 2 engine (in the tail)NR2?
If it can't climb with an engine out it wouldn't take off. IOW that scenario would not occur.Must have had the engine issue past V1, and maybe too heavy to climb on only 2 engines?
Shades of AAL191. Is the mounting of the engine to the wing on an MD-11 similar to that on a DC-10?The #1 engine departed the airframe. That’s why the fireball was so big


Another video. It got worse.
The engine mount is irrelevant when the wing is gone.
Put another way, the 35 feet at the end of takeoff field length is the ONLY certification case for continued takeoff after a malfunction, and that malfunction is a simple single engine failure…and it sounds like this was a worse-than-certification case. As you said, probably a no way out situation.I think worst case the thing is certified to clear the end of the runway by a scant 35 feet or something.
If I’m seeing that right, it looks like the big fireball starts before the wing touches anything, or just barely. It’s right after that fireball that the plane starts to turn in from what I can tell.Another video. It got worse.
The engine mount is irrelevant when the wing is gone.
It looks like it likely lost the left wing in the supply chain building it struck. That slice through the building seems like it's consistent with that. Then it rolled from there with all the extra lift of right wingIf I’m seeing that right, it looks like the big fireball starts before the wing touches anything, or just barely. It’s right after that fireball that the plane starts to turn in from what I can tell.
Awful tragedy. Thoughts and prayers with the families.

This was more than an engine fire... There's a whole engine sitting next to the runway, and elsewhere I saw what looked like the front of a nacelle and I could've sworn there was a fan in it.An engine fire by itself shouldn’t have that result.

The fire, the engine next to the runway (presumably #1), plus the apparent compressor stalls in #2... That plane was not going to climb, period. My only thought was "I wonder how fast an MD-11 can dump fuel" but I'm sure it wouldn't have made a difference.If one engine threw pieces to take out number two… ya… it’s gotta be able to climb one engine out, not two.

It's not always the end if there's a post-V1 abort - See Ameristar 9363.This is the ONE scenario, engine craps at V1, that airline pilots live and breathe. Frequently briefed “we’ll only abort after v1 if the airplane just won’t fly”. It’s not practiced because there is no good scenario. Guys brief it just to say if it won’t fly I may close the throttles to mitigate the impending and almost certainly catastrophic crash.
It'll be interesting to see what they knew when for sure.As someone that is an infant in 121 flying, I wonder when they were first alerted to the engine fire. The smoke appears to start "way back when"
View attachment 146827
I hope you got a good thorough debrief on that one!One time, I had a flight where we were in the "Any abnormalities" phase and had an issue and my captain said "continue".
He had to make a split second decision.
At this time, there are 825 comments to that post. No clue what video you're referring to.There is another video posted in the comments here where you can see it tried to fly. Here's the building across the street from the airport, clearly it made contact there. You can see the approach lights in this picture: