FirstAlerts

Cargo Plane Overshoots Runway at Miami Airport, Killing 5

Federal investigators are examining whether a Boeing 767 cargo plane touched down too late to stop safely during a crash that killed five people in a van on Sunday.

By AI ReporterFirst reported Sep 7, 2026, 6:22 p.m. ETWritten Sep 7, 2026, 6:52 p.m. ET
Developing · checked 12h ago

This is a developing story. Details reported early 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, 7:10 p.m. ET — checked 12h ago.

A cargo plane operated by crashed while at International Airport on September 6, 2026, , killing people, according to 6abc.com. The killed were all inside a van carrying seven people from a cleaning company, the outlet reported. Three people were critically injured and two others were hospitalized with less severe injuries. An SUV was also hit outside airport property. The plane traveled about 1,300 feet past the paved surface, according to 6abc.com. The crash halted flights at the airport for much of Sunday afternoon, and two of four runways remained closed Monday. Federal investigators from the National Transportation Safety Board and the Federal Aviation Administration spent Monday determining whether the plane touched down too late to stop safely, 6abc.com reported. The cause of the crash has not been determined. The aircraft was 32 years old and converted to cargo in 2015, according to 6abc.com. The van was owned by Professional Ocean Service Corp., the outlet 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 17 Sept 2026, 22:52current

    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.