LAX82FVG34 · Cessna 210
Cessna 210 · Accident: total loss of engine power (non-mechanical) en route
From S. LAKE TAHOE, CA to Conrad, MT
Event
- NTSB case
- LAX82FVG34
- 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 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
- N9620T
- Operator
- William Lowry
- Onboard fatalities
- Unknown
- Route
- From S. LAKE TAHOE, CATo Conrad, MT
- 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 · descent
- 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
- 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
- Pilot in command › Refueling, not performed
Approximate · Estimated position: the centre of Placerville, CA, the place the record names. Not the accident site.
NTSB narrative
PILOT STATES HE WAS DESCENDING FROM 10,000 FEET TO 8,000 FEET WHEN ENGINE QUIT. FURTHER STATED FUEL WAS ABOVE RED ARC-NO STEEP OR SHARP MANEUVERS. NO MENTION OF RATE OF DESCENT OR DECK ANGLE IN DESCENT. FORCED LANDING WAS MADE CIRCLING TO RIGHT-USEABLE FUEL WAS IN THE RIGHT TANK. LANDING GEAR DOWN AND FULL FLAPS FOR LANDING. LANDING WAS HARD COLLAPSING RIGHT MAIN AND NOSE GEAR. FUEL LATER DRAINED WAS TWO TO THREE GALS. FROM BOTH TANKS. LESS THAN ONE FROM LEFT AND LESS THAN 2 FROM RIGHT TANK. AIRCRAFT REMAINED UPRIGHT. PILOT MADE INITIAL DEPARTURE WITH ZERO FUEL INDICATION ON LEFT TANK AND RIGHT TANK 3/4 FULL.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX82FVG34
- Event ID
- 20020917X04776
- Case number
- LAX82FVG34
- 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: 535a03f8ef2faecac2bad82f41eab814d4c6797a84e760233c2c18e52f62a829; retrieved 2026-09-21T18:06:20.593Z.