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.
Defuniak Springs, FL
The pilot listened to the recorded weather information then took off on the airport’s only paved runway with a direct crosswind of about 5 kts. He described that during the initial climb, the airplane encountered either a downdraft or increasing wind over trees next to the runway that resulted in the airplane rolling left. The pilot attempted to counteract the roll; however, the airplane settled off the sloped left side of the runway, impacted a berm, bounced up, and came to rest on the taxiway. The left wing was substantially damaged. The pilot reported that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation. Postaccident communication with the Federal Aviation Administration revealed that the airport manager’s weather reporting system included gusting wind that was not reported by the automated weather system.
The pilot's failure to maintain directional control while taking off in a crosswind, which resulted in a runway excursion and impact with a berm. Contributing was the automated weather briefing which failed to include accurate wind information.
The pilot listened to the recorded weather information then took off on the airport’s only paved runway with a direct crosswind of about 5 kts. He described that during the initial climb, the airplane encountered either a downdraft or increasing wind over trees next to the runway that resulted in the airplane rolling left. The pilot attempted to counteract the roll; however, the airplane settled off the sloped left side of the runway, impacted a berm, bounced up, and came to rest on the taxiway. The left wing was substantially damaged. The pilot reported that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation. Postaccident communication with the Federal Aviation Administration revealed that the airport manager’s weather reporting system included gusting wind that was not reported by the automated weather system.