FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05FA026 · Cessna T210M

4 Nov 2004 · Lomita, CA, United States

Cessna T210M · Accident: total loss of engine power (non-mechanical) on approach

From John Wayne Orange County International Airport (SNA) to Zamperini Field (TOA)

Report a problem

Event

NTSB case
LAX05FA026
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
Visual Meteorological Cond

Cessna T210M

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
N732RW
Operator
Jerry Hoke
Onboard fatalities
Unknown
Route
From John Wayne Orange County International Airport (SNA), Santa Ana, CATo Zamperini Field (TOA), Torrance, 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 · VFR pattern final
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
Total loss of engine power (non-mechanical)
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; Utility pole
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Fluid, fuel › Starvation
  • Pilot in command › Aircraft preflight, inadequate
  • Pilot in command › Fuel management, inadequate

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The engine lost power at night while the pilot was on short final for the runway during a 12-minute positioning flight between nearby airports, and the airplane collided with a house. Witnesses reported that the engine sound was quiet prior to impact with trees, power lines, and a house. The airplane came to rest inverted in the backyard of a residence. The total flight time since the last refueling of 40 gallons was 2.1 hours tachometer time. The owner estimated that when the 40 gallons were added, the fuel tanks would have been near empty. Fuel calculations based on charts in the Cessna Pilot's Operating Handbook indicated that approximately 30 gallons would have been used during the 2.1 hours. At the accident site, the intact right fuel tank contained about 8 ounces of fuel. The left fuel tank was breached but approximately 1 gallon was drained from the tank when it was moved for recovery and a strong odor of fuel was present in the soil beneath the airplane's left wing. The fuel selector was positioned to the right fuel tank. Prior to the airplane's departure on the accident flight, the owner noted that the fuel gauges were reading about 1/4 tank. The fuel line from the fuel pump to the engine was removed and a residual amount of fuel drained out. No control or operational anomalies were noted with the airplane, and the engine was test-run successfully. Interviews with friends of the pilot revealed that the pilot was to reposition the airplane over the previous days leading up to the accident, and that the owner had expressed his disapproval that the repositioning had not been done yet. According to the pilot's friends, the pilot had flown a twin engine Cessna earlier in the day. That evening, the accident pilot was delayed while waiting for a ferry airplane and pilot to arrive, in order to fly him to pickup the accident airplane. The certified flight instructor (CFI) that flew the accident pilot to pickup the airplane reported that immediately after dropping the pilot at the airplane, he began his return trip. The accident airplane was two airplanes behind the CFI during landing. As the CFI was taxiing to parking, he saw a flash of fire in the direction of the accident site. Besides the accident airplane, two other airplanes were for sale at the owners facility; one of these airplanes was the same make and model of the accident airplane. About 2 weeks prior to the accident, the owner of the aircraft sales company and the accident pilot refueled these two airplanes; however, the accident airplane was not refueled.

Probable cause

A loss of engine power due to fuel starvation as a result of the pilot's mismanagement and inadequate preflight inspection.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05FA026
Event ID
20041116X01823
Case number
LAX05FA026
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2004-11-05.
  • API snapshot SHA-256: c10a072f24c7f1d704f4627bdb039c12b7dc0513dc0efb83d46dd6f4fb1b9e0c; retrieved 2026-09-20T18:13:14.047Z.