Boeing 767-300 Cargo Plane Crash in Miami Kills 5
A Boeing 767-300 cargo plane overshot the runway and struck vehicles at Miami International Airport on Sunday, September 6, 2026, killing five people and injuring five 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
- Shocking Details as 5 People Die in Amazon Cargo Plane Crashthedailybeast.com
- Experts Weigh In on Amazon Plane Crash That Killed 5newser.com
- Investigators search for what went wrong after Amazon cargo plane crash in Miami kills 5nbcmiami.com
- Amazon cargo plane crash claims five livesmaravipost.com
- Amazon Cargo Plane Crash in Miami — Captain Reactsfreerepublic.com
- Federal Officials Reveal New Information About Victims of Amazon Plane Crash (VIDEO)freerepublic.com
Revision history
- Version 68 Sept 2026, 16:22current
Updated to include the date in the opening paragraph and to attribute the operator conflict more precisely.
- Version 58 Sept 2026, 11:52
Updated to include the aircraft type and flight number in the lead, and clarified the operator discrepancy.
- Version 48 Sept 2026, 00:22
Boeing 767-300 Cargo Plane Crash Near Miami Kills Five
- Version 37 Sept 2026, 10:51
Updated to reflect conflicting operator reports and investigation status.
- Version 27 Sept 2026, 07:25
Updated to reflect conflicting operator reports and investigation status.
- Version 17 Sept 2026, 00:20
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.