ERA16LA122
2016-03-01 · Chester, Connecticut, United States · None · 1 aircraft · Status: Completed
Airport SNC
Current FAA registration · N94569
- Make / Model
- CESSNA 152
- Year of manufacture
- 1983 · 33 years old at event
- Engine
- LYCOMING 0-235 SERIES (115 hp)
- Seats / Engines
- 2 seats · 1 engine
- Last airworthiness date
- 19830408
- ADS-B equipped
- Yes — Mode-S AD2307
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot’s failure to maintain directional control of the airplane during the landing, which resulted in a runway excursion.
Factual narrative
On March 1, 2016, about 1130 eastern standard time, a Cessna 152, N94569, was substantially damaged during a runway excursion after landing at the Chester Airport (SNC), Chester, Connecticut. The private pilot was not injured. Visual meteorological conditions prevailed and no flight plan was filed for the local flight conducted under the provisions of 14 Code of Federal Regulations Part 91. According to a Federal Aviation Administration (FAA) inspector, the airplane landed on runway 35, a dry, 2,722-foot-long, 50-foot-wide, asphalt runway. After landing, the airplane continued off the right side on the runway, through a fence, and came to rest in the grassy area. According to witnesses, the airplane touched down about 200 feet beyond the midpoint of the runway. In a written statement the pilot stated that during rollout the right brake felt "ok", but the left brake felt "spongy", and that the airplane failed to stop before it departed the right side of the runway. According to a flight instructor for the operator, he and the pilot flew together for approximately two hours on both the day before and the day of the accident to complete a pre-rental checkout for the pilot in the accident airplane. At no time did the pilot mention anomalies or malfunctions of the airplane's braking system. Postaccident examination of the airplane by an FAA inspector and an airframe and powerplant mechanic revealed substantial damage to the engine firewall. Functional testing of the brakes showed that they were operational and did not reveal evidence any pre- or post-impact mechanical anomalies. A detailed examination of the brake revealed that there were no signs of hydraulic fluid or damage to the brake lines, and the brake pucks were nominal in size with no abnormal wear. The airplane was equipped with a Lycoming O-235 series, 108-horsepower engine. The airplane had been operated for about 100 hours since its most recent annual inspection, which was performed on September 1, 2015. The pilot reported 1,300 hours of total flight experience, of which 75 hours were in the accident airplane make and model. The private pilot completed a prerental checkout in the airplane and then departed for a local flight. Upon return to the airport, the pilot landed the airplane beyond the midpoint of the 2,722-ft-long runway, and the airplane then veered off the right side of the runway and impacted a fence. The pilot reported no anomalies with the brakes to the operator during his prerental checkout in the airplane. However, after the accident, he reported that one of the brakes felt "spongy" during the landing attempt. Postaccident examination of the brakes revealed no evidence of any anomalies that would have precluded normal operation. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
Verbatim from NTSB's published report. Source file
NTSB_2016_ERA16LA122.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 (runway excursion). All research papers
- 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 2023 · Article (EClinicalMedicine) Efficacy and tolerability of an endogenous metabolic modulator (AXA1125) in fatigue-predominant long COVID: a single-centre, double-blind, randomised controlled phase 2a pilot study
Summary Background ‘Long COVID’ describes persistent symptoms, commonly fatigue, lasting beyond 12 weeks following SARS-CoV-2 infection.