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.
Baker City, OR
As the pilot turned the aircraft onto the final approach leg of the traffic pattern, he referenced the Precision Approach Path Indicator (PAPI) of the landing runway. The PAPI indicated that the aircraft was above the standard glidepath, so the pilot reduced engine power to help the aircraft descend to glidepath altitude. According to the pilot, the aircraft "dropped too fast" and he applied power in an attempt to correct the descent rate. The aircraft then stalled above the runway and bounced on touchdown. The pilot recovered from the bounced landing and was able to taxi the aircraft back to the ramp. A post accident inspection revealed that the aircraft's firewall was bent.
The pilot's failure to maintain airspeed and misjudged flare during landing.
As the pilot turned the aircraft onto the final approach leg of the traffic pattern, he referenced the Precision Approach Path Indicator (PAPI) of the landing runway. The PAPI indicated that the aircraft was above the standard glidepath, so the pilot reduced engine power to help the aircraft descend to glidepath altitude. According to the pilot, the aircraft "dropped too fast" and he applied power in an attempt to correct the descent rate. The aircraft then stalled above the runway and bounced on touchdown. The pilot recovered from the bounced landing and was able to taxi the aircraft back to the ramp. A post accident inspection revealed that the aircraft's firewall was bent.