FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR12LA070 · Ryan NAVION

27 Dec 2011 · Concord, CA, United States

Ryan NAVION · Accident: fuel contamination during takeoff

From Buchanan Field (CCR) to Buchanan Field (CCR)

Report a problem

Event

NTSB case
WPR12LA070
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

Ryan NAVION

Aircraft type
Ryan NAVION
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
N4398K
Operator
Unknown
Onboard fatalities
Unknown
Route
From Buchanan Field (CCR), Concord, CATo Buchanan Field (CCR), Concord, CA
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
Takeoff
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 contamination
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 › 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 shortly after takeoff, the engine lost power, and during the subsequent attempt to return to the airport, the airplane collided with the terrain. A postaccident examination of the engine fuel system revealed that the fuel in the accumulator sump and the carburetor inlet screen line were contaminated with debris and water. It is likely that the loss of engine power was due to this contamination as no further evidence of a mechanical malfunction or failure that would have precluded normal operation was found.

Probable cause

The pilot's inadequate preflight inspection of the airplane and the subsequent total loss of engine power as a result of debris and water contamination in the fuel system.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR12LA070
Event ID
20111227X94050
Case number
WPR12LA070
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: 4aca54b593080ba3d4eb2417b6ccd44b879e171e90dc741ce641cf723eed07c5; retrieved 2026-09-15T17:01:40.983Z.