FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA09CA018 · Piper PA-28-140

14 Oct 2008 · Repton, AL, United States

Piper PA-28-140 · Accident: fuel exhaustion en route

From Jackson Municipal Airport (4R3) to Monroe County Aeroplex Airport (KMVC)

Report a problem

Event

NTSB case
ERA09CA018
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
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
Visual Meteorological Cond

Piper PA-28-140

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
N7314J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Jackson Municipal Airport (4R3), Jackson, ALTo Monroe County Aeroplex Airport (KMVC), Monroeville, AL
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
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

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

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

NTSB narrative

The pilot and his passenger were performing aerial observations, checking paper mill inventories. After approximately three hours of flying, they made an intermediate stop. No attempt was made to purchase fuel at the airport. During the return leg, the left fuel gauge read zero, so the pilot switched to the right tank. The engine began to lose power when the right tank read zero. The pilot switched back to the left tank and was able to restore power for about two more minutes, then the engine quit again. Unable to restore power, he made a forced landing in a wooded area. The airplane collided with trees and came to rest inverted. An A and P mechanic who recovered the wreckage reported that there was no fuel in the tanks and no evidence of fuel leakage on the ground.

Probable cause

Fuel exhaustion due to the pilot's inadequate preflight planning.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA09CA018
Event ID
20081015X70300
Case number
ERA09CA018
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: 4db7b73ff6a05486f10e3bda7f70e08deebac5faf5df1bb6a9955eeb3111ec71; retrieved 2026-09-15T10:28:17.247Z.