The U.S. aircraft register, updated daily
Accidents · NTSB WPR26LA182 · Final report

American AA-5 accident near Jurupa Valley, California, May 12, 2026

On May 12, 2026 at about 3:40 am local time, a 1972 American AA-5, registered N5832L, was substantially damaged in an accident during landing (flare/touchdown) near Jurupa Valley, California (Flabob Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
May 12, 2026 · about 3:40 am local time · cases in 2026
Place
Jurupa Valley, California · Flabob Airport · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
American AA-5, built 1972 · all AA-5s on the register
Registration
N5832L · registry record · serial AA5-0232
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Collision during takeoff/land during landing (flare/touchdown) defining event

The NTSB's findings

  • Personnel issues › Experience/knowledge › Experience/qualifications › Recent experience › Pilot
  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Environmental issues › Conditions/weather/phenomena › Light condition › Dark › Effect on personnel
  • Environmental issues › Operating environment › Airport facilities/design › Ground support/equipment › Awareness of condition
  • Environmental issues › Operating environment › Airport facilities/design › Runway lighting › Effect on personnel

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 2,056 hours in all; 1,726 in this make and model; 10 in the last 90 days; 1 in the last 30 days; 1,936 as pilot in command
  • Last flight review: June 28, 2025
  • Medical certificate: Class 3 (waiver time limited special)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 4,201 hours
  • Last inspection: annual inspection, June 23, 2025; 42 hours since
  • Maximum gross weight: 1,800 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O360-A4M (piston); 4,360 hours total

The flight

  • Flight plan: none
  • Runway 06/2, 3,190 ft by 50 ft

Weather at the time

  • Light: night
  • Wind: from 260° at 7 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 72°F (22°C), dew point 57°F (14°C)
  • Altimeter: 29.94 inHg
  • Observation at 8:00 pm from KRAL, 3 miles away

Weather report (METAR): METAR KRAL 110253Z 26007KT 10SM CLR 22/14 A2994 RMK AO2 SLP124 T02170139 53017

Injuries

FatalSeriousMinorNone
Flight crew1

Photographs from the investigation 6 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

4 documents, released by the NTSB on August 20, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/WPR26LA182.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.