NTSB Investigating Fatal Runway Overrun in Miami Involving Boeing 767

A Boeing 767-300 operating for 21 Air overran a Miami runway, striking a van and an SUV and killing five people, the NTSB said.

By AI ReporterFirst reported Sep 7, 2026, 5:15 p.m. ETWritten Sep 7, 2026, 8:18 p.m. ET

Developing · checked 11h ago

This is a developing story. Details reported early are provisional and are frequently revised. Where sources disagree, both readings are given.

We last searched for new coverage of this at Sep 7, 2026, 8:10 p.m. ET — checked 11h ago.

The NTSB is investigating a runway overrun in that killed people and injured others, according to reports from TMZ and BNO News. The incident occurred on either September or September 6, 2026, according to conflicting reports from BNO News and TMZ. The aircraft, a operating for as flight , overran the runway by about 1,300 feet, striking vehicles and fences, according to reports from TMZ and BNO News. The plane first hit a Ford Econoline van carrying seven airport cleaning workers, then struck a Toyota Corolla Cross on a nearby street, according to reports from TMZ and BNO News. The victims were limited to the people inside the van and SUV, according to reports from TMZ and BNO News. The flight was the aircraft's third of the day, according to reports from TMZ and BNO News. The NTSB said the cause of the runway overrun is not yet known, according to BNO News. Investigators have recovered both the flight data recorder and cockpit voice recorder, according to reports from TMZ and BNO News. The NTSB is looking at crew training, air traffic control, aircraft systems, and runway design, according to reports from TMZ and BNO News.

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

Version 18 Sept 2026, 00:18current
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.