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.
Hawthorne, NV
The pilot reported that he made a radio call on the CTAF frequency for airport advisories, but that there was no response. He overflew the airport and observed the windsock showing no wind. He entered left traffic for runway 10. As the aircraft slowed after touchdown, a gust of wind or dust devil caused the aircraft to turn radically to the right. The aircraft started to ground loop and he added full power to recover. The aircraft departed the runway on a stable heading and collided with a fence.
The pilot's inadequate compensation for the existing wind condition and his subsequent failure to maintain directional control.
On September 23, 1997, at 1705 hours Pacific daylight time, a Piper PA-18-150, N82259, veered off runway 10, contacted a chain link fence with the landing gear and came to rest inverted while landing at the Hawthorne, Nevada, airport. The aircraft sustained substantial damage, and the co-owner/pilot and one passenger were not injured. Visual meteorological conditions existed for the personal flight, and no flight plan was filed. The flight had originated from the Jackpot, Nevada, airport at 1400 on the day of the accident. The pilot reported that he attempted a radio call on the Hawthorne CTAF frequency for airport advisories, but that there was no response. He stated that he overflew the airport and observed the windsock showing no wind. He entered left traffic for runway 10. The pilot reported that as the aircraft slowed after touchdown, a gust of wind or dust devil caused the aircraft to turn radically to the right. The aircraft started to ground loop and he added full power to recover from the ground loop. The aircraft departed the runway on a "stable heading and clipped [a] short fence." He reported no mechanical problems with the aircraft.