BFO93LA009 · Ryan NAVION
Ryan NAVION · Accident: total loss of engine power (mechanical failure) en route
From Pittsburgh/Butler Regional Airport (BTP) to 27J · NEWBURY, SC
Event
- NTSB case
- BFO93LA009
- 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
Ryan NAVION
- Aircraft type
- Ryan NAVION
- 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
- N4488K
- Operator
- Michael G. Quinlan · private individual
- Onboard fatalities
- Unknown
- Route
- From Pittsburgh/Butler Regional Airport (BTP), BUTLER CITY, PATo 27J · NEWBURY, SC
- 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
- En route · cruise
- 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
- Total loss of engine power (mechanical failure)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel starvation
- 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
- Fluid, fuel › Starvation
- Fuel system, fuel control › Output low
- Maintenance, adjustment › Improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
ACCORDING TO THE PILOT, THE ENGINE STOPPED RUNNING DURING CRUISE FLIGHT. FUEL WAS AVAILABLE, BUT THE ENGINE COULD NOT BE RESTARTED. DURING AN EMERGENCY WHEELS-UP LANDING ON ROUGH TERRAIN, THE AIRPLANE SLID INTO A TREE. EXAMINATION OF THE FUEL SYSTEM REVEALED THAT THE FUEL PRESSURE REGULATOR WAS ADJUSTED TO A MINIMUM PRESSURE SETTING. ABOUT 4 PSI OF FUEL PRESSURE WAS AVAILABLE; A MINIMUM OF 10 PSI WAS NEEDED FOR THE PRESSURE CARBURETOR TO OPERATE. WITH THE LINE FROM THE ENGINE DRIVEN FUEL PUMP TO THE FUEL PRESSURE REGULATOR BLOCKED (FOR A TEST), THE FUEL PRESSURE WOULD READ IN EXCESS OF 15 PSI. NO REASON WAS FOUND FOR THE IMPROPER ADJUSTMENT.
Probable cause
IMPROPER ADJUSTMENT OF THE FUEL PRESSURE REGULATOR WHICH PRODUCED AN INADEQUATE FUEL FLOW AND SUBSEQUENT FUEL STARVATION. FACTORS RELATED TO THE ACCIDENT WERE: THE ROUGH TERRAIN AND TREES IN THE EMERGENCY LANDING AREA.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO93LA009
- Event ID
- 20001211X15998
- Case number
- BFO93LA009
- 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: 2d465452748cdf48b18da3e4cf18bbd0098ffbbd1a64ee4679b2965045317ccc; retrieved 2026-09-21T14:38:07.467Z.