# NTSB WPR20CA060: Cessna 150, N45069, Twentynine Palms, CA, January 4, 2020 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: January 3, 2020, 20:00 local (Jan 4, 2020, 04:00 UTC) - Place: Twentynine Palms, CA - Coordinates: 34.136112, -115.944442 - Nearby events: https://openairdocs.org/map.md?lat=34.1361&lon=-115.9444&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Fuel related](https://openairdocs.org/ntsb-events/190) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report August 17, 2020 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 100780 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR20CA060 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/100780/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=100780 - Page: https://openairdocs.org/ntsb/WPR20CA060 ## Probable cause The pilot's poor preflight planning, during which he failed to verify the proper procedure to activate the runway lights; his inability to locate the airport without lighting; and the airplane’s subsequent low-fuel state as he circled looking for the airport, which necessitated a precautionary off-airport landing, during which the nose landing gear separated. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Planning/preparation: flight planning/navigation](https://openairdocs.org/ntsb-findings/02061025): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 150M, 1 case](https://openairdocs.org/ntsb-findings/02061025/cases.md?model=2071830), [All aircraft, 179 cases](https://openairdocs.org/ntsb-findings/02061025/cases.md) - [Light condition: dark](https://openairdocs.org/ntsb-findings/03036020): Environmental issues › Conditions/weather/phenomena · Effect on personnel (probable cause); cases with it: [Cessna 150M, 3 cases](https://openairdocs.org/ntsb-findings/03036020/cases.md?model=2071830), [All aircraft, 448 cases](https://openairdocs.org/ntsb-findings/03036020/cases.md) - [Fluids: fuel](https://openairdocs.org/ntsb-findings/01071010): Aircraft › Fluids/misc hardware · Fluid level (probable cause); cases with it: [Cessna 150M, 11 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md?model=2071830), [All aircraft, 1,695 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md) - [Use of equip/info: use of policy/procedure](https://openairdocs.org/ntsb-findings/02063032): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 150M, 3 cases](https://openairdocs.org/ntsb-findings/02063032/cases.md?model=2071830), [All aircraft, 191 cases](https://openairdocs.org/ntsb-findings/02063032/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Fuel related](https://openairdocs.org/ntsb-events/190) (defining event); cases with it: [Cessna 150M, 7 cases](https://openairdocs.org/ntsb-events/190/sequence.md?model=2071830), [All aircraft, 361 cases](https://openairdocs.org/ntsb-events/190/sequence.md) - [Landing: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Cessna 150M, 17 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=2071830), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) - [Landing-landing roll: Part(s) separation from AC](https://openairdocs.org/ntsb-events/338); cases with it: [Cessna 150M, 1 case](https://openairdocs.org/ntsb-events/338/sequence.md?model=2071830), [All aircraft, 563 cases](https://openairdocs.org/ntsb-events/338/sequence.md) ## Analysis The pilot reported that, upon arrival at the airport after dark, he attempted to activate the pilot-controlled lights by keying the mike seven times. Shortly later, he repeated the process twice, but the runway lights did not turn on. He circled the area to try to locate the airport but was unsuccessful. The airplane was now low on fuel, so the pilot began looking for a place to make a precautionary landing. He landed the airplane on a dirt road, and during the landing rollout, the nose landing gear separated, and the left wing was substantially damaged. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. The Federal Aviation Administration Airport Facility Directory noted that medium-intensity runway lights were available at the airport. To activate the pilot-controlled lighting, the pilot must key the mike five times in 5 seconds. The pilot reported that he did not check what the proper procedures were for operating the pilot-controlled lighting for the runway. Airport personnel checked the pilot-controlled lighting system the day after the accident and reported that there were no malfunctions with the system. ## Factual narrative The pilot reported that upon arrival at the airport after dark, he attempted to activate the pilot-controlled lights by keying the mike 7 times. He waited a short period and repeated the process two more times, but the runway lights did not turn on. He circled the area to try to locate the airport but was unsuccessful. The pilot stated he was now low on fuel, so he began to look for a place to make a precautionary landing. The airplane landed on a dirt road and during the landing rollout, the nose landing gear separated, and the left wing was substantially damaged. The pilot reported that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation. The Federal Aviation Administration (FAA) Airport Facility Directory identified that medium intensity runway lights were available at the airport. To activate the pilot-controlled lighting, the pilot is to key the mike 5 times in 5 seconds for medium or lower intensity lights. The pilot reported that he did not check what the proper procedures were for operating the pilot-controlled lighting for the runway. Airport personnel performed a check of the pilot-controlled lighting system the following day and reported that there were no malfunctions with the system. ## Aircraft - Registration: [N45069](https://openairdocs.org/deregistered/N45069-2023-09-19), registration cancelled 2023-09-19, S/N 15076722, built 1975 (OpenAirDocs) - Reported make and model: Cessna 150 (M) - Registry model: [Cessna 150M](https://openairdocs.org/model/cessna-150m) (registry code 2071830) (OpenAirDocs) - Registry engine: [Continental 0-200 series](https://openairdocs.org/engine/continental-0-200-series) (registry code 17020, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 15076722 - Year built: 1975 - Airframe hours: 6295.3 - Engines: Continental O-220-A 100 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal; Standard, Utility - Last inspection: Annual, November 18, 2019 - Departed: A39, Maricopa, AZ - Destination: TNP, Twentynine Palms, CA - Airport: TNP, Twentynine Palms ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 24; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 1, without waivers/limitations; last flight review January 12, 2018; seat: left; flight hours: 260 total, 28.8 in this make and model ## Weather - Conditions: Visual (VMC), Night - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 61 °F, dew point 32 °F - Altimeter: 30.37 inHg - Observed at: KNXP, 15 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 20200103004919A](https://openairdocs.org/incident/20200103004919A), Jan 3, 2020: Cessna 150M, Twentynine Palm, CA, Substantial damage. The pilot departed french valley airport (F70) at 1:30 pm. The route of flight was blythe (kblh) then to phoenix regional airport(A39). The pilot departed from… ## Docket (4 files) The files NTSB released with the investigation on June 5, 2020, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=100780. 1.9 MB in all. - NTSB Summary of Findings (item 1, .PDF, 54 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40484147&FileExtension=.PDF&FileName=NTSB%20Summary%20of%20Findings-Master.PDF - FAA Airport Facility Directory Excerpt TNP Airport Diagram (item 2, .PDF, 160 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40484149&FileExtension=.PDF&FileName=FAA%20Airport%20Facility%20Directory%20Excerpt%20TNP%20Airport%20Diagram-Master.PDF - FAA Airport Facility Directory Excerpt Runway Lighting Legend (item 3, .PDF, 286 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40484150&FileExtension=.PDF&FileName=FAA%20Airport%20Facility%20Directory%20Excerpt%20Runway%20Lighting%20Legend-Master.PDF - Photos (item 4, .PDF, 1.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40484151&FileExtension=.PDF&FileName=Photos-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.