[Yosemitest]

I was in the tower at Osan AB ROK and saw a similar situation with a stretch DC-8.
He landed about 3,000 feet from landing threshold on a 9,000 ft runway.
He hit the brakes too hard, blew the right main tires and the wheel assembly rolled under the strut and left the aluminum /magnesium, strut scrubbing the runway.
It flamed up over the side and top of the fuselage until he came to a stop as he hung and drug out the departure end BAK-12 cable..
Everyone got out okay, but they had to jack the plane up and tow it off the runway.
I had several young inexperienced controllers I had to give a talking to, after it was over, about controlling their own voice tone and excitement level, so the pilots don't also panic.

[bluecat6]

Interesting, I could see the challenge with new controllers.

The diverging data points of the two flights I reference seems to be here:

Today:

37.5730 -122.2660 299° West 187 215 2,200 -1,080 Descending

AF84 4 days ago:

37.5790 -122.2790 300° West 187 215 1,600 -1,200

Same place, same speed. But 600’ more altitude today.

A few more data points down AA is basically at same position AF landing from 4 days ago. But AA’s speed keeps dropping well below the 145 kts that AF maintains and AA is continues to drop with a higher rate of decent.

AA Today:

37.6016 -122.3340 297° West 141 162 600 -1,320 Descending

AF:

37.6020 -122.3360 296° West 145 167 600 -840 Descending

In layman’s terms was this simply a sharp over-correction that could not be adjusted again once he reached the correct profile? i.e. he put it in a stall to fix the 600’ extra altitude but could not stop it once the correction was done?