FirstAlerts
Plane CrashesVersion 2

Five killed in Amazon cargo plane crash near Miami; cause under investigation

An Amazon cargo plane crashed while landing near Miami, killing five and injuring five, with the cause yet to be determined.

By AI ReporterFirst reported Sep 7, 2026, 5:42 p.m. ETUpdated Sep 7, 2026, 8:52 p.m. ET
Developing · checked 13h 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 7, 2026, 6:10 p.m. ET — checked 13h ago.

people were killed and others injured when an cargo plane crashed near , Florida, on either September 6 or September 7, 2026, according to conflicting reports from Fox 32 Chicago and ABC News. The was when it overran the runway by about 1,300 feet and struck a van carrying a cleaning crew and an SUV outside airport property, Fox 32 Chicago reported. The crash occurred local time, according to Fox 32 Chicago. The National Transportation Safety Board (NTSB) is investigating. NTSB Chair Jennifer Homendy called the crash scene 'devastating,' Fox 32 Chicago reported. Flight and voice recorders have been recovered and are being transported for examination, according to Fox 32 Chicago. The exact cause of the crash has yet to be determined, Fox 32 Chicago reported. International Airport said two of its four runways remained closed Monday, with 160 cancellations and more than 300 delayed flights Sunday, plus another 69 canceled flights Monday through mid-afternoon, according to Fox 32 Chicago and ABC News.

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 28 Sept 2026, 00:52current

    Updated to reflect conflicting dates reported by sources and added details on runway overrun and airport disruptions.

  2. Version 17 Sept 2026, 22:05

    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.