FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL96FA022 · Piper PA-46-310P

14 Dec 1995 · Greenwood, SC, United States

Epps Aviation Piper PA-46-310P · Accident: total loss of engine power (non-mechanical) en route

From Charlotte Douglas International Airport (CLT) to DeKalb Peachtree Airport (PDK)

Report a problem

Event

NTSB case
ATL96FA022
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
1 · 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-46-310P

Aircraft type
Piper PA-46
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
N9102V
Onboard fatalities
Unknown
Route
From Charlotte Douglas International Airport (CLT), Charlotte, NCTo DeKalb Peachtree Airport (PDK), Chamblee, GA
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
Wire, transmission; Pole
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 flight was en route on a return flight from Charlotte, North Carolina, to Chamblee, Georgia, when the engine lost power. The pilot reported that he had 18 gallons of fuel in the right fuel tank and more than 25 gallons in the left fuel tank when the power loss occurred. He indicated that he switched from the right to the left fuel tank position. The pilot called on the UNICOM frequency to report that he was low on fuel and needed assistance in finding an airport. The pilot of another airplane gave him the vectors to the Greenwood airport. The last radio transmission heard from the pilot was "I'm over a four-lane highway…no more fuel." He later stated that instead of saying "no more fuel," he should instead have reported that he had "lost the engine." During the forced landing, the airplane struck two power lines and two utility poles and came to rest on its right side with the left wing in the near-vertical position. A power line penetrated the left wing, breaching the left fuel tank, but the left wing did not burn or explode. The fuel selector was selected to the left fuel tank. The right wing was separated from the fuselage, and the fuel tank was ruptured. A fire ensued. One witness stated that he saw fluid leaking from the left wing and onto the engine compartment. He stated that he assumed the fluid was aviation fuel because whenever it hit the engine compartment, the fire flared up. The second witness indicated that he smelled fuel and assumed fuel was sustaining the postcrash fire. When the airplane was turned upright, the day after the accident, less than 1 gallon of fuel was drained from the left fuel tank. The pilot reported that during his preflight inspection at the Peachtree-Dekalb Airport in Chamblee, he determined that the left and right wing fuel tanks each had more than 25 gallons of fuel. He added 15 gallons of fuel per tank for a total of 80 gallons. The airplane's total fuel capacity is 122 gallons, of which 120 gallons are usable. Safety Board staff calculated that the airplane burned 20 gallons of fuel per hour at 75 percent power. The total 2.2-hour flight was therefore calculated to have consumed about 44 gallons of fuel, not counting the fuel used to taxi, take off, and climb. The fuel remaining was therefore adequate to complete the flight. Examination of the engine did not disclose evidence of mechanical malfunction. At the time of the accident, the pilot had a total of 10 hours experience in this make and model airplane, all obtained over a period of about 4 years.

Probable cause

the loss of engine power for undetermined reason.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL96FA022
Event ID
20001207X04945
Case number
ATL96FA022
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: d645b94d23cb001c78a37dbc2bf7de160de81ed3556e7e2b28a51ec8d211fbc1; retrieved 2026-09-20T23:29:50.921Z.