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.
Coldwater, MI
The pilot departed on a short cross-country flight and arrived at his destination airport about 1100. The pilot stated that he overflew the airport and observed blowing snow on both runways. Because the wind was from 220 degrees, he elected to land on runway 22. During the roll-out, the airplane collided with plowed snow at the intersection of runway 07/25. The airplane's nose gear collapsed resulting in substantial damage to the airplane's fuselage. The pilot added that the snow banks should have been removed from the intersection and a NOTAM (notice to airmen) should have been published. A review of the Airport/Facilities Directory's (A/FD) note section for the airport had the notice: "Runway 07/25 plowed during winter months, contact the airport manager for conditions". At 1055, the automated weather reporting station at the airport reported the visibility at 3 miles in light snow, with the wind from 260 degrees at 11 knots. The weather station normally broadcasts the A/FD message about runway 07/25 being plowed during winter months; however, an electrical power interruption erased the message prior to the accident. With reduced visibility and blowing snow on the runways, it's likely that a pilot would not be able to see plowed snow banks at the intersection of runway 04/22 and 07/25.
Airport personnel did not remove the snow banks from the intersecting runway and/or close the intersection runway, which resulted in the airplane impacting the snow banks. Contributing to the accident was the reduced visibility inhibiting the pilot's ability to see the plowed snow hazard.
The pilot departed on a short cross-country flight and arrived at his destination airport about 1100. The pilot stated that he overflew the airport and observed blowing snow on both runways. Because the wind was from 220 degrees, he elected to land on runway 22. During the roll-out, the airplane collided with plowed snow at the intersection of runway 07/25. The airplane's nose gear collapsed resulting in substantial damage to the airplane's fuselage. The pilot added that the snow banks should have been removed from the intersection and a NOTAM (notice to airmen) should have been published. A review of the Airport/Facilities Directory's (A/FD) note section for the airport had the notice: "Runway 07/25 plowed during winter months, contact the airport manager for conditions". At 1055, the automated weather reporting station at the airport reported the visibility at 3 miles in light snow, with the wind from 260 degrees at 11 knots. The weather station normally broadcasts the A/FD message about runway 07/25 being plowed during winter months; however, an electrical power interruption erased the message prior to the accident.