MQ-9A Reaper Crashes in Victorville After Pilot Terminates Data Link

Casualties unknown • VICTORVILLE, CA, US

An MQ-9A Reaper sustained heavy damage after a takeoff abort procedure led to a loss of remote connectivity and a subsequent stall at Southern California Logistics Airport.

What happened

On 18 January 2023, an MQ-9A Reaper, tail number 11-4123, crashed during takeoff operations at Southern California Logistics Airport (SCLA) in Victorville, California. The aircraft, belonging to the 432nd Wing and operated by a contract Launch and Recovery Element from i3, was performing a takeoff sequence when the crew initiated an abort procedure.

During the takeoff roll, the aircraft reached speeds of 82-83 KIAS, at which point the sensor operator called for an abort. The pilot executed the abort procedures at 91 KIAS; however, the aircraft had already become airborne, reaching an altitude of 18 feet AGL. Following the ascent, the pilot commanded the sensor operator to "Kill the GDT," effectively terminating the Ground Data Terminal link. This action caused a total loss of remote-control connectivity while the aircraft was in a stalled state at 67 KIAS and 2 feet AGL. The aircraft impacted the runway centerline, veered off the paved surface, and sustained extensive damage to its engine, landing gear, radome, Multi-Spectral Targeting System (MTS), and lower data-link antenna.

The investigation

The Accident Investigation Board examined pre-flight ground operations, cockpit communications, and technical procedures. The board reviewed maintenance logs regarding Angle of Attack (AOA) sensor checks and analyzed the adherence to established takeoff standards and Technical Orders (TO). Simulations were also conducted to determine if maintaining the data link during the abort would have prevented the loss of control.

Findings

  • The primary cause of the mishap was the pilot's decision to terminate the Ground Data Terminal link while the aircraft was at a low altitude and airspeed, resulting in a lost link.
  • During pre-flight ground operations, the pilot failed to identify that the AOA sensor readings were outside of the permitted Technical Order parameters.
  • The sensor operator did not verbalize the "ROTATE" command at the prescribed 78 KIAS.
  • The sensor operator issued an "ABORT" command after the aircraft had already exceeded the rotation speed and the established commit point.

Probable cause

The pilot's decision to terminate the ground data link while the aircraft was in a stalled state caused the loss of remote control, leading to the crash; contributing factors included improper AOA sensor verification during pre-flight and failures by the sensor operator to follow standardized verbal callouts for rotation and abort limits.

Frequently asked questions

What happened in the 2023-01-18 MQ-9A accident near VICTORVILLE, CA?

An MQ-9A Reaper sustained heavy damage after a takeoff abort procedure led to a loss of remote connectivity and a subsequent stall at Southern California Logistics Airport.

What aircraft was involved and where did it happen?

The accident on 2023-01-18 involved a MQ-9A, registration 11-4123, operated by Air Combat Command (ACC), at VICTORVILLE, CA.

What was the probable cause of the accident?

The pilot's decision to terminate the ground data link while the aircraft was in a stalled state caused the loss of remote control, leading to the crash; contributing factors included improper AOA sensor verification during pre-flight and failures by the sensor operator to follow standardized verbal callouts for…

Loading the flight search…