FirstAlerts
Plane CrashesVersion 4

Boeing 767 cargo flight overshoots Miami runway, killing 5

A Boeing 767 cargo flight arriving from San Juan, Puerto Rico, overshot a runway and struck vehicles near Miami on September 6, 2026, killing five people, according to multiple reports.

By AI ReporterFirst reported Sep 6, 2026, 4:56 p.m. ETUpdated Sep 7, 2026, 9:52 a.m. ET
A Boeing 767 cargo flight overshot a runway and struck vehicles on a nearby road before coming to rest in flames near on September 6, 2026, according to reports from TMZ, Time, and others. The aircraft was arriving from San Juan, Puerto Rico, and the crash killed people and injured others, according to those outlets. The plane overran Runway 30 and hit several vehicles near the 2100 block of Northwest 42nd Avenue, according to reports. Video showed the aircraft scorched and surrounded by smoke and flames, and a responder was heard warning, "Guys, the plane's on fire, plane's on fire, put your game faces on," TMZ reported. Miami-Dade Fire Rescue responded with more than 60 units and approximately 200 personnel, according to reports. The operator of the flight is disputed: TMZ, biztoc.com, and gulte.com report it as , while Time, Free Republic, and indiablooms.com report it as . The flight number is also disputed: TMZ and Time report it as , while Free Republic and indiablooms.com report it as . The cause of the accident has not been determined, and the investigation is ongoing, according to reports. The National Transportation Safety Board and the Federal Aviation Administration are investigating, according to Time, while indiablooms.com and Free Republic report that the FAA said it would investigate.

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 47 Sept 2026, 13:52current

    Boeing 767 cargo flight overshoots Miami runway, killing 5

  2. Version 37 Sept 2026, 09:55

    Updated to reflect conflicting reports on operator, flight number, and investigating bodies.

  3. Version 27 Sept 2026, 01:51

    Added NTSB investigation attribution and biztoc.com as a source.

  4. Version 16 Sept 2026, 21:51

    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.