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.
Lynchburg, VA
The pilot reported that, during landing, the airplane approached with "extra speed" and ballooned in the landing flare. He added that, "instantly my training took over" and he applied power to go-around, but then also remembered he could not go around when landing in this direction, at this airport, due to terrain and obstacles. He further added that he then reduced power to idle and "stalled the airplane to the ground" and impacted the remining runway hard. Subsequently, he taxied the airplane to the ramp without further incident. The ailerons, wings, and firewall sustained substantial damage. During a telephone conversation with the NTSB investigator-in-charge, the pilot reported that he had flown into this airport numerous times prior to the accident and knew that, "once you get to the powerlines you are committed to landing." The power lines were located about ¼ nautical miles from the runway threshold. The pilot did not report that there were any preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. The Federal Aviation Administration Chart Supplement for the airport stated in part: "Land Rwy [runway] 28 (west) tkf [takeoff] Rwy [runway] 10 (east)." The pilot reported that the landing was on runway 28.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Incorrect use/operation - C
The pilot reported that, during landing the airplane approached with "extra speed" and ballooned in the landing flare. He added that, "instantly my training took over" and he applied power to go-around, but then also remembered you "cannot go around" when landing in this direction, at this airport, due to terrain and obstacles. He further added that, he then reduced power to idle and "stalled the airplane to the ground" and impacted the remining runway hard. Subsequently, he taxied the airplane to the ramp without further incident. The ailerons, wings, and firewall sustained substantial damage. During a telephone conversation with the NTSB investigator-in-charge, the pilot reported that he had flown into this airport numerous times prior to the accident and knew that, "once you get to the powerlines you are committed to landing." The power lines were located about one 1/4 nautical miles from the runway threshold. The pilot did not report that there were any preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. The Federal Aviation Administration Chart Supplement for the airport stated in part: "Land Rwy [runway] 28 (west) tkf [takeoff] Rwy [runway] 10 (east). The pilot reported that the landing was on runway 28.