IAD97GA081 · Piper PA-18-150
Piper PA-18-150 · Accident: total loss of engine power (non-mechanical) en route
From Shenandoah Valley Regional Airport (SHD) to an unrecorded destination
Event
- NTSB case
- IAD97GA081
- 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-18-150
- Aircraft type
- Piper PA-18
- 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
- N4310Z
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Shenandoah Valley Regional Airport (SHD), Weyers Cave, VATo 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
- 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
- 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
- Fuel system, tank › Starvation
- Pilot in command › Fuel management, inattentive
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The commercial pilot and observer were flying an official survey flight for the state Game and Inland Fisheries. After 2 hours 20 minutes, they were returning to the airport when the engine began to 'spit and sputter'. The pilot was able to get the engine running again for about 5 seconds, and then declared that they were going to land. The pilot spotted a grass strip and attempted a downwind landing, when he noticed a mobile home at the end of the strip. The pilot reported that he ran the right wing into a tree in order to avoid the home. Examination of the wreckage revealed that the right fuel tank was empty and the left tank was full. The fuel selector was set on the right tank. The pilot reported that he was preoccupied during the flight and forgot to switch tanks.
Probable cause
The pilot's preoccupation which led to fuel starvation of the selected tank and the subsequent forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD97GA081
- Event ID
- 20001208X08145
- Case number
- IAD97GA081
- 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: 5bc1a279f6574c83e3a75c52411c4ca6673902a9ebf23943a054cc22a2a2e6e0; retrieved 2026-09-21T21:25:59.017Z.