LAX03LA216 · Cessna 210D
Cessna 210D · Accident: total loss of engine power (mechanical failure) en route
From Nut Tree Airport (VCB) to Scottsdale Airport (SDL)
Event
- NTSB case
- LAX03LA216
- 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 210D
- 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
- N3826Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Nut Tree Airport (VCB), Vacaville, CATo Scottsdale Airport (SDL), Scottsdale, AZ
- 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
- En route · cruise
- 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 (mechanical failure)
- 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 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 › Exhaustion
- Fluid, fuel › Leak
- Fuel system, gascolator › Cracked
- Other maintenance personnel › Maintenance, installation, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane lost engine power and made a forced landing on a road, encountered rough terrain, and nosed over. The pilot fueled the airplane with about 5 hours of fuel. After about 4 hours she contacted the tower and told them of her intention to land. Soon after, the engine failed. She switched tanks, the engine restarted, and then it quit again. She realized there must have been a fuel leak and radioed the tower to advise them of the engine failure. She attempted to land at a private airport; however, the airplane landed on a road and came to rest inverted. No fuel was discovered at the scene of the accident. A post accident inspection revealed a crack on the bottom of the elbow fitting, which was on the bottom of the gascolator. A Federal Aviation Administration inspector performed a test using soap and water. At 3 to 5 pounds of pressure, the assembly began bubbling at the crack, indicating a leak. The inspector noted blue stains along the bottom of the airplane. The inspector opined that the crack was the result of excessive torque used to tighten the fitting.
Probable cause
fuel exhaustion due to a crack on the elbow fitting to the gascolator resulted in a fuel leak.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX03LA216
- Event ID
- 20030708X01043
- Case number
- LAX03LA216
- 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: e1dcf503fd578be1531d7cbaa67a73ee703a8520794d5654daee3b8b8a9c59cf; retrieved 2026-09-21T09:26:18.609Z.