FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA18CA184 · Piper PA32 260

4 Mar 2018 · Camas, WA, United States

Piper PA32 260 · Accident: fuel exhaustion en route

From Salem-Willamette Valley Airport/McNary Field (SLE) to Grove Field (1W1)

Report a problem

Event

NTSB case
GAA18CA184
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 PA32 260

Aircraft type
Piper PA32
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
N3756W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Salem-Willamette Valley Airport/McNary Field (SLE), Salem, ORTo Grove Field (1W1), Camas, WA
Aircraft age
About 52 years (built 1966)
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
Defining eventThe 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
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

  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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 reported that, before departure, he estimated that the right tip fuel tank was three-quarters full (about 14 gallons), and each main fuel tank had about 20 gallons of fuel.

The pilot reported that, during cruise, he decided to use the right tip fuel tank, even though he was aware that the right tip fuel tank gauge was inoperative. He added that, after about 25-30 minutes, he performed various stall maneuvers before returning to the departure airport to land. The pilot noticed a reduction in engine power and a drop in the manifold pressure and concluded that the airplane would not be able to return to the airport, so he continued a left turn toward a farm field. The pilot began to troubleshoot for carburetor ice to no avail. The airplane landed in the farm field and impacted a ditch.

The airplane sustained substantial damage to the engine mounts.

The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

The pilot added that, during a postaccident examination, it was revealed that the right tip fuel tank was dry and "that the engine lost power due to fuel starvation."

Probable cause

The pilot’s inadequate inflight fuel management and his failure to switch to a fuel tank with adequate fuel, which resulted in fuel starvation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA18CA184
Event ID
20180305X54709
Case number
GAA18CA184
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 44bd1f21c41dcbe9c31f33714f8c82d9d187a7cd0eaeba9f08e0331c3c8c533d; retrieved 2026-09-16T06:34:40.520Z.