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.
Creswell, OR
The pilot entered the traffic pattern and planned to land on runway 33. Initially, no traffic was observed in the pattern; however, just before announcing the base turn another airplane pilot announced that he was turning base for runway 33. The pilot observed the other airplane, which was ahead of his airplane, and he extended his downwind leg for spacing. The pilot indicated that he needed to perform a series of "S" turns to "delay landing" for spacing with the preceding airplane while heading back to the runway's center line. The pilot stated that he arrived over the threshold with above normal sink rate and below normal forward speed. The airplane bounced on the runway, the pilot lost directional control, and the airplane ground looped. The airplane came to rest in the grass with a collapsed left main landing gear. Upon the pilot's subsequent examination of the airframe, he observed that the left wing spar was cracked. The pilot said that the airplane's final approach flight path was not stabilized and that he should have performed a go-around.
The pilot's failure to maintain a stabilized approach, inadequate recovery from a bounced landing, and failure to maintain directional control.
According to the accident pilot, he took off for the local area personal flight at 0925. After performing a few maneuvers and sightseeing, he returned to the airport, entered the traffic pattern, and planned to land on runway 33. Initially, no traffic was observed in the pattern. However, just before announcing "turning base" another airplane pilot announced that he was turning base for runway 33. The accident pilot observed the other airplane, which was ahead of his airplane, and he extended his downwind leg for spacing. Thereafter, the accident pilot indicated that he needed to perform a series of "S" turns to "delay landing" while heading back to the runway's center line. The pilot stated that he arrived over the threshold with above normal sink rate and below normal forward speed. The airplane bounced on the runway, the pilot lost directional control, and the airplane ground looped. The airplane came to rest in the grass with a collapsed left main landing gear. Upon the pilot's subsequent examination of the airframe, he observed that the left wing spar was cracked. The pilot acknowledged in his completed "Pilot/Operator Aircraft Accident Report" that the airplane's final approach flight path was not stabilized, and he should have performed a go-around.