FREE delivery & up to 40% Discount select items! Place your 1st order in.
FREE delivery & 40% Discount for next 3 orders! Place your 1st order in.
FREE delivery & 40% Discount for next 3 orders! Place your 1st order in.
Order now and get it within 3 to 5 days!
To see and take advantage of all discounted products.
Click HereAmazon Prime Air Cargo Plane Crash in Miami: What Investigators Know So Far
U.S. News · Aviation
Amazon Prime Air Cargo Plane Crash in Miami: What Investigators Know So Far
The NTSB’s preliminary evidence describes the landing and recorder sequence. The investigation remains open, and observations are not a final finding of cause.
By OnelROR Editorial Team · Originally published September 8, 2026 · Updated October 11, 2026 · Miami · 3 min read
Cover: archival photograph of N1997A approaching Miami, December 15, 2025, by Hector Ossa J.; cropped by Cubnorth on September 7, 2026, and displayed here at reduced size. CC BY 4.0. This photograph does not depict the September 6 accident.
What is established
On September 6, 2026, at about 1:53 p.m. eastern daylight time, 21 Air Flight 7598 overran Runway 30 after landing at Miami International Airport. The Boeing 767-33A, registration N1997A, had arrived from San Juan, Puerto Rico, on a domestic cargo flight operating on behalf of Amazon.com Services LLC. The National Transportation Safety Board says the airplane subsequently struck two ground passenger vehicles and sustained substantial damage, including a fire on its right wing.
Five people on the ground died. The NTSB’s October 1 update records three serious injuries on the ground and minor injuries to the two crewmembers aboard. These categories matter: a combined injury total should not conceal the different consequences for people in the vehicles and people in the cockpit. The investigation is DCA26MA352, and its official status remains ongoing as checked on October 11.
What the recorders show
Investigators recovered both the cockpit voice recorder and flight data recorder, took them to the NTSB laboratory in Washington, and successfully read them. The agency’s September 9 investigative update describes audio containing repeated cautions about excessive speed and a later call for a go-around. It also describes the recorded sequence of touchdown, braking and changes in engine power.
In the flight data summary, the nose and right main landing gear touched down before the left main gear. Brakes were applied, later released as the throttles increased to a setting consistent with go-around thrust, and then reapplied after the throttles returned to idle. The data contained no indication that speed brakes or thrust reversers were deployed. These are preliminary observations, not a final explanation of why the sequence occurred.
The NTSB specifically cautions that the voice-recorder and flight-data-recorder times in that update had not been precisely synchronized. Readers should therefore avoid combining the two countdown tables into a supposedly exact second-by-second reconstruction. The source’s qualifications belong alongside the dramatic details, rather than disappearing when the events are summarized.

Weather and runway protection
Reuters reported on October 1 that the preliminary report described wind information not being provided to the pilots with their landing clearance. That is a reported finding about the information available to the crew. It does not establish a final allocation of responsibility or prove that weather alone caused the crash.
Runway-overrun protection is a separate question. The Federal Aviation Administration explains that an Engineered Materials Arresting System, or EMAS, uses crushable material beyond a runway end: aircraft tires sink into it and the airplane decelerates. Its August 12, 2026 overview describes the role of these installations where a full standard runway safety area is impracticable. A general description of that technology cannot establish how a particular installation would have performed in this accident.
What remains unresolved
The NTSB labels the information preliminary and subject to change. Its investigation page does not present a final probable-cause determination. Recorded speed, braking, engine-power changes and cockpit calls are pieces of evidence; none should be promoted into a complete causal account without the agency’s analysis.
That distinction also prevents a technical description from becoming an unsupported allegation against an individual pilot, controller, operator or manufacturer. The same caution applies to the aircraft’s maintenance and runway infrastructure. A possible investigative question is not proof of a defect, violation or contribution to the accident.

How to follow the investigation
Use the NTSB case number to identify the official record, and check the date and status of each document before sharing it. The accident occurred September 6; the recorder update is dated September 9; the investigation page was updated October 1. This article’s October 11 editorial update is a separate date and does not mean that a final report was issued today.
The original article appeared September 8. This revision brings the account into line with the current official summary, consolidates repeated cautions and removes details that could not be independently rechecked in this review. The five deaths and the serious injuries remain central to the story. Further verified findings should be added with their own dates, while the unresolved cause remains explicitly unresolved.





