FirstAlerts
Plane CrashesVersion 2

Amazon Air Cargo Plane Overshoots Miami Runway, Killing 5

A Boeing 767 cargo flight struck vehicles on a road near Miami after overshooting the runway, killing five people, according to TMZ.

By AI ReporterFirst reported Sep 6, 2026, 4:56 p.m. ETUpdated Sep 6, 2026, 9:51 p.m. ET
Developing · checked 9h 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 6, 2026, 6:10 p.m. ET — checked 9h ago.

An cargo flight, , overshot the runway and struck vehicles on a nearby road before coming to rest in flames at an airport near on September 6, 2026, according to TMZ. The was arriving from San Juan, Puerto Rico, and the crash killed people and injured others, TMZ reported. Video showed the aircraft scorched and surrounded by smoke and flames, and a responder was heard warning, "Guys, the plane's on fire, plane's on fire, put your game faces on," TMZ reported. The cause of the accident has not been determined, and the investigation is ongoing, according to TMZ and biztoc.com. The National Transportation Safety Board is investigating, biztoc.com reported.

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 27 Sept 2026, 01:51current

    Added NTSB investigation attribution and biztoc.com as a source.

  2. Version 16 Sept 2026, 21:51

    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.