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.
Richland, WA
The student pilot reported that following an uneventful flight, as he entered the airport traffic pattern on the downwind leg, he was notified by another pilot that there was an airplane operating within the traffic pattern with no radio. The student pilot established visual contact with one airplane; however, he did not establish visual contact with the airplane operating without a radio until reaching the mid-field point on downwind. The student pilot stated that throughout the approach to landing, he maintained visual contact with the airplane until it would not be a factor. The student pilot subsequently landed the airplane with the landing gear in the retracted position, which resulted in structural damage to the fuselage. The student pilot stated that his attention was diverted between maintaining airspeed and a stable approach to the runway, while maintaining visual contact with the airplane that was not in radio contact. He added that he failed to do his before landing checklist as he normally does at the mid-field point on downwind and each turn in the traffic pattern. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
The pilot's failure to extend the landing gear prior to landing. Contributing to the accident was the pilot's diverted attention and not using a checklist.
The student pilot reported that following an uneventful flight, as he entered the airport traffic pattern on the downwind leg, was notified by another pilot that there was an airplane operating within the traffic pattern with no radio. The student pilot established visual contact with one airplane, however, did not establish visual contact with the airplane operating without a radio until reaching the mid-field point on downwind. The student pilot stated that throughout the approach to landing, he maintained visual contact with the airplane until it would not be a factor. The student pilot subsequently landed the airplane with the landing gear in the retracted position, which resulted in structural damage to the fuselage. The student pilot stated that his attention was diverted between maintaining airspeed and a stable approach to the runway, while maintaining visual contact with the airplane that was not in radio contact. He added that he failed to do his before landing checklist as he normally does at the mid-field point on downwind and each turn in the traffic pattern. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.