WPR23LA100 · Aeronca 65-CA
Aeronca 65-CA · Accident: ground collision while standing
Event
- NTSB case
- WPR23LA100
- 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
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
- N29447
- Operator
- Jones Cody
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- 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
- Standing · engine(s) start-up
- 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
- Ground collision
- 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 reported that, the airplane does not have an electrical system and needed to be hand propped to start the engine. There were no tire chocks or tie-down ropes on the ramp, so he asked an individual at the airport, whom he believed was a pilot and said that he had experience with assisting in hand propping an airplane. The pilot instructed the individual on the procedures and with the throttle set to 1/8 inch open, and the individual in the pilot’s seat, he then positioned himself in front of the airplane and spun the propeller. The engine started as expected and the engine immediately went to a high rpm setting. The airplane began forward movement under high rpm and speed and subsequently collided with a light pole and airport hangar after the individual in the cockpit could not stop the airplane. Both wings were substantially damaged. The pilot reported that after the collision, he found the throttle positioned to the full forward high rpm position instead of the idle position and that the individual reported that he went the wrong direction with the throttle. The pilot reported that there were no mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause
The occupant’s improper throttle movement during the start procedure, which resulted in forward movement and loss of airplane control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR23LA100
- Event ID
- 20230130106654
- Case number
- WPR23LA100
- 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, cause areas. Values present in the bulk record are kept.
- The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
- API snapshot SHA-256: d8d15098afb5d50d55c93595c40120b5065bb19272c54fe2960ca62a530a5274; retrieved 2026-09-16T17:17:37.693Z.