ERA16CA264 · Aeronca 7BCM
Aeronca 7BCM · Accident: aircraft/propeller/rotor contact with person while standing
From Joseph A. Hardy Connellsville Airport (VVS) to Joseph A. Hardy Connellsville Airport (VVS)
Event
- NTSB case
- ERA16CA264
- 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
- 0
- 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 7BCM
- Aircraft type
- Aeronca 7
- 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
- N1639E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Joseph A. Hardy Connellsville Airport (VVS), Connellsville, PATo Joseph A. Hardy Connellsville Airport (VVS), Connellsville, PA
- Aircraft age
- About 70 years (built 1946)
- 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
- 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
- Substantial
Cause areas
- Aircraft › Aircraft handling/service
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that he hand-propped the engine, boarded the airplane, and began to taxi and that, shortly thereafter, the engine "sputtered and stalled." He then realized that he had left the fuel selector in the "off" position. He set the parking brake, turned the fuel on, exited the airplane, and hand-propped the engine again. The engine started and ran at a high rpm. The airplane moved forward and began to spin in circles. The pilot attempted to get back in the cockpit; however, the door had swung closed, and the airplane struck him, knocking him to the ground. The airplane spun a few more times before striking a hangar, which resulted in substantial damage to the right wing, and coming to a stop. Afterward, the pilot recalled that he had forgotten to retard the throttle before attempting the second engine start. The airplane was not equipped with an electric starter.
Probable cause
The pilot's failure to properly set the throttle and secure the airplane before hand-propping the engine for startup.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA16CA264
- Event ID
- 20160721X24536
- Case number
- ERA16CA264
- 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: 7a5ff2c7b3b8df92fadc3aa97dbe074ca02773dda284e4a7ab38c18207b6fd2f; retrieved 2026-09-16T03:40:54.947Z.