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.
Santa Paula, CA
The pilot entered the downwind leg of the traffic pattern to the destination runway. While on approach, the pilot noted the airplane was excessively high, moving at a faster-than-normal airspeed. He attributed the unstabalized approach to be the result of a short downwind leg. The airplane landed hard and bounced. It subsequently veered off the runway surface and collided with a fence, coming to rest on a dirt berm. The pilot reported no preimpact mechanical malfunctions or failures with the airframe or engine.
The pilot's unstabilized approach, which resulted in a hard, bounced landing. Also causal was the pilot's inadequate recovery from the bounced landing and his failure to maintain directional control.
In a written report, the pilot stated that while en route, he noticed his GPS was inoperative and decided to divert to a nearby airport. As he approached the vicinity of the airport, he noted that other traffic was utilizing runway 22, and accordingly entered the traffic pattern on the downwind leg. While on the approach, the pilot could discern that the airplane was excessively high and at a faster-than-normal airspeed, which he believed was a result of his decision to make a short downwind leg. The airplane landed hard and bounced twice, veering off the runway surface. It continued forward and collided with a fence, coming to rest upright on a dirt berm. The pilot reported no preimpact mechanical malfunctions or failures with the airframe or engine. The aircraft sustained substantial damage, including the damage to a wing that would require a major repair.