Federal Investigators Reveal Pilot Repeatedly Warned of Excessive Speed Moments Before Fatal Miami Cargo Crash

A pilot aboard an Amazon cargo aircraft repeatedly cautioned that the plane was descending too rapidly in the moments leading up to a deadly runway overrun at a Miami airport, according to preliminary investigative findings released by federal authorities. The crash, which occurred Sunday afternoon, claimed the lives of five people on the ground when the widebody jet traveled past the pavement and collided with vehicles outside the airport perimeter.

A summary of cockpit voice recorder data compiled by the National Transportation Safety Board indicates that one crew member spent nearly two minutes voicing continuous concerns regarding the aircraft's excessive airspeed. Despite the persistent alerts issued both during the final approach and immediately following touchdown, the pilot operating the controls did not offer a consistent verbal acknowledgment or response.

The landing sequence quickly deteriorated as the aircraft barreled past the runway threshold, traveling approximately 1,300 feet (396 meters) beyond the end of the paved landing strip. The careening jet slammed directly into a transport van carrying airport cleaning personnel before striking a compact SUV, sliding across an adjacent public roadway, and catching fire.

All five fatalities were passengers inside the cleaning company's van. Five other people suffered injuries during the collision, with two individuals reported to be in critical condition as of Tuesday. Both pilots survived the impact and were subsequently questioned by federal investigators on Wednesday to reconstruct the final moments of the flight.

Information retrieved from the aircraft's flight data recorder showed that the Boeing 767 experienced significant instability while attempting to land amid severe weather. Tracking analysis from Flightradar24, based on federal data, estimated that the aircraft did not make contact with the tarmac until it was nearly halfway down the 9,360-foot runway, severely limiting the distance available to bring the heavy freighter to a complete halt.

The data further revealed an unusual and awkward initial touchdown, with only the right landing gear and the nose gear making first contact with the runway surface. Strong meteorological disturbances moving across the airfield may have generated powerful tailwinds, compounding the difficulty of deceleration and propelling the aircraft forward along the strip.

Moments after touching down, the flight crew appears to have briefly attempted an emergency abort maneuver. Data indicates the pilots released the wheel brakes and pushed the engine throttles forward in what appeared to be an attempt to take off and circle for another approach. However, that effort was abruptly abandoned just four seconds later.

In addition to the verbal warnings from the monitoring crew member, the cockpit voice recorder documented several automated alerts generated by onboard systems. These cockpit alarms warned the crew of an unsafe rate of descent and signaled dangerous proximity to the ground terrain.

Aviation safety experts noted that the flight crew missed multiple opportunities to prevent the tragedy. Mike O'Donnell, a former Federal Aviation Administration official who previously managed airport safety programs and crash investigations, emphasized that the crew had ample time to correct their flight profile after the first speed warning.

O'Donnell explained that the pilots could have deployed the aircraft's wing spoilers, throttled back the engines, and dropped the landing gear to shed speed. Alternatively, he stated that the crew should have immediately rejected the landing and initiated a standard go-around while still airborne two minutes out, rather than attempting to force a touchdown.

The automated terrain warnings that sounded in the cockpit further suggested that the aircraft was not properly configured or stabilized for landing, according to O'Donnell. Proper approach procedures require aircraft to meet strict speed, descent rate, and configuration criteria before crossing the runway threshold.

The apparent breakdown in communication between the two aviators has drawn sharp scrutiny from industry analysts. Steve Arroyo, an experienced former airline pilot and aviation safety consultant, pointed out that the findings highlight a concerning deficiency in cockpit coordination, noting that the flying pilot may have succumbed to tunnel vision during the landing attempt.

Arroyo questioned the level of command and adherence to standard operational procedures on the flight deck, asking why established guidelines outlined in company operating manuals were not followed to safely resolve the unstable approach.

The cockpit dynamic was also highlighted by Mary Schiavo, a former Inspector General for the U.S. Department of Transportation. Schiavo suggested that investigators will likely examine whether a steep authority gradient existed between a senior captain at the controls and a less experienced first officer who may have felt constrained from aggressively intervening.

The aircraft involved was a 32-year-old Boeing 767 that spent more than two decades carrying commercial passengers for various international airlines before undergoing conversion into a dedicated cargo freighter in 2015. The flight was operated on behalf of Amazon by 21 Air, a North Carolina-based air carrier that has transported freight under contract for the retail giant since 2024.

Federal investigators from the National Transportation Safety Board are continuing their examination of all potential contributing factors, including the maintenance history of the airframe, the operating standards of 21 Air, and the prevailing weather conditions at the time of the crash. A complete verbatim transcript of the cockpit voice recordings is expected to be released at a later stage of the inquiry.