FirstAlerts
Plane CrashesVersion 4

Amazon Air Boeing 767 Overruns Miami Runway, Killing Five

A cargo jet operated by Amazon Air struck vehicles after overrunning a runway at Miami International Airport on September 6, 2026, killing five and injuring five, according to multiple reports.

By AI ReporterFirst reported Sep 7, 2026, 10:00 a.m. ETUpdated Sep 8, 2026, 5:26 p.m. ET
A cargo jet operated by overran a runway at International Airport during on September 6, 2026, and struck vehicles, killing people and injuring others, according to biztoc.com, newser.com, and wfmd.com. The aircraft, flight , continued at least 1,300 feet beyond the paved surface, crashed through the airport perimeter, and struck multiple vehicles, including a van with passengers inside and a civilian Toyota Corolla, before impacting a fence line near Tesla robotaxis, as reported by biztoc.com, newser.com, and wfmd.com. The cause of the accident has not been determined, and the investigation is ongoing, according to biztoc.com, newser.com, and wfmd.com. Federal investigators, including the National Transportation Safety Board (NTSB) and the Miami-Dade Sheriff's Office, are investigating. NTSB Chair Jennifer Homendy said that whether Engineered Materials Arresting Systems (EMAS) should be standard 'everywhere at every airport' will be central to the investigation, as reported by newser.com. International Airport lacks EMAS crushable concrete beds, according to biztoc.com and newser.com.

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 48 Sept 2026, 21:26current

    No substantive changes from v3; updated to reflect published status.

  2. Version 38 Sept 2026, 18:22

    Added flight number and additional details on the overrun and vehicles struck, and clarified investigating bodies.

  3. Version 28 Sept 2026, 13:52

    Updated to include date, aircraft type, injuries, and NTSB investigation details.

  4. Version 18 Sept 2026, 04:32

    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.