FirstAlerts
Plane CrashesVersion 4

Cargo Plane Overruns Miami Runway, Killing Five; Investigation Open

A Boeing 767-300 cargo flight went off the end of a runway at Miami International Airport on Sunday, September 6, 2026, killing five people and injuring five, according to conflicting reports.

By AI ReporterFirst reported Sep 7, 2026, 11:48 p.m. ETUpdated Sep 9, 2026, 10:27 p.m. ET
A cargo plane overran a runway at International Airport on Sunday, September 6, 2026, killing people, according to local10.com, wpbf.com, wptv.com, pilotonline.com, wjno.iheart.com, express.co.uk, abcnews.com and dailystar.co.uk. The aircraft, a , was when it went off the end of the runway and struck several vehicles, catching fire, according to the same outlets. The investigation is open and the cause has not been determined. people were injured, according to local10.com, dailystar.co.uk, express.co.uk and wjno.iheart.com, while abcnews.com and pilotonline.com reported . All fatalities were ground casualties, according to pilotonline.com and abcnews.com. Three people were transported to trauma centers in critical condition and more were treated at a local hospital, according to local10.com. Officials have not provided additional information on the injuries suffered by people inside the vehicles, local10.com reported. survivors were reported by abcnews.com. The operator is disputed: wesh.com, local10.com, wpbf.com, dailystar.co.uk, wptv.com and express.co.uk reported , while local10.com, wjno.iheart.com, abcnews.com and pilotonline.com reported . The flight number is also disputed, with express.co.uk reporting and local10.com reporting 798. The time of the crash was reported as by wpbf.com, local10.com and dailystar.co.uk, by local10.com and express.co.uk, by local10.com, and by wptv.com. The aircraft has not been identified; registry records list one aircraft under , but that is not an identification of the aircraft involved. The plane overran runway 30 and came to rest in a field adjacent to the runway, according to local10.com. It collided with a 2012 Ford van carrying a seven-person airport cleaning crew, then struck a fence and a Toyota Corolla on a perimeter road, local10.com reported. The cleaning crew worked for Professional Ocean Service Corp., according to local10.com, and the victims were wrapping up an eight-hour shift cleaning planes, according to wpbf.com, wesh.com, wptv.com, local10.com, pilotonline.com, wjno.iheart.com, express.co.uk, abcnews.com and dailystar.co.uk. The Federal Aviation Administration said the flight departed from Luis Muñoz Marín International Airport in San Juan, Puerto Rico, according to local10.com. The National Transportation Safety Board and the Federal Aviation Administration are investigating, according to wptv.com and wesh.com. NTSB chair Jennifer Homendy is leading the investigation but has not revealed preliminary theories on why the plane crashed, according to dailystar.co.uk and express.co.uk. NTSB investigators questioned Joseph Carol and Jaime Silva about the record on the flight data and cockpit voice recorders, local10.com reported. The recorders have been recovered, according to local10.com. , wpbf.com reported. A ground stop was initially issued, but flights have resumed arriving and departing from MIA, according to local10.com. As of Monday afternoon, 360 flights out of MIA were delayed and 89 were canceled, according to Flight Aware, as reported by local10.com. Nearly 600 flights were canceled or delayed on Sunday, and of the airport's four runways remain closed, local10.com reported. Miami-Dade Fire Rescue responded with over 200 firefighters, local10.com reported.

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 410 Sept 2026, 02:27current

    Expanded attribution across all outlets, added the disputed flight number, ground-casualty breakdown, survivor figure, NTSB chair and investigator details, and registry note that the aircraft has not been identified.

  2. Version 38 Sept 2026, 08:52

    Added operator dispute and time conflict; updated investigation status.

  3. Version 28 Sept 2026, 08:22

    Added details on aircraft type, operator, speed, flight disruptions, and investigation status from additional sources.

  4. Version 17 Sept 2026, 23: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.