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.
Baldwin City, KS
The pilot reported that he rented the accident airplane for the purpose of gaining night cross-country flight experience. He flew to two other airports and made successful landings at each airport. On the accident flight, as the airplane approached the airport, the pilot attempted to activate the pilot-controlled runway lights but was unsuccessful. He elected to continue the landing attempt to the grass runway. He stated that the landing approach was on-speed per the airplane flight manual, and he touched down on the runway but was unable to stop the airplane before it impacted trees at the end of the runway. The pilot reported that there were no mechanical malfunctions or failures of the airplane that would have precluded normal operations. The airplane received substantial damage to the left wing. The destination airport had a 3,303 ft. by 80 ft. turf runway equipped with non-standard low-intensity runway lighting. The airport manager reported that the functionality of the pilot-controlled runway lighting system was confirmed following the accident.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained
The pilot reported that he rented the accident airplane for the purpose of gaining night cross-country flight experience. He flew to two other airports and made successful landings at each airport. On the accident flight, as the airplane approached the airport, the pilot attempted to activate the pilot-controlled runway lights but was unsuccessful. He elected to continue the landing attempt to the grass runway. He stated that the landing approach was on-speed per the airplane flight manual, and he touched down on the runway but was unable to stop the airplane before it impacted trees at the end of the runway. The pilot reported that there were no mechanical malfunctions or failures of the airplane that would have precluded normal operations. The airplane received substantial damage to the left wing. The destination airport had a 3,303 ft. by 80 ft. turf runway equipped with non-standard low-intensity runway lighting. The airport manager reported that the functionality of the pilot-controlled runway lighting system was confirmed following the accident.