LAX06LA196 · Cessna P210N
Cessna P210N · Accident: total loss of engine power (non-mechanical) on approach
From Carson Airport (CXP) to an unrecorded destination
Event
- NTSB case
- LAX06LA196
- 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 P210N
- 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
- N7762K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Carson Airport (CXP), Carson City, NVTo not recorded
- 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 downwind
- 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 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
- Pilot in command › Preflight planning/preparation, inadequate
- Pilot in command › Refueling, not performed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that he taxied his airplane from one hangar to another when he decided to take the airplane up for a quick flight. He flew the airplane around the local area and returned to the airport after about 15 minutes. The airplane was on a left downwind for runway 27, and the pilot had completed the before landing checklist (he extended the landing gear and lowered 20 degrees of flaps) when the "engine quit producing power." The pilot turned on the electric fuel pump, as well as the high boost pump, and made a left turn toward the runway. The pilot reported engaging the high boost pump switch until landing the airplane. He opened the throttle and applied a full rich mixture, but the engine did not restart. The pilot observed the fuel quantity gauges and noted that both right and left fuel tanks displayed needles "above the red warning area." The pilot realized the airplane would not make it to the airport and noticed a suitable landing site. He maneuvered the airplane over power lines and houses, and lowered the nose of the airplane to gain airspeed. He flared the airplane for landing, but the nose landing gear contacted the ground before the main gear. Subsequently, the nose gear and main gear collapsed and the airplane came to rest about 150 to 200 feet from the initial touchdown point after impacting a fence and a mailbox. Following the accident, inspectors from the Federal Aviation Administration Reno Flight Standards District Office (FSDO) examined the airplane at the accident site. According to the FSDO inspectors, approximately 1/2-inch of fuel or less remained in the left wing when it was placed in a level position. They reported that slightly more remained in the right fuel tank. The recovery personnel drained 3 gallons of fuel from the left fuel tank and 5 gallons from the right; however, he noted that some had spilled out during the recovery process. The pilot could not remember which fuel tank was selected at the time of the loss of engine power. The pilot reported no mechanical malfunction or failures. He added that he had last refueled the airplane in May 2006, about a month prior to the accident, in Ely, Nevada, before flying back to Carson City. Post accident inspections revealed no mechanical irregularities.
Probable cause
Fuel exhaustion which resulted in a loss of engine power during approach for landing due to the pilot's failure to refuel the aircraft and the pilot's failure to perform an adequate preflight inspection.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX06LA196
- Event ID
- 20060615X00739
- Case number
- LAX06LA196
- 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: fc6a2fc6d0046297605adb20008448437ea5f8e923915ecfc479892505804adb; retrieved 2026-09-21T18:45:12.871Z.