ATL82FKQ13 · Cessna 182P
Cessna 182P · Accident: overrun during takeoff
From Winona–Montgomery County Airport (5A6) to Winona–Montgomery County Airport (5A6)
Event
- NTSB case
- ATL82FKQ13
- 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
- 0
- 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 182P
- 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
- N52562
- Operator
- I T Crosby · private individual
- Onboard fatalities
- Unknown
- Route
- From Winona–Montgomery County Airport (5A6), Winona, MSTo Winona–Montgomery County Airport (5A6), Winona, MS
- 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
- Takeoff
- 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 › Aircraft preflight, inadequate
- Pilot in command › Removal of control/gust lock(s), not performed
Approximate · Estimated position: the centre of Winona, MS, the place the record names. Not the accident site.
NTSB narrative
THE PILOT STATED THAT AFTER A TAKEOFF RUN, THE CONTROLS LOCKED AND HE COULD NOT PULL THE AIRCRAFT OFF OF THE RUNWAY. SUBSEQUENTLY, THE PLANE COLLIDED WITH A DIRT BANK BEYOND THE END OF THE RUNWAY, BECAME INVERTED, AND SLID BACKWARDS. AN INSPECTION OF THE AIRCRAFT FLIGHT CONTROLS REVEALED PROPER CONTINUITY. TWO FLIGHT CONTROL LOCKS WERE FOUND IN THE AIRCRAFT. ONE WAS FOR A CESSNA 182 AND THE OTHER WAS FOR A CESSNA 172. THE CESSNA 182 CONTROL LOCK WAS FOUND IN THE SIDE POCKET NEAR THE LEFT SEAT. THE CESSNA 172 CONTROL LOCK WAS FOUND ON THE WINDSHIELD BELOW THE PILOT'S CONTROL COLUMN. IT WAS NOTED THAT WHEN THE CESSNA 172 CONTROL LOCK WAS INSTALLED IN THIS AIRCRAFT, IT WOULD NOT COVER THE IGNITION AND MASTER SWITCHES. THE CONTROL COLUMN LOCKING HOLE IN THIS AIRCRAFT WAS ORIENTED IN A HORIZONTAL POSITION, WHEREAS, LOCKING HOLES IN CESSNA 172 AIRCRAFT ARE INSTALLED VERTICALLY.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL82FKQ13
- Event ID
- 20020917X02874
- Case number
- ATL82FKQ13
- 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: investigation status. 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: e6cb16c309eb069210c600fc4dd389dbcc361863650da6efed827b1751da36e9; retrieved 2026-09-21T18:14:44.710Z.