BFO95LA029 · Piper PA-34-200T
Piper PA-34-200T · Accident: loss of engine power during initial climb
From Madison County Airport (UYF) to The Ohio State University Airport - Don Scott Field (OSU)
Event
- NTSB case
- BFO95LA029
- 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
- Instrument Meteorological Cond
Piper PA-34-200T
- Aircraft type
- Piper PA-34
- 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
- N2299M
- Operator
- Ronald L Mason · private individual
- Onboard fatalities
- Unknown
- Route
- From Madison County Airport (UYF), OHTo The Ohio State University Airport - Don Scott Field (OSU), Columbus, 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
- Initial climb
- 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 engine power
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- All engines
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT DEPARTED ON A DARK, FOGGY NIGHT TO REPOSITION THE AIRPLANE FOR AVIONICS WORK. THE AIRPLANE HAD JUST HAD FUEL FLOW TRANSDUCERS INSTALLED. ACCORDING TO THE PILOT, HE COMPLETED HIS PREFLIGHT INSPECTION AND ENGINE RUN-UPS SATISFACTORILY, BUT DURING THE CLIMB, ABOUT 150 FEET ABOVE THE GROUND THE LEFT ENGINE LOST POWER. SHORTLY THEREAFTER THE RIGHT ENGINE ALSO LOST POWER. THE AIRPLANE STRUCK TREES DURING THE SUBSEQUENT FORCED LANDING AND THE AIRPLANE WAS DESTROYED BY POSTIMPACT FIRE. POSTACCIDENT INSPECTION REVEALED NO EVIDENCE OF PREIMPACT MECHANICAL MALFUNCTION OF ENGINES OR FUEL TRANSDUCERS. THE ENGINES WERE TRANSPORTED TO A TEST FACILITY, WHERE THEY OPERATED SATISFACTORILY DURING A TEST RUN.
Probable cause
the loss of engine power (both engines, cause undetermined) shortly after lift off. Related factors are the foggy, dark night conditions, and the unsuitable terrain encountered during the subsequent forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO95LA029
- Event ID
- 20001207X03079
- Case number
- BFO95LA029
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1995-03-07.
- API snapshot SHA-256: 97caf9dbbbc0cd36dd5c27b427c136f57109977d148233502f9ab1b22f4367f3; retrieved 2026-09-21T22:22:16.276Z.