NTSB CAROL · Event
Event CEN22LA103
Aircraft involved
Probable cause & findings
The pilot’s loss of directional control during the takeoff for reasons that could not be determined based on the available evidence, which resulted in a runway excursion.
Factual narrative
On January 18, 2022, about 1100 central standard time, a Cessna 120 airplane, N90129, was substantially damaged when it was involved in an accident near Sturtevant, Wisconsin. The private pilot sustained serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Security camera footage was obtained from the Sylvania Airport (C89), Sturtevant, Wisconsin. A review of the footage showed the airplane was attempting to depart to the east, using runway 08R. The takeoff roll was initiated and about a quarter way down the length of the runway, the airplane departed the runway to the left (north). The footage showed the airplane travel over a flat grass field with the engine running. The footage did not show the airplane become airborne at any time, and the tailwheel appeared to remain on the ground during the runway excursion. The airplane came to rest after it impacted the cabin of an unoccupied, parked fuel truck. The pilot reported he recalled taxiing for takeoff and applying engine power for the takeoff, however he was unable to recall any additional events. The airplane sustained substantial damage to the left wing, the left-wing lift struts, and the fuselage. Postaccident examination of the airframe revealed no mechanical anomalies. Flight control continuity and airframe to engine control continuity was established. The main landing gear brake lines sustained impact damage, which precluded a system brake test. The main wheels were found free to rotate, and the brake pads and rotors for both wheels showed minimal wear. No signs of foreign object debris jamming or restricting operation of the cockpit controls was noticed. The pilot had reported no medical conditions and no use of medications to the FAA. Ketamine, fentanyl, propofol, and lidocaine were administered in the prehospital and immediate stages of his hospital care. No note is made in the hospital documentation of any identification of underlying natural disease such as a stroke or heart attack that may have been affecting the pilot prior to the collision of his airplane with the fuel truck. Toxicology testing was performed by the FAA’s Forensic Sciences Laboratory on blood and urine left over from specimens obtained during the pilot’s initial hospital admission. The results included medications administered during his post-crash care including ketamine and its metabolite norketamine, fentanyl and its metabolite norfentanyl, lidocaine, and propofol. In addition, atorvastatin, famotidine, and fexofenadine were identified, which are non-impairing medications. A review airport security camera footage showed the airplane was attempting to depart to the east. About a quarter way down the length of the runway after the beginning of the takeoff roll, the airplane departed the runway to the left (north). Airport security video footage showed the airplane travel over a flat grass field with the engine running. The footage did not show the airplane become airborne at any time, and the tailwheel appeared to remain on the ground during the runway excursion. The airplane came to rest after it impacted the cabin of an unoccupied, parked fuel truck. The pilot reported he recalled taxiing for takeoff and applying engine power for the takeoff; however, he was unable to recall any additional events. Postaccident examination of the airframe revealed no mechanical anomalies. The postaccident emergency care did not identify any medical conditions the pilot had that might have contributed to the accident. The pilot’s pre-accident use of atorvastatin, famotidine, and fexofenadine, all non-impairing medications identified by toxicology testing of the pilot’s samples, also did not contribute to the circumstances of this accident. It is likely a loss of control occurred during the takeoff, which resulted in a runway excursion and a collision with an object. Based on the available evidence, the reason for the loss of control could not be determined. 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).
- — Not determined-Not determined-(general)-(general)-Unknown/Not determined
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained
- — Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot
Verbatim from NTSB's published report. Source file
NTSB_2022_CEN22LA103.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 (loss of control, 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.
- Embry-Riddle Scholarly Commons 2017 · Conference paper
Energy Safety Management: Mitigating Loss of Control Inflight
Under the new Airman Certification Standards (ACS), the Federal Aviation Administration (FAA) has mandated for the first time that private and commercial pilot candidates demonstrate understanding of …
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Loss of Control In-Flight (LOC-I) — SKYbrary Knowledge Base
SKYbrary comprehensive knowledge-base entry on Loss of Control In-Flight — definitions, contributing factors, accident case studies (Air France 447, Colgan 3407), and prevention strategies.
- 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 2022 · Accident report
Loss of Control on Takeoff in Icing Conditions — Citation 560XL
Cessna Citation 560XL fatal takeoff icing accident, March 2018. Investigation of a Citation 560XL loss-of-control takeoff accident in icing conditions.
- Semantic Scholar 2021 · Article (Aviation)
ANALYSIS OF GENERAL AVIATION FIXED-WING AIRCRAFT ACCIDENTS INVOLVING INFLIGHT LOSS OF CONTROL USING A STATE-BASED APPROACH
Inflight loss of control (LOC-I) is a significant cause of General Aviation (GA) fixed-wing aircraft accidents. The United States National Transportation Safety Board’s database provides a rich source…
Browse the full corpus — academia portal ↗