BFO96LA024 · Cessna 210J
Cessna 210J · Accident while standing
From 7I7 to James M. Cox Dayton International Airport (DAY)
Event
- NTSB case
- BFO96LA024
- 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
Cessna 210J
- Aircraft type
- Cessna 210
- 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
- N3328S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 7I7To James M. Cox Dayton International Airport (DAY), Dayton, 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
- Miscellaneous/other
- 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 › Starting procedure, inadvertent activation
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT TRIED TO START THE AIRPLANE ENGINE 4 OR 5 TIMES WITHOUT SUCCESS. HE REPORTED THAT THE AIRPLANE'S BATTERY WAS WEAK DUE TO INFREQUENT USE, AND HE DECIDED TO TURN OFF THE IGNITION AND ROTATE THE PROPELLER THROUGH BY HAND. ALSO, HE STATED THAT HE WAS SURPRISED WHEN THE ENGINE STARTED AS HE ROTATED THE PROPELLER BY HAND. THE AIRPLANE MOVED ACROSS THE RAMP AND COLLIDED WITH A PARKED AIRPLANE AND A HANGAR. POSTACCIDENT EXAMINATION REVEALED THAT THE KEY WAS STILL IN THE IGNITION, AND THE IGNITION WAS IN THE RIGHT MAGNETO-ONLY POSITION. NO AIRCRAFT SYSTEM MALFUNCTION/ANOMALY WAS FOUND.
Probable cause
THE PILOT UNKNOWNLY LEFT THE IGNITION SWITCH IN RIGHT MAGNETO-ONLY POSITION, WHILE MOVING THE PROPELLER BY HAND, WHICH ALLOWED AN INADVERTENT START OF THE ENGINE. THE WEAK BATTERY WAS A RELATED FACTOR.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO96LA024
- Event ID
- 20001207X04816
- Case number
- BFO96LA024
- 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: 5918bd860c3e60c3286f3f49b6476c2a4a0123f87f47ceec483e88ea44336694; retrieved 2026-09-22T23:01:40.084Z.