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.
Annapolis, MD
The pilot reported that when he arrived at the destination airport, the active runway was wet, with areas of standing water. He stated that when the airplane touched down, he believed there was sufficient runway remaining to bring the airplane to a stop. However, he reported that when he applied brakes, he noted no braking action. Also, he reported the airplane ran off the departure end of the runway and veered left, where it impacted the airport boundary fence. The pilot noted that the accident might have been prevented if he had made a go-around at the first sign of no braking action, or if he had retracted the flaps to obtain better breaking action.
the pilot's improper planning/decision, and/or failure to go around while there sufficient airspeed and runway remaining during the approach/landing. Factors relating to the accident were: standing water on the runway, and resultant hydroplaning conditions.
On October 4, 1995, at 2130 eastern daylight time, a Beech BE55, N6648W, piloted by the owner/operator, ran off the end of runway 12 after landing at Lee Airport, in Annapolis, Maryland. The pilot and the one passenger, the sole occupants, reported no injuries. The airplane sustained substantial damage when it impacted a fence located off the departure end of the runway. Visual meteorological conditions prevailed for the flight, which operated on an IFR flight plan. The personal flight operated under 14 CFR Part 91, and originated from Elkins, West Virginia, at approximately 2030. The pilot reported that the airplane touched down "...just beyond..." the displaced threshold on runway 12, with full flaps extended. He stated that he "...determined [that there was] ample runway remaining to stop [the] aircraft. Applied brakes, no braking action, applied brakes to lock tires, still no braking action noted. Released brakes and reapplied, still no braking action." The pilot stated that after all attempts to stop the airplane failed, there was insufficient runway remaining to perform a go around. He reported that as the airplane departed the end of the runway, it veered left, and impacted the airport boundary fence. The pilot reported that the 2,100 foot long runway was wet, with areas of standing water. The pilot stated that the accident could have been prevented "...if go around [had been] initiated at very first sign of [no] braking action..." or by "...retracting flaps to facilitate killing lift and subsequent weight shift to wheels."