The U.S. aircraft register, updated daily
Accidents · NTSB DCA18IA269 · Final report

DJI Phantom incident near Blacksburg, Virginia, August 14, 2018

On August 14, 2018 at about 5:30 pm local time, a DJI Phantom (helicopter), registered FA3HCWCR4X, suffered minor damage in an incident during landing near Blacksburg, Virginia. It was flown under small-drone rules (Part 107). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

the drone pilot's incorrect control inputs due to insufficient knowledge of the aircraft flight manual procedures. Contributing to the incident was the close proximity of the observers, and the decision to conduct a demonstration near the observers in a confined area with no assistance.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
August 14, 2018 · about 5:30 pm local time
Place
Blacksburg, Virginia · map
Type
Incident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
DJI Phantom 4
Registration
FA3HCWCR4X · no longer on the register · serial unk
Damage
Minor damage
Flight
Flight · small-drone rules (Part 107)

The NTSB's narrative final · quoted from the NTSB record

The sUAS was operating under the provisions of Part 107 within Class G airspace. The pilot was appropriately certificated for the flight. Examination of the drone data logs revealed no anomalies with the aircraft or software. The drone responded to control inputs as expected. The pilot erroneously believed that the "down and in" CSC input would result in a landing or in-flight shutdown of the motors. The Phantom 4 user manual specifies that the "down and in" CSC shuts down the motors only when the drone is on the ground. Inputting that command in flight would result in the drone yawing right, pitching backward, and banking left. Logs indicated that the drone maneuvered consistently with the stick inputs. Further, the pilot indicated the drone would not land. Logs indicate that he used the Autoland feature, which scans the landing surface with optical sensors (Visual Positioning System or VPS) to determine if the surface is suitable. Logs indicate the VPS did not calculate a suitable landing surface. This is consistent with the pilot's report of trying to land on a plastic table, which likely created excessive reflections. In order to conduct a normal landing, the pilot would need to switch out of Autoland, or override it by holding the throttle (left stick) fully back for 2 seconds. Logs indicate the aircraft remained in Autoland mode, and the stick was not pulled fully back for more than ½ second at any time. The demonstration flight was conducted in a small area, confined by trees, and within close proximity of the observers, 10 feet or less according to witness statements. Although there is no evidence that the pilot flew directly over unprotected persons, or purposely in a hazardous manner, at the time that he perceived a problem with the drone and decided to crash it, the close proximity to the observers should have been accounted for either by warning them to clear away, having an assistant do the same, or to conduct the forced landing in an area clear of the observers. At the time of the incident, the university and CMI did not have any documented procedure for conducting such demonstrations. Although not required by regulation, the incident pilot did not have any documented aircraft-specific training that might have included the flight manual procedures noted above.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of control in flight during landing defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › Action › Incorrect action selection › Pilot
  • factor Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • factor Environmental issues › Physical environment › Object/animal/substance › Person › Decision related to condition
  • Organizational issues › Support/oversight/monitoring › Training › Initial training › Other institution/organization

The aircraft

  • Maximum gross weight: 4 lb
  • Seats: 0
  • Landing gear: fixed

The flight

  • Departed from: Blacksburg VA
  • Destination: Blacksburg VA
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Temperature: 0°F (-18°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

4 documents, released by the NTSB on August 26, 2019. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 11 pages View Download
2 Data Logs zip file Download
3 Data Log Plots PDF, 12 pages View Download
4 Vt UAS Policy 5820 PDF, 5 pages View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.