# NTSB WPR10CA311: Cessna 172F, N8793U, Rancho Murieta, CA, July 8, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: July 7, 2010, 22:42 local (Jul 8, 2010, 05:42 UTC) - Place: Rancho Murieta, CA - Coordinates: 38.486946, -121.102775 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=38.4869&lon=-121.1028&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach: Fuel exhaustion](https://openairdocs.org/ntsb-events/192) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report October 21, 2010 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 76428 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR10CA311 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/76428/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=76428 - Page: https://openairdocs.org/ntsb/WPR10CA311 ## Probable cause A total loss of engine power in flight due to fuel exhaustion as a result of the pilot's inadequate fuel planning. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Fluids: fuel](https://openairdocs.org/ntsb-findings/01071010): Aircraft › Fluids/misc hardware · Fluid management (probable cause); cases with it: [Cessna 172F, 7 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md?model=2072414), [All aircraft, 1,695 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md) - [Planning/preparation: fuel planning](https://openairdocs.org/ntsb-findings/02061030): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 172F, 3 cases](https://openairdocs.org/ntsb-findings/02061030/cases.md?model=2072414), [All aircraft, 719 cases](https://openairdocs.org/ntsb-findings/02061030/cases.md) - [Fluids: fuel](https://openairdocs.org/ntsb-findings/01071010): Aircraft › Fluids/misc hardware · Fluid level (probable cause); cases with it: [Cessna 172F, 7 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md?model=2072414), [All aircraft, 1,695 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach: Fuel exhaustion](https://openairdocs.org/ntsb-events/192) (defining event); cases with it: [Cessna 172F, 5 cases](https://openairdocs.org/ntsb-events/192/sequence.md?model=2072414), [All aircraft, 804 cases](https://openairdocs.org/ntsb-events/192/sequence.md) - [Approach: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341); cases with it: [Cessna 172F, 10 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=2072414), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md) - [Emergency descent: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Cessna 172F, 9 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=2072414), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) - [Landing: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172F, 22 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072414), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot reported that when he was about 7 miles from his intended destination the engine began to run rough and lost all power about one minute later. He unsuccessfully attempted to restart the engine multiple times. The pilot decided to try to land at a closer airport but realized he would not be able to make it to that airport, either, so he elected to land in an open field. During landing the airplane bounced and the right wing collided with a tree, which spun the airplane around. The airplane sustained substantial damage to both wings. Local fire department first responders reported that when they arrived on scene there were no fuel leaks and there was no odor of fuel present on-scene. They attempted to drain fuel from the sump but no fuel came out. A Federal Aviation Administration inspector examined the airplane and reported that there was no fuel at the selector valve or in the wing tanks. The pilot stated that "... adding additional fuel in excess of [the] perceived minimum fuel level would likely have avoided [the] power loss...." ## Factual narrative In a written statement, the pilot reported that when he was about 7 miles from his intended destination the engine began to run rough and lost all power about one minute later. He unsuccessfully attempted to restart the engine multiple times. The pilot decided to try to land at a closer airport but realized he would not be able to make it to that airport, either, so he elected to land in an open field. During landing the airplane bounced and the right wing collided with a tree, which spun the airplane around. The airplane sustained substantial damage to both wings. Local fire department officials reported that when they arrived on scene there were no fuel leaks and there was no odor of fuel present on-scene. They attempted to drain fuel from the sump but no fuel came out. The Federal Aviation Administration inspector stated that there was no fuel at the selector valve or in the wing tanks. Recovery personnel found no fuel in the system when they disassembled the airplane for movement and said the fuel system was intact. The pilot stated that "... adding additional fuel in excess of [the] perceived minimum fuel level would likely have avoided power loss...." ## Aircraft - Registration: [N8793U](https://openairdocs.org/deregistered/N8793U-2010-08-25), registration cancelled 2010-08-25, S/N 17252698, built 1965 (OpenAirDocs) - Reported make and model: CESSNA 172F (F) - Registry model: [Cessna 172F](https://openairdocs.org/model/cessna-172f) (registry code 2072414) (OpenAirDocs) - Registry engine: [Continental 0-300 series](https://openairdocs.org/engine/continental-0-300-series) (registry code 17022, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17252698 - Airframe hours: 6844 - Engines: Continental O-300 145 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Low Flying Angels, Inc. - Registered owner: Low Flying Angels, Inc. - Airworthiness certificate: Standard, Normal - Last inspection: Annual, July 2, 2010, 3 hours before - Departed: KHJO, Hanford, CA - Destination: KMHR, Sacramento, CA - Airport: KRIU, Rancho Murieta ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 59; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review October 28, 2008; seat: left; flight hours: 2,060 total, 1,600 in this make and model ## Weather - Conditions: Visual (VMC), Night - Wind: 140° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 64 °F, dew point 50 °F - Altimeter: 29.82 inHg - Observed at: KMHR ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20100708040219A](https://openairdocs.org/incident/20100708040219A), Jul 8, 2010: Cessna 172F, Rancho Murrieta, CA, Substantial damage. Pilot was on a long cross country flight that included several stops. On the return flight, at night, pilot stopped at a local airport for gas. Pilot visually… ## Docket (1 files) The files NTSB released with the investigation on August 3, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=76428. 875 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 875 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40334034&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.