Verified

NTSB Data Shows Late Abort Attempt and Speed Warnings in Fatal Miami Cargo Jet Crash

r/US •

Darom AI September 10, 2026

Federal investigators examining the fatal runway overrun at Miami International Airport revealed that the crew of the Amazon cargo jet briefly attempted to abort their landing seconds before impact, following repeated cockpit warnings about excessive speed.

According to data released by the National Transportation Safety Board (NTSB) on September 9, the Boeing 767-33A—operating as Amazon Air Flight 7598 and flown by 21 Air LLC—was coming in too fast during its final approach. Flight data and cockpit voice recorder transcripts show that one pilot repeatedly warned the other about the aircraft's high speed for nearly two minutes prior to touchdown.

Key Findings from Flight Recorders

The NTSB's preliminary readouts detail a turbulent final descent punctuated by automated altitude and descent-rate warnings, including "sink rate" and "too low terrain" alerts. Approximately 33 seconds after those automated warnings and about 15 seconds before the recording ended, the crew called for a go-around and increased engine throttles to a setting consistent with an aborted landing.

Investigators noted that the maneuver came too late to prevent the catastrophe. The thrust increase lasted only briefly before throttles were pulled back again, and recorded data showed no indication that the aircraft's speed brakes or thrust reversers were deployed after touchdown.

Accident Context and Ground Impact

The aircraft arrived from San Juan, Puerto Rico, on its third flight of the day before overrunning runway 30. The jet barreled approximately 1,300 feet past the paved surface, tearing through perimeter fencing and striking two vehicles on the ground.

The collision killed five people and injured five others. According to federal officials, all five fatalities occurred within the two impacted vehicles: an airline cleaning services van located on airport property and an SUV traveling on a nearby public roadway. Two of the injured individuals were transported to Jackson Memorial Hospital.

The NTSB has not yet determined an official cause for the crash. Investigators are continuing to analyze the recovered flight data and cockpit voice recorders, alongside scheduled interviews with both surviving flight crew members.

Fact Check Analysis AI Verified

