FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR23LA177 · Cessna 210M

3 May 2023 · Pasco, WA, United States

Cessna 210M · Accident: fuel starvation during landing

From Richland Airport (RLD) to an unrecorded destination

Report a problem

Event

NTSB case
WPR23LA177
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 210M

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
N777CF
Operator
Unknown
Onboard fatalities
Unknown
Route
From Richland Airport (RLD), Richland, WATo not recorded
Aircraft age
About 46 years (built 1977)
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
Landing
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 starvation
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 › Aircraft systems
  • 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 was returning the airplane to its home airport after completion of a 100-hour inspection, an annual inspection, and additional maintenance that was required due to the improper installation of the battery. While on the base leg for landing, the engine lost total power. The pilot initiated an off-airport emergency landing and during the rollout, the airplane contacted road signs, which substantially damaged the left and right wings and the right horizontal stabilizer. Recorded engine data revealed consistent operation of the engine throughout the flight until about 1-minute before the loss of data, when the data indicated a total loss of power. Examination of the engine revealed the fuel outlet line to the fuel servo was loose on the fuel outlet fitting, which resulted in fuel starvation of the engine. When the improper maintenance to the fuel line occurred could not be determined; the recent maintenance performed on the engine did not require removal of the fuel outlet line.

Probable cause

Improper maintenance on the fuel outlet line to the fuel servo, which resulted in the line partially separating from the fuel outlet fitting and the subsequent fuel starvation and total loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR23LA177
Event ID
20230505109772
Case number
WPR23LA177
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-05-04.
  • API snapshot SHA-256: fb3400e29b2392189195f79a1ae80e71194f0cae5f24f72761bdbc1ace160ae0; retrieved 2026-09-16T17:34:26.540Z.