Amazon 767 Overrun Killed Five; Data Shows No Speed Brakes or Thrust Reversers

Federal investigators have identified a consequential gap in the recorded landing sequence of the Amazon Prime Air Boeing 767 that overran a runway at Miami International Airport: the data showed no indication that its speed brakes or thrust reversers deployed. The 21 Air-operated cargo jet continued roughly 1,300 feet beyond the runway, struck a cleaning-service van on airport property, passed through a fence and hit an SUV on a public street.

Five cleaning workers in the van died. Two other van occupants and both pilots survived. At the final available flight-data point, the aircraft still had a recorded ground speed of 65 knots. These facts focus the inquiry on how the aircraft was or was not decelerating, but the National Transportation Safety Board has cautioned that its investigation remains preliminary and has not determined a cause.

What the missing indications mean and what they do not

Speed brakes and thrust reversers perform different jobs after touchdown. Raised speed brakes disrupt airflow over the wings, reducing lift and placing more of the aircraft’s weight on its landing gear. That increases the tire contact force available for wheel braking. Thrust reversers redirect engine airflow to provide another source of deceleration, particularly during the faster portion of the landing roll.

The absence of recorded deployment indications is therefore important, but it is not itself a mechanical diagnosis. Investigators still must establish what the crew commanded, what the aircraft systems did, what the recorders captured and whether the relevant components and sensors functioned as designed. A recorded nondeployment can support several investigative questions; it cannot, at this stage, answer why the systems were not shown as deployed.

The NTSB recovered the cockpit voice recorder and began reviewing flight data. Its work includes crew and air-traffic-control interviews, aircraft examinations, and reviews of the 32-year-old jet’s ownership, maintenance and operating history. The aircraft began life as a passenger jet and was converted for cargo service in 2015, according to Flightradar24, but that age and conversion history are background for inspection not evidence of a failure.

Weather will also be evaluated. The aircraft was arriving from Puerto Rico as storms developed around Miami, and winds above 25 knots were reported that afternoon. Outside experts have attributed the long touchdown to an apparent tailwind after reviewing the landing, but that interpretation is not an NTSB finding. It remains unresolved how wind, touchdown location, aircraft configuration, crew decisions and system performance interacted.

The runway boundary became part of the outcome

The aircraft’s path beyond the pavement makes airport protection another central part of the inquiry. Miami has a 1,000-foot safety buffer at the end of its runways and appears to comply with federal requirements, according to experts familiar with the airport. Yet the Boeing traveled beyond that area and reached workers, a perimeter fence and public-road traffic.

Miami does not have an Engineered Materials Arresting System at the runway end involved. EMAS uses a bed of lightweight, crushable material that allows an overrunning aircraft’s tires to sink, creating controlled resistance and slowing the aircraft. The Federal Aviation Administration says a standard installation will stop most aircraft entering at 70 knots and reports that the technology has safely stopped 26 aircraft carrying 497 crew members and passengers.

That comparison is relevant because the Boeing’s last recorded speed was 65 knots, but it does not establish that an EMAS bed would have stopped this particular aircraft. Entry speed at the runway end, aircraft mass, landing-gear condition, trajectory, bed dimensions and airport geometry all matter. The final data point also may not correspond to the precise point where an arresting bed would begin. Any conclusion about the counterfactual requires engineering analysis specific to the accident sequence and site.

EMAS is installed at about 120 U.S. airports, often where terrain, roads, water or development prevents construction of a full conventional runway safety area. Where adequate clear land exists, regulators can accept a graded safety area instead. Compliance and consequence mitigation are therefore related but distinct questions: an airport can meet its applicable design standard while investigators still examine whether another protective layer could have changed an overrun’s result.

The decisive evidence will have to connect the aircraft’s approach, touchdown, control commands, system responses and speed history into one validated sequence. Until that work is complete, the missing speed-brake and thrust-reverser indications remain a major investigative fact not a finding of pilot error, mechanical failure or crash causation.

By Thomas Caldwell — AMI’s senior editor for mechanical and mobility engineering, covering vehicle electronics, systems integration, electrification, chassis systems, propulsion, and safety policy.