Plane CrashesVersion 2

Five Killed as Cargo Jet Overruns Miami Runway; NTSB Investigating

A Boeing 767-300 operated by 21 Air for Amazon Prime Air struck vehicles after overrunning Runway 30 at Miami International Airport on Sept. 6, killing five.

2 reports on this incident · first at Sep 7, 2026, 1:22 p.m. ET

By AI ReporterFirst reported Sep 7, 2026, 12:54 p.m. ETUpdated Sep 9, 2026, 7:58 p.m. ET

A cargo jet operated by under contract for Amazon Prime Air overran Runway 30 at International Airport on Sept. 6, crossed a perimeter road, and struck vehicles, killing people and injuring others, according to the International Business Times and Tech Times. The aircraft, registration , was at ET, according to Tech Times, or , according to the International Business Times. The flight number was reported as by the International Business Times and as by Tech Times. The National Transportation Safety Board sent a go-team led by Chair Jennifer Homendy and scheduled its first public briefing for Monday, according to the International Business Times. The NTSB investigation was launched Sunday afternoon by Chairwoman Jennifer Homendy, according to Tech Times. The crash shut the airport's runways and taxiways, causing over 160 cancellations and nearly 325 delays, the International Business Times reported. The aircraft did not have an engineered materials arresting system, the outlet reported. Registry records list the registered owner as Andromeda Leasing II LLC; the owner of record is not necessarily the operator of the flight. The cause of the crash has not been determined. The NTSB and the Federal Aviation Administration are investigating, according to the International Business Times, Tech Times, and WSAU.

Earlier reports

Sep 7, 2026, 1:22 p.m. ETFirst report
Cargo Jet Overruns Runway at Miami Airport, Strikes Vehicles; 5 Dead
A Boeing 767-300 cargo jet operating as Prime Air Flight 7598 overran Runway 30 at Miami International Airport at around 2 p.m. on September 6, 2026, crossed a perimeter road, and struck vehicles, according to a report by IBTimes Australia. The report says five people were killed and five were injured. The aircraft was operated by 21 Air under contract for Amazon Prime Air, the report states.
The National Transportation Safety Board (NTSB) has sent a go-team led by Chair Jennifer Homendy and scheduled its first public briefing for Monday, according to the report. The Federal Aviation Administration is also investigating. The crash shut the airport's runways and taxiways, causing over 160 cancellations and nearly 325 delays, the report says. The aircraft did not have an engineered materials arresting system, the report adds.
The cause of the accident has not been determined. The NTSB and FAA are investigating.
Aircraft registry records list the aircraft as a Boeing 767-33A with registration N1997A, and list the registered owner as Andromeda Leasing II LLC; the owner of record is not necessarily the operator of the flight. Registry records also show that a Boeing 767 with registration N1217A, owned by the same owner of record, was involved in a fatal accident in 2019 in Trinity Bay, Texas; that history says nothing about the cause of this accident.

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.

Registration: N1997A
Type: Boeing 767-33A — twin-engine jet landplane
Engines: GE CF6-80C2B6F
Registered owner: Andromeda Leasing Ii LlcThe owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight.
Terrain elevation: 23 ft
Nearest aerodrome: 6.2 miles ESE of Miami International Airport (KMIA/MIA)

Sources

Revision history

Version 29 Sept 2026, 23:58current
Added flight number, time, and investigation status conflicts as sourced ranges; added owner background and other cases; clarified investigation status.
Version 17 Sept 2026, 17:26
First published.
Version 17 Sept 2026, 17:22current
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.