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.
Helena, MT
The pilot was returning to his home airport and approached the airport from the north. He was initially cleared to land runway 27 but requested to land runway 17 because he was conveniently aligned with it. When about five miles from the airport he slowed the airplane, lowered the landing gear, and “pulled the throttle all the way back.” He stated that he did not recall “raising the propeller speed.” He further stated that he was too high, and extended the flaps to full down, which was something he normally did not do. During the landing flare, he waited for the airplane to settle onto the runway. He realized that the airplane had not touched down as it passed the midpoint of the 2,989 ft long runway and initiated a go-around. During the go-around, the pilot initially thought he had pushed the throttle control full forward, but when “nothing happened,” he looked down and realized he had pushed the mixture control forward. He added throttle and felt the airplane pick up speed. The pilot recalled that he pulled the yoke back to clear the airport perimeter fence and felt the airplane climb. The pilot stated that he had a positive rate of climb and thought he was high enough to begin a left turn and considered raising the flaps and contacting the tower when the airplane impacted the ground and slid into a building. A security video captured the airplane in a wings level attitude beyond the departure end of the runway. The airplane appeared to reach a height of about 20 ft above ground level before the left wing dropped and the airplane descended. Subsequently, it impacted a road and slid into a building, which resulted in substantial damage to both wings. Postaccident pictures of the airplane showed that the landing gear was extended and the flaps were retracted. The throttle control was pulled out about ½-inch, and the mixture control was about 1 ½-inch from full forward. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
The pilot’s failure to properly configure the airplane during a go-around which resulted in the airplane exceeding its critical angle of attack and an aerodynamic stall at a low altitude.
The pilot was returning to his home airport and approached the airport from the north. He was initially cleared to land runway 27 but requested to land runway 17 because he was conveniently aligned with it. When about five miles from the airport he slowed the airplane, lowered the landing gear, and “pulled the throttle all the way back.” He stated that he did not recall “raising the propeller speed.” He further stated that he was too high, and extended the flaps to full down, which was something he normally did not do. During the landing flare, he waited for the airplane to settle onto the runway. He realized that the airplane had not touched down as it passed the midpoint of the 2,989 ft long runway and initiated a go-around. During the go-around, the pilot initially thought he had pushed the throttle control full forward, but when “nothing happened,” he looked down and realized he had pushed the mixture control forward. He added throttle and felt the airplane pick up speed. The pilot recalled that he pulled the yoke back to clear the airport perimeter fence and felt the airplane climb. The pilot stated that he had a positive rate of climb and thought he was high enough to begin a left turn and considered raising the flaps and contacting the tower when the airplane impacted the ground and slid into a building. A security video captured the airplane in a wings level attitude beyond the departure end of the runway. The airplane appeared to reach a height of about 20 ft above ground level before the left wing dropped and the airplane descended. Subsequently, it impacted a road and slid into a building, which resulted in substantial damage to both wings. Postaccident pictures of the airplane showed that the landing gear was extended and the flaps were retracted. The throttle control was pulled out about ½-inch, and the mixture control was about 1 ½-inch from full forward. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.