BFO92LA136 · Piper PA-44-180T
P.C. Flyers Piper PA-44-180T · Accident: total loss of engine power (non-mechanical) en route
From MKC · Kansas City, KS to Louisville Muhammad Ali International Airport (SDF)
Event
- NTSB case
- BFO92LA136
- 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-44-180T
- Aircraft type
- Piper PA-44
- 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
- N83628
- Operator
- P.C. Flyers
- Onboard fatalities
- Unknown
- Route
- From MKC · Kansas City, KSTo Louisville Muhammad Ali International Airport (SDF), Louisville, KY
- 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 · descent
- 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 (non-mechanical)
- 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 exhaustion
- 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 › Exhaustion
- Pilot in command › In-flight planning/decision, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT WAS DESCENDING THROUGH 4000 FEET EN ROUTE TO HIS DESTINATION WHICH WAS 75 MILES AWAY WHEN THE LEFT ENGINE LOST POWER. THE PILOT STATED THAT HE FOLLOWED THE EMERGENCY CHECK LIST AND POWER WAS RESTORED; HOWEVER, SHORTLY THEREAFTER BOTH ENGINES LOST POWER. THE PILOT RADIOED HIS DESTINATION APPROACH CONTROL THAT HE HAD A SICK PASSENGER ON BOARD, AND ASKED FOR THE CLOSEST AIRPORT. HE WAS PROVIDED VECTORS TO AN AIRPORT 10 MILES AWAY, BUT DECIDED TO MAKE A FORCED LANDING IN A FIELD AS HE STATED THAT HE WAS LOW ON FUEL. ACCORDING TO THE FAA, A VISUAL INSPECTION OF BOTH NACELLE FUEL TANKS DISCLOSED NO EVIDENCE OF FUEL, AND NO NOTICEABLE FUEL VAPORS WERE PRESENT. THE EXAMINATION ALSO REVEALED THAT THE TANKS WERE NOT RUPTURED OR DAMAGED. THE PILOT REPORTED THAT THERE WAS NO MECHANICAL MALFUNCTION, NOR COULD THE BASIS FOR THE REPORT OF THE SICK PASSENGER BE ESTABLISHED.
Probable cause
THE PILOT'S IN-FLIGHT PLANNING/DECISION WHICH RESULTED IN FUEL EXHAUSTION.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO92LA136
- Event ID
- 20001211X15621
- Case number
- BFO92LA136
- 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: 593a6bbc8963c5e3c3d1fd22a74f2ebafbc2d0b94b8969bfcc3f7ccd4a7f79a1; retrieved 2026-09-23T02:39:12.601Z.