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.
Oshkosh, WI
The pilot stated that, during landing, he was concentrating on touching down at a particular location, and he forced the airplane onto the runway at an airspeed that was too fast. The airplane bounced two or three times and traveled off the right side of the runway/taxiway into the grass where it contacted a taxiway light. The pilot stated that the brakes were ineffective due to the speed and the grass. The airplane continued across a service road where it contacted six heavy military vehicles that were among a row of parked vehicles. Both wings and the firewall were substantially damaged. The pilot stated that there was nothing mechanically wrong with the airplane.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
The airplane was arriving at EAA AirVenture when the accident occurred. During AirVenture, the 6,300 foot long taxiway that parallels the right side of runway 36 is designated as runway 36R and is used for takeoffs and landings as determined by the control tower. In addition, there are four colored dots placed on runway 36L and pilots are issued landing instructions in reference to the dots. The pilot reported he was cleared to land on runway 36R, abeam the “yellow dot” which was on runway 36L. The yellow dot was located 2,900 feet from the runway threshold. The pilot stated he was concentrating on touching down at the yellow dot and he forced the airplane onto the runway at too fast of an airspeed. The airplane bounced two or three times and traveled off the right side of the runway/taxiway into the grass where it contacted a taxiway light. The pilot stated the brakes were ineffective due to the speed and the grass. The airplane continued across a service road where it contacted six heavy military vehicles that were among a row of parked vehicles. Both wings and the firewall were substantially damaged. The pilot stated there was nothing mechanically wrong with the airplane.