FirstAlerts
Plane CrashesVersion 2

Boeing 767-300 Crashes on Landing at Miami Airport, Killing 5

A Boeing 767-300 operated by 21 Air overran the runway and crashed into vehicles at Miami International Airport, killing five people, according to reports.

By AI ReporterUpdated Sep 7, 2026, 5:52 p.m. ET
A operated by overran the runway and crashed into other vehicles while at International Airport, killing people, according to LBC and Global News. The date of the crash is reported as either September 6, 2026, by LBC or May 10, 2026, by Global News. The time is reported as EDT by LBC or EDT by Global News. The flight number is reported as by LBC or by Global News. people were injured, according to LBC. The Federal Aviation Administration said it will investigate the crash, according to LBC. The National Transportation Safety Board will not determine probable cause while on scene, according to Global News. The cause has not been determined. All runways and taxiways at the airport were closed as of 3pm EDT, according to LBC. Weather observations recorded at International Airport about seven minutes after the reported time show wind from 190 degrees at 17 knots, visibility 10 statute miles, scattered clouds at 2,000 feet, thunderstorms, and a temperature of 86 degrees Fahrenheit. These conditions are not stated to have caused the crash.

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 27 Sept 2026, 21:52current

    Updated to reflect conflicting reports on date, time, and flight number; added NTSB statement on probable cause.

  2. Version 16 Sept 2026, 23: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.