ERA22LA037 · Piper PA-30
Piper PA-30 · Accident: fuel exhaustion en route
From Music City Executive Airport (XNX) to an unrecorded destination
Event
- NTSB case
- ERA22LA037
- 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
- Event fatalities
- Unknown
- 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 PA-30
- Aircraft type
- Piper PA-30
- 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
- N30SH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Music City Executive Airport (XNX), Gallatin, TNTo not recorded
- Aircraft age
- About 55 years (built 1966)
- 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
- 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 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot departed on a cross-county flight in his twin-engine airplane and set the fuel selector to the auxiliary tanks. About 7-10 minutes into the flight, the auxiliary tanks ran out of fuel and the pilot switched the fuel selector handles to the main tanks, which the fuel gauge indicated were a ¼-full. The pilot then decided to land and purchase fuel. When the airplane was on a four-mile final approach to the diversion airport, the left engine stopped producing power. About 30 seconds later, the right engine stopped producing power. The pilot was unable to maintain altitude and made a forced landing to a field. The airplane struck a hay bale, which resulted in substantial damage to the fuselage and wings. Postaccident examination of the airplane revealed six fuel tanks were intact and empty of fuel. A fuel line fitting to the right auxiliary tank was observed to be loose, stained blue/green, and most likely had been actively leaking fuel. The amount of fuel lost due to this leak could be not determined. The airplane was equipped with three fuel tanks (main, auxiliary and tip tank) in each wing, for a total of 120 gallons total (114 useable). Each tank was independent of each other, so the leak in the right auxiliary fuel tank would have only affected the fuel level in that tank. The pilot reported there was about 55 gallons of fuel onboard when he departed, and the airplane consumed an average of 15 gallons per hour. Based on this information, if the right auxiliary tank (15 gallons total) was empty due to the leak, there still should have been about 40 gallons of fuel onboard (or about 2.6 hours of fuel). The pilot said that he did not visually check the fuel quantity prior to flight because the airplane “…does not have a way to visually check the fuel and know how much fuel you have in the tanks.” However, the Pilot Operating Handbook states, that the pilot should visually check the fuel supply in each tank before flight. As such, even though the pilot thought he had sufficient fuel to complete his flight, postaccident examination of the airplane revealed the fuel tanks were not breached and empty of fuel. A loose fuel line fitting in the right auxiliary fuel tank likely contributed to some unquantifiable loss of fuel from that tank. Had the pilot used the preflight checklist, and visually looked in all six fuel tanks, he would have seen that there was insufficient fuel in all of the tanks to complete the flight. As a result, both engines lost total power due to fuel exhaustion 20 minutes after takeoff, which resulted in a forced landing to field.
Probable cause
The pilot’s improper pre-flight fuel planning, which resulted in a total loss of engine power to both engines due to fuel exhaustion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22LA037
- Event ID
- 20211101104185
- Case number
- ERA22LA037
- 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: ff25869e4b4d037f224ddc2e86eabebf798df0fb4d92646e58d6b3ae4f9664a8; retrieved 2026-09-16T14:42:37.928Z.