CEN13LA503 · Cessna 182A
Cessna 182A · Accident: runway excursion during takeoff
From Concord, WI (private airstrip) to Marion Airport (C17)
Event
- NTSB case
- CEN13LA503
- 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 182A
- 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
- N5131D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Concord, WI (private airstrip)To Marion Airport (C17), Marion, IA
- 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 · rejected 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
- Runway excursion
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was attempting to depart from a 1,800-foot-long turf runway at the time of the accident. He noted that the grass was about 4 inches high and the ambient temperature was about 84 degrees F. The pilot stated that takeoff acceleration was slow and, when the airplane did not lift off within 200 feet of the expected point, he decided to abort the takeoff. He subsequently realized that he would not be able to stop the airplane on the remaining runway and intentionally veered to the left to avoid trees. The airplane encountered a soybean field and a small tree during the runway excursion. The pilot reported no mechanical failures or malfunctions with the airplane that would have precluded normal operation. He noted that the airplane weight was near the maximum certificated takeoff gross weight and commented that he should have more closely factored the effect of density altitude on the operation.
The airport elevation was 833 feet, and the associated density altitude was about 2,070 feet. The airplane owner's handbook provided takeoff data applicable to a hard surfaced runway with a 20-degree flap setting. From a hard surface runway, at 2,500 feet mean sea level, an ambient temperature of about 81 degrees F, and calm wind, the expected ground roll would be about 750 feet.
The investigation revealed that the pilot did not configure the airplane for a maximum performance takeoff as specified in the owner's handbook. The pilot attempted the accident takeoff with a 10-degree flap deflection instead of a 20-degree flap deflection, as specified. In addition, available takeoff performance data were only applicable to a hard-surfaced runway; takeoff data were not available for a turf runway. The takeoff from a turf runway and the improper flap setting, as well as the elevated density altitude that day, would be expected to increase the takeoff ground roll.
Probable cause
The pilot's failure to properly plan for a maximum performance takeoff by not fully addressing the elevated density altitude or the nonstandard runway surface conditions and his failure to properly configure the airplane's flap setting for the accident takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN13LA503
- Event ID
- 20130826X24422
- Case number
- CEN13LA503
- 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. 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: 51649d3d46cf042624f8b07d0f10d7a0be43908cce3683fb0164f4ffc60d0ec9; retrieved 2026-09-15T22:37:03.589Z.