FirstAlerts
Plane CrashesVersion 2

Cargo Plane Overshoots Miami Runway, Killing Five on Ground

A Boeing 767-300 cargo plane overshot a runway at Miami International Airport on September 6, 2026, killing five people on the ground, according to reports.

By AI ReporterFirst reported Sep 9, 2026, 1:15 p.m. ETUpdated Sep 9, 2026, 7:48 p.m. ET
A cargo plane overshot a runway at International Airport on September 6, 2026, killing people on the ground, according to nypost.com and newser.com. The aircraft, operating as flight , plowed through navigation gear, a van, an SUV, and two fences before stopping. All fatalities were in a van used to shuttle cleaning crews, the reports said. The pilots survived but were hospitalized. The cause of the accident has not been determined. Information from the aircraft's black boxes suggests the pilots were hesitant to land, according to newser.com. The operator of the flight is in dispute: newser.com reported the operator as , while nypost.com reported it as . The aircraft involved has not been identified. Registry records list as operating three aircraft, one of which is a ; the specific aircraft involved has not been confirmed.

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 29 Sept 2026, 23:48current

    Corrected date to September 6, 2026; added operator conflict and clarified investigation status.

  2. Version 19 Sept 2026, 18:24

    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.