# NTSB LAX03CA261: Cessna 150C, N7909Z, Tucson, AZ, August 22, 2003 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: August 22, 2003, 11:20 local (18:20 UTC) - Place: Tucson, AZ - Coordinates: 32.116111, -110.941108 - Nearby events: https://openairdocs.org/map.md?lat=32.1161&lon=-110.9411&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report November 25, 2003 - Report: Approved by Office Director - Parties: FAA FSDO - NTSB case key (mKey): 57773 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX03CA261 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/57773/pdf - Page: https://openairdocs.org/ntsb/LAX03CA261 ## Probable cause the pilot's inadequate inflight planning/decision, which resulted in fuel exhaustion and loss of engine power due to an inadequate fuel supply. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of engine power, cruise - fluid,fuel - exhaustion (cause) - in-flight planning/decision - inadequate, pilot in command (cause) - fuel supply - inadequate, pilot in command (cause) - Forced landing, emergency descent/landing - In flight collision with object, landing - object - tree(s) ## Analysis During cruise, the airplane lost total engine power and collided with a tree during the emergency landing. The pilot departed earlier that day with full fuel. After a series of stops, the pilot was going to make an unscheduled stop to have breakfast and refuel. Suddently, the engine sputtered and then regained normal rpm. The engine instruments were indicating normal operations. Shortly thereafter, the engine completely quit and the pilot made a forced landing. During the landing sequence, the left wing collided with a tree. The pilot felt the engine stopped due fuel exhaustion. ## Factual narrative On August 22, 2003, at 1120 mountain standard time, a Cessna 150C, N7909Z, lost total engine power during cruise and collided with a tree during the forced landing near Tucson, Arizona. The pilot/owner was operating the airplane under the provisions of 14 CFR Part 91. The private pilot and one passenger were not injured; the airplane sustained substantial damage. The cross-country flight departed Gila Bend Municipal Airport (E63), Gila Bend, Arizona, about 1030, and was en route to Ryan Field (RYN), Tucson. Day visual meteorological conditions prevailed and a visual flight rules (VFR) flight plan had been filed. In a phone conversation, the pilot reported to the Safety Board investigator-in-charge (IIC) that during a cross-country flight from Gila Bend Airport to Ryan Field, the airplane's engine sputtered, followed by a loss of power. The engine quit and he made a forced landing. He felt that the engine stopped due to fuel exhaustion. In a written statement, the pilot reported that he departed from Imperial Airport (IPL), Imperial, California, at 0740, with full fuel. He then flew to Calexico International Airport. At Calexico, the pilot filed a VFR flight plan to Ryan Field and anticipated the arrival about 1130. En route to Ryan Field, the pilot stopped at Gila Bend Airport to rest. At 1030, the pilot departed Gila Bend. Approximately 6 nautical miles from Tucson International Airport (TUS), the decision was made to detour to Marana Northwest Regional Airport (AVQ), Marana, Arizona, to have breakfast and refuel. Suddently, the engine began to sputter and then resumed the normal rpm. The engine instruments were indicating normal operations. After contacting Tucson tower to declare an emergency, he turned toward Tucson International. The engine sputtered a second time and died. After an unsuccessful restart attempt, he established best glide airspeed. The pilot completed a soft field landing in a desert field, resulting in substantial damage to the nose gear, wing tips, and right side of the fuselage. In an interview with the Tucson Airport Police Department, the pilot stated that he could not make it to the airport because the airplane ran out of fuel. The officer noted that the airplane's left wing collided into a tree during the forced landing. ## Aircraft - Registration: [N7909Z](https://openairdocs.org/deregistered/N7909Z-2013-05-09), registration cancelled 2013-05-09, S/N 15060009, built 1963 (OpenAirDocs) - Reported make and model: Cessna 150C - Registry model: [Cessna 150C](https://openairdocs.org/model/cessna-150c) (registry code 2071808) (OpenAirDocs) - Registry engine: [Continental 0-200 series](https://openairdocs.org/engine/continental-0-200-series) (registry code 17020, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 15060009 - Engines: Continental O200-A Series reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Raul Anaya - Airworthiness certificate: Standard, Normal - Departed: KE63, Gila Bend, CA - Destination: KRYN, Ryan, AZ - Flight plan: VFR ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 41; injuries: none; private; airplane ratings: single-engine land; medical: class 3; flight hours: 145 total, 39 in this make and model, 70 as pilot in command ## Weather - Conditions: Visual (VMC), Day - Wind: 230° at 6 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 95 °F, dew point 59 °F - Altimeter: 29.96 inHg - Observed at: KSAN ## Other investigations on N7909Z (1) 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. - [NTSB ANC96LA151](https://openairdocs.org/ntsb/ANC96LA151), Sep 9, 1996: Cessna 150 (N7909Z), Willow, AK, substantial damage. Probable cause: The loss of engine power for an undetermined reason. Factors associated with the accident are the soft terrain and brush in the airstrip overrun area. 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.