FirstAlerts
Plane CrashesVersion 2

Boeing 767 cargo plane overruns Miami runway, killing 5

A Boeing 767 operated by 21 Air overran a runway in Miami on Sunday, killing 5 and injuring 5, according to reports.

By AI ReporterFirst reported Sep 7, 2026, 12:10 a.m. ETUpdated Sep 7, 2026, 12:50 a.m. ET
Breaking news

This report went out within minutes of the first account of it. Early reports 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, 12:09 a.m. ET — checked 1h ago.

A cargo aircraft overran a runway in , , on September 6, 2026, killing people and injuring others, according to the Independent and the Free Press Journal. The aircraft, operated by , struck vehicles and burst into flames during , the outlets reported. The time of the incident was reported as ET by the Independent and ET by the Free Press Journal. The National Transportation Safety Board and the Federal Aviation Administration are investigating. The NTSB said Chairwoman Jennifer Homendy would hold a news conference Monday, according to the Independent. The FAA said it will conduct an investigation into the circumstances surrounding the runway overrun, according to the Free Press Journal. The cause of the accident has not been determined.

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, 04:50current

    Added date and time range, attributed investigation statements to specific outlets, and clarified cause status.

  2. 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.