NTSB CAROL · Event
Event ERA11LA491
Aircraft involved
Probable cause & findings
The pilot did not maintain directional control during the landing roll.
Factual narrative
On September 5, 2011, about 1905 eastern daylight time, a Cessna TR182, N950RC, registered to Coral Bay Company, operated by a private individual, had a runway excursion during the landing roll at Bay Bridge Airport (W29), Stevensville, Maryland. Instrument meteorological conditions prevailed at the time and an instrument flight rules flight plan was filed for the 14 Code of Federal Regulations (CFR) Part 91 personal flight from Savannah/Hilton Head International Airport (SAV), Savannah, Georgia, to W29.The airplane sustained substantial damage and the certificated commercial pilot, the sole occupant, was not injured. The flight originated from SAV about 1600. The pilot stated that he executed a GPS approach to runway 29 though most of the approach was flown in visual meteorological conditions. It was not raining at the time of the accident but the runway was damp/wet and the wind was from 290 degrees at 4 knots based on the automated weather observing station located on the airport. The touchdown point was about 200 feet from the threshold of the approach end of runway 29, and after touchdown he equally and moderately applied the brakes. The airplane “pulled sharply” to the left and he released the brakes. The airplane departed the left side of the runway and rolled onto wet grass where he again applied the brakes but reported he was not able to brake effectively. The airplane rolled into a swale which partially collapsed the nose landing gear. The pilot further stated that he did not notice any discrepancy with the brakes at the departure airport. Postaccident inspection of the airplane by an FAA inspector revealed damage to the firewall. The airplane was raised on jacks and the normal brake system appeared to be in good shape with the exception that the brake caliper locating pins were “stiff” which did not allow the calipers to move freely. The brake reservoirs were full of fluid, and no leaks were noted. The brakes operationally checked satisfactory with no indications of a brake failure noted. Inspection of the main landing gear tires revealed no flat spots indicating that the brakes were locked up on landing. A surface observation taken at the accident airport at 1906, or about 1 minute after the accident indicated the wind was from 250 degrees at 3 knots. The pilot was cleared for a global positioning system approach to runway 29, which was damp/wet, although most of the approach was flown in visual meteorological conditions. He reported that he equally and moderately applied the brakes after touchdown but that the airplane pulled sharply to the left. He released the brakes and the airplane departed the left side of the runway and rolled onto wet grass with ineffective braking. The airplane then rolled into a swale, which partially collapsed the nose landing gear. No discrepancies of the brake system were noted by the pilot at the departure airport and a postaccident examination revealed no evidence of a preimpact failure or mechanical malfunction. There were no flat spots on either of the main landing gear tires and no leaks of the brake system were noted. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Personnel issues-Task performance-(general)-(general)-Pilot - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
- — Environmental issues-Physical environment-Terrain-Wet/muddy-Contributed to outcome
Verbatim from NTSB's published report. Source file
NTSB_2011_ERA11LA491.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (runway excursion). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Runway Excursion — SKYbrary Knowledge Base
SKYbrary runway excursion review — RE-OE (overruns) + RE-LO (lateral). Risk drivers: long landing, high approach speed, contaminated surface, tailwind, mis-set autobrakes.
- NTSB Aircraft Accident Reports 2019 · Accident report
Embraer ERJ 175 Runway Excursion at Charlotte Douglas
Republic Airline ERJ-175 runway excursion CLT, January 2018. Examines a low-energy runway excursion involving misuse of autobrakes + thrust reverser response after a high-crosswind landing on a contam…
- NASA NTRS 2025 · Presentation
Uncovering Resilient Behavior in the Aviation Safety Reporting System Using Large Language Models
Resiliency is present in everyday life, both in system design and exhibited by the operators that function within these systems.
- NASA NTRS 2025 · Conference Paper
Uncovering Resilient Behavior in the Aviation Safety Reporting System Using Large Language Models
Resiliency is present in everyday life, both in system design and exhibited by the operators that function within these systems.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Runway Safety Initiative Final Report (RSI)
Foundation Runway Safety Initiative final report — comprehensive analysis of runway excursion + incursion risk drivers worldwide.
- Semantic Scholar 2020 · Article
Towards online prediction of safety-critical landing metrics in aviation using supervised machine learning
Abstract In recent years, due to the increased availability of data and improvements in computing power, application of machine learning techniques to various aviation safety problems for identifying,…
Browse the full corpus — academia portal ↗