GAA17CA055 · Diamond Aircraft IND Inc DA 20 C1
Diamond Aircraft IND Inc DA 20 C1 · Accident: abnormal runway contact during landing
From Charlottesville Albemarle Airport (CHO) to Washington Manassas Harry P. Davis Field (HEF)
Event
- NTSB case
- GAA17CA055
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Diamond Aircraft IND Inc DA 20 C1
- Aircraft type
- Diamond DA-20
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N781MA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Charlottesville Albemarle Airport (CHO), Charlottesville, VATo Washington Manassas Harry P. Davis Field (HEF), Bristow, VA
- Aircraft age
- About 12 years (built 2004)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Abnormal runway contact
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, after multiple previous landings that night to runway 34L, the airplane was thrown "off course" after it encountered a crosswind. The pilot pulled the power off briefly during the landing, and the airplane touched down. However, he reported that he made a late decision to go around and reapplied the power to establish a climb. He added that the airplane was "off course" at a low airspeed and that he applied full power, but he panicked and reduced his right rudder application, and the airplane veered to the left. The airplane stalled and impacted the ground, the nose landing gear became embedded in the mud, and the airplane nosed over and came to rest inverted. The airplane sustained substantial damage to the left wing root and empennage.
According to the airport security camera video, the airplane descended over runway 34L and made an immediate sharp left 270° turn to the left of the runway heading and rapidly ascended. After the sharp left turn, the airplane was airborne for about 534 ft before impacting the ground and nosing over.
White paint transfer markings observed on the runway surface and damage to the airplane's left wing indicated that the airplane had impacted the runway surface during the accident sequence.
About 25 minutes before the accident, the published METAR for the accident airport reported that the wind was from 320° at 6 knots. There were no reported wind gusts at the time of the accident, and there were no published wind gusts at the airport for the remainder of the day.
The pilot reported that he had 99 hours of total flight time, 78 hours of which were in the accident airplane make and model, and 4 hours of which were within the 90 days before the accident.
The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot’s loss of directional control during a landing attempt at night, which resulted in a delayed go-around procedure and subsequent impact with terrain. Contributing to the accident was the pilot’s lack of recent flight experience.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA17CA055
- Event ID
- 20160726X83922
- Case number
- GAA17CA055
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2016-10-31.
- API snapshot SHA-256: b28bb9744a93bcd803be00ba8e9b4d160df22d784e9c1a62e702bdca6fe74751; retrieved 2026-09-16T03:42:17.540Z.