BFO92LA068 · Piper PA-24-180
Piper PA-24-180 · Accident: loss of control on ground/water while standing
From IG8 · Toronto, OH to Carroll County-Tolson Airport (TSO)
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- BFO92LA068
- 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
Piper PA-24-180 Possible conflict
- Aircraft type
- Piper PA-24
- 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
- N6105P
- Operator
- William Oliver Carman
- Onboard fatalities
- Unknown
- Route
- From IG8 · Toronto, OHTo Carroll County-Tolson Airport (TSO), TOLSON, OH
- 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
- First occurrenceThe 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/water
- 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
- Pilot in command › Aircraft unattended/engine(s) running, inadequate
- Pilot in command › Starting procedure, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT ATTEMPTED TO HAND PROP THE ENGINE WITH HIS WIFE, A NON-PILOT, IN THE RIGHT FRONT SEAT. HE STATED THAT HE 'SET THE PARK BRAKE' AND EXITED THE AIRPLANE. AFTER THE THIRD ATTEMPT THE AIRPLANE STARTED. THE PILOT TRIED TO STOP THE AIRPLANE BY PUSHING AGAINST THE LEADING EDGE OF THE RIGHT WING, BUT HE WAS UNSUCCESSFUL. THE AIRPLANE ACCELERATED ACROSS THE RAMP WHERE IT COLLIDED WITH ANOTHER PIPER AIRPLANE WHICH STRUCK A CESSNA 172. ACCORDING TO THE FAA FLIGHT TRAINING HANDBOOK, IT IS RECOMMENDED THAT AN ENGINE NEVER BE 'HAND PROPPED'UNLESS A QUALIFIED PERSON THOROUGHLY FAMILIAR WITH THE OPERATION OF ALL THE CONTROLS IS SEATED AT THE CONTROLS AND THE BRAKES ARE SET.
Probable cause
THE PILOT'S INADEQUATE STARTING PROCEDURE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO92LA068
- Event ID
- 20001211X14593
- Case number
- BFO92LA068
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 43a5b390f034901ab3b94e28de185f673241e1fe3d9e5f23665beec97398cf25; retrieved 2026-09-23T03:08:46.500Z.