CEN18LA041 · Cessna 182S
Cessna 182S · Accident: loss of control on ground during takeoff
From Bolingbrook's Clow International Airport (1C5) to Bolingbrook's Clow International Airport (1C5)
Event
- NTSB case
- CEN18LA041
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 182S
- Aircraft type
- Cessna 182
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N7111W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bolingbrook's Clow International Airport (1C5), Bolingbrook, ILTo Bolingbrook's Clow International Airport (1C5), Bolingbrook, IL
- Aircraft age
- About 18 years (built 1999)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Takeoff
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control on ground
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
The pilot’s failure to maintain directional control during takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN18LA041
- Event ID
- 20171128X05050
- Case number
- CEN18LA041
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 9cbea93ec60960e143e92af30980da57729e51d856caf9c9841aab3ccf5328b9; retrieved 2026-09-16T06:02:30.916Z.