FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC08CA002 · Piper PA-28-180

3 Oct 2007 · Fairview, TN, United States

Piper PA-28-180 · Accident: total loss of engine power (non-mechanical) en route

From Shreveport Downtown Airport (DTN) to M33 · Gallatin, TN

Report a problem

Event

NTSB case
NYC08CA002
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-180

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
N7751N
Operator
Stephen R. Pomeroy · private individual
Onboard fatalities
Unknown
Route
From Shreveport Downtown Airport (DTN), Shreveport, LATo M33 · Gallatin, TN
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
Fuel exhaustion; Tree(s)
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

  • Fluid, fuel › Exhaustion

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

NTSB narrative

The pilot of the Piper PA-28-180 had been flying for about 3 hours 35 minutes when the engine lost power due to fuel exhaustion, and he performed a forced landing to trees. The airplane impacted 50-foot tall trees prior to striking the ground. The pilot reported that he had topped-off the airplane's fuel tanks, which had a total capacity of 44 gallons of usable fuel prior to the flight. He leaned the fuel mixture during the flight, and expected the airplane to have an endurance of 4.6 hours. Examination of the wreckage and accident site did not reveal any evidence that either fuel tank contained an appreciable amount of fuel at impact. The pilot reported 94 hours of total flight experience; which included about 13 hours in the same make and model as the accident airplane.

Probable cause

A loss of engine power due to fuel exhaustion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC08CA002
Event ID
20071111X01781
Case number
NYC08CA002
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: 335934ec23ce2ba08ff00b20ef8a63782fd1ccb1bfc93479a1594c6f5f9890c0; retrieved 2026-09-21T18:22:55.405Z.