Federal Investigators Reveal Amazon Cargo Jet Crew Repeatedly Warned of Excessive Speed Before Deadly Miami Runway Overrun

Federal investigators examining the fatal crash of an Amazon cargo aircraft in Miami have discovered that one of the pilots issued multiple warnings regarding excessive speed for nearly two minutes before the plane careened off the runway. According to investigative updates released Wednesday, the urgent warnings continued both during the final approach and after the widebody jet touched down on the tarmac.

A preliminary summary of the cockpit voice recorder provided by the National Transportation Safety Board indicates that the pilot operating the controls never offered a consistent verbal reply to the co-pilot’s alerts. Following an awkward initial touchdown, the crew briefly attempted to take off again before abandoning the maneuver and sliding past the airfield boundary, ultimately slamming into a ground vehicle carrying five workers.

The catastrophic sequence unfolded on Sunday afternoon when the heavy cargo plane arrived at high speed and overshot the runway threshold by roughly 1,300 feet. The sliding airframe crossed a public thoroughfare, colliding with a service van belonging to an aircraft cleaning contractor and striking a compact sport utility vehicle before coming to a halt and erupting in flames.

The collision proved fatal for all five occupants inside the cleaning company’s transport van. Five additional individuals sustained various injuries during the crash, with two victims remaining hospitalized in critical condition through Tuesday. Both pilots aboard the cargo jet survived the impact and were formally interviewed by federal investigators on Wednesday.

Aviation safety specialists emphasized that the flight crew had sufficient time and available procedures to correct their airspeed or abandon the approach altogether. Former Federal Aviation Administration official Mike O'Donnell, who previously led airport safety and accident investigations, noted that the pilots could have deployed the wing spoilers, throttled back engine power, or lowered the landing gear to shed excessive speed during the approach.

O'Donnell stated that having two minutes of advance warning provided the flight crew ample opportunity to either bleed off speed or initiate an immediate go-around to circle back for a safer approach. Aviation protocols routinely instruct crews to abort unstable approaches rather than force a dangerous landing.

Data retrieved from the flight data recorder late Tuesday demonstrated that the aircraft was markedly unstable as it neared the ground in the presence of turbulent weather. The telemetry revealed that after touching down, the crew briefly released the brakes and advanced the throttles in what appeared to be an attempt to take off again, only to terminate the abort attempt a mere four seconds later.

Cockpit audio logs further documented a succession of automated cockpit alerts warning the pilots about excessive descent rates and impending terrain proximity. According to O'Donnell, the activation of ground proximity warnings underscores that the aircraft was unstable and points to the likelihood that the plane was not properly configured for its final approach.

The jet touched down deep along the airstrip, initially making contact on only its right main gear and nose gear, which drastically shortened the remaining pavement available to bring the heavy aircraft to a complete stop. Flightradar24, utilizing data from the safety board, calculated that the jet did not make its initial runway contact until nearly halfway down the 9,360-foot landing strip.

Adverse meteorological conditions moving through the airport area likely worsened the aircraft's landing rollout. Strong winds associated with approaching storms may have generated a significant tailwind, which would have increased ground speed and propelled the aircraft further down the runway during the landing roll.

While safety officials have published an initial review of the audio and data recorders, the complete verbatim transcript of the flight crew's cockpit communications will remain sealed until a later phase of the federal investigation.

The emerging evidence has drawn sharp criticism from aviation professionals regarding cockpit discipline and adherence to standard operating procedures. Former airline pilot and aviation safety consultant Steve Arroyo pointed out that the findings suggest a severe breakdown in flight deck coordination, raising concerns that the flying pilot may have succumbed to task fixation while attempting the landing.

Arroyo questioned the overall leadership and management inside the cockpit, asking why standard guidelines outlined in the carrier's operating manual were not enforced to manage the approach properly.

Mary Schiavo, a former Inspector General for the U.S. Department of Transportation, raised the possibility of a steep authority gradient within the cockpit. She noted that if a senior captain was flying while a less experienced first officer called out the airspeed warnings, the junior crew member may have hesitated to forcefully intervene or take control of the aircraft.

The airframe involved in the disaster was a 32-year-old Boeing 767 that spent over two decades operating as a passenger airliner for international carriers before undergoing conversion into a dedicated cargo freighter in 2015.

The ill-fated flight was operated by 21 Air, a North Carolina-based air freight company that has provided contracted cargo transport services for Amazon since 2024.

National Transportation Safety Board investigators are currently conducting a comprehensive inquiry into the disaster, reviewing 21 Air's flight operations, the jet's complete maintenance history, past ownership records, and the prevailing weather patterns at the airport during the accident.