ATL92LA003 · Cessna 320
Cessna 320 · Accident: total loss of engine power (non-mechanical) on approach
From PFN · Panama City, FL to an unrecorded destination
Event
- NTSB case
- ATL92LA003
- 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 320
- Aircraft type
- Cessna 320
- 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
- N4726X
- Operator
- Barker, E. Gerry · private individual
- Onboard fatalities
- Unknown
- Route
- From PFN · Panama City, FLTo not recorded
- 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
- Approach
- 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)
- 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
- Fbo personnel › Maintenance, installation, improper
- Fuel system, electric boost pump › Inoperative
- Pilot in command › Procedures/directives, improper
- Throttle/power lever, push/pull rod › Starvation
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT WAS AWARE OF A PROBLEM WITH THE AIRCRAFT FUEL SYSTEM, SINCE FUEL FROM THE RIGHT MAIN TANK WOULD FEED QUICKER THAN FROM THE LEFT MAIN TANK. RATHER THAN HAVE THE A/C REPAIRED IN FLORIDA, HE ELECTED TO FLY THE A/C TO HIS HOME IN INDIANA TO HAVE THE REPAIRS DONE THERE. WHILE ON APPROACH TO A REFUELING STOP, HE REPORTED THAT BOTH ENGINES QUIT SIMULTANEOUSLY. A FORCED LANDING WAS MADE IN A NEARBY FIELD. THE INVESTIGATION REVEALED THAT THE LT TANK BOOST PUMP WAS INOP, AND THE FUEL SYSTEM CROSSFEED LINES WERE INCORRECTLY INSTALLED (NORMAL X-FEED WAS DISABLED). THUS, FUEL FROM THE RT, MAIN TANK WAS PRESSURE FED TO THE LT, MAIN TANK, AND THEN OVERBOARD, UNTIL THE RT TANK WAS EMPTIED, AND THE RT ENGINE QUIT. HOWEVER, FUEL WAS STILL AVAILABLE TO THE LT ENGINE. THEREFORE THE SAFETY BOARD BELIEVES THAT THE PILOT SELECTED X-FEED ON THE LT FUEL SELECTOR AFTER THE RT ENGINE QUIT; THIS SUBSEQUENTLY SHUT OFF FUEL TO THE LT ENGINE.
Probable cause
FUEL STARVATION DUE TO INCORRECT FUEL LINE INSTALLATIONS, AN INOPERATIVE FUEL BOOST PUMP, AND INCORRECT PILOT PROCEDURE. A FACTOR IN THIS ACCIDENT WAS THE PILOT'S INTENTIONAL OPERATION WITH A KNOWN FUEL SYSTEM DEFICIENCY.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL92LA003
- Event ID
- 20001212X18237
- Case number
- ATL92LA003
- 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: 0a408f6a9c78f4fa7667b2df0d057781afd4580b6b663ed200193e68b5c6da15; retrieved 2026-09-21T23:25:01.846Z.