# NTSB GAA18CA059: Mooney M20, N6002Q, Tucson, AZ, November 26, 2017 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: November 26, 2017, 16:00 local (23:00 UTC) - Place: Tucson, AZ - Coordinates: 32.141666, -111.183334 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=32.1417&lon=-111.1833&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Defining event: [Takeoff: Fuel starvation](https://openairdocs.org/ntsb-events/191) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report May 14, 2018 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 96382 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA18CA059 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/96382/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=96382 - Page: https://openairdocs.org/ntsb/GAA18CA059 ## Probable cause The pilot’s inadequate preflight and in-flight fuel management, which resulted in an intermittent loss of engine power due to fuel starvation. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Inspection: preflight inspection](https://openairdocs.org/ntsb-findings/02061510): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Mooney M20E, 3 cases](https://openairdocs.org/ntsb-findings/02061510/cases.md?model=5870212), [All aircraft, 551 cases](https://openairdocs.org/ntsb-findings/02061510/cases.md) - [Use of equip/info: use of equip/system](https://openairdocs.org/ntsb-findings/02063015): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Mooney M20E, 2 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md?model=5870212), [All aircraft, 1,391 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md) - [Fluids: fuel](https://openairdocs.org/ntsb-findings/01071010): Aircraft › Fluids/misc hardware · Fluid management (probable cause); cases with it: [Mooney M20E, 7 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md?model=5870212), [All aircraft, 1,695 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md) - [Fluids: fuel](https://openairdocs.org/ntsb-findings/01071010): Aircraft › Fluids/misc hardware · Fluid level (probable cause); cases with it: [Mooney M20E, 7 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md?model=5870212), [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. - [Takeoff: Fuel starvation](https://openairdocs.org/ntsb-events/191) (defining event); cases with it: [Mooney M20E, 2 cases](https://openairdocs.org/ntsb-events/191/sequence.md?model=5870212), [All aircraft, 733 cases](https://openairdocs.org/ntsb-events/191/sequence.md) - [Initial climb: Loss of engine power (partial)](https://openairdocs.org/ntsb-events/342); cases with it: [Mooney M20E, 9 cases](https://openairdocs.org/ntsb-events/342/sequence.md?model=5870212), [All aircraft, 1,858 cases](https://openairdocs.org/ntsb-events/342/sequence.md) - [Initial climb: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Mooney M20E, 28 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=5870212), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot reported that, during the preflight inspection, in preparation for the local flight to accomplish three touch-and-go landings, he removed the fuel filler caps and visually confirmed what appeared to be an adequate amount of fuel in each tank. The pilot did not use the fuel dip stick to confirm the quantity. The pilot reported that the fuel selector was selected to the right-side fuel tank before departure. After the second takeoff, about 600 ft above ground level (agl) and just before turning crosswind, the engine surged once or twice and then experienced a total loss of engine power. The pilot checked the engine controls and turned left back toward the runway. About 300 ft agl, he switched the fuel selector to the left fuel tank. Seconds later, the engine regained power; however, the airplane had descended low enough that the airplane collided with the tops of mesquite brush and then the ground. Postaccident examination of the airplane revealed that the right fuel tank was empty and that the left fuel tank contained about 10 gallons of fuel. There was no evidence of a breach or fuel leak. The fuselage was substantially damaged. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. ## Factual narrative The pilot reported that during the preflight inspection, in preparation for the local flight to accomplish 3 touch-and-go landings, he removed the fuel filler caps and visually confirmed what appeared to be an adequate amount of fuel in each tank. The pilot did not use the fuel dip stick to confirm the quantity. The pilot reported that the fuel selector was selected to the right-side fuel tank prior to departure. After the second takeoff, about 600 ft above ground level (agl), and just before turning crosswind, the engine surged once or twice, and then experienced a total loss of engine power. The pilot checked the engine controls and made a left turn back toward the runway. About 300 ft agl, he switched the fuel selector to the left fuel tank. Seconds later, the engine regained power, however the airplane had descended low enough that the airplane collided with the top(s) of mesquite brush and then the ground. A postaccident examination of the airplane revealed that the right fuel tank was empty, and the left fuel tank contained about 10 gallons of fuel. There was no evidence of a breach or fuel leak. The fuselage was substantially damaged. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. ## Aircraft - Registration: [N6002Q](https://openairdocs.org/deregistered/N6002Q-2019-02-05), registration cancelled 2019-02-05, S/N 860, built 1965 (OpenAirDocs) - Reported make and model: MOONEY M20 (E) - Registry model: [Mooney M20E](https://openairdocs.org/model/mooney-m20e) (registry code 5870212) (OpenAirDocs) - Registry engine: [Lycoming I0360 series](https://openairdocs.org/engine/lycoming-i0360-series) (registry code 41515, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 860 - Year built: 1966 - Airframe hours: 4260 - Engines: LYCOMING IO-360 reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, October 31, 2017 - Departed: RYN, Tucson, AZ - Destination: RYN, Tucson, AZ - Airport: RYN, Ryan Field, runway 33, 4,000 × 75 ft, asphalt - Equipment: ADS-B, Satellite tracking device ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 74; injuries: none; flight instructor, commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review November 10, 2016; seat: left; restraint: 3-point; flight hours: 2,135 total, 300 in this make and model, 1,996 as pilot in command ## Weather - Conditions: Visual (VMC), Day - Wind: 310° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 90 °F, dew point 28 °F - Altimeter: 30.01 inHg - Observed at: KRYN, 1 nm away ## 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 20171126022059A](https://openairdocs.org/incident/20171126022059A), Nov 26, 2017: Mooney M20E, Tucson, AZ, Substantial damage. Asel M-20 Mooney accident: During a flight within the traffic pattern of Ryan airfield (ryn) near Tucson, AZ., the airman experienced a significant loss of… ## Docket (3 files) The files NTSB released with the investigation on March 29, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=96382. 4.6 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 4.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40461432&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - ROC Pilot (item 2, .PDF, 145 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40461433&FileExtension=.PDF&FileName=ROC%20Pilot-Master.PDF - Accident Photo (Courtesy of FAA) (item 3, .PDF, 1 photo, 306 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40461434&FileExtension=.PDF&FileName=Accident%20Photo%20(Courtesy%20of%20FAA)-Master.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.