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.
Idaho Falls, ID
The pilot and his passenger departed from the pilot's home airport for a brief personal flight. About 10 minutes later, the pilot returned to the airport traffic area and entered the traffic pattern. In his initial telephone interview with the NTSB, the pilot reported that there "was a crosswind, with some gusting," and that the airplane bounced after its initial touchdown. It then bounced several more times, ground looped, and veered off the runway, substantially damaging the left wing. The pilot reported that he did not experience any mechanical malfunctions or failures of the airplane. In his subsequent written statement to the NTSB, the pilot reported that, while on the downwind leg, he was asked by the controller to "keep [the] pattern short," since his airplane was slow and there was another airplane behind him. The pilot said that he landed close behind a Cessna 182 that had just departed. The pilot was uncertain whether the bounces and loss of control were due to the wind or to the wake turbulence from the departing airplane. The automated weather observation at the airport, which was posted about 2 minutes before the accident, included variable wind at 4 knots.
The pilot’s improper landing flare, inadequate recovery from a bounced landing, and subsequent failure to maintain directional control.
The pilot and his passenger departed from the pilot's home airport for a brief personal flight. About 10 minutes later, the pilot returned to the airport traffic area and entered the traffic pattern. In his initial telephone interview with the NTSB, the pilot reported that there "was a crosswind, with some gusting," and that the airplane bounced after its initial touchdown. It then bounced several more times, ground looped, and veered off the runway, substantially damaging the left wing. The pilot reported that he did not experience any mechanical malfunctions or failures of the airplane. In his subsequent written statement to the NTSB, the pilot reported that while on the downwind leg, he was asked by the controller to "keep [the] pattern short," since his airplane was slow and there was another airplane behind him. The pilot said he landed close behind a Cessna 182 that had just departed. The pilot was uncertain whether the bounces and loss of control were due to the wind, or to the wake turbulence from the departing airplane. The automated weather observation at the airport, which was posted about 2 minutes before the accident, included "variable" winds at 4 knots.