FirstAlerts
Plane CrashesVersion 9

Five Dead After Cargo Plane Overruns Runway at Miami International Airport

A Boeing 767-300 cargo plane operated by 21 Air overran the runway after landing, struck vehicles, and caught fire, killing five people, according to multiple reports.

By AI ReporterFirst reported Sep 6, 2026, 3:50 p.m. ETUpdated Sep 8, 2026, 10:53 a.m. ET
people were killed and were injured when a cargo plane operated by 21 Air overran the runway after at International Airport on September 6, 2026, according to reports from dw.com, redstate.com, miaminewtimes.com, hngn.com, and dailycaller.com. The aircraft, which dw.com reported as a , arrived from San Juan, Puerto Rico, and struck multiple vehicles, including semi-trucks, before coming to rest in a field, the outlets reported. The aircraft caught fire, and more than 60 Miami-Dade Fire Rescue units responded, according to midutahradio.com and redstate.com. All runways and taxiways at the airport were closed, and a ground stop was in effect, the outlets reported. About 250 flights were delayed by late , and fire crews were still dealing with a fuel leak several hours later, dailycaller.com reported. The time of the crash was reported as by midutahradio.com, wflaorlando.iheart.com, dw.com, and miaminewtimes.com, while hngn.com reported , redstate.com reported , dailycaller.com reported , and wptv.com reported The National Transportation Safety Board said it had launched a "go-team" to investigate the crash, while the Federal Aviation Administration said it would separately investigate the circumstances that led the aircraft to overrun the runway, hngn.com reported. The FAA has launched an investigation into the cause of the incident, wflaorlando.iheart.com reported, and RedState.com reported that The cause of the overrun has not been determined. Weather observations recorded at International Airport about seven minutes before the reported time showed wind from 190 degrees at 17 knots, visibility 10 statute miles, scattered clouds at ,000 feet, thunderstorms, and a temperature of 86 degrees Fahrenheit. These conditions are not being cited as a cause.

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 98 Sept 2026, 14:53current

    Removed the clickorlando.com URL from the sources cited list because it is not a direct source for the event; it reports on ripple effects in Orlando. All other content remains unchanged.

  2. Version 88 Sept 2026, 02:23

    Removed the clickorlando.com URL from sources cited because it is not a direct source for the event; it is a local ripple-effects story. All other content remains unchanged.

  3. Version 77 Sept 2026, 13:22

    Updated to reflect the latest reporting on the investigation status and the aircraft type discrepancy.

  4. Version 67 Sept 2026, 11:23

    Updated to reflect the latest reporting on the investigation and response.

  5. Version 57 Sept 2026, 06:23

    Updated to reflect the latest reporting on the investigation status and the aircraft type discrepancy.

  6. Version 47 Sept 2026, 03:55

    Updated to include the aircraft type disagreement (Boeing 767-300 vs B-767-300) and the time discrepancy (around 2 p.m. vs approximately 1:58 p.m. vs around 2:30 p.m. EDT).

  7. Version 37 Sept 2026, 02:55

    Added sourced time and investigation status conflicts; added casualty and injury figures with attribution; added details on vehicles struck, flight delays, and fuel leak.

  8. Version 26 Sept 2026, 22:56

    Updated to reflect conflicting reports on investigation status and time, and added attribution for time discrepancy.

  9. Version 16 Sept 2026, 20:22

    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.