You only dirtied them on the backside; got it.
An interesting bit of non-foresight in my writing. Oops … IOW … I really shit the bed with that one.
I meant “up front” as in cockpit. But you got me fair and square. D’oh!
You reminded me of a competition sail plane story ( not mine ).
A pilot in a European contest had an eagle strike and it came into the cockpit.
He did survive to tell the tale but damn - eagles are big and full of sharp bits…I’m sure it was dazed or dead but sailplane cockpits are small…wrestling it out of the plane while trying to deal with flying the plane, the broken canopy and an unwanted guest.
What a horror.
Preliminary report is out of the Bering Air Flight 445 a month ago which killed 10 people, So apparently a combination of the icing conditions and being overweight.
Report is at:
https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/199662/pdf
Speaking of preliminary reports, here’s one from the Canadian Transportation Safety Board about the Delta CRJ900 that landed and rolled at Toronto Pearson back in February (first noted here in The Great Ongoing Aviation Thread (general and other) - #7385 by Darren_Garrison):
https://www.npr.org/2025/03/20/nx-s1-5334692/delta-plane-crash-investigation-toronto
(Via NPR. Actual report document is embedded.)
1100 ft/min sink rate at touchdown. Somehow “hard landing” understates a bit.
That doesn’t mean that rate was carried down to the runway but clearly it was a hard landing. Commercial pilots can weigh in on when a descent rate exceeds the ability to flare.
Reading the detailed chronology in the report, it does appear that this sink rate was present at touchdown.
At 1412:43.6, the right main landing gear (MLG) contacted the runway. The aircraft was in a 7.5° bank to the right with 1° of nose-up pitch and 3g vertical acceleration, at a rate of descent of approximately 1098 fpm (18.3 fps).
(Emphasis mine.)
CNN article on deicing explained
Ref
See actual report here:
Here’s the money quote:
At 1412:26, while the aircraft was descending through 175 feet AGL, its indicated airspeed was 144 knots, with a ground speed of 121 knots, and a rate of descent of 672 fpm. The thrust remained
at approximately 64% N1.At 1412:30, while the aircraft was descending through 153 feet AGL, its indicated airspeed increased to 154 knots whereas the ground speed did not change appreciably, consistent with a performance-increasing wind gust. The PF pulled back the thrust levers, and as a result, over the following
5 seconds, N1 decreased from 64% to approximately 43%, where it remained until touchdown. The
airspeed began to decrease.At 1412:40 (3.6 seconds before touchdown), when the aircraft was at a height of 50 feet AGL, the indicated airspeed was 145 knots, and the ground speed was 112 knots. The rate of descent had increased to 1114 fpm. The enhanced ground proximity warning system (EGPWS) aural alert “fifty” sounded to indicate the aircraft was at 50 feet AGL, which is a standard callout.
One second later (2.6 seconds before touchdown), the EGPWS alert “sink rate” sounded, indicating a high rate of descent. The aircraft’s indicated airspeed was 136 knots, its ground speed was 111 knots, and the rate of descent had remained at about 1100 fpm. The bank angle increased to a 4.7° right bank. The engine thrust was steady at approximately 43% N1.
At 1412:42 (1.6 seconds before touchdown), the aircraft’s indicated airspeed was 136 knots, and its ground speed was 111 knots. The aircraft was slightly below the glide slope, but on the visual segment of the approach and tracking the runway centreline. The rate of descent had increased to 1072 fpm, and the bank angle was 5.9° to the right.
Less than 1 second before touchdown, the aircraft’s indicated airspeed was 134 knots, and its ground speed was 111 knots. The bank angle was 7.1° to the right, and the pitch attitude was 1° nose up. The rate of descent was recorded as 1110 fpm.
At 1412:43.6, the right main landing gear (MLG) contacted the runway. The aircraft was in a 7.5° bank to the right with 1° of nose-up pitch and 3g vertical acceleration, at a rate of descent of approximately
1098 fpm (18.3 fps).At touchdown, the following occurred: the side-stay that is attached to the right MLG fractured, the landing gear folded into the retracted position, the wing root fractured between the fuselage and the landing gear, and the wing detached from the fuselage, releasing a cloud of jet fuel, which caught fire.
The exact sequence of these events is still to be determined by further examination of the fracture surfaces. The aircraft then began to slide along the runway. The fuselage slid down Runway 23, rolling to the right until it became inverted. A large portion of the tail, including most of the vertical stabilizer and the entire horizontal stabilizer, became detached during the roll.
The aircraft went off the right side of the runway into the snow-covered grass area and came to a rest on Runway 15L, near the intersection with Runway 23, about 75 feet beyond the right edge of Runway 23 (Figure 1). The right wing, including the right MLG, became fully detached from the aircraft
Note that the entire quoted narrative is of the final 16-1/2 seconds of flight. And all the exciting shit is the last 5 seconds. This was a highly dynamic situation. At 175 feet AGL ~= 12 seconds from typical touchdown, they were totally normal, on-parameters, & looking good. Then their world went apeshit.
A big gust drove them fast and trending high, they reduced thrust, they started sinking like mad as the gust ended, they recognized the sink rate, pulled hard to avoid the impending impact, while rolling to maintain track and counteract gust-induced roll, then hit anyhow since they had no excess IAS energy to trade for G-energy & sink rate reduction.
They hit good and hard on one gear leg. which promptly failed in overload, as did the wing spar when that hit the ground too a few milliseconds later. Oops. Sux to be you.
So much for facts. IMO …
~1100 FPM is beyond design loads for two gear legs absorbing the impact, much less one. The airplane structure failed more or less as expected given the abuse it was subjected too. Throwing no shade on Bombardier, except for building an 21st century airliner with no auto-throttle.
One can argue the right answer for any significant wind delta event below 200 feet is to go around. But the early indications were not bad, and we don’t have insight into the rest of the global situation. So being spring loaded to recover, not chicken out, may well have been the reasonable thing to do based on traffic, fuel, duty day, area weather, etc. Their actual indicated airspeed was not outside of typical parameters even a fraction of a second before impact.
It’s also the case that a badly decreasing performance shear at ~150-200 feet tends to trigger both EGPWS / PWS warnings, and an instinctive escape reaction, whereas the same amount of increasing performance shear is treated as just another gust to be managed. Which usually leads to a opposite decreasing performance counter-shear reaction either at a critically low altitude or, more frequently, after touchdown. The latter is trivially manageable. The former is often not. As these poor bastards learned to their detriment.
All in all, the millions of operations around the Americas claimed another example of really bad luck. Should not have happened, but yet it did.
LSL, thanks for the report and synopsis. I’d change the report to replace the word “touchdown” with “impact”.
So they hit the gust 13.6 seconds before touchdown. Even if they had decided at that point to go around, would they have had enough time and/or thrust to succeed?
I decided not to start a new thread. Anyway, Heathrow Airport is closed for the time being after a fire at an electrical substation knocked out power to a large portion of London.
Well THAT is going to throw a whole damn lot of the system for a loop…
Almost certainly.
I’m tracking a Tokyo-London flight right now - scheduled to land at LHR at 3:45 local time (an hour from now as I write). I’m curious to see where it goes. Maybe Gatwick?
Just looked at Planefinder, looks like most flights are headed to Gatwick/Stansted/Luton but not sure if they have handle all the heavies, so yeah, a FUBAR is the likely result.
Looks like my Tokyo flight is about to land (400 ft). It flew south over Scotland, but it looks too far south to be landing at Edinburgh. Newcastle maybe? Can it handle a 787-9?
Update: I see a “Diverted to NCL”.
1300 flights a day not going there today. I saw some were diverted to Shannon Ireland; they can’t just charter you buses to your final destination from there.
Question - This isn’t a weather delay & it’s not the airline’s fault. Would travelers be compensated, & who would pay for their delay when the airport closes?
The fire that shut the airport down is now being investigated by counter terrorism police. All starting to sound a bit Die Hard 2. Stay away from the annexe skywalk!
I’m also puzzled at how a facility like Heathrow didn’t have backup generators - but maybe those were also disabled in the fire?