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.
Julian, NC
According to the pilot, he departed on the personal flight for the purpose of having an annual inspection performed on his airplane at the destination airport. While approaching the airport, he observed the windsock indicating the wind was from the south, and chose the appropriate runway. The pilot planned his approach to clear the fence at the end of the runway and still have enough distance for the roll out on the grass runway. Knowing that the terrain sloped upward from the fence to the runway threshold, he aimed to touchdown on the crest of the hill. As the airplane approached the runway, the pilot added power to compensate for a fast rate of descent, then reduced power when he felt he was aligned appropriately. The airplane touched down about half way up the slope and the nose gear collapsed; the airplane came to rest at the top of the slope. According to the Federal Aviation Administration inspector, the firewall was substantially damaged. The pilot reported that there were no mechanical malfunctions prior to the accident.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - C
According to the pilot, he departed on the personal flight for the purpose of having an annual inspection performed on his airplane at the destination airport. While approaching the airport, he observed the windsock indicating the wind was from the south, and he planned to land on runway 23. The pilot stated that he planned his approach to clear the fence at the end of the runway and still have enough room to stop on the 1,400-foot grass runway. He also stated that he knew that the terrain sloped upwards from the fence to the runway threshold, and that he "was aiming for the crest of the hill." As the airplane approached the runway, the pilot first added power to compensate for a "fast rate of decent," then reduced power when he felt he had the runway made. However, "the rise was greater than I thought, and the airspeed was lower than I thought." The airplane touched down about half way up the slope, the nose gear collapsed, and the airplane came to rest at the top of the slope. According to the Federal Aviation Administration inspector, the firewall was substantially damaged. The pilot reported that there were no mechanical malfunctions prior to the accident.