TRACE THE
FAILURE
Aviation · Evidence and investigation

Miami cargo overrun.
Brakes on. Brakes off. Brakes on.

The Miami cargo overrun's recorders reveal a sequence. Explaining why it happened requires more than matching timestamps.

Follow the evidence
Illustrative cargo aircraft approaching a runway, seen from behind
AI-generated cargo-aircraft illustration from the episode. Not accident footage or a verified reconstruction of the aircraft’s runway position.
THE COMPANION FILMThe Deadly Panic That Caused the Amazon Jet Crash Watch episode 4:52

On September 6, 2026, Amazon Air Flight 7598, operated by 21 Air, overran runway 30 at Miami International Airport. The NTSB’s preliminary record describes speed concerns on approach and a changing sequence of braking and thrust after touchdown. It does not yet establish the cause of the overrun. The investigation remains ongoing in the official record checked on September 22. NTSB investigation

Watch the evidence explained

The companion episode follows the approach warnings, the flight-data sequence and the separate recorder clocks with explanatory diagrams. Its narration reflects the public evidence checked on September 20, 2026. This article’s primary-source refresh is dated September 22.

What happened in Miami?

Flight 7598 was a Boeing 767 cargo flight from San Juan, Puerto Rico, to Miami. The NTSB identifies the event as a landing overrun at the end of runway 30. Its recorder summaries describe parts of the approach and landing. NTSB, What Happened

The cockpit voice recorder summary records a pilot raising speed concerns during the approach. It also identifies sounds consistent with autopilot disconnection and warnings about descent rate and terrain. Later entries describe sounds similar to touchdown, a go-around call and sounds similar to leaving the paved surface. These selected, preliminary observations do not give a complete account of the crew’s decisions. NTSB September 9 update, CVR table

Braking, increased thrust, then braking again

The flight data recorder summary describes the aircraft’s recorded actions. Times count backward from the end of the FDR recording, which is not an independently established impact time. Groundspeeds measure movement over the ground; they are not indicated airspeeds.

Before FDR recording ends Published observation
30 seconds Nose and right main gear touchdown, at 158 knots groundspeed.
23 seconds Brake application, at 146 knots.
19 seconds Left main gear touchdown, at 134 knots.
15 seconds Brakes released at 120 knots; throttle values increase consistently with go-around thrust.
11 seconds Throttles return to idle; brakes are applied again at 117 knots. Those conditions continue to the recording’s end.

Source: NTSB September 9 update, FDR table. Times and descriptions are preliminary and subject to change.

The summary records braking, brake release with increased thrust, then braking again. It does not explain why each action occurred or give a precise runway position for each one.

Did the brakes fail?

The published summary records brake applications and does not establish brake failure. It reports no recorded indication that speed brakes or thrust reversers deployed. Those are separate systems, and the absence of a deployment indication alone does not show that a component was broken. NTSB September 9 update, FDR rows

The summary supports neither a claim that the aircraft had no braking nor a claim that every system operated normally.

Why two “15 seconds” entries do not prove synchronization

The voice-recorder table places a go-around call 15 seconds before that recording ends. The flight-data table places brake release and increased thrust 15 seconds before its recording ends.

The NTSB says the CVR and FDR times have not been precisely synchronized. Each table counts back from the end of its own recording, so equal countdown values cannot establish that the two events happened simultaneously. NTSB September 9 update, introductions to both tables

Connecting the crew’s words to control inputs and aircraft response requires a synchronized timeline that these selected summaries do not yet provide.

What remains unresolved?

The official page still lists the investigation as ongoing. The inspected record does not provide a final explanation for the overrun. These selected entries also do not establish enough information to calculate a reliable stopping distance or reconstruct every action’s runway position. NTSB investigation and preliminary update

On September 17, the operator said the aircraft had been moved to a secure airport location following its release after initial onsite work, and that it continued cooperating with investigators. Moving the aircraft was a recovery step, not a final finding. In its earlier statement, 21 Air acknowledged that lives were lost. 21 Air updates

The sources checked for this article document approach concerns and changing braking and thrust after touchdown. They leave the reason for that sequence unresolved.

Primary sources

Sources checked September 22, 2026. The investigation remains ongoing in the inspected record.