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.
St Charles, MO
The airplane was substantially damaged when it impacted the runway during landing. The pilot reported that he entered a right downwind for runway 27. Upon turning final, he realized that the airplane was high. He corrected by increasing the flap setting to 30 degrees and reducing power in order to descend "a little quicker." He stated, "As I came over the threshold, I realized I was coming down too fast, but still felt I was OK. In the last seconds, I realized I was in trouble. The force with which we hit the runway was much harder than I expected." The airplane bounced upon contact with the runway. The pilot noted, "I thought it would bounce and then settle down. When it porpoised, I failed to take action to correct it, resulting in the wreck."
The pilot's failure to properly judge the landing flare and his inadequate recovery from the resulting bounced landing. A contributing factor was the inadvertent pilot induced oscillation (porpoise) after initial runway contact.
The airplane was substantially damaged when it impacted the runway during landing. The pilot and passenger were not injured. The pilot reported that he was returning from a local flight when the accident occurred. He noted that the winds were calm. The pilot reported that he entered a right downwind for runway 27. Upon turning final, he realized that the airplane was high. He corrected by increasing the flap setting to 30 degrees and reducing power in order to descend "a little quicker." He stated, "As I came over the threshold, I realized I was coming down too fast, but still felt I was OK. In the last seconds, I realized I was in trouble. The force with which we hit the runway was much harder than I expected." The pilot stated that the airplane bounced upon contact with the runway. He noted, "I thought it would bounce and then settle down. When it porpoised, I failed to take action to correct it, resulting in the wreck." The pilot reported no mechanical malfunctions or failures associated with the aircraft prior to the accident. The post accident examination revealed that the nose landing gear had collapsed and the firewall was damaged.