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.
Willis, MI
The pilot reported that he decided to utilize a known closed runway to land at the airport, due to the wind conditions. During the approach to the dry turf runway, he reported the airplane was “considerably too high and almost certainly too fast.” The pilot deployed full flaps, and the airplane started to descend “steeply” toward the end of the runway. When the airplane touched down on the runway, it bounced, and the airplane departed the runway straight ahead. The airplane crossed a road and impacted several trees next to a home. The airplane came to rest upright, and the pilot was able to egress from the airplane without further incident. The airplane sustained substantial damage to both wings. The pilot reported that there were no preimpact mechanical malfunctions or failures with the airframe or the engine that would have precluded normal operation. The pilot further reported that during the approach, he should have performed a go-around and established a stabilized approach. According to the Federal Aviation Administration Airport/Facility Directory, the runway the pilot selected to use is not listed for use at the airport.
The pilot’s failure to maintain a stabilized approach, that resulted in a runway excursion and subsequent collision with trees. Contributing to the accident, was the pilot’s decision to attempt to land to a closed runway.
The pilot reported that he decided to utilize a known closed runway to land at the airport, due to the wind conditions. During the approach to the dry turf runway, he reported the airplane was “considerably too high and almost certainly too fast.” The pilot deployed full flaps, and the airplane started to descend “steeply” toward the end of the runway. When the airplane touched down on the runway, it bounced, and the airplane departed the runway straight ahead. The airplane crossed a road and impacted several trees next to a home. The airplane came to rest upright, and the pilot was able to egress from the airplane without further incident. The airplane sustained substantial damage to both wings. The pilot reported that there were no preimpact mechanical malfunctions or failures with the airframe or the engine that would have precluded normal operation. The pilot further reported that during the approach, he should have performed a go-around and established a stabilized approach. According to the Federal Aviation Administration Airport/Facility Directory, the runway the pilot selected to use is not listed for use at the airport.