Cargo Plane Overruns Miami Runway, Killing 5
A Boeing 767 cargo aircraft overran a runway while landing in Miami on September 6, killing 5 people and injuring 5 others, according to multiple 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
- Amazon Prime cargo plane crash: At least 5 killed after aircraft overruns runway and strikes multiple vehicles on ground in Miamieconomictimes.indiatimes.com
- Investigators hunt for what went wrong after cargo plane crash in Miami kills at least 5the-independent.com
- Moment Amazon plane crash lands in Miamialjazeera.com
- DOJ’s civil rights unit tasked with voter fraud and 5 dead after cargo plane crashes in Miami: Morning Rundownnbcnews.com
- Amazon cargo plane crash victims were in vehicles that were hit, NTSB sayscbsnews.com
- Miami Airport Plane Crash: 5 Killed, 5 Injured After Amazon Cargo Aircraft Overruns Runway, Strikes Vehicles And Bursts Into Flames | Watchfreepressjournal.in
- Video shows firefighters free pilot and co-pilot after cargo plane overshoots MIA runway, crashes into cars, killing 5local10.com
- Flight data recorders recovered from US cargo plane crashrte.ie
Revision history
- Version 47 Sept 2026, 19:22current
Updated to reflect the latest reporting on the investigation status and operator attribution.
- Version 37 Sept 2026, 12:57
Updated to reflect conflicting reports on operator and time, and added details on vehicles struck and critical injuries.
- Version 27 Sept 2026, 04:50
Added date and time range, attributed investigation statements to specific outlets, and clarified cause status.
- Version 17 Sept 2026, 04:09
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.