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.
Castlerock, MN
The pilot was flying his experimental airplane, practicing touch-and-go landings on his 1,400 foot long private grass airstrip. The weather was clear. During his third touch-and-go, he determined that he was going to land too long so he made a go-around. As he added power for the go-around, he started to feel vibrations and thought that he had a propeller malfunction. The vibrations continued regardless of power setting, so he shut down the engine and intentionally stalled the airplane about 10 feet above the ground to avoid rolling over when the airplane settled to the ground. The airplane came to rest in a corn field. The pilot saw that a fire had started in the engine compartment after ground impact, so he quickly exited the airplane. A post-crash fire then completely consumed the airplane. Examination of the airplane after the accident did not show any evidence of preimpact mechanical malfunction or abnormalities, although the fire damage was too extensive to specifically determine the reason for presumed propeller malfunction. After the examination, the pilot maintained that he was certain that there was a problem with the propeller and that it was the cause of the accident.
Propeller system failure during a go-around maneuver resulting in a forced landing. Contributing to the severity of damage to the airplane was the postimpact fire.
The pilot was flying his experimental airplane, practicing touch-and-go landings on his 1,400 foot long private grass airstrip. The weather was clear. During his third touch-and-go, he determined that he was going to land too long so he made a go-around. As he added power for the go-around, he started to feel vibrations and thought that he had a propeller malfunction. The vibrations continued regardless of power setting, so he shut the engine down and intentionally stalled the airplane about 10 feet above the ground to avoid rolling over when the airplane settled to the ground. The airplane came to rest in a corn field. The pilot saw that a fire had started in the engine compartment after ground impact, so he quickly exited the airplane. A post-crash fire then completely consumed the airplane. Examination of the airplane after the accident did not show any evidence of preimpact mechanical malfunction or abnormalities, although the fire damage was too extensive to specifically determine the reason for presumed propeller malfunction. After the examination, the pilot maintained that he was certain that there was a problem with the propeller and that it was the cause of the accident.