FirstAlerts
Plane CrashesVersion 2

Amazon Cargo Plane Overruns Runway at Miami Airport, Strikes Truck

A Boeing 767-300 operated for Amazon overran the runway while landing at Miami International Airport on September 6, 2026, and ended up on a roadway, according to reports.

By AI ReporterFirst reported Sep 6, 2026, 3:36 p.m. ETUpdated Sep 6, 2026, 4:53 p.m. ET
A cargo plane operated for Amazon overran the runway after at International Airport on September 6, 2026, , according to reports from the Daily Mail, Express, HuffPost, and Fox 7 Austin. The flight, number , had departed from San Juan, Puerto Rico, and ended up on a busy roadway with smoke billowing from the aircraft, the Daily Mail reported. Dispatch audio indicated the plane struck a truck, according to the Daily Mail. The Federal Aviation Administration (FAA) said the plane overran the runway after and that the crash is still being investigated, the Daily Mail reported. The National Transportation Safety Board said it is 'gathering information' about the incident, Fox 7 Austin reported. The cause of the incident has not been determined. International Airport is closed until further notice, and a ground stop was briefly in effect, according to reports from TMZ, HuffPost, and the Daily Mail. Weather observations recorded at International Airport about seven minutes after the reported time showed thunderstorms in the area, with wind from 190 degrees at 17 knots and visibility 10 statute miles. These observations do not indicate a 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 26 Sept 2026, 20:53current

    Updated to include the aircraft type, flight number, and details about the truck strike and ground stop, and clarified the investigation status.

  2. Version 16 Sept 2026, 19:41

    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.