# Accident 20161002019799A: Volaircraft 10A, Mandan, ND, October 2, 2016

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 2, 2016, 15:57 local time
- Place: Mandan, ND
- Airport: Mandan Municipal
- Damage: Destroyed
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 46.8806° N, 100.9944° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=46.8806&lon=-100.9944&mi=10
- Aircraft: N6666D, a cancelled registration (https://openairdocs.org/deregistered/N6666D-2018-04-19) (OpenAirDocs)
- Registry model: Volaircraft 10A (registry code 9550104, https://openairdocs.org/model/volaircraft-10a) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: VOLAIRCRAFT 10A
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Student
- NTSB investigation: [NTSB CEN17LA004](https://openairdocs.org/ntsb/CEN17LA004) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20161002019799A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

PILOT TOUCHED DOWN SHORT OF RUNWAY 13. IMPACT CAUSED NOSE GEAR STRUT TO DEPART AIRCRAFT. AIRCRAFT SLID 492 FEET DOWN THE RUNWAY.  GASCULATOR/FUEL DRAIN WAS RUPTURED DURING SLIDE AND IGNITED.  AIRCRAFT WAS CONSUMED BY POST CRASH FIRE.  PILOT ESCAPED WITHOUT INJURY.

## The NTSB's investigation of this event (1)

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.

- [NTSB CEN17LA004](https://openairdocs.org/ntsb/CEN17LA004), Oct 2, 2016: Volaircraft 10A (N6666D), Mandan, ND, destroyed. Probable cause: The student pilot’s failure to maintain the proper approach path on landing, which resulted in impact with terrain short of the runway.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.