--- > **Claim:** Federal investigators examining the fatal runway overrun at Miami International Airport revealed that the crew of the Amazon cargo jet briefly attempted to abort their landing seconds before impact, following repeated cockpit warnings about excessive speed. - **Verdict:** Verified - **Analysis:** The NTSB released data showing the crew of the Amazon cargo jet attempted a late go-around/landing abort seconds before impact after experiencing repeated warnings about high speed. [ABC News](https://abcnews.com/US/ntsb-release-readout-cockpit-voice-recorder-amazon-cargo/story?id=136292103) --- --- > **Claim:** According to data released by the National Transportation Safety Board (NTSB) on September 9, the Boeing 767-33A—operating as Amazon Air Flight 7598 and flown by 21 Air LLC—was coming in too fast during its final approach. - **Verdict:** Verified - **Analysis:** NTSB data released on September 9 confirms the Boeing 767-33A operating as 21 Air Flight 7598 for Amazon Air was moving too fast during its final approach into Miami. [USA Today](https://www.usatoday.com/story/news/state/florida/miami/2026/09/09/ntsb-release-readout-cockpit-voice-recorder-amazon-crash-mia/91670964007/) --- --- > **Claim:** Flight data and cockpit voice recorder transcripts show that one pilot repeatedly warned the other about the aircraft's high speed for nearly two minutes prior to touchdown. - **Verdict:** Verified - **Analysis:** Cockpit voice recorder summaries indicate a pilot repeatedly warned about high speed for nearly two minutes leading up to the touchdown and subsequent overrun. [ABC News](https://abcnews.com/US/ntsb-release-readout-cockpit-voice-recorder-amazon-cargo/story?id=136292103) --- --- > **Claim:** The NTSB's preliminary readouts detail a turbulent final descent punctuated by automated altitude and descent-rate warnings, including "sink rate" and "too low terrain" alerts. - **Verdict:** Verified - **Analysis:** Preliminary readouts detailed automated altitude and descent-rate warnings, including "sink rate" and "too low terrain" alerts. [CNN](https://www.cnn.com/2026/09/09/us/amazon-cargo-plane-crash-data) --- --- > **Claim:** Approximately 33 seconds after those automated warnings and about 15 seconds before the recording ended, the crew called for a go-around and increased engine throttles to a setting consistent with an aborted landing. - **Verdict:** Verified - **Analysis:** NTSB readouts confirm that roughly 15 seconds before the recording ended, a pilot called for a go-around and throttles were increased for an aborted landing. [ABC News](https://abcnews.com/US/ntsb-release-readout-cockpit-voice-recorder-amazon-cargo/story?id=136292103) --- --- > **Claim:** The thrust increase lasted only briefly before throttles were pulled back again, and recorded data showed no indication that the aircraft's speed brakes or thrust reversers were deployed after touchdown. - **Verdict:** Verified - **Analysis:** Investigators noted the thrust increase lasted only briefly before being pulled back, and data showed no indication of speed brake or thrust reverser deployment. [USA Today](https://www.usatoday.com/story/news/state/florida/miami/2026/09/09/ntsb-release-readout-cockpit-voice-recorder-amazon-cargo/story?id=136292103) --- --- > **Claim:** The aircraft arrived from San Juan, Puerto Rico, on its third flight of the day before overrunning runway 30. - **Verdict:** Verified - **Analysis:** The flight originated from San Juan, Puerto Rico, marking the aircraft's third trip of the day before it overran Runway 30 at Miami International Airport. [ABC News](https://abcnews.com/US/cargo-plane-overruns-runway-miami-international-airport-faa/story?id=136242081) --- --- > **Claim:** The jet barreled approximately 1,300 feet past the paved surface, tearing through perimeter fencing and striking two vehicles on the ground. - **Verdict:** Verified - **Analysis:** Records show the jet traveled approximately 1,300 feet past the paved runway surface, breached the perimeter fence, and struck two ground vehicles. [CNBC](https://www.cnbc.com/2026/09/07/crashed-amazon-cargo-jet-struck-two-vehicles-ended-up-1300-feet-past-runway-ntsb-says.html) --- --- > **Claim:** The collision killed five people and injured five others. - **Verdict:** Verified - **Analysis:** Federal officials confirmed that the crash resulted in five fatalities and five injuries on the ground. [AP News](https://apnews.com/article/amazon-cargo-plane-miami-airport-47411c751782887757922efa5f634aa5) --- --- > **Claim:** All five fatalities occurred within the two impacted vehicles: an airline cleaning services van located on airport property and an SUV traveling on a nearby public roadway. - **Verdict:** Verified - **Analysis:** Officials confirmed that all five fatalities occurred within the two impacted ground vehicles: an airport cleaning services van and a public roadway SUV. [ABC News](https://abcnews.com/US/cargo-plane-overruns-runway-miami-international-airport-faa/story?id=136242081) --- --- > **Claim:** Two of the injured individuals were transported to Jackson Memorial Hospital. - **Verdict:** Verified - **Analysis:** News reports detailing the transport of casualties confirm that injured individuals from the crash were taken to Jackson Memorial Hospital. [AP News](https://apnews.com/article/amazon-cargo-plane-miami-airport-47411c751782887757922efa5f634aa5) ---

AI Research Queries

🔍 NTSB" "Flight 7598" "21 Air" "September 9" Boeing 767 Miami
🔍 NTSB cockpit voice recorder transcript Amazon flight Miami speed warning go-around
🔍 Amazon cargo plane San Juan third flight Miami runway 30 overrun
🔍 Miami cargo plane crash 1300 feet past runway perimeter fence vehicles
🔍 Miami plane crash five dead cleaning van SUV Jackson Memorial Hospital

Key Findings from Flight Recorders

Accident Context and Ground Impact

Comments (0)