NTSB CAROL · Event
Event CEN10CA231
Aircraft involved
Probable cause & findings
The pilot's failure to maintain directional control while landing in a crosswind.
Factual narrative
The private pilot was attempting to land his single-engine airplane in a crosswind, when the airplane drifted to the right of the runway and touched down. The left wing lifted and the pilot reacted by adding power for a go-around, but realized that a go-around was not a suitable option and reduced engine power. The airplane veered toward a fence and a road, so the pilot again added power in an attempt to lift the airplane over them. Subsequently, the left wing hit a telephone pole and a car. The pilot reduced power and the airplane skidded to a stop and remained upright on the landing gear. The pilot reported no mechanical deficiencies with the airplane and stated the he failed to maintain control of the airplane after touchdown while attempting to land in a crosswind. The private pilot was attempting to land his single-engine airplane in a crosswind when the airplane drifted to the right of the runway and touched down. The left wing lifted and the pilot reacted by adding power for a go-around, but he then determined that a go-around was not a suitable option and reduced engine power. The airplane veered toward a fence and a road, so the pilot again added power in an attempt to lift the airplane over them. Subsequently, the left wing hit a telephone pole and a car. The pilot reduced power and the airplane skidded to a stop and remained upright on the landing gear. The pilot reported no mechanical deficiencies with the airplane and stated that he failed to maintain control of the airplane after touchdown while attempting to land in a crosswind. 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 Environmental issues-Conditions/weather/phenomena-Wind-Crosswind-Response/compensation - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-(general)-Not attained/maintained - C
Verbatim from NTSB's published report. Source file
NTSB_2010_CEN10CA231.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 (go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2022 · Journal article (JAAER)
SMS for Part 135 Commuter and On-Demand Operations - The Practitioner’s Perspective
On May 15th, 2017, N452DA, a Learjet 35A operated by Trans-Pacific Air Charter, LLC, departed from Philadelphia to Teterboro, New Jersey (TEB) on a positioning flight under 14 Code of Federal Regulati…
- NTSB Aircraft Accident Reports 2021 · Accident report
Crash of Atlas Air Flight 3591, Boeing 767-300 (N1217A)
Atlas Air 3591 crashed into Trinity Bay, Texas, February 23, 2019. Investigation of the in-flight loss-of-control crash of Atlas Air 3591 into Trinity Bay, Texas.
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
Editor's Note: Celebrating 35 Years of Scholarly Excellence
A letter from the editor, Dr. Dahai Liu, on the JAAER's 35th anniversary.
- NASA NTRS 2024 · Presentation
Part 135 and Business Operator Low Altitude Events: An Analysis of ASRS Reports
This presentation provides an aviation SME's human factors analysis of selected Low Altitude and Controlled Flight Towards Terrain (CFTT) events involving Part 135 and business jet operators as report…
- NASA NTRS 2022 · Conference Paper
The In-time Aviation Safety Management System Concept for Part 135 Operators
Transformations of the National Airspace System, such as envisioned with Advanced Air Mobility, will enable improvements for managing and assuring safety for Part 135 transportation of passengers and …
- Embry-Riddle Scholarly Commons 2020 · Journal article (IJAAA)
Analysis of Part 135 Aircraft Accidents to Facilitate Flight Data Monitoring
The scheduled and on-demand air services with Title 14 Code of Federal Regulations (CFR) Part 135 certificate are operating with relatively less stringent safety program criteria compared to Part 121 …
Browse the full corpus — academia portal ↗