NYC02LA176 · Piper PA-38-112
Fairfield County Airport Authority Piper PA-38-112 · Accident: total loss of engine power (non-mechanical) en route
From Mid Ohio Valley Regional Airport (PKB) to Fairfield County Airport (LHQ)
Event
- NTSB case
- NYC02LA176
- 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-38-112
- Aircraft type
- Piper PA-38
- 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
- N4307E
- Onboard fatalities
- Unknown
- Route
- From Mid Ohio Valley Regional Airport (PKB), Parkersburg, WVTo Fairfield County Airport (LHQ), Lancaster, OH
- 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 starvation; 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
- 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
During the return leg of the student pilot's cross-country flight, the engine lost all power, and the student pilot performed a forced landing to trees. Examination of the wreckage by an FAA inspector revealed that the left fuel tank was full, but the right fuel tank contained about 1 gallon of fuel. Prior to the student renting the airplane, it was completely fueled, then flown 1.1 hours. A flight instructor met with the student pilot prior to her flight, and told her to fly out on the right tank, and fly back on the left. However, the student pilot thought she had 12 gallons of fuel in the right tank, and flew the entire cross-country flight with the fuel selector positioned to the right tank. After the power loss, the student pilot did not switch fuel tanks. The right fuel tank had indicated mid-range, and she believed that sufficient fuel remained in the right tank. Review of a discrepancies form revealed that during the 2 months prior to the accident, the right fuel tank gauge was entered twice, but the operator took no corrective action.
Probable cause
The student pilot's improper fuel management, which resulted in fuel starvation during cruise flight. A factor was the operator's failure to perform maintenance on a fuel gauge that was noted twice in a discrepancy log.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC02LA176
- Event ID
- 20020905X01531
- Case number
- NYC02LA176
- 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: 002775c116d76a2585e7f25bfc9570ed69ef26df8a7bfee9c724e445aa9a8e00; retrieved 2026-09-22T10:24:14.019Z.