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.
Forest, VA
Before departing, the pilot referred to the Airport Facilities Directory to check the runway length at his destination. On arrival, he checked the windsock and determined that there was a direct crosswind, and decided to land on Runway 34, a 3,164-foot long runway. The pilot intentionally planned for a higher approach because of the 'limited light, and terrain.' As the airplane landed on Runway 34, about 60-65 MPH, with 30 degrees of flaps, the pilot noticed the gas pumps and hangers located on the northwest side of the airport abeam the airplane to his left. The airplane bounced once, began to float, and touched down again with about 240 feet of runway remaining. The pilot attempted to use maximum baking, but could not stop. The fuel pumps and hangers were located in a position that corresponded to about 800 feet remaining on Runway 34.
The pilot's misjudgment of distance/speed, also causal was his failure to execute a go-around. Contributing factors were the night conditions and the tailwind.
On June 28, 1999, about 2140 Eastern Daylight Time, a Cessna 182, N5481B, was substantially damaged while landing at the New London Airport (W90), Forest, Virginia. The certificated commercial pilot, and passenger were not injured. Visual meteorological conditions prevailed and no flight plan was filed for the personal fight conducted under 14 CFR Part 91. The pilot stated that the airplane was being repositioned from Roanoke Regional Airport, Roanoke, Virginia, to W90 for maintenance. Before departing, the pilot referred to the Airport Facilities Directory to check the runway length at W90. Arriving at W90, the pilot circled the airport to check the windsock, and determined there was a direct crosswind. A decision was made to land on Runway 34, a 3,164-foot long runway, as it was slightly uphill. The pilot intentionally planned for a higher approach because of the "limited light, and terrain." As the airplane landed on Runway 34, about 60-65 MPH, with 30 degrees of flaps, the pilot noticed the gas pumps and hangers located on the northwest side of the airport abeam the airplane to his left. The airplane bounced once, began to float, and touched down again with about 240 feet of runway remaining. The pilot attempted to use maximum braking, but could not stop. The airplane ran off the end of the runway, nosed over, and came to rest inverted on the side of a road. Review of the 1999 Virginia Airport Directory indicated that the fuel pumps and hangers were located in a position that corresponded to about 800 feet remaining on Runway 34. The weather at a nearby airport reported winds of 190 degrees at 10 knots.