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.
Alexandria, MN
About 35 miles southeast of the destination airport, the pilot obtained the local weather information and requested the instrument landing system approach (ILS) to runway 31. Upon descending to the decision height, the pilot saw the runway end identifier lights and continued the approach. The pilot then saw the visual approach slope indicator lights and the runway lights and decided to land. The airplane touched down about 1,000 feet down the 5,100-foot-long runway. The pilot reported that when the tires came in contact with the runway, the brakes alternately skidded then "grabbed" the runway surface. The pilot decided not to go around and to remain on the runway and attempt to stop the airplane. The airplane traveled into the snow-covered terrain off the departure end of the runway where it contacted an ILS antenna pylon, resulting in substantial damage to the left wing spar. The pilot reported that the downsloping runway was ice covered and that he landed with an approximate 8-knot tailwind. He reported no preimpact mechanical failures or malfunctions with the airplane that would have precluded normal operation. He also stated he had no prior knowledge of what the braking action on the runway would be.
The pilot’s failure to stop the airplane on the downsloping, ice-contaminated runway after landing with a tailwind. Contributing to the accident was the pilot’s failure to account for the wind conditions and failure to obtain runway conditions.
About 35 miles southeast of the destination airport, the pilot received the local weather information. The pilot requested the instrument landing system approach (ILS) to runway 31. Upon descending to the decision height, the pilot saw the runway end identifier lights and continued the approach. The pilot then saw the visual approach slope indicator (VASI) lights and the runway lights, and decided to land. The airplane touched down approximately 1,000 feet down the runway. The pilot reported that when the tires came in contact with the runway the brakes would skid, then "grab", skid, and then "grab". The pilot elected not to go around, remain on the runway and attempt to stop the airplane. The airplane traveled into the snow covered terrain off the departure end of the runway where it contacted an ILS antenna pylon, which resulted in substantial damage to the left wing spar. The pilot reported that the downsloping runway was ice covered, that he landed with an approximate 8 knot tailwind, and there were no mechanical failures or malfunctions of the airplane. He also stated he had no prior knowledge of what the braking action on the runway would be.