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.
Corona, CA
The pilot reported that, because the automated airport weather station report was unavailable prior to landing, he overflew the airport and determined from the windsock that runway 24 was favored. About the time the airplane touched down, it encountered a strong wind gust, which prompted the pilot to initiate a go-around. As he applied power, the airplane drifted to the left, and his attempts to correct back to the right were unsuccessful. The airplane subsequently collided with a stationary airplane, an automobile, and a hangar, which resulted in substantial damage to both wings and the fuselage. A review of the reported weather data for the airport revealed that, around the time of the accident, wind gusts of about 25 knots from 040 degrees were recorded. The pilot reported no mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
The pilot reported that as the automated weather reporting facility was inoperable prior to landing, he overflew the airport and determined from the windsock that runway 24 was favored. The pilot stated that about the time he touched down he encountered a strong wind gust, which prompted him to initiate a go-around. The pilot added that as he applied power the airplane drifted to the left and that his attempts to correct back to the right were unsuccessful. The airplane subsequently collided with a stationary airplane, an automobile and a hangar. The airplane came to rest in an upright position and had sustained substantial damage to both wings and its fuselage. A review of the Aviation Routine Weather Report (METAR) data for the airport revealed that from about 34 minutes prior to, to about 26 minutes after the accident, wind gusts were reported to be from 040 degrees at 24 knots and 25 knots respectively. The pilot reported no mechanical malfunctions or failures with the airplane that would have precluded normal operation.