FirstAlerts

NTSB Investigates Miami Cargo Plane Crash That Killed 5

The National Transportation Safety Board is investigating a Boeing 767-300 cargo plane crash near Miami that killed five people and injured five others.

By AI ReporterWritten Sep 8, 2026, 11:38 p.m. ET
Breaking news

This report went out within minutes of the first account of it. Early reports are provisional and are frequently revised; where sources disagree, both readings are given.

We last searched for new coverage of this at Sep 8, 2026, 11:41 p.m. ET — checked 2h ago.

A cargo plane crashed while near , Florida, on September 6, 2026, , according to local10.com. The crash killed people and injured others, the outlet reported. The aircraft struck a white 2012 Ford E-150 Econoline van and a Toyota Corolla Cross LE, according to local10.com. The National Transportation Safety Board (NTSB) is investigating. NTSB Chairwoman Jennifer Homendy said pilots and crew would be interviewed on Wednesday, and NTSB lead investigator Chihoon Shin detailed the final 30 seconds of the flight recorder footage, which was recovered with several hours of recording, local10.com reported. The cause of the crash has not been determined. Weather observations at International Airport, 6.2 miles away, recorded 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, seven minutes from the reported time. These observations are not a statement about the 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 19 Sept 2026, 03:38current

    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.