When a Boeing 767 touches down at nearly 300 kilometers per hour on a wet runway, physics leaves very little room for error. Newly released National Transportation Safety Board (NTSB) findings from the tragic crash of 21 Air Flight 7598—operating on behalf of Amazon Prime Air—paint a troubling picture of an unstable cockpit, repeated speed warnings, and a missed opportunity to abort.
If you're wondering how a routine cargo flight from San Juan, Puerto Rico, to Miami International Airport turned into a fatal runway overrun, the answer lies in the flight data recorder and cockpit voice recorder logs. Let's look at what actually happened during those critical final minutes.
The Warning Signs in the Cockpit
For nearly two minutes before the aircraft met the tarmac, one pilot repeatedly called out the danger. The plane was coming in too fast, and the data proves it. The Boeing 767-300 was clocking in at 158 knots (approximately 292 km/h) upon landing—well on the high end for a commercial jet arrival.
As automated alarms blared, including a "sink rate" and "too low terrain" callout, tension mounted in the flight deck. One pilot flagged the excessive speed multiple times. Yet, investigators noted a stark and alarming detail: there was no consistent verbal response from the other crew member.
Communication breakdowns in aviation are rarely simple, but they are almost always fatal. When cockpit resource management fails under pressure, hesitation takes over. Aviation experts suggest the pilot flying may have suffered from target fixation, focusing entirely on getting the wheels down rather than processing the mounting hazard indicators.
A Doomed Approach and a Flawed Recovery Attempt
The plane landed long down the 9,360-foot runway, eating up critical stopping distance before its nose and right main gear touched the ground. Strong winds and potential tailwinds only added to the forward momentum as storms moved across the Miami area.
What happened next compounds the mystery. Data shows the crew briefly disengaged the brakes, pushed the throttles forward for four seconds as if attempting an emergency go-around, and then abruptly pulled them back to idle, reapplying the brakes. By then, it was too late.
The cargo jet blew past the runway end, crashing through a perimeter fence, striking equipment, and colliding with vehicles on a public road. Five people working in an aircraft-cleaning crew van tragically lost their lives, while others sustained injuries. Both pilots survived the impact and subsequent fire, providing investigators with interviews that match the harrowing audio logs.
Why Didn't the Crew Abort?
The primary question facing the NTSB is straightforward: why didn't the crew execute a go-around while they still had time?
Former regulatory officials and safety veterans point out that pilots have multiple checkpoints to save an unstable approach. When a plane is traveling too fast two minutes out, standard operating procedure provides clear options:
- Extend the speed brakes and lower landing gear configurations completely.
- Cut throttles aggressively.
- Abort the landing entirely, climb back up, and circle for another attempt.
Instead, late flap deployments and delayed actions left the aircraft flying too close to the ground without proper configuration. Flaps were deployed much later in the sequence, likely reacting frantically to the excessive speed rather than anticipating it.
Accidents like this remind us that modern aviation safety relies entirely on rigid discipline, clear communication, and mutual accountability in the cockpit. When warnings are ignored or met with silence, catastrophe follows.
Take time to review how your own operational procedures handle safety margins and communication protocols when things don't go according to plan. Never ignore the red flags until it is too late to fix them.
Amazon Pilot Warned of Excessive Speed Seconds Before Crash
This video provides an overview of the NTSB data and details regarding the pilot's speed warnings ahead of the crash.
http://googleusercontent.com/youtube_content/1
