FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX98LA049 · Cessna T210N

2 Dec 1997 · Union City, CA, United States

Cessna T210N · Accident: loss of engine power on approach

From Salinas Municipal Airport (KSNS) to Hayward Executive Airport (HWD)

Report a problem

Event

NTSB case
LAX98LA049
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
0
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 T210N

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
N1396U
Operator
Unknown
Onboard fatalities
Unknown
Route
From Salinas Municipal Airport (KSNS), Salinas, CATo Hayward Executive Airport (HWD), Hayward, 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
Approach
First occurrenceThe 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
Loss of engine power
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. 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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The aircraft was being repositioned to home base following a partial repaint. While on short final to land the engine lost power and the aircraft landed in a residential area. Postaccident examination of the fuel and ignition systems found the fuel flow transducer to be restricted. After several attempts it was possible to blow air through it, but with resistance. Nothing foreign was found in the lines or blown from the transducer. The component was sent to the manufacturer of the fuel system and met flow specifications. The component was then sent to a testing laboratory for examination where it was opened and examined. The interior, turbine, and bearing points appeared to be normal and functional.

Probable cause

Blockage of the fuel flow transducer, which resulted in fuel starvation and the loss of engine power. Unsuitable terrain for an emergency landing was a contributing factor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX98LA049
Event ID
20001208X09329
Case number
LAX98LA049
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 94cc7170e852c88bd94d33010ecc412f86a853497cfa4d45981412521afc6914; retrieved 2026-09-21T21:02:12.022Z.