NTSB Findings Reveal Unheeded Cockpit Speed Warnings Preceded Deadly Amazon Cargo Plane Crash in Miami

Cockpit voice recordings from a fatal Amazon cargo plane crash in Miami show that one aviator repeatedly cautioned that the aircraft was traveling at excessive speeds during the final approach and landing, federal investigators revealed on Wednesday. Despite urgent warnings spanning nearly two minutes, the flight crew failed to stabilize the descent or execute a timely missed approach before overrunning the runway with catastrophic results.

The disaster unfolded on Sunday afternoon when the twin-engine cargo jet touched down deep along the runway, surged beyond the tarmac boundary by roughly 1,300 feet (396 meters), and traversed across an active public thoroughfare. During its destructive path, the plane violently struck a transport vehicle carrying aircraft cleaning personnel, collided with a compact SUV, and burst into flames outside airport grounds.

Five occupants inside the cleaning company's transport van were killed in the collision. An additional five individuals sustained varying injuries, with two victims remaining hospitalized in critical condition as of Tuesday. Both pilots survived the violent sequence and were formally interviewed by officials from the National Transportation Safety Board on Wednesday as part of the agency's comprehensive investigation.

According to an official summary of the cockpit voice recorder released by safety investigators, one of the pilots repeatedly raised alarms about the jet's excessive velocity both as they neared the airfield and following wheel contact. However, the summary noted that the pilot handling the controls never provided a consistent verbal reply to acknowledge or act upon the persistent airspeed warnings.

Data retrieved from the aircraft's flight data recorder illustrated severe instability throughout the landing sequence. After the aircraft made an awkward initial touchdown on its right main and nose landing gear, the flight crew momentarily disengaged the wheel brakes and pushed the throttles forward in what appeared to be an attempt to take off and retry the landing. That go-around attempt was abandoned after just four seconds, leaving the jet unable to halt before the runway ran out.

The late touchdown severely reduced the available tarmac necessary to decelerate the heavy widebody jet. Based on preliminary federal data, flight-tracking service Flightradar24 calculated that the aircraft did not make contact with the ground until it was already nearly halfway down the 9,360-foot runway, drastically compounding the stopping distance problem.

Complicating the final approach were turbulent environmental conditions surrounding the Miami airport. As convective storms moved into the immediate vicinity, strong and shifting winds were present, which aviation analysts note may have generated a significant tailwind that pushed the speeding jet forward and further impeded the crew's braking efforts.

In addition to the verbal exchanges between the crew members, audio logs recovered from the cockpit captured multiple automated system alarms. The aircraft's internal safety equipment issued repeated automated alerts regarding an unsafe rate of descent and the rapid closure rate with approaching terrain as the plane descended toward the ground.

Aviation specialists pointed out that the flight crew had ample opportunity to remedy their unstable approach long before touching the tarmac. Mike O'Donnell, a former Federal Aviation Administration official who previously directed airport safety and crash investigations, emphasized that the crew could have deployed aerodynamic spoilers, cut the engine throttles, and lowered the gear earlier to bleed off speed, or simply aborted the landing entirely.

O'Donnell stated that a flight crew has plenty of time to initiate a standard go-around procedure when speed anomalies are identified two minutes out from touchdown. He also observed that the sounding of terrain proximity alerts strongly indicates that the Boeing aircraft was unstable and potentially misconfigured for a safe landing profile.

The evident lack of communication has raised sharp questions among safety analysts regarding crew resource management. Steve Arroyo, an experienced former airline captain and aviation safety expert, remarked that the emerging details point to a breakdown in flight deck leadership and coordination, suggesting the pilot at the controls might have suffered from task fixation while attempting to force an unsafe landing.

Former Department of Transportation Inspector General Mary Schiavo raised concerns about potential flight deck authority gradients. Schiavo suggested that if an experienced senior captain was flying while a less seasoned first officer was verbalizing the speed warnings, the junior pilot may not have felt sufficiently empowered to aggressively assert control or enforce an immediate go-around.

Records indicate the ill-fated aircraft was a 32-year-old Boeing 767. The airframe originally entered service as a commercial passenger airliner, operating for several overseas carriers across more than two decades before undergoing conversion into a dedicated cargo freighter in 2015, according to tracking data from Flightradar24.

At the time of the crash, the aircraft was being operated by 21 Air, a cargo charter airline headquartered in North Carolina. The carrier has been contracted to fly freight shipments and transport customer packages on behalf of Amazon since early 2024.

National Transportation Safety Board investigators are continuing to examine all potential contributing elements, including 21 Air's flight operations, the jet's complete maintenance history, aircraft ownership records, and the adverse weather at the time of arrival. Agency officials confirmed that a complete transcript of the cockpit voice recording will be published at a later stage of the investigation.