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.
Madill, OK
The pilot reported that, during a solo night flight, he "landed long" and was unable to complete a touch-and-go as planned. The airport did not have a parallel taxiway leading to the departure end of the runway, so the pilot taxied onto the ramp area to turn around. During the taxi on the ramp, the lighting was "poor," and the right wing tip struck a hangar. He reported that he "did not realize" the right wing struck the hangar and continued the flight back to his home airport. After landing and securing the airplane, the pilot noticed that the right wing was damaged and told flight school maintenance personnel. A postaccident examination of the airplane revealed that it had sustained substantial damage to its right-wing rear spar. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. According to the flight school's flight operations manual, flight operations were not permitted at the accident airport due to the requirement for the runway to be at least 4,000 ft long. The accident airport runway was 3,005 ft long. In addition, the manual prohibited touch-and-go landings at night.
Environmental issues-Physical environment-Object/animal/substance-Airport structure-Effect on operation - C
The pilot reported that during a solo night flight, he "landed long" and was unable to complete a touch-and-go as planned. The airport did not have a parallel taxiway leading to the departure end of the runway, so the pilot taxied onto the ramp area to turn around. During the taxi on the ramp the lighting was "poor" and the right wingtip struck a hangar. He reported that he "did not realize" the right wing struck the hangar and continued the flight back to his home airport. After landing and securing the airplane, he noticed the right wing was damaged and told the flight school maintenance personnel. A post-accident review revealed the airplane had sustained substantial damage to its right-wing rear spar. The pilot reported that there were no pre-accident mechanical failures or malfunctions with the airplane that would have precluded normal operation. According to the flight school's flight operations manual, flight operations were not permitted at the accident airport due to the requirement for the runway to be at least 4000 ft. long. The accident airport runway was 3,005 ft. long. In addition, the manual prohibited touch-and-go landings at night.