CEN17LA234 · Aeronca 65 CA
Aeronca 65 CA · Accident: aircraft/propeller/rotor contact with person before flight
From Wynkoop Airport (6G4) to an unrecorded destination
Event
- NTSB case
- CEN17LA234
- 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
Aeronca 65 CA
- Aircraft type
- Aeronca 65
- 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
- N33778
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Wynkoop Airport (6G4), Mount Vernon, OHTo not recorded
- Aircraft age
- About 76 years (built 1941)
- 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
- Prior to flight
- 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
- Aircraft/propeller/rotor contact with person
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Aircraft › Aircraft power plant
- 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 prepared to hand-prop the airplane, which was not equipped with an electrical starter, by tying the tail down with a nylon rope. The pilot then hand-propped the engine, which started at a high power setting. The airplane moved forward, breaking the rope, and continued to taxi in circles. The pilot and another individual tried to stop the airplane; however, the propeller struck the pilot, resulting in fatal injuries. The airplane eventually came to stop farther down the runway. Although the pilot attempted to secure the airplane by tying down the tail, the throttle was set at a high engine power setting, allowing the airplane's movement.
Probable cause
The pilot's improper starting procedure before hand propping the engine, and his subsequent attempt to stop the moving airplane, which resulted in him being struck by the propeller.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17LA234
- Event ID
- 20170619X92534
- Case number
- CEN17LA234
- 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: 7a94afc0b1dcb47fcc9804e018a8865456717dec049457e9088270599782c037; retrieved 2026-09-15T06:04:36.398Z.