CEN10CA569 · Central Ohio Dragonfly Clubllc DRAGONFLY-C
Central Ohio Dragonfly Clubllc DRAGONFLY-C · Accident: flight control system malfunction/failure during takeoff
From Orient, OH (private airstrip) to Orient, OH (private airstrip)
Event
- NTSB case
- CEN10CA569
- 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
Central Ohio Dragonfly Clubllc DRAGONFLY-C
- Aircraft type
- Central Ohio Dragonfly Clubllc DRAGONFLY-C
- 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
- N667DF
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Orient, OH (private airstrip)To Orient, OH (private airstrip)
- Aircraft age
- Not recorded
- 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
- Flight control system malfunction/failure
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot planned for a short local flight with a passenger between his continuous aero-tow operations. In an effort to expedite the quick passenger flight, the pilot disconnected the tow line; however, he left the V-Bridal line attached to the rudder post of the airplane. The pilot had conducted previous flights in the same configuration without incident. During taxi, the pilot turned the airplane 180 degrees to position it for an upwind takeoff. Shortly after rotation, the pilot experienced an uncommanded right turn. He attempted to counteract the turn to no avail. The airplane impacted terrain with the right wing and right main landing gear. Examination of the airplane by the pilot and a Federal Aviation Administration inspector revealed the V-Bridal line became entangled in the rudder and tailwheel during the takeoff.
Probable cause
The pilot's failure to disconnect the tow bridal line prior to takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10CA569
- Event ID
- 20100928X11225
- Case number
- CEN10CA569
- 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. 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: 37cae64bd2052de1b9630fd3fb8e7d05deb41471139affc9c56e1d73addf91f1; retrieved 2026-09-15T15:23:08.147Z.