FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC99LA031 · Piper PA-28-180

25 Nov 1998 · Reno, OH, United States

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

From Sussex Airport (FWN) to Mid Ohio Valley Regional Airport (PKB)

Report a problem

Event

NTSB case
NYC99LA031
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
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-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
N7177W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Sussex Airport (FWN), Sussex, NJTo Mid Ohio Valley Regional Airport (PKB), Parkersburg, WV
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
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 › Information, disregarded

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

NTSB narrative

The airplane departed on a cross country flight with full fuel tanks. The pilot flight-planned for 4 hours of flight, but after 2 1/2 hours noticed the 'fuel gauges looked unusually low.' He diverted to an airport, and 1/2 hour later, about 2 nautical miles from that airport, the engine lost power. The pilot performed a forced landing to a field. Post flight inspection revealed evidence of slight fuel leakage at the carburetor fuel inlet fitting, a pinhole leak in the fuel primer line, and a very slight fuel stain emanating from the left wing fuel cap. There was no evidence of faulty fuel gauges at low fuel levels. A review of the local sectional aeronautical chart revealed that the pilot selected an airport which was ahead, and along the intended route. However, there were numerous other airports which were closer, and could have been selected, but were not along the intended route.

Probable cause

The pilot's disregard of the information provided by the fuel gauges, which resulted in fuel exhaustion. Factors in the accident included leaks in the fuel system, and the pilot's reliance on using timing alone to determine fuel consumption.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC99LA031
Event ID
20001211X11494
Case number
NYC99LA031
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: 715d28ad8eb10418bf84d10d963bd69fd23970ee9fd38e9aca301e2ffd0c957c; retrieved 2026-09-22T16:16:07.568Z.