Earlier quoted context omitted.
Take this with all the salt that random third-party guesses about a still-in-investigation event should be taken with -- think fully salt-cured ham -- but it looks like the landing was with a quartering tail wind, and the upwind (left) gear never really got weight on it; the wheel bogie needs to be straightened by weight against both the front and back wheels to register weight-on-wheel, and the auto-brake systems ne…
AIUI, they should never have gotten that far. They should have gone around at 1000 feet.
NTSB issues investigative update on B-767 runway excursion accident in Miami
11–20 of 297 posts
Re: NTSB issues investigative update on B-767 runway excursion accident in Miami
#12> There was no indication in the recorded data that speed brakes or thrust reversers were deployed. I don't know anything about flying. Is this normal? Doesn't sound like it, but I don't know why the pilots would not have used these things that sound useful.
Depending on the plane they need the wheels to have sufficient weight on them first. Also strangely the flaps 30 and flaps 40 call outs do not match.
Re: NTSB issues investigative update on B-767 runway excursion accident in Miami
#13What I don't understand from his analysis though was early on he said the tail wind increased a minute before landing which is too quick to have communicated. If that's true, we need to get better about this. A minute to send a message is ages. It should be automatic between the airport and the aircraft.
Re: NTSB issues investigative update on B-767 runway excursion accident in Miami
#14tldw, per Blancolirio: unstable approach, crew should have done a go around at 1000 agl but did not attempt one until it was too late, then aborted the go around.
Re: NTSB issues investigative update on B-767 runway excursion accident in Miami
#15tldw, per Blancolirio: unstable approach, crew should have done a go around at 1000 agl but did not attempt one until it was too late, then aborted the go around.
Re: NTSB issues investigative update on B-767 runway excursion accident in Miami
#16Re: NTSB issues investigative update on B-767 runway excursion accident in Miami
#17> There was no indication in the recorded data that speed brakes or thrust reversers were deployed. I don't know anything about flying. Is this normal? Doesn't sound like it, but I don't know why the pilots would not have used these things that sound useful.
Take this with all the salt that random third-party guesses about a still-in-investigation event should be taken with -- think fully salt-cured ham -- but it looks like the landing was with a quartering tail wind, and the upwind (left) gear never really got weight on it; the wheel bogie needs to be straightened by weight against both the front and back wheels to register weight-on-wheel, and the auto-brake systems ne…
Really that's all that needs to be said at the moment. They had way too much energy[1], which anyone with flight sim or RC experience will recognize as a routine mistake when hand-flying.
The question is why all (all!) the layers of checklists and warnings and process and ATC direction somehow failed in combination to prevent. Yeah, they should have aborted for sure, but they didn't, and we won't know why for a good while yet.
[1] Which can just as easily mean "too high" as "too fast", c.f. the sink rate warnings in the logs which would be consistent with trying to squeeze the airplane down onto the runway. But again we won't know without more data.
Re: NTSB issues investigative update on B-767 runway excursion accident in Miami
#18tldw, per Blancolirio: unstable approach, crew should have done a go around at 1000 agl but did not attempt one until it was too late, then aborted the go around.
Yep, its also the most intuitive way to reason about it when you look at the data. Unfortunately, a bad call. I'm sure many of us would have made the same mistake.
Re: NTSB issues investigative update on B-767 runway excursion accident in Miami
#19tldw, per Blancolirio: unstable approach, crew should have done a go around at 1000 agl but did not attempt one until it was too late, then aborted the go around.
Yep, its also the most intuitive way to reason about it when you look at the data. Unfortunately, a bad call. I'm sure many of us would have made the same mistake.
From the reporting and commenting on this incident, that is not the impression I'm getting. This wasn't one bad call after getting half way down the runway, this was a continuous stream of bad decision making for the entire approach, with the copilot suggesting the pilot go around too.
Also: this kind of incident is very rare, so obviously, the vast majority of pilots don't make this mistake.
Re: NTSB issues investigative update on B-767 runway excursion accident in Miami
#20Earlier quoted context omitted.
Yep, its also the most intuitive way to reason about it when you look at the data. Unfortunately, a bad call. I'm sure many of us would have made the same mistake.
Private pilot here. No, I'm quite sure very few of you here would have made the same mistake as evidenced by the fact that literally hundreds of thousands of aircraft land successfully every day, many of them under much more adverse conditions. This is not a oh-it-could-have-happened-to-anyone kind of screwup, this is a did-this-guy-really-go-through-basic-pilot-training kind of screwup.