ATL99FA045 · Piper PA-28-181
Piper PA-28-181 · Accident: total loss of engine power (non-mechanical) while maneuvering
From 6A3 · Andrews, NC to an unrecorded destination
Event
- NTSB case
- ATL99FA045
- 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-28-181
- 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
- N1875H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 6A3 · Andrews, NCTo not recorded
- 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
- Maneuvering
- 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
- Fuel exhaustion; Tree(s); Wire, transmission
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Fluid, fuel › Exhaustion
- Pilot in command › In-flight planning/decision, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported a low fuel condition to the air traffic controller. The air traffic controller gave the pilot alternate airports available for landing in the immediate vicinity of the accident site. The pilot circled the area for approximately 2.5 hours. After failing to identify any of the airports, the pilot flew towards Brevard, NC. While in a descent towards the vicinity of Brevard, the airplane struck several trees and a power line before impacting the ground. The airframe and engine examinations failed to disclose any evidence of a mechanical malfunction or component failure. The post-impact examination of the engine and airframe fuel system components failed to show evidence of fuel. A small quantity of fuel was observed in the carburetor. There were no obvious indications of fuel spillage at the accident site; nor did the emergency response personnel report the odor of fuel upon their arrival at the accident site.
Probable cause
The pilot's inadequate inflight planning that resulted in fuel exhaustion and the subsequent loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL99FA045
- Event ID
- 20001204X00007
- Case number
- ATL99FA045
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1999-01-28.
- API snapshot SHA-256: 83ff1ed56ac594676441d01938ac29846fb99d271f97aaa184aa9d283844e260; retrieved 2026-09-20T22:15:49.290Z.