FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA15FA088 · Piper PA34 200T

2 Jan 2015 · Kuttawa, KY, United States

Fro-Gutz Air Piper PA34 200T · Accident: fuel starvation en route

From Tallahassee International Airport (TLH) to Mount Vernon Outland Airport (MVN)

Report a problem

Event

NTSB case
ERA15FA088
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
4 · all aircraft and ground
Ground fatalities
Unknown
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 PA34 200T

Aircraft type
Piper PA34
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
N81291
Operator
Fro-Gutz Air
Onboard fatalities
Unknown
Route
From Tallahassee International Airport (TLH), Tallahassee, FLTo Mount Vernon Outland Airport (MVN), Mount Vernon, IL
Aircraft age
About 36 years (built 1979)
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
Defining eventThe 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
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

  • Aircraft › Aircraft systems
  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The commercial pilot departed on a cross-country flight in night instrument meteorological conditions with the airplane's fuel tanks full, providing an estimated fuel endurance of 4 hours 50 minutes. Two hours 50 minutes into the flight, the pilot reported a loss of engine power on the right engine, which was followed by a loss of engine power on the left engine. The pilot attempted to land at a nearby airport; however, the airplane impacted trees about 8 miles short of the airport. A review of weather information revealed no evidence of in-flight icing or other weather conditions that may have contributed to the accident.

Postaccident examination of the airframe and engines revealed no preimpact failures or malfunctions that would have precluded normal operation. All fuel tanks were compromised; however, an undetermined amount of fuel spilled from the left fuel tank during recovery of the wreckage. The left engine fuel selector valve was found in the "X-FEED" (crossfeed) position, and the corresponding cockpit fuel selector switch was found in an intermediate position, which was likely the result of impact damage. The right engine fuel selector valve and the corresponding cockpit fuel selector switch were found in the "ON" position. With the valves in these positions, both the left and right engines would have consumed fuel from the right fuel tank. Review of performance charts and fueling records indicated that if the flight was conducted with the valves in the as-found positions, exhaustion of the fuel in the airplane's right fuel tank would have occurred about the time the pilot reported the dual engine failure. In addition, the yaw trim was found in the full nose-right position. It is possible that the pilot used nose-right yaw trim to counteract an increasing left-turning tendency during the flight as fuel was burned from only the right wing's fuel tank making it relatively lighter than the left wing.

According to the expanded checklist in the pilot's operating handbook for the airplane, during taxi, the pilot was to move each fuel selector to "X-FEED" for a short time, while the other selector was in the "ON" position, before returning both fuel selectors to the "ON" position before takeoff. According to a checklist found in the airplane, the fuel selectors were to be set to "X-FEED" during taxi and then to "ON" during engine run up. GPS data recovered from onboard devices indicated that the pilot taxied from the ramp and onto the active runway without stopping in about 3 minutes, indicating that it is unlikely he performed a complete run up of both engines before takeoff. He likely failed to return the left engine fuel selector from the "X-FEED" to the "ON" position, where it remained throughout the flight and resulted in fuel starvation and a loss of engine power on both engines.

Toxicological testing revealed that the pilot was taking citalopram (an antidepressant) and rosuvastatin (a statin); however, it is unlikely these drugs contributed to the accident. Review of medical and pathological information revealed no evidence of any medical condition that may have contributed to the accident.

Probable cause

The pilot's failure to properly set the left engine fuel selector before takeoff and to recognize the incorrect setting during the flight, which resulted in fuel starvation and a loss of engine power on both engines.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA15FA088
Event ID
20150103X93856
Case number
ERA15FA088
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 7092e343c5b23f4cef5353196a593c7fe2f124045f4a50aec577c2c5cbfca61f; retrieved 2026-09-14T17:30:34.788Z.