NTSB CAROL · Event
Event ERA15CA056
Registry · N60155
FAA Aircraft Registry record.
Make / Model
CESSNA 172S
Year of manufacture
2006 · 8 years old at event
Engine
LYCOMING IO-360-L2A (180 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
20060501
ADS-B equipped
Yes — Mode-S A7CE1B
Registrant of record
JLS AVIATION LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The student pilot's failure to maintain airplane control during the initial climb, resulting in a runway excursion and substantial damage to the engine firewall. The student pilot's lack of overall flying experience was a factor.
Factual narrative
According to the student pilot, he was performing his second solo flight, and he reported a total flying time of 45 hours. As the airplane became airborne during the initial takeoff, it "…violently veered 90 degrees to the left." He immediately applied right rudder and reduced the throttle to idle. The airplane was landed on the left side of the runway and it departed the runway surface, into the grass. It then crossed the intersecting runway. As the airplane approached a taxiway, the pilot brought it to a full stop. A Federal Aviation Administration inspector reported that the excursion resulted in a buckling of the engine firewall. The student pilot did not report any mechanical problems with the airplane at the time of the accident. A review of local wind conditions at the airport did not reveal evidence of gusts. According to the student pilot, he was performing his second solo flight, and he reported a total flying time of 45 hours. As the airplane became airborne during the initial takeoff, it "…violently veered 90 degrees to the left." He immediately applied right rudder and reduced the throttle to idle. The airplane was landed on the left side of the runway and it departed the runway surface, into the grass. It then crossed the intersecting runway. As the airplane approached a taxiway, the pilot brought it to a full stop. A Federal Aviation Administration inspector reported that the excursion resulted in a buckling of the engine firewall. The student pilot did not report any mechanical problems with the airplane at the time of the accident. A review of local wind conditions at the airport did not reveal evidence of gusts. 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 Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Lateral/bank control-Not attained/maintained - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Student/instructed pilot - C
- F Personnel issues-Experience/knowledge-Experience/qualifications-Total experience-Student/instructed pilot - F
Verbatim from NTSB's published report. Source file
NTSB_2014_ERA15CA056.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 ↗