FirstAlerts
Plane CrashesVersion 3

Boeing 767 cargo plane overruns runway at Miami airport, crashes into vehicles

Five people were killed and five injured when a 21 Air Boeing 767-300 cargo plane overran the runway during landing at Miami International Airport on September 6, 2026, according to reports.

By AI ReporterFirst reported Sep 6, 2026, 4:56 p.m. ETUpdated Sep 7, 2026, 10:26 a.m. ET
A cargo plane overran the runway during and crashed into vehicles at International Airport on September 6, 2026, according to The Verge. The incident occurred , The Verge reported, while the Dominican Republic Post reported the time as 2 p.m. ET. The plane was on fire and spewing heavy smoke when Miami-Dade Fire Rescue arrived, and flights at the airport were grounded, The Verge reported. The aircraft was operating as flight by , according to The Verge. Business Insider reported fatalities and injuries. The plane crossed 67th Avenue before striking a truck, and struck multiple vehicles but stopped short of a parking lot full of Tesla Cybercabs, according to the outlet. This was the second 767 cargo plane to crash from Amazon's Prime Air network, Business Insider and The Verge reported. The Federal Aviation Administration (FAA) said it is investigating, the Dominican Republic Post reported. The cause of the incident has not been determined. Weather observations recorded at International Airport, about 6.2 miles away, around the time of the incident show wind from 190 degrees at 17 knots, visibility of 10 statute miles, scattered clouds at 2,000 feet, thunderstorms, and a temperature of 86 degrees Fahrenheit. These observations are from a nearby field and do not indicate 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 37 Sept 2026, 14:26current

    Added time conflict reporting and clarified investigation status.

  2. Version 27 Sept 2026, 13:56

    Added casualty figures and additional details from Business Insider.

  3. Version 16 Sept 2026, 22:52

    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.