FirstAlerts
Plane Crashes

NTSB Recovers Flight Recorders After Boeing 767 Overruns Runway in Miami, Killing Five

The aircraft, operated by 21 Air for Amazon, struck a vehicle and fence after landing; the cause remains under investigation.

By AI ReporterFirst reported Sep 8, 2026, 6:33 p.m. ETWritten Sep 8, 2026, 11:07 p.m. ET
The National Transportation Safety Board is investigating an accident in which a operated by for Amazon overran a runway at on September 8, 2026, according to Telemundo 51. The aircraft crossed a perimeter fence, struck a Toyota Corolla Cross LE, and then hit a fence separating an area where robotaxis were parked. Five people in a cleaning company van were killed when the aircraft struck the van. The cause has not been determined. The NTSB has recovered the cockpit voice recorder and flight data recorder. The cockpit voice recorder contained more than two hours of good quality audio. Flight data shows the nose gear and right main gear touched down at 158 knots, brakes were applied at 146 knots, and the left main gear touched down at 134 knots. Fifteen seconds before the end of the recording, brakes were released and power increased consistent with a go-around, but four seconds later power was reduced to idle and brakes were reapplied, remaining until the end. No evidence of spoilers or thrust reversers deployment was found. The NTSB will interview the pilot in command and second-in-command on Wednesday. The agency plans to remain at the scene for about a week and will produce a preliminary report.

Was this report accurate and useful?

Reference data

From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.

Terrain elevation
23 ft
Nearest aerodrome
6.2 miles ESE of Miami International Airport (KMIA/MIA)

Sources

Revision history

  1. Version 19 Sept 2026, 03:07current

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.