Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

January 4, 2020 · Cessna 150 M · N45069

Twentynine Palms, CA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
January 4, 2020
Injury Outcomes
No injuries (1 uninjured)
Location
Twentynine Palms, CA
Aircraft
Cessna 150 M (1975)
Tail Number
N45069
Injuries
None
Aircraft Damage
Substantial
NTSB Number
WPR20CA060

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.

NTSB 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.

Full 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.

Flight

Event TypeAccident
Event Time20:00 PST
Nearest AirportTwentynine Palms (0nm NNE)
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 150 M
Tail NumberN45069
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsContinental · O-220-A · Reciprocating · 100
Seats2

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 24 · First Class · None

Conditions

ConditionsVMC
LightNight
WindCalm
Visibility10 sm
CeilingNone
Temperature / Dew Point61 F / 32 C
Altimeter30.37 inHg
Observation Time18:56
Weather SourceWFAC

Appendix: Source Data