FirstAlerts
Plane CrashesVersion 5

NTSB Investigates Miami Cargo Plane Crash That Killed 5 on the Ground

A Boeing 767-33A cargo jet overran the runway at Miami International Airport on Sunday, September 6, 2026, striking vehicles and killing five people, as federal investigators recover recorders and examine the airport's lack of an arresting system.

By AI ReporterFirst reported Sep 7, 2026, 11:14 a.m. ETUpdated Sep 9, 2026, 9:58 p.m. ET
A overran the runway while at International Airport on Sunday, September 6, 2026, , striking vehicles on the ground and killing people, according to The Boston Globe, NBC , and The Globe and Mail. The aircraft was operated by , according to Daily Maverick, The Epoch Times, The Globe and Mail, The Boston Globe, NBC , and KPLC-TV; ABC13 and NBC News described it as an plane. The aircraft was an on its third flight of the day, coming from San Juan, Puerto Rico, according to Daily Maverick. people were on board and survived, according to Daily Maverick and The Epoch Times. All of the dead were on the ground, according to The Epoch Times, ABC13, NBC News, and NBC . The victims were employees of Professional Ocean Service Corp., which cleans planes at the airport, according to Daily Maverick, The Epoch Times, and NBC . The aircraft overran the runway by about 1,300 feet before crashing into an Econoline van carrying seven people from an airline cleaning crew, then went through a perimeter fence and crashed into a Toyota Corolla Cross SUV on Northwest 67th Avenue, according to Daily Maverick. It continued onto the grass and impacted another fence line separating an area where Tesla robo-taxis were stationed, Daily Maverick reported. The plane also hit a Ford van owned by Professional Ocean Service Corporation, according to NBC . Reports of injuries differ: Daily Maverick, The Epoch Times, and ABC13 reported injuries, while NBC reported . The date of the crash also differs among outlets: The Boston Globe, NBC , KPLC-TV, Daily Maverick, and ABC13 reported September 6, 2026; The Epoch Times reported September 7; and The Globe and Mail reported September 6, 2023. The time was reported as by The Globe and Mail, The Boston Globe, and NBC , and as by Daily Maverick and The Epoch Times. The time zone was given as ET by The Epoch Times and EDT by Daily Maverick. The National Transportation Safety Board is investigating. The Globe and Mail, The Boston Globe, and KPLC-TV reported that the NTSB has sent a team led by Chairwoman Jennifer Homendy to , where she is expected to give the agency's first briefing on the investigation Monday. The Epoch Times reported that NTSB investigators recovered the flight data recorder and cockpit voice recorder, and that Chairwoman Homendy said a probable cause would not be determined until the end of the investigation. Daily Maverick reported that the NTSB is still recovering and recording evidence, and that probable cause will not be determined until the end of the investigation. NBC News reported that The NTSB is examining the lack of an Engineered Materials Arresting System (EMAS) at the airport, according to Daily Maverick. The cause of the crash 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 510 Sept 2026, 01:58current

    Added KPLC-TV and ABC13 to the operator attribution and NBC Miami's Ford van detail; added NBC News's line that the NTSB will look at air traffic control and aircraft performance.

  2. Version 410 Sept 2026, 00:52

    Added the conflicting date and time reports, the differing injury figures, the ground-fatality detail, the vehicle and victim details, and the NTSB recorder recovery and EMAS examination.

  3. Version 38 Sept 2026, 06:52

    Cargo Plane Crash in Miami Kills 5; Investigation Underway

  4. Version 28 Sept 2026, 01:22

    Corrected date to September 6, 2026, per most sources; added details on runway overrun, injuries, and NTSB investigation status.

  5. Version 17 Sept 2026, 14:12

    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.