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.
Polson, MT
On the day of the accident, the pilot was performing a series of touch-and-go landings in variable gusty wind conditions in order to "...maintain proficiency on a gusty day." After three successful touch-and-go landings, the pilot decided to make the next landing a full-stop termination of the flight. During the subject landing, the wind shifted from a quartering headwind to a quartering tailwind, and although the touchdown was uneventful, during the landing roll the aircraft suddenly started turning toward the side of the runway. Although the pilot applied control inputs in an attempt to keep the aircraft on the runway, his inputs were not adequate to overcome the effects of the varying wind conditions, and therefore the aircraft departed the side of the runway. The pilot then added full power in order to regain control and execute a go-around. During that sequence of events, the aircraft's left wing contacted the ground and the left horizontal stabilizer impacted a runway marker. The pilot was then able to complete the go-around, whereupon he flew a normal traffic pattern and returned for a subsequent full-stop landing. He discovered the damage to the airframe after taxiing to his hangar and shutting the aircraft down. There was no evidence of any anomaly in the flight control or wheel brake systems.
The pilot's inadequate compensation for the changing wind conditions at the time of the landing. Factors include gusty, variable, crosswinds, and a runway marker near the edge of the runway the pilot was landing on.
On May 16, 2004, approximately 0945 mountain daylight time, a Cessna 185A, N1624H, impacted a runway marker during a go-around from a planned full-stop landing at Polson Airport, Polson, Montana. The private pilot, who was the sole occupant, was not injured, but the aircraft, which is owned and operated by the pilot, sustained substantial damage. The 14 CFR Part 91 personal pleasure flight, which originated at the Polson Airport about 15 minuets earlier, was being operated in visual meteorological conditions. No flight plan had been filed. There was no report of an ELT transmission. According to the pilot, he was performing a series of touch-and-go landings in variable gusty wind conditions in order to "...maintain proficiency on a gusty day." After three successful touch-and-go landings, the pilot decided to make the next landing a full-stop termination of the flight. During the subject landing, the wind shifted from a quartering headwind to a quartering tailwind, and although the touchdown was uneventful, during the landing roll the aircraft suddenly started turning toward the side of the runway. Although the pilot applied control inputs in an attempt to keep the aircraft on the runway, he was unable to overcome the effects of the varying wind conditions, and the aircraft departed the side of the runway. He therefore added full power in order to regain control and execute a go-around. During that sequence of events the left wing contacted the ground and the left horizontal stabilizer impacted a runway marker. The pilot was then able to complete the go-around, whereupon he flew a normal traffic pattern and retuned for a subsequent full-stop landing. He discovered the damage to the airframe after taxiing to his hanger and shutting the aircraft down. According to the FAA inspector who responded to the accident, there was no evidence of any anomaly in the flight control or wheel braking systems.