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

May 12, 2026 · American AA-5 · N5832L

Jurupa Valley, CA

Overview

Report Status
Probable Cause
Event Type
Accident
Date
May 12, 2026
Injury Outcomes
No injuries (1 uninjured)
Location
Jurupa Valley, CA
Aircraft
American AA-5 (1972)
Tail Number
N5832L
Injuries
None
Aircraft Damage
Substantial
NTSB Number
WPR26LA182

The pilot reported that he had planned the flight to include three take-offs and landings after dark, to renew his night currency after several years of not flying at night. He entered the traffic pattern in near-dark conditions and attempted several times to activate the pilot controlled runway lights, but was unable to do so, and elected to land without the runway lights illuminated. He reported that he lost visual contact with the runway and started searching for the runway while judging his position based on the airport buildings. At about 20-30 ft above the surface, he observed the ground just in front of the airplane and realized the airplane was not aligned with the runway. He added power to perform a go-around, but the airplane struck an airport perimeter fence located to the left of the runway. The airplane spun around to the right before coming to rest in the dirt/grass area next to the runway. During the accident sequence the airplane sustained substantial damage to the wings and fuselage. According to the pilot, he did not review the FAA notice to airmen (NOTAM) advising that the airport was closed daily from sunset to sunrise, which was in effect at the time of the accident. The pilot reported that there were no pre-accident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

NTSB Probable Cause

The pilot’s decision to land at night on a runway without illuminated runway lights. Contributing to the accident was the pilot’s failure to review NOTAMs for a nightly airport closure.

Full Narrative

The pilot reported that he had planned the flight to include three take-offs and landings after dark, to renew his night currency after several years of not flying at night. He entered the traffic pattern in near-dark conditions and attempted several times to activate the pilot controlled runway lights, but was unable to do so, and elected to land without the runway lights illuminated. He reported that he lost visual contact with the runway and started searching for the runway while judging his position based on the airport buildings. At about 20-30 ft above the surface, he observed the ground just in front of the airplane and realized the airplane was not aligned with the runway. He added power to perform a go-around, but the airplane struck an airport perimeter fence located to the left of the runway. The airplane spun around to the right before coming to rest in the dirt/grass area next to the runway. During the accident sequence the airplane sustained substantial damage to the wings and fuselage. According to the pilot, he did not review the FAA notice to airmen (NOTAM) advising that the airport was closed daily from sunset to sunrise, which was in effect at the time of the accident. The pilot reported that there were no pre-accident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Flight

Event TypeAccident
Event Time21:00 PDT
Nearest AirportFLABOB (0nm N)
Runway06/2
Runway Length3190 ft
Runway Width50 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftAmerican AA-5
Tail NumberN5832L
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O360-A4M · Reciprocating · 180
Seats4

People & Injuries

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

Conditions

ConditionsVMC
LightNight
Wind7 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point0 C / 0 C
Altimeter0
Observation Time20:00
Weather SourceWFAC

Appendix: Source Data