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.
Fullerton, CA
According to the pilot, no mechanical problems were noted with the airplane during his flight from Santa Ana to Fullerton. The pilot reported that the airplane was slightly high on approach to Fullerton's runway 24, which is 3,121 feet long, so he initiated a go-around passing midfield. Seconds later, upon perceiving a degradation in climb performance, he terminated the attempted go-around and the airplane collided with the airport's perimeter fence. The pilot subsequently reported that during his landing approach the flaps had malfunctioned. The FAA examined the flap operating system and the engine. No evidence of any preimpact malfunction was found. The 124-hour total time pilot had received a private pilot certificate 3 months earlier. His total experience flying the Cessna was 4 hours.
the pilot's misjudged glide path and delayed remedial action by not promptly initiating a go-around. A contributing factor was the pilot's lack of experience flying the airplane.
On August 10, 1996, at 1146 hours Pacific daylight time, a Cessna 172N, N42ES, operated by the Orange County Flight Center, collided with a perimeter fence during an aborted landing on runway 24 at the Fullerton Municipal Airport, Fullerton, California. The airplane was substantially damaged and the private pilot was not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the personal flight which originated from Orange County, California, at 1130. The pilot reported that no mechanical problems were noted with the airplane during the initial approach to the runway, which is 3,121 feet long. According to the pilot, he was slightly high on the approach, and he began the landing flare around midfield while in a flaps up configuration. The pilot further indicated that he believed there was insufficient runway on which to stop, so he commenced a go-around by adding engine power. The engine responded, but the airplane impacted a perimeter fence after overflying the departure end of the runway. In the pilot's completed report, he stated that during his landing approach the flaps failed to extend beyond the 10-degree setting due to a mechanical malfunction. The pilot also reported that after he initiated a go-around the airplane's performance "appeared to deteriorate," so he initiated a precautionary landing during which the airplane collided with the fence. The pilot received his private pilot certificate in May, 1996. By the accident date, he had a total of 124 hours of flight time which included 4 hours in the Cessna 172 airplane. The Federal Aviation Administration examined the airplane's flap operating system and the engine. No evidence of preimpact malfunctions was noted.