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.
Pittsburgh, PA
While on the downwind leg of the airport traffic pattern for runway 17, the pilot was advised over the airport traffic frequency that winds were favoring runway 35. The pilot elected to continue the approach to runway 17, since he could "clearly see the wind sock," which was indicating a "direct crosswind." During the landing flare, the pilot encountered an "updraft" and landed approximately "half way" down the 3,500-foot-long runway. Upon touchdown, he retracted the wing flaps, applied "very strong" pressure on the brakes, and made "shallow turns" in an attempt to stop the airplane. The airplane ran off the end of the runway, and came to rest in a ditch approximately 10 to 20 feet beyond the runway edge. A Federal Aviation Administration inspector who examined the airplane after the accident reported that it sustained substantial damage to the engine firewall, and exhibited extensive wrinkling and buckling of the fuselage, particularly at the wing roots. The pilot reported no mechanical anomalies. The nearest weather reporting station, located 12 nautical miles northwest of the accident site, reported wind direction variable between 280 degrees and 350 degrees at 7 knots at the time of the accident. The pilot stated that he should have landed on runway 35, since there were "several hills" on the approach to runway 17, and "turbulence and updrafts made speed control and altitude control difficult." In addition, runway 17 had a "downhill slope."
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - C
While on the downwind leg of the airport traffic pattern for runway 17, the pilot was advised over the airport traffic frequency that winds were favoring runway 35. The pilot elected to continue the approach to runway 17, since he could "clearly see the wind sock," which was indicating a "direct crosswind." During the landing flare, the pilot encountered an "updraft" and landed approximately "half way" down the 3,500-foot long runway. Upon touchdown, he retracted the wing flaps, applied "very strong" pressure on the brakes, and made "shallow turns" in an attempt to stop the airplane. The airplane ran off the end of the runway, and came to rest in a ditch approximately 10 to 20 feet beyond the runway edge. A Federal Aviation Administration inspector who examined the airplane after the accident reported that it sustained substantial damage to the engine firewall, and exhibited extensive wrinkling and buckling of the fuselage, particularly at the wing roots. The pilot reported no mechanical anomalies. The nearest weather reporting station, located 12 nautical miles northwest of the accident site, reported wind direction variable between 280 degrees and 350 degrees at 7 knots at the time of the accident. The pilot stated that he should have landed on runway 35, since there were "several hills" on the approach to runway 17, and "turbulence and updrafts made speed control and altitude control difficult." In addition, runway 17 had a "downhill slope."