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

September 20, 2004 · Iar Sa Brasov 823 · N823WT

Denair, CA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
September 20, 2004
Injury Outcomes
No injuries (2 uninjured)
Location
Denair, CA
Aircraft
Iar Sa Brasov 823
Tail Number
N823WT
Injuries
None
Aircraft Damage
Substantial
NTSB Number
LAX04CA326

The airplane experienced a loss of engine power and collided with terrain during a forced landing in a soft, wet field. Prior to departure, the pilot performed a preflight inspection, at which time he visually verified the airplane's fuel quantities by both physically looking inside the wing tanks, and by checking his fuel computer/totalizer inside the cockpit. The pilot did not use a dipstick or other means to physically quantify the fuel on board. He determined that he had a more than adequate amount of fuel for the 1- to 1 1/2-hour flight. While en route, the pilot compared the "fuel remaining time" with the "time en route remaining" on his gauges numerous times. As he came in the proximity of the airport the engine coughed once and subsequently quit. Despite his efforts, the engine would not restart and the pilot made an emergency landing. While descending, the left wing tip contacted the ground first, and the landing gear touched down on the soft wet ground. The pilot drained both fuel tanks and found about 1 gallon of fuel remaining. The pilot opined that 12 gallons of fuel was siphoned from the airplane prior to departure. The pilot stated that the accident could have been prevented if he had used a fuel quantity dipstick. The pilot reported no mechanical malfunctions of failures with the airplane prior to impact.

NTSB Probable Cause

the pilot's failure to verify the fuel quantity on board prior to departure, which resulted in fuel exhaustion and loss of engine power due to an inadequate fuel supply.

Full Narrative

On September 20, 2004, about 1500 Pacific daylight time, an experimental IAR SA Brasov 823, N823WT, experienced a loss of engine power and collided with terrain during a forced landing near Denair, California. The pilot/owner was operating the airplane under the provisions of 14 CFR Part 91. The commercial pilot and one passenger were not injured; the airplane sustained substantial damage. The personal cross-country flight departed Reno/Stead Airport, Reno, Nevada, about 1330, with a planned destination of Turlock Municipal Airport, Turlock, California. Visual meteorological conditions prevailed, and a flight plan had not been filed. In a written statement, the pilot reported that he had flown to Reno several days prior to the accident, and during the duration of his stay, he parked the airplane in a tie down area on the ramp. Prior to departing, the pilot performed a preflight inspection, at which time he visually verified the airplane's fuel quantities by both physically looking inside the wing tanks, and by checking his fuel computer/totalizer inside the cockpit. The pilot did not use a dipstick or other means to physically verify the quantity. He estimated about 33 gallons of fuel on board, which he thought would be more than adequate for the 1- to 1 1/2-hour flight. Having flown the same route of flight many times before, he calculated the airplane's fuel burn to be about 13.4 gallons per hour. The pilot stated that while en route, he compared the "fuel remaining time" with the "time en route remaining" on his gauges numerous times. As he came in the proximity of Turlock, about 3 miles away, he maneuvered the airplane in a descent to 1,000 feet above ground level in preparation to enter the left downwind leg of the traffic pattern for runway 30. The engine coughed once and subsequently quit. In an effort to troubleshoot the engine's loss of power, he turned the boost pump to the "on" position, manipulated the mixture knob to the "full rich" position, and verified the fuel selector was in the "both" position. Despite his efforts, the engine would not restart and the pilot configured the airplane for an emergency landing; he opted to land between sprinkler systems in alfalfa field. While descending, the left wing tip contacted the ground first, and the landing gear touched down on the soft wet ground. The pilot further noted that after egressing the airplane, he tried to troubleshoot the engine failure. He discovered that the left wing tank was empty, and the right tank had a very minimal amount of fuel left inside. The fuel computer/totalizer indicated 13.1 gallons remaining. The airplane incurred damage to wings, landing gear, and propeller. After recovery, under the auspice of a Federal Aviation Administration inspector, the pilot drained both fuel tanks and found about 1 gallon of fuel remaining. The pilot opined that 12 gallons of fuel was siphoned from the airplane while on parked on the ramp at Reno. He stated that this missing amount of fuel would not be detected by the fuel calculator/ totalizer, and would be difficult to assess when visually inspecting the fuel tanks (about an inch difference). He further noted that the accident could have been prevented if he had used a quantity dipstick. The pilot reported no mechanical malfunctions of failures with the airplane prior to impact.

Flight

Event TypeAccident
Event Time15:00 PDT
Nearest AirportTurlock Municipal Airport (3nm)
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo

Aircraft

AircraftIar Sa Brasov 823
Tail NumberN823WT
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO-540-GID5 · Reciprocating

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 46 · Second Class

Conditions

ConditionsVMC
LightDaylight
WindCalm
CeilingNone
Temperature / Dew Point0 C / 0 C
Altimeter0

Appendix: Source Data