DCA19LA154
2019-06-04 · Manassas, Virginia, United States · None · 1 aircraft · Status: Completed
Airport KHEF
Aircraft involved
Probable cause & findings
a loss of hover lift thrust provided by the eight lift motors due to a false on-ground rotor speed reduction command, resulting from excessive vibration.
Factual narrative
HISTORY OF FLIGHT
On June 4, 2019, at 0709 eastern daylight time (EDT), an Aurora Flight Sciences Pegasus Passenger Air Vehicle (PAV) unmanned aircraft system, N83AU, crashed during landing on runway 34L at the Manassas Regional Airport, Manassas, VA. There were no injuries, and the aircraft was substantially damaged. The aircraft was operated as a developmental test flight under the provisions of 14 CFR part 91 and an FAA Certificate of Waiver or Authorization (COA). The aircraft was positioned on runway 34L for a vertical takeoff and landing, along with low speed maneuvering test. The aircraft took off normally and the pilot, who controlled the aircraft from a ground station in a building on the east side of the airport, entered pre-planned flight test stability check maneuvers, including brief lateral maneuvers followed by forward translations along the runway centerline in accordance with the test plan. The flight test engineers noted some brief data dropouts and abnormal motor speeds, and the team decided to terminate the flight. The pilot entered the autoland command, and the aircraft initially responded. After a small descent, the aircraft motors went to idle and the aircraft descended vertically at a high rate and impacted the runway, breaking the aft booms, the horizontal stabilizer, and other significant structure. The #3 motor exhibited a brief flash of fire or sparking on impact. The aircraft remained with the planned test area.
INJURIES TO PERSONS
None.
DAMAGE TO AIRCRAFT
There was structural damage to the booms, horizontal tail, vertical tails, and warping of the main aircraft structure. The aft section of the booms, with the two aft-most lift motors, were fractured.
PERSONNEL INFORMATION
The pilot, age 46, was an FAA certified commercial pilot airplane and helicopter, and reported 3,500 hours total time. The aircraft was also supported by a visual observer stationed nearby the runway, and a team of flight test engineers in the control station located in a building on the east side of the airport.
AIRCRAFT INFORMATION
The PAV is a developmental unmanned aircraft intended for Urban Air Mobility applications. The aircraft consists of a center fuselage which contains two (simulated) occupants, the main power battery, avionics and flight control computers, and an essential bus flight control battery. At the aft of the fuselage is an electric motor with pusher propeller for fixed-wing mode flight (this motor was disabled during the accident flight).The aircraft has a forward canard, main wing, and an aft mounted horizontal stabilizer with dual vertical stabilizers. A boom runs along each side containing 8 total vertical takeoff/landing (VTOL) electric motors. The aircraft was controlled from a ground control station located at the Manassas Airport, and linked to the aircraft via a 2.4gHz connection with two radio nodes. The normal landing maneuver for the PAV was an autoland, which establishes a vertical descent and transitions to on-ground mode using a combination of squat switches and a time derivative of acceleration known as "jerk" logic. When the aircraft contacts the ground and either the squat switches close or an acceleration spike is detected, the logic switches to ground mode and commands the VTOL motors to idle. The aircraft was equipped with a radar altimeter, but in this test configuration it was not used for ground detection in the autoland sequence.
METEOROLOGICAL INFORMATION
Weather was clear with calm wind.
COMMUNICATIONS
There were no communications difficulties with the accident flight.
AERODROME INFORMATION
The Manassas Regional Airport/Harry P. Davis Field (HEF), was located about 3 miles southwest of Manassas, Virginia, at an elevation of 192 feet mean sea level (msl). The airport has an FAA Air Traffic Control Tower which operates from 0630-2230 local time daily. The airport has two parallel runways 16L/34R, and 16R/34L (the accident runway). Runway 16R/34L had an asphalt surface 3,175 feet long and 100 feet wide. There were no reported abnormalities with the airport or facilities.
RECORDED DATA
A review of the recorded data was provided by the operator/manufacturer revealed that airframe vibration occurred in a resonant mode and was transmitted through the structure into the flight controller. The accelerations resulting from the vibrations briefly exceeded the jerk logic threshold and the aircraft entered the ground mode, subsequently commanding the motors to shutdown. The aircraft experienced a vibrational excitation environment which exceeded the previously measured accelerations used to establish an autopilot ground-sensing threshold. The excessive oscillations activated the ground-sensing system, which transitioned the autopilot from Autoland into "ground" mode and commanded a reduction in rotor speed. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Aircraft-Aircraft systems-Auto flight system-(general)-Malfunction - C
Verbatim from NTSB's published report. Source file
NTSB_2019_DCA19LA154.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (autopilot). All research papers
- arXiv 2025 · arXiv preprint ROSflight 2.0: Lean ROS 2-Based Autopilot for Unmanned Aerial Vehicles
ROSflight is a lean, open-source autopilot ecosystem for unmanned aerial vehicles (UAVs). Designed by researchers for researchers, it is built to lower the barrier to entry to UAV research and acceler…
- arXiv 2025 · arXiv preprint ROSplane 2.0: A Fixed-Wing Autopilot for Research
Unmanned aerial vehicle (UAV) research requires the integration of cutting-edge technology into existing autopilot frameworks.
- arXiv 2024 · arXiv preprint A Data-Driven Autopilot for Fixed-Wing Aircraft Based on Model Predictive Control
Autopilots for fixed-wing aircraft are typically designed based on linearized aerodynamic models consisting of stability and control derivatives obtained from wind-tunnel testing.
- arXiv 2022 · arXiv preprint Experimental Flight Testing of a Fault-Tolerant Adaptive Autopilot for Fixed-Wing Aircraft
This paper presents an adaptive autopilot for fixed-wing aircraft and compares its performance with a fixed-gain autopilot.
- arXiv 2021 · arXiv preprint An Adaptive Digital Autopilot for Fixed-Wing Aircraft with Actuator Faults
This paper develops an adaptive digital autopilot for a fixed-wing aircraft and compares its performance with a fixed-gain autopilot.
- arXiv 2026 · arXiv preprint Enabling Beyond-Visual-Line-of-Sight Drones Operation over Open RAN 5G Networks with Slicing
Among the foretold claims of the transition from 5G to 6G, Beyond-Visual-Line-of-Sight (BVLoS) drone operation has emerged as a prominent Internet-of-Robots enabler.