FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05LA033 · Cessna 210

12 Nov 2004 · Apple Valley, CA, United States

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

From Apple Valley Airport (APV) to Apple Valley Airport (APV)

Report a problem

Event

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

Cessna 210

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
N5LT
Operator
Unknown
Onboard fatalities
Unknown
Route
From Apple Valley Airport (APV), Apple Valley, CATo Apple Valley Airport (APV)
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/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

  • Fluid, fuel › Starvation/exhaustion
  • Pilot in command › Fuel supply, not verified
  • Pilot in command › Preflight planning/preparation, 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 on final approach and the airplane's nose landing gear struck a chain link fence about 1,000 feet from the approach end of the runway. The pilot reported that the purpose of the flight was to both look at the progress of work at a construction site and to perform a post maintenance test flight following maintenance on the landing gear. He said he conducted a thorough preflight inspection that included checking the fuel for water contamination. In the pilot's written statement he reported that 18 gallons of fuel was in the left fuel tank and 12 gallons of fuel was in the right fuel tank; however, he did not describe how he determined the amount of fuel. During the hour-long flight, the pilot maneuvered the airplane around the construction site at 6,500 feet mean sea level (msl), and as he returned to the airport he switched to the right fuel tank, and cycled the gear several times. After entering the airport environment, the pilot did two touch-and-go takeoffs and landings. During the third touch-and-go landing, the runway direction was switched due to a wind shift. After takeoff, the pilot exited the pattern and climbed to 5,500 feet msl to set up for a full stop landing. A slower airplane was landing in front of him, and he slowed his airplane down to follow it while he conducted the before landing checklist, which included switching to the fullest fuel tank (right). The slower airplane turned base, and the pilot extended his pattern to allow for adequate spacing for landing. While on final approach with the airplane configured at an airspeed of 80 knots, he added another 10 degrees of flaps (for a total of 20 degrees flaps down), and reduced the power. He noted that the airplane was sinking and attempted to apply power to maintain the airplane's glide path. The pilot observed that the engine was not generating power, pulled back on the yoke to stop the descent rate, and switched to the left fuel tank. He advanced the throttle full forward, with no response from the engine, and switched back to the right fuel tank. The pilot set up for an off-airport forced landing and was in the flare when the nose landing gear struck a fence. A sheriff's deputy arrived on-scene, and noted no sound of liquid in the fuel tanks when he moved the wings, an indication that the fuel tanks were empty. He did observe a trickle of fuel near the wing roots. A Federal Aviation Administration principal maintenance inspector recovered a total of 7.5 gallons of fuel from the right fuel tank and 1.5 gallons of fuel from the left fuel tank. According to the airplane manufacturer, the airplane holds 32.5 gallons of fuel in each wing, with 5 gallons of fuel per wing unusable in normal flight maneuvers. At 2,500 feet msl, with 2,450 rpm's (revolutions per minute), fuel burn is 14.2 gallons of fuel per hour. At a gross weight of 2,900 pounds on a standard day the fuel used during the takeoff and climb is 2.0 gallons.

Probable cause

loss of engine power due to fuel starvation/exhaustion, which was a result of the pilot's inadequate preflight inspection and failure to ensure there was enough fuel onboard for the flight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05LA033
Event ID
20041201X01898
Case number
LAX05LA033
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, 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: e3b86c345fe67da89cc1dfa811276d2e96a55d7f8af04e32d65d1348c791d226; retrieved 2026-09-22T06:31:30.452Z.