WPR20CA060

NTSB accident investigation · Cessna 150 · Twentynine Palms, CA · January 4, 2020

Accident · No injuriesData collectionFinal report
Date
January 3, 2020, 20:00 local (Jan 4, 2020, 04:00 UTC)
Place
Twentynine Palms, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N45069Cessna 150
Defining event
Landing: Fuel related
Weather
Visual (VMC) · Night
Status
Completed · report August 17, 2020
Report
Approved by Office Director
NTSB office
Western Pacific Region
Parties
Federal Aviation Administration
FAA report
20200103004919A
Case key
100780

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

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 · 4

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Planning/preparation: flight planning/navigationPersonnel issues › Task performance · PilotCessna 150M: 1 caseAll aircraft: 179 casesProbable cause
Light condition: darkEnvironmental issues › Conditions/weather/phenomena · Effect on personnelCessna 150M: 3 casesAll aircraft: 448 casesProbable cause
Fluids: fuelAircraft › Fluids/misc hardware · Fluid levelCessna 150M: 11 casesAll aircraft: 1,695 casesProbable cause
Use of equip/info: use of policy/procedurePersonnel issues › Task performance · PilotCessna 150M: 3 casesAll aircraft: 191 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

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
Reported as
Cessna 150 (M)
Category
Airplane
Serial number
15076722
Built
1975
Airframe hours
6,295.3
Engine
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

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
24
Injuries
None
Certificate
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

Docket · 4

The files NTSB released with the investigation on June 5, 2020, on NTSB’s docket system: statements, records, photos and specialists’ reports. 1.9 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.