BFO86LA045 · Piper PA-28-181
Piper PA-28-181 · Accident: total loss of engine power (non-mechanical) en route
From Cape Fear Regional Jetport / Howie Franklin Field Airport (SUT) to W22 · Woodbridge, VA
Event
- NTSB case
- BFO86LA045
- 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-28-181
- Aircraft type
- Piper PA-28
- 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
- N4350K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cape Fear Regional Jetport / Howie Franklin Field Airport (SUT), Southport, NCTo W22 · Woodbridge, VA
- 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 (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 › Fuel supply, inadequate
- Pilot in command › In-flight planning/decision, improper
Approximate · Estimated position: the centre of Fredericksburg, VA, the place the record names. Not the accident site.
NTSB narrative
THE ACFT NOSED OVER DRG A FORCED LNDG FOLLOWING A TOTAL LOSS OF PWR DUE TO FUEL EXHAUSTION. THE PLT RPRTD THAT BOTH HE &THE PASSENGERS VISUALLY CHECKED THE FUEL TANKS PRIOR TO DEPARTURE TO VERIFY THAT THEY WERE FULL OF FUEL. THE PWR LOSS OCCURRED APRX 25 MI FROM THE DESTN. THE PLT SWITCHED FUEL TANKS & WAS ABLE TO RESTART THE ENG WHICH OPERATED FOR 2 TO 3 MIN BEFORE QUITTING AGAIN. THE ACFT CLEARED PWR LINES DRG THE FORCED LNDG APCH; HOWEVER, IT TOUCHED DOWN HARD ON ROUGH GROUND & NOSED OVER WHILE ROLLING ON UPHILL TERRAIN. THE PLT RPRTD THE EN ROUTE FLT TIME WAS 1 HR & 35 MIN; HOWEVER, A POLICE RPRT INDICATED A TIME OF AT LEAST 3 HRS & 5 MIN. FUEL CONSUMPITON DRG A 2.5 HR FLT ON THE PREVIOUS DAY WAS APRX 11 GPH. NO EVIDENCE OF FUEL SPILLAGE WAS FOUND AT THE ACDNT SITE. THE ACFT WAS CHECKED FOR FUEL LEAKS & NONE WERE FOUND. THE PLT STATED THE FUEL QUANTITY INDICATORS WERE INACCURATE; HOWEVER, THEY WERE ACCURATE DRG A POST ACDNT EXAM.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record BFO86LA045
- Event ID
- 20001213X34728
- Case number
- BFO86LA045
- 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: 4094641bf509e44437cabac0861382dcf123503353424b20e452e3c8378b42ae; retrieved 2026-09-22T01:13:46.579Z.