Amazon cargo plane crash in Miami: what the recorders now show
The investigation has moved well beyond the first-day questions. NTSB flight-data and cockpit-recording disclosures now show a high-speed, unstable approach, repeated cockpit warnings, a late and uneven touchdown, and a brief attempt to initiate a go-around after touchdown before the crew returned the throttles to idle and reapplied the brakes. Recorded data showed no deployment of the speed brakes or thrust reversers. Investigators have not yet determined probable cause or why the crew continued the approach and then abandoned the go-around.1,2,3,6,7,8
The FAA says 21 Air Flight 7598, a Boeing 767 cargo aircraft operating for Amazon Prime Air, overran Runway 30 after arriving from San Juan, Puerto Rico, at Miami International Airport on September 6. The aircraft struck airport equipment and vehicles beyond the runway. Five people on the ground were killed; the two pilots survived.1,2
The NTSB recovered both the flight-data recorder and cockpit-voice recorder. By September 9 and 10, investigators had begun publicly describing what those recorders showed, resolving several questions that were open when this report was first published.2,6,7,8
Those disclosures are preliminary evidence, not a cause finding. The NTSB is still examining crew decisions and coordination, aircraft performance and systems, weather, training and airline operations. A final probable-cause determination has not been issued.2,4,6,7
What the recorders now show
NTSB investigator Chihoon Shin said the nose gear and right main landing gear first contacted the runway at a recorded ground speed of 158 knots. The left main landing gear did not contact the pavement until 11 seconds later. Engine power then increased to values consistent with go-around thrust.3,8
The attempted go-around did not continue. Eleven seconds before the recording ended, the throttles were reduced to idle and the brakes were reapplied. Recorded data showed no indication that the speed brakes or thrust reversers deployed during the rollout.4,6,8
The cockpit recording adds another piece that was not public when the first version of this report was written: one pilot repeatedly raised concern about excessive speed as the aircraft descended, while automated alerts including sink-rate and terrain warnings sounded. The crew nevertheless continued the approach. Investigators are now focused in part on why an unstable approach was continued and why the go-around was started only after touchdown and then abandoned.2,3,6,7
What changed from the first version of this report
On September 7, the exact touchdown sequence, verified speed profile, use of the speed brakes and thrust reversers, and whether the crew attempted a go-around were still open questions. They are no longer wholly unknown. The NTSB has now released specific recorder-derived facts about each of them.6,8
What remains unresolved is the explanation. The data show what the aircraft and crew did in the final seconds; they do not yet establish why the crew persisted with the approach, why the go-around was abandoned, whether aircraft systems behaved as commanded, or how weather, training, procedures and crew coordination contributed.2,3,4,6,7,8
The runway-safety question
Miami's runway had the federally compliant safety area required beyond the pavement, but it did not have an Engineered Materials Arresting System, or EMAS, designed to slow an aircraft that overruns a runway. Investigators are examining the absence of such a system as part of the accident review.1,3,9
That does not establish that an arresting system would have prevented the deaths. The aircraft traveled roughly 1,300 feet beyond the runway before coming to rest, and the NTSB has not issued a conclusion about what difference EMAS would have made in this crash.2,9
The aircraft, crew and operator
The aircraft was a 32-year-old Boeing 767-33A freighter operated by 21 Air for Amazon Prime Air and converted from passenger to cargo service. Investigators have said they will examine the aircraft's maintenance and performance as well as the crew's experience and training and the operator's procedures. Age alone is not evidence of a cause.2,3,5,6
Reuters reported that the pilots had substantial overall flight experience but were comparatively recent 767 type-rating holders. The NTSB's latest disclosures have put crew coordination and decision-making squarely into the investigation, but that is still an investigative line rather than a final finding of cause.2,4,6,7
21 Air Flight 7598, operating for Amazon Prime Air and arriving from San Juan, lands at Miami International Airport and overruns Runway 30. Five people on the ground are killed; both pilots survive.1,2
The NTSB says the flight-data recorder and cockpit-voice recorder have been recovered and sent for analysis. Investigators continue documenting the scene.2,4
The NTSB releases preliminary flight-data findings showing the touchdown sequence, a brief go-around-thrust command after touchdown, the return to idle and braking, and no recorded deployment of speed brakes or thrust reversers.6,8
Further cockpit-recording details show repeated concern about excessive speed and automated warnings during the approach, sharpening the investigation around the decision to continue the unstable landing.6,7
- Why the crew continued an unstable, high-speed approach instead of executing a go-around before touchdown.
- Why go-around thrust was applied after touchdown and then abandoned seconds later.
- Why recorded data show no deployment of the speed brakes or thrust reversers, including whether this reflected crew action, aircraft configuration, system behavior or another factor.
- What role weather, wind and runway conditions played in the approach and overrun.
- Whether training, airline procedures, crew coordination, aircraft condition or maintenance materially contributed.
- Whether an arresting system or different runway-end infrastructure would have materially changed the outcome.
- What the NTSB ultimately determines to be the probable cause and contributing factors.
- FAASept. 6 — FAA statements on aviation accidents and incidents
Origin: manual_report
- ReutersSept. 7 — Investigators recover black boxes from cargo plane crash in Miami
Origin: manual_report
- Associated PressSept. 7 — Federal investigators probe Amazon cargo jet's fiery runway crash that killed 5 in Miami
Origin: manual_report
- CBS MiamiSept. 7 — Amazon cargo plane flight data and cockpit voice recorders recovered
Origin: manual_report
- CBS MiamiSept. 7 — Delays, cancellations mount after deadly Amazon cargo plane crash
Origin: manual_report
- ReutersSept. 10 — Pilot pressed on with landing despite warnings in Miami cargo crash, NTSB says
Origin: manual_report
- Associated PressSept. 10 — A pilot warned the Amazon cargo plane was coming in too fast
Origin: manual_report
- CBS MiamiSept. 9 — Flight data shows pilot started go-around then reversed course
Origin: manual_report
- NPRSept. 10 — NPR follow-up on the Miami cargo plane crash
Origin: manual_report
- Revision 2 · September 10, 2026
- Revision 1 · September 6, 2026