FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR23LA294 · Cessna 195

30 Jul 2023 · Ravensdale, WA, United States

Cessna 195 · Accident: fuel related en route

From Cavanaugh Bay Airport (66S) to Norman Grier Field (S36)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
WPR23LA294
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
Event fatalities
Unknown
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

Cessna 195

Aircraft type
Cessna 195
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
N195JL
Operator
Unknown
Onboard fatalities
Unknown
Route Possible conflict
From Cavanaugh Bay Airport (66S), Priest River, IDTo Norman Grier Field (S36), Covington, WA
Aircraft age
About 71 years (built 1952)
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 related
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

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 and a passenger departed with about 57 to 60 gallons of fuel on board. The pilot estimated that the flight would last about 2 hours and the fuel consumption rate would be about 18 to 21 gallons per hour; given the available fuel and consumption rate, the airplane should have had sufficient fuel for about 2.5 to 3.1 hours of flight. The pilot reported that while en route, there were indications of a fuel imbalance between the left and right fuel tanks while the fuel selector was positioned on BOTH, along with the smell of fuel. The pilot adjusted the fuel selectors until the fuel level was about equal in the left and right fuel tanks. About 15 minutes before reaching the destination, the engine sputtered and lost power but remained running near the idle setting of 600 rpm for the remainder of the flight. The pilot performed a forced landing to an off-airport site and impacted obstacles, which substantially damaged the fuselage, wings, and empennage. The pilot shut the engine down before exiting the airplane. The total flight time was considerably less than the calculated fuel endurance. During the wreckage recovery, about 5 gallons of fuel was removed from the left-wing tank and about 3 gallons were removed from the right tank. The airplane’s unusable fuel was about 2.5 gallons per tank, which revealed that both tanks were very close to the unusable fuel quantity; however both tanks had usable fuel in them. Postaccident examination revealed additional evidence of fuel escaping. The left wing exhibited a dirt and fuel residue that ran from the fuel filler port to the trailing edge of the wing, indicating that fuel siphoned out of the filler port during the accident flight. The left-wing filler port exhibited wear marks near the cap locking seat, which may have provided a loose fit between the cap to the seal. The right wing did not exhibit similar staining. The pilot found evidence of fuel leaking from the carburetor during his postaccident inspection and surmised that the carburetor bowls may have become lodged and did not meter the fuel in the bowl correctly. No other mechanical malfunctions or failures with the airframe or engine were observed that would have precluded normal operation. A test run of the engine revealed normal operations up to 2,200 rpm with no evidence of fuel leaks before , during or after the test run.

Probable cause

Partial loss of power for undetermined reasons. Contributing to the accident was the siphoning of fuel from the left-wing fuel filler port due to wear on the fuel filler cap.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR23LA294
Event ID
20230731192761
Case number
WPR23LA294
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, cause areas. 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: 26c76f7eab5f61ec0ea71c9bacbddfe0b6975a02698153ed7625c87611e46383; retrieved 2026-09-16T17:56:38.436Z.