CHI03LA169 · Cessna 182L
Cessna 182L · Accident: overrun during landing
From Terre Haute Regional Airport, Hulman Field (HUF) to Amelia Earhart Airport (K59)
Event
- NTSB case
- CHI03LA169
- 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 182L
- 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
- N42713
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Terre Haute Regional Airport, Hulman Field (HUF), Terre Haute, INTo Amelia Earhart Airport (K59), Atchison, KS
- 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
- 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 › In-flight planning/decision, inadequate
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 was substantially damaged when it overran the runway and impacted an embankment while landing on runway 16. The pilot reported that as she turned base for landing, she noted the winds shifted to favor the opposite runway. The pilot noted she entered a traffic pattern for that runway and made a normal approach. She reported encountering a tailwind upon landing and was unable to stop the airplane. The airplane overran the end of the runway and impacted an embankment. A weather station 17 nautical miles from the accident site reported the winds from 050 degrees at 12 knots, gusting to 18.
Probable cause
The pilot's inadequate inflight decision, which resulted in a landing with a tailwind and an overrun of the runway. Factors contributing to the accident were the tailwind encountered on landing rollout, the variable, gusty winds encountered while in the traffic pattern, and the embankment.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI03LA169
- Event ID
- 20030620X00919
- Case number
- CHI03LA169
- 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, 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: fb1b3b880a1387a7378f6bc53ccc866c451d4ffd61c77653584690bb2203747a; retrieved 2026-09-21T19:26:41.049Z.