CHI03LA283 · Cessna 182
Cessna 182 · Accident: overrun during landing
From Whiteside County Airport - Joseph H Bittorf Field (SQI) to Cady Aerial Restricted Landing Area (0IS3)
Event
- NTSB case
- CHI03LA283
- 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 182
- 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
- N5360B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Whiteside County Airport - Joseph H Bittorf Field (SQI), Sterling, ILTo Cady Aerial Restricted Landing Area (0IS3), Deer Grove, IL
- Aircraft age
- Not recorded
- 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
- Landing · landing roll
- First occurrenceThe 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
- Overrun
- 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
- Pilot in command › Go-around, not performed
- Pilot in command › Proper touchdown point, exceeded
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane landed downwind, approximately halfway down the runway, overran the end of the runway and nosed over. The pilot reported that while en route he monitored a nearby automated weather observing system (AWOS) and the winds were "230 [degrees true] at 3 knots." The pilot stated, "I decided I would use either end of [the] runway since [the] wind was calm." The pilot reported he elected to land on runway 36 (2,500 feet by 60 feet, turf/gravel) and extended his downwind to "loose altitude." The pilot stated that on final approach the airplane was "too high" and he "tried to side slip in." The pilot reported the airspeed on final approach was "too high" and the airplane "floated down the runway." The pilot stated the accident could have been prevented if he had performed a go-around. The pilot reported the airplane had no mechanical malfunctions or failures during the accident flight. The winds were 220 degrees true at 4 knots, approximately five minutes after the reported accident time.
Probable cause
The pilot's failure to attain the proper touchdown point, and his failure to execute a go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI03LA283
- Event ID
- 20030828X01423
- Case number
- CHI03LA283
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2003-08-25.
- API snapshot SHA-256: 96b111169c94e54e3d3c8c23856fbd526f424805a2e013391aa94245045fbaf2; retrieved 2026-09-21T19:23:07.026Z.