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.
Nora Springs, IA
The pilot reported that while landing on a wet grass runway, the airplane touched down “a little long.” The pilot was unable to stop the airplane, and it departed the end of the runway surface into an agricultural field. He then attempted to avoid the agricultural vegetation off the end of the runway by turning the airplane to the left; however, the airplane entered a skid and subsequently impacted the vegetation which resulted in substantial damage to the fuselage. The pilot reported the airplane’s braking was ineffective due to the runway being wet and recently rolled. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. At the time of the accident, the pilot was landing the airplane on runway 09 with wind from 230° at 6 knots. The calculated total landing distance required from the landing distance performance chart was 3,943 ft, which was 1,493 ft more than the available runway distance.
The pilot’s improper decision-making for the attempted landing, which resulted in a runway overrun due to inadequate runway landing distance with a quartering tailwind. Contributing to the accident was the wet condition of the runway.
The pilot reported that while landing on a wet grass runway, the airplane touched down “a little long.” The pilot was unable to stop the airplane, and it departed the end of the runway surface into an agricultural field. He then attempted to avoid the agricultural vegetation off the end of the runway by turning the airplane to the left; however, the airplane entered a skid and subsequently impacted the vegetation which resulted in substantial damage to the fuselage. The pilot reported the airplane’s braking was ineffective due to the runway being wet and recently rolled. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. At the time of the accident, the pilot was landing the airplane on runway 09 with wind from 230° at 6 knots. The calculated total landing distance required from the landing distance performance chart was 3,943 ft, which was 1,493 ft more than the available runway distance.