The 767 that ran off a Miami runway landed at 158 knots with no reversers recorded

Five people died on 6 September when a 21 Air Boeing 767-33A freighter flying cargo for Amazon came down on Runway 30 at Miami International Airport and kept going. The jet crossed the perimeter road and struck vehicles, killing the occupants of a cleaning-crew van, and the National Transportation Safety Board has now put numbers on how fast the airplane was moving when it arrived.

The nose and right main gear touched down at 158 knots, about 182 mph, and the recorded data showed no sign of speed brakes or thrust reversers. Both findings are early ones.

NTSB recorder findings on the 158-knot touchdown

The NTSB investigative update on the Miami excursion, issued 9 September, is a statement of recorder facts and not a finding of cause. Investigators recovered both recorders from the wreckage and read more than two hours of cockpit audio and 54 hours of flight data covering over 400 parameters. The update says the nose and right main landing gear touched down at 158 knots on Runway 30 roughly 30 seconds before the cockpit voice recording ended.

On the recorded data itself, the board was direct: “There was no indication in the recorded data that speed brakes or thrust reversers were deployed.” The wording matters. It describes what the recorders captured, which is a narrower thing than saying the crew chose not to use the devices or that they failed.

Cockpit speed callouts and a late go-around

The voice recording adds a human thread. According to the NTSB, one pilot cautioned that the aircraft was too fast about a minute and 42 seconds before touchdown, and the callouts about speed were repeated, yet “there was not a consistent verbal response to the comments about speed.” The agency said a cockpit voice recorder group would convene at its Washington headquarters to review the recording and produce a written transcript, so the exact words, their order and the crew’s replies, if any, remain unreleased. Until that transcript exists, the only public description of the exchange is the board’s two-sentence summary, and it does not name which pilot spoke or how many times the warning was repeated.

Later briefings filled in the sequence after wheels met pavement. Reporting on remarks by NTSB Chair Jennifer Homendy, AJOT described brakes being released and throttles advanced to go-around thrust a few seconds after touchdown, then pulled back to idle with brakes reapplied. A second account of the same briefing gives the left main gear’s contact speed as 134 knots, the speed at idle as 117 knots and the last recorded groundspeed as 65 knots.

Those figures describe a long float down the pavement. The same account says Runway 30 is 9,360 feet long and that the jet touched down at least 4,000 feet along it, well beyond the 3,000-foot limit usually cited for a touchdown zone.

The runway, the aircraft and the people on the ground

The airplane was a 32-year-old 767-300, registration N1997A, built in 1994 as a passenger jet and converted to freight in 2015, according to Aerocorner’s account. It was arriving from San Juan, Puerto Rico. The runway is the airport’s crosswind strip, and the same report says the jet left the paved surface by roughly 2,000 feet past the overrun area before catching fire near a warehouse lot.

The dead were not aboard. TimesLIVE reported that all five were members of a cleaning crew in a van operated by Professional Ocean Service Corp, and that two other van occupants and both pilots survived. Homendy called the scene “utter devastation” and said the airport lacked runway excursion prevention systems, adding that the board’s earlier recommendations on excursion prevention have to be implemented to keep such accidents from recurring.

Weather remains unconfirmed as a factor, and the NTSB says it will examine it alongside the aircraft systems, the recorders and the runway.

Open causes in the Runway 30 investigation

Everything above is early-stage factual material, and the board has issued no probable cause. Several explanations remain live: an unstable approach, a long landing, a tailwind, a mechanical limitation, or some mix. The recorder data cannot yet distinguish them, and the NTSB’s own update stops short of ranking them. Investigators typically spend a year or more before a probable-cause finding, and the docket for this accident is still being assembled.

The 158-knot figure is a groundspeed at one instant, not an indicated airspeed or a comparison against the aircraft’s reference speed, and the update as published does not give the weight or the flap setting. Those missing values will decide whether 158 knots was fast for that landing. The transcript from the cockpit voice recorder group is the next document the NTSB has promised, and the weight, flap setting and wind at touchdown are the three values that would turn 158 knots from a raw number into a measured excess over the aircraft’s target speed for that runway on that afternoon.

This article was produced with the assistance of AI and reviewed by Morning Overview editors prior to publication.

More from Morning Overview