Cockpit Recordings Reveal Pilot Repeatedly Warned of Excessive Speed Moments Before Fatal Amazon Cargo Jet Crash

Federal investigators looking into the deadly crash of an Amazon cargo aircraft in Miami have discovered that one of the pilots repeatedly raised alarms about the plane’s excessive speed in the final minutes of the flight. Newly disclosed records from the National Transportation Safety Board show that the warning calls went unheeded without a consistent verbal acknowledgment from the other crew member, culminating in a runway overrun that claimed the lives of five people on the ground.

According to preliminary cockpit voice recorder findings released by the safety agency, the urgent verbal warnings continued for nearly two minutes as the wide-body jet descended toward the runway and even persisted after the wheels hit the tarmac. The recording captured a tense environment in which the pilot monitoring the approach tried multiple times to flag the dangerous approach speed, yet received no steady or coherent response from the pilot at the controls.

The flight ended in catastrophe on a Sunday afternoon when the jet failed to decelerate and blasted through the perimeter of the runway. The cargo transport traveled roughly 1,300 feet (396 meters) past the designated pavement, hurtled across an active public thoroughfare, and crashed violently into a vehicle transport van carrying workers employed by an airport cleaning company. The plane also clipped a compact SUV before coming to a stop and bursting into flames.

The impact proved devastating for the occupants of the cleaning company van, with all five fatalities confirmed to be workers inside that vehicle. In addition to the deaths, five other individuals sustained injuries, including two victims who remained hospitalized in critical condition days after the accident. Both flight crew members survived the crash with non-fatal injuries and were subsequently questioned by federal investigators as part of the formal inquiry.

Aviation specialists indicate that the substantial time frame during which the warnings occurred provided the flight crew with ample opportunity to rectify their configuration or pull up entirely. An aircraft traveling too rapidly toward the runway can be managed through deliberate aerodynamic measures or, if stabilized approach criteria cannot be met, by initiating an immediate go-around to circle back for a safer attempt.

Former Federal Aviation Administration official Mike O'Donnell, who previously oversaw airport safety standards and crash investigations, pointed out that the crew had several standard operational options at their disposal when the speed warnings initially arose. He noted that pilots facing high approach speeds can deploy spoilers, pull back the engine throttles, and drop the landing gear to create drag. O'Donnell emphasized that with nearly two minutes of advance warning, the crew had more than enough time to abandon the landing and execute a standard go-around procedure.

Information recovered from the jet’s flight data recorder illustrated that the aircraft was notably erratic and unstable as it lined up with the runway in turbulent weather. The data revealed a chaotic sequence immediately after touchdown, showing that the flight crew briefly released the wheel brakes and pushed the throttles forward in what appeared to be an attempt to take off again and perform a missed approach. However, that effort was abruptly abandoned just four seconds later, leaving the plane without sufficient runway to halt its momentum.

Investigators also noted that the cockpit audio captured persistent automated alarms sounding within the flight deck. These electronic warning systems repeatedly cautioned the pilots about an unsafe rate of descent and alerted them to the rapid approach of the ground. Aviation experts noted that such terrain and descent rate warnings further suggest that the jet was unstable on its glide path and may not have been properly configured for touchdown.

The aircraft's landing posture also severely limited its ability to stop safely on the available tarmac. Initial physical contact with the runway occurred unevenly on the right landing gear and the nose gear, rather than a standard main-gear touchdown. Data analyzed by tracking service Flightradar24 indicated that the plane did not touch down until it had already traveled nearly halfway down the 9,360-foot runway, significantly diminishing the stopping distance ahead while strong convective storm winds likely created a tailwind pushing the aircraft forward.

The newly revealed communications have led aviation safety professionals to scrutinize the flight deck management and crew resource coordination during the critical phases of the landing. Former airline pilot and safety specialist Steve Arroyo questioned the breakdown in basic flight deck discipline, noting that the details indicate a profound failure of leadership and coordination. Arroyo suggested that the handling pilot might have experienced tunnel vision, fixating entirely on forcing the landing rather than adhering to established company manual guidelines.

The dynamic between the two cockpit crew members has also emerged as a central line of inquiry for investigators. Mary Schiavo, a former Inspector General of the Department of Transportation, remarked that the communication breakdown might reflect an authority gradient between a senior captain flying the aircraft and a junior first officer who called out the warnings. Schiavo raised concerns over whether the junior pilot felt empowered to aggressively challenge the dangerous approach or intervene to take control of the aircraft.

The aircraft involved in the fatal incident was a 32-year-old Boeing 767 that began its service life configured for commercial passenger operations. Flight tracking records show that the airframe operated for multiple international airlines across more than two decades before undergoing an extensive cargo freighter conversion in 2015 to support package distribution networks.

At the time of the crash, the plane was operated by 21 Air, a North Carolina-based cargo airline contracted to transport freight for Amazon since 2024. The operating airline's safety practices, crew training protocols, and maintenance compliance are now under close examination alongside the physical wreckage.

National Transportation Safety Board investigators are continuing their comprehensive review of all contributing elements, including the aircraft's multi-decade maintenance logs, 21 Air's flight deck procedures, and the severe weather patterns active around the airport. While the preliminary summary has provided crucial context regarding the crew's final minutes, the federal agency stated that a complete, word-for-word transcript of the cockpit voice recording will be released at a later stage of the investigation.