FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL05LA022 · Piper PA-32-260

8 Nov 2004 · Chamblee, GA, United States

Piper PA-32-260 · Accident: partial loss of engine power (non-mechanical) during initial climb

From DeKalb Peachtree Airport (PDK) to Barrow County Airport (WDR)

Report a problem

Event

NTSB case
ATL05LA022
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-32-260

Aircraft type
Piper PA-32
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
N411CP
Operator
Unknown
Onboard fatalities
Unknown
Route
From DeKalb Peachtree Airport (PDK), Dekalb, GATo Barrow County Airport (WDR), Winder, 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
Initial climb
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
Partial 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
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

  • Pilot in command › Fuel management, improper

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Shortly after takeoff the engine started to "sputter" and lose power. Efforts by the pilot to restore power were unsuccessful. The pilot declared an emergency and during the forced landing the airplane collided with a house. Examination of the airplane found no fuel in the right and left main fuel tanks and about five gallons of fuel in the left tip tank. The right tip tank separated during the collision sequence. There was no browning of grass or remnants of fuel at the location of the right tip tank. Fuel was not present in the fuel lines leading from the right tip tank to the engine. The engine was successfully run. According to the pilot, the airplane departed with 14 gallons of fuel in the right tip tank.

Probable cause

The pilot's mismanagement of the fuel supply, which resulted in fuel starvation and the subsequent loss of engine power. .

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL05LA022
Event ID
20041206X01927
Case number
ATL05LA022
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, coordinates. 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: 5279c41be79695be44af676f682440833d3414aa86599cd3220a92f44c084c72; retrieved 2026-09-21T19:06:42.370Z.