LAX03FA031 · Cessna T210L
Cessna T210L · Accident: loss of engine power on approach
From Whiteman Airport (WHP) to Whiteman Airport (WHP)
Event
- NTSB case
- LAX03FA031
- 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 T210L
- 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
- N76TL
- Operator
- Ruben Piranian
- Onboard fatalities
- Unknown
- Route
- From Whiteman Airport (WHP), Pacoima, CATo Whiteman Airport (WHP), Pacoima, 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 go-around
- 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; Tree(s); Pole
- 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 › Flow restricted
- Fluid, fuel › Starvation
- Pilot in command › Fuel management, inadequate
- Pilot in command › In-flight planning/decision, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On final approach for landing, the engine lost power and the pilot made a forced landing on a city street. The airplane struck trees, the ground, and a stopped car before coming to rest impaled on a pole at a corner auto sales lot. According to the owner, the airplane had about 20 gallons of fuel in each tank when he dropped off the airplane at the maintenance shop on October 19, 2002, for the 50-hour inspection, and historical experience showed the engine consumed 17.3 gallons per hour in cruise. The mechanic/pilot was conducting a flight test of the autopilot and turbocharger systems following a 50-hour inspection. He indicated that there was 40 gallons of fuel onboard the airplane prior to takeoff, and the test flight lasted about 45 minutes. He further reported that the left fuel tank gage read 1/4 tank, and the right fuel tank gage read between 1/4 and 1/2 tank. When the flight reached the cruise altitude of 16,000 feet, the pilot switched the fuel tank selector, but did not recall which tank he selected. About 30 minutes into the flight, the pilot told the passenger that they were low on fuel, but that it would be okay. The passenger noted that both fuel gages read less than 1/4 tank each at that time. The pilot tested the autopilot for 8 minutes and then returned to the airport for landing. Prior to entering the airport environment, the pilot switched the fuel selector to the fullest tank, which he believed was the right fuel tank. The first approach was too high and the pilot requested and received clearance to conduct a go-around in order to lose altitude. During the second approach, the engine quit. First responders to the accident site reported seeing fuel leaking from the engine area, and then a fire started. The airplane sustained fire damage to the cabin and aft engine areas, as well as both wings. The fuel selector was selected to the right fuel tank. A warning in the fuel systems description section of the manufacturer's approved flight manual states that with 1/4 full or less of fuel in the fuel tanks, prolonged uncoordinated flight (slips or skids) can cause the fuel tank outlets to become uncovered causing fuel starvation and engine stoppage. A post-accident airframe and engine inspection was conducted with no mechanical anomalies noted.
Probable cause
a loss of engine power due the inadvertent unporting of the fuel pickup tube, which resulted in fuel starvation during the go-around. The pilot's preflight and in-flight decisions regarding fuel quantity and fuel system management are also causal.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX03FA031
- Event ID
- 20021123X05513
- Case number
- LAX03FA031
- 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: 2c8a113c7385eeab8b1ff3d597e447888785454ababf2272c9565b83a9e5f5da; retrieved 2026-09-21T19:34:49.401Z.