# NTSB DCA19LA154: Aurora PAV, N83AU, Manassas, VA, June 4, 2019 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: June 4, 2019, 07:19 local (11:19 UTC) - Place: Manassas, VA - Coordinates: 38.721942, -77.517776 - Nearby events: https://openairdocs.org/map.md?lat=38.7219&lon=-77.5178&mi=10 - Phase of flight: [Uncontrolled descent](https://openairdocs.org/ntsb-phases/650) (OpenAirDocs' grouping) - Defining event: [Uncontrolled descent: Flight control sys malf/fail](https://openairdocs.org/ntsb-events/333) - Highest injury: No injuries - Status: Completed, report March 13, 2020 - Report: Approved by Office Director - NTSB office: Major Investigations Division - NTSB case key (mKey): 99537 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=DCA19LA154 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/99537/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=99537 - Page: https://openairdocs.org/ntsb/DCA19LA154 ## Probable cause 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. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Auto flight system](https://openairdocs.org/ntsb-findings/01022200): Aircraft › Aircraft systems · Malfunction (probable cause); cases with it: [All aircraft, 8 cases](https://openairdocs.org/ntsb-findings/01022200/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Uncontrolled descent: Flight control sys malf/fail](https://openairdocs.org/ntsb-events/333) (defining event); cases with it: [All aircraft, 410 cases](https://openairdocs.org/ntsb-events/333/sequence.md) ## Analysis 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. ## 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 toon-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. ## Aircraft - Registration: N83AU (not matched to a registry record) - Reported make and model: AURORA PAV - Category: Helicopter, unmanned - Serial number: 1 - Engines: Magicall electric; Magicall electric; Magicall electric; Magicall electric; Magicall electric; Magicall electric; Magicall electric; Magicall electric; Magicall electric - Damage: Substantial damage - Flight: Flight test, Part 91 - Operator: Aurora Flight Sciences - Registered owner: Aurora Flight Sciences - Airworthiness certificate: Special, Experimental (Special) - Departed: KHEF, Manassas, VA - Destination: KHEF, Manassas, VA - Airport: KHEF, Manassas, runway 34L, 3,500 × 100 ft, asphalt - Equipment: Data recorder, Auto-pilot ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Temperature: 46 °F, dew point 45 °F - Altimeter: 30.19 inHg - Observed at: KHEF ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20190604024389A](https://openairdocs.org/incident/20190604024389A), Jun 4, 2019: Aurora Flight Sciences Corp PEGASUS, Manassas, VA, Substantial damage. Registration: N83AU Make: Aurora Flight Sciences Corp Model: Pegasus Serial number: AU-083 Remote pilot certificate number: [privacy data omitted] Frequency… ## Docket (3 files) The files NTSB released with the investigation on October 1, 2019, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=99537. 2.5 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 2.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40476349&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Report from Party (item 2, .PDF, 358 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40476350&FileExtension=.PDF&FileName=Report%20from%20Party-Master.PDF - Party Form (item 3, .PDF, 73 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40476351&FileExtension=.PDF&FileName=Party%20Form-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.