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.
Waterford, MI
The pilot of the airplane reported that, while on an instrument flight rules approach to land in instrument meteorological conditions at night, he was "a little late descending" on the glideslope. He added that, during the approach, he increased the descent rate and became "a little right of course." He noticed approach lights but became "fixated" on the instruments while attempting to correct for being off course. Subsequently, the airplane struck the tops of trees, and he immediately pulled up. He landed without further incident. The airplane sustained substantial damage to the right wing, empennage, and fuselage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The automated weather observation system at the accident airport reported, about the time of the accident, that the wind was from 140° at 5 knots, visibility 3/4 statute mile, light rain, and clouds overcast at 200 ft. The pilot landed on runway 9 and flew the RNAV GPS runway 9 approach.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - C
The pilot of the airplane reported that, while on an instrument flight rules approach to land in instrument meteorological conditions at night, he was "a little late descending" on the glide slope. He added that, during the approach, he increased the descent rate and also became "a little right of course". He noticed approach lights, but became "fixated" on the instruments while attempting to correct for being off course. Subsequently, the airplane struck the tops of trees and he immediately pulled up. He landed without further incident. The airplane sustained substantial damage to the right wing, empennage and fuselage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The automated weather observation system at the accident airport reported, about the time of the accident, that the wind was from 140° at 5 knots, visibility ¾ statute mile, light rain, clouds overcast at 200 ft. The pilot landed on runway 9, flying the RNAV (GPS) runway 9 approach.