BFO96LA002
1995-10-04 · ANNAPOLIS, Maryland, United States · None · 1 aircraft · Status: Completed
Airport ANP
Current FAA registration · N6648W
- Make / Model
- BEECH 95-B55 (T42A)
- Engine
- CONT MOTOR I0-470 SERIES (260 hp)
- Seats / Engines
- 6 seats · 2 engines
- Last airworthiness date
- 19790529
- ADS-B equipped
- Yes — Mode-S A8C69A
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
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.
Factual narrative
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." 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. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1995_BFO96LA002.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (go-around). All research papers
- NASA NTRS 2025 · Conference Paper A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research) Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace) Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes) Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…