CEN17FA067 · Demmer BD-4
Demmer BD-4 · Accident: loss of control on ground during takeoff
From Capitol Drive Airport (02C) to New River Valley Airport (PSK)
Event
- NTSB case
- CEN17FA067
- 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
- 1 · 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
Demmer BD-4
- Aircraft type
- Demmer BD-4
- 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
- N311SD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Capitol Drive Airport (02C), Brookfield, WITo New River Valley Airport (PSK), Dublin, VA
- Aircraft age
- About 15 years (built 2002)
- 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
- Takeoff
- 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
- Loss of control on ground
- 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
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot was departing from runway 21 for a cross-country flight; the windsock indicated a 15 kt or greater right crosswind. A nearby weather station reported wind from 280° at 20 kts gusting to 28 kts about the time of the accident. The rear seat passenger reported that, during the takeoff roll, the airplane became airborne twice and the pilot applied right rudder to return to the runway centerline. The airplane then continued left over the grass next to the runway and travelled several hundred feet before impacting a sport utility vehicle (SUV) parked in an aircraft tie-down area about 250 ft from the runway 21 centerline. The passenger reported that, before impact, the pilot was "vigorously pumping the rudders back and forth (left and right)." A witness reported that he could not see the airplane when it started its takeoff, but when it came into view, the airplane appeared to be "having difficulty." The nose was slightly up, and the right wing was down, and the tail was "oscillating." Examination of the accident site revealed skid marks on the runway and tire tracks in the grass leading to the main wreckage. The total distance from the beginning of the skid marks on the runway to the SUV was 953 ft. The skid marks showed that the airplane veered to the left, departed the runway, and momentarily became airborne twice before settling back to the ground, then continuing another 262 ft to impact the SUV.
A postaccident examination of the airplane revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. Given the lack of mechanical anomalies and the wind conditions present at the time of the takeoff, the accident is consistent with a loss of control during takeoff in crosswind conditions.
Probable cause
The pilot's failure to abort the takeoff when he was not able to maintain directional control in the strong crosswind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17FA067
- Event ID
- 20170105X81632
- Case number
- CEN17FA067
- 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: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: c74af1b2ac3068a4fa18ec6aebd8f728d37c17e71fe3eafba5f15b2f42b8a325; retrieved 2026-09-14T22:05:42.288Z.