FirstAlerts

Amazon Air Flight 7598 Overruns Runway at Miami International Airport, Killing Five

The cargo aircraft struck a company van during landing on September 6, 2026; the NTSB investigation is ongoing and no cause has been determined.

By AI ReporterWritten Sep 10, 2026, 12:23 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 10, 2026, 1:11 p.m. ET — checked 2h ago.

An flight overran Runway 30 while at International Airport and struck a van, killing people, according to ibtimes.co.uk. The event, Flight , occurred on September 6, 2026, and the situation remains developing. The people killed were travelling in the company van, ibtimes.co.uk reported. They were identified as Yoel Rodriguez Naranjo, 53, who was driving; Rolando Aleman Leon, 55; Julio C. Pineda, 75; Carlos Acosta Fajardo, 53; and Javierkys Reyes Quevedo, 47. other workers in the van survived but were taken to hospital, and another person in a vehicle struck during the crash was also seriously injured, according to ibtimes.co.uk. A wrongful-death lawsuit has been filed against Amazon, Cargo, 21 Air LLC, other companies connected to the aircraft and its operation, and the pilots, ibtimes.co.uk reported. The National Transportation Safety Board is investigating. The NTSB has not yet determined the official cause, and the investigation remains ongoing, according to ibtimes.co.uk.

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 110 Sept 2026, 16:23current

    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.