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.
Tallahasee, FL
The pilot of the airplane stated that he was flying the global-positioning-system approach for runway 9, when the active runway was changed to runway 27. He then flew the instrument-landing-system approach for runway 27, using left crosswind correction. After touchdown, while on centerline, a microburst "lifted the airplane in the air and slammed it down," compressing the nose strut and resulting in a subsequent propeller strike. Approximately 35 minutes before the accident, the winds were reported from 130 degrees at 10 knots, gusting to 15 knots. No microburst or windshear activity was reported by the control tower at the time of the accident. The pilot did not report the accident until he tried to obtain a ferry permit about 2 months later.
The pilot's failure to maintain aircraft control after touchdown. Contributing to the accident were the gusting winds.
The pilot of the Piper PA-34-200T stated that he was flying the global positioning system (GPS) approach for runway 9, when the active runway was changed to runway 27. He then flew the instrument landing system (ILS) approach for runway 27, using left crosswind correction. After touchdown, while on centerline, a microburst "lifted the airplane in the air and slammed it down," compressing the nose strut and resulting in a subsequent propeller strike. Approximately 35 minutes before the accident, the winds were reported from 130 degrees at 10 knots, gusting to 15 knots. No microburst or wind shear activity was reported by the control tower at the time of the accident. The pilot did not report the accident until he tried to obtain a ferry permit about 2 months later.