Cargo Plane Overruns Miami Runway, Killing Five; Investigation Open
A Boeing 767-300 cargo flight went off the end of a runway at Miami International Airport on Sunday, September 6, 2026, killing five people and injuring five, according to conflicting reports.
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
- Fatal Miami cargo plane crash sparks questions over lack of safety systemwptv.com
- Cleaning crew killed in Miami jet crash was wrapping up shift at hard, demanding jobabcnews.com
- Half Of MIA's Runways Closed After Deadly Amazon Plane Crash | 1290 WJNOwjno.iheart.com
- Amazon cargo jet pilot dashes from wreckage after horror fatal crashdailystar.co.uk
- Terrifying moment pilot runs for life after Amazon cargo plane horror crashexpress.co.uk
- Hundreds of flights delayed, cancelled at MIA 1 day after cargo plane crashlocal10.com
- NTSB: Cargo plane struck cleaning van, SUV before coming to stop outside MIAlocal10.com
- ‘Hesitation is deadly’: Pilots face scrutiny after fatal cargo plane crash at Miami International Airportlocal10.com
- Cleaning crew killed in Miami cargo jet crash was wrapping up shift at hard, demanding jobpilotonline.com
- How weather could have potentially played a role in a Miami plane crashwesh.com
- Aviation expert examines factors in Miami cargo plane crashwpbf.com
Revision history
- Version 410 Sept 2026, 02:27current
Expanded attribution across all outlets, added the disputed flight number, ground-casualty breakdown, survivor figure, NTSB chair and investigator details, and registry note that the aircraft has not been identified.
- Version 38 Sept 2026, 08:52
Added operator dispute and time conflict; updated investigation status.
- Version 28 Sept 2026, 08:22
Added details on aircraft type, operator, speed, flight disruptions, and investigation status from additional sources.
- Version 17 Sept 2026, 23:22
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.