NTSB CAROL · Event
Event CEN18LA041
Registry · N7111W
FAA Aircraft Registry record.
Make / Model
CESSNA 182S
Year of manufacture
1999 · 18 years old at event
TCDS
3A13 · TEXTRON AVIATION INC
Engine
LYCOMING IO-540 SER (300 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19990603
ADS-B equipped
Yes — Mode-S A98254
Registrant of record
BETTER LIVING AVIATION INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot’s failure to maintain directional control during takeoff.
Factual narrative
On November 22, 2017, about 1040 central standard time, a Cessna 182S airplane, N7111W departed the runway and impacted terrain while taking off from the Bolingbrook's Clow International Airport (1C5), Bolingbrook, Illinois. The pilot, sole occupant, was not injured and the airplane was substantially damaged during the accident. The airplane was registered to Better Living Aviation, Inc, Wilmington, Delaware, and operated by A&M Aviation, Bolingbrook, Illinois, under the provisions of 14 Code of Federal Regulations Part 91 as personal flight. Visual meteorological conditions prevailed at the time. The local flight was originating at the time of the accident. The pilot reported that he used the airplane's checklist to complete a preflight inspection. He taxied the airplane to the warm-up pad to complete the checklist items and configure the airplane for the takeoff. He then taxied on to runway 36. The pilot continued that he aligned the airplane with the centerline and slowly added takeoff power. The initial takeoff roll was straight down the runway, but the airplane started to turn right. The pilot was unable to correct the turn or stop the airplane, before the airplane exited the side of the runway. The airplane became airborne, settled and impacted a ditch, and came to rest upside down. The responding Federal Aviation Administration (FAA) inspector reported that the airplane's nose landing gear, and wings were damaged, and the fuselage sustained substantial damage during the accident. Additionally, an examination of the airplane's steering and rudder system did not find any preimpact abnormalities. The pilot added that he did not remember what else he did when the airplane started to turn, and why it did not work. Nor did he noticed any undirected braking of the airplane, or unusual taxi characteristics of the airplane prior to it turning to the right. At 1055, the automated weather observation facility located at the Lewis University Airport (KLOT), about 5 miles south of the accident site recorded; wind at 240 degrees at 4 knots. The commercial pilot completed a preflight inspection of the airplane before departing on a local flight. Upon adding power for takeoff, the airplane initially tracked straight but then started to turn right; the pilot was unable to correct the turn or stop the airplane, and the airplane exited the side of the runway before coming to rest inverted. An examination of the steering and rudder system did not find any preimpact abnormalities. The pilot added that he did not notice any undirected braking or unusual taxi characteristics of the airplane before the takeoff. An automated weather observation facility located about 5 miles south of the accident site recorded a crosswind at 4 knots about the time of the accident, which the pilot should have been able to compensate for. Given the lack of mechanical anomalies and light wind conditions, it is likely that the pilot failed to maintain directional control during the takeoff, which resulted in a runway excursion. 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-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_2017_CEN18LA041.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 ↗