Overall Trends
Total, fatal, and serious accidents in the selected range.
Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.
Fast key and full-text search with live filters, watches, and precise metadata.
Use quotes for exact phrase matches (for example "fuel selector valve").
Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.
Major cases, deep-report coverage, and investigation media across decades of NTSB history.
Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.
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.
Stockton, CA
After a loss of engine power, the airplane landed short of the runway, collapsing the nose gear and buckling the engine firewall. The pilot departed with both fuel tanks full. His route of flight usually takes 3 hours to fly. He encountered turbulence and strong winds, which had the effect of increasing the flight time to 4 hours. As he lined up for a straight-in approach to the runway, the engine stopped due to fuel exhaustion. The pilot executed a forced landing short of the approach end of runway and collided with the ground and a fence. The pilot stated that the airplane and engine had no mechanical malfunctions. An FAA inspector examined the airplane at the accident scene and confirmed that there was no fuel onboard.
The loss of engine power due to fuel exhaustion resulting from the pilot's inaccurate fuel consumption calculations and failure to refuel while en route.
The pilot stated in the Pilot/Operator Accident Report that he departed El Monte, California, with both fuel tanks full of 100LL. His route of flight, El Monte to Stockton, California, usually takes 3 hours to fly. He encountered turbulence and strong winds, which had the effect of increasing the flight time to 4 hours. As he lined up for a straight-in approach to the Stockton Metropolitan Airport, the engine stopped due to fuel exhaustion. The pilot executed a forced landing short of the approach end of runway 29, which collapsed the nose gear and buckled the engine firewall. The pilot stated that the airplane and engine had no mechanical malfunctions. An FAA inspector examined the airplane at the accident scene and confirmed that there was no fuel onboard. The airplane had been modified with the installation of a higher horsepower Lycoming O-360-A1A engine in place of the original O-320.