FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR24FA037 · Cessna P210N

15 Nov 2023 · San Diego, CA, United States

Cessna P210N · Accident: fuel exhaustion on approach

From Buchanan Field (CCR) to French Valley Airport (F70)

Report a problem

Event

NTSB case
WPR24FA037
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
1 · 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
Instrument Meteorological Cond

Cessna P210N

Aircraft type
Cessna 210
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
N1400
Operator
Unknown
Onboard fatalities
Unknown
Route
From Buchanan Field (CCR), Concord, CATo French Valley Airport (F70), Murietta, CA
Aircraft age
About 44 years (built 1979)
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
Approach · IFR missed approach
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 › Experience/knowledge
  • 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 instrument-rated pilot was conducting a personal night cross-county flight into an area where instrument flight rules (IFR) conditions prevailed. The pilot had flown nearly 4 hours and was conducting an instrument landing system (ILS) approach to an airport that he had diverted to due to poor weather at his intended destination and an ILS that was out of service by NOTAM at his filed alternate. There was no record of the pilot obtaining a weather briefing before the flight. During the approach, the airplane drifted from the localizer course. The pilot then reported a missed approach to air traffic control, requested another approach, and reported about 10 minutes of fuel remaining. Subsequently, the airplane made a series of erratic turns and altitude changes, and the pilot requested an emergency landing. Shortly afterward, the pilot informed the controller that he was completely out of fuel. While the controller attempted to vector the airplane toward a runway, the airplane maneuvered northwest of the airport and then communication and contact were lost. A witness reported that visibility in the area was almost zero and the ceiling was 200-300 ft above ground level (agl) with light rain and wind. However, a pilot flying behind the accident airplane on the approach was able to follow the ILS and land without issue. The airplane was not located and was the subject of a Federal Aviation Administration Alert Notice. Subsequently, a search located the airplane early the following morning on the side of a hill in a residential area about 3 miles west of the airport. A review of the pilot’s logbooks revealed that within the 6 months preceding the accident flight, he had not performed the tasks required to act as pilot-in-command under IFR. His most recent actual or simulated instrument flight occurred about 19 months before the accident flight. This lack of recent instrument experience likely contributed to the pilot’s difficulty completing the ILS approach. Postaccident examination of the airplane revealed that the fuel tanks were not damaged during the impact and were absent of fuel. In addition, there was no evidence of preimpact mechanical failures or malfunctions that would have precluded normal operation. The airplane had a specified cruise endurance of 4.2 hours with full fuel. The postaccident airplane examination, the airplane’s maximum endurance, and the pilot’s communications on his fuel status were all consistent with a total loss of engine power due to fuel exhaustion.

Probable cause

A total loss of engine power due to fuel exhaustion. Contributing to the accident were the pilot’s inadequate flight and fuel planning and his decision to fly in night instrument meteorological conditions despite his lack of recent instrument flight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR24FA037
Event ID
20231116193391
Case number
WPR24FA037
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: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2023-11-16.
  • API snapshot SHA-256: 5b9f8a2319d8121714543c3034690dcf1ae475848a848e1ab4a7b9f93dc6465c; retrieved 2026-09-15T08:08:10.825Z.