CHI03LA135
2003-05-14 · Kirksville, Missouri, United States · None · 1 aircraft · Status: Completed
Airport IRK
Current FAA registration · N9908V
- Make / Model
- CESSNA R172K
- Year of manufacture
- 1977 · 26 years old at event
- Engine
- CONT MOTOR IO-360 SER (300 hp)
- Seats / Engines
- 4 seats · 1 engine
- Last airworthiness date
- 19770216
- ADS-B equipped
- Yes — Mode-S ADD627
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's improper in-flight decision to land with a tailwind and failure to perform an aborted landing, resulting in the pilots decision to control the aircraft off of the right edge of the runway to avoid obstructions. Contributing factors were the tailwind, the sudden wind shift, the turbulence, and the obstacles.
Factual narrative
On May 14, 2003, at 1800 central daylight time (cdt), a Cessna R172K, N9908V, piloted by a private pilot, sustained substantial damage when it ran off the runway while landing on runway 18 (6,005 feet by 100 feet, concrete) at Kirksville Regional Airport (IRK), Kirksville, Missouri. Visual meteorological conditions prevailed at the time of the accident. The personal flight was operating under the provisions of 14 CFR Part 91 without a flight plan. The pilot was uninjured. The local flight departed about 1700. Around the time of departure, the pilot reported conditions as scattered clouds and winds from 270 degrees at 9 knots. Approximately 15 minutes into the flight, the pilot observed a "large storm cell developing ten to twelve miles north northwest over the city of Kirksville." The pilot monitored the movement of the cell as he executed touch and goes on runway 18. According to the pilot, the cell and cold front were moving slowly and he did not anticipate its arrival at the airport prior to the conclusion of his flight. The pilot reported that as he entered the downwind leg of the traffic pattern he experienced "extreme vertical turbulence." The pilot reported great difficulty flying the aircraft. The pilot continued with the landing and upon touchdown, he was unable to stop the aircraft before the end of the runway. He reported, "I could see that I would be unable to stop by the time I reached the end of the runway. I allowed the aircraft to veer off to the west side of the runway because there were no obstructions there." The aircraft left the runway 300 feet from the end. An approach lighting system was located 400 feet from the end of the runway. The pilot reported the nose gear collapsed and causing the left wing to strike terrain as it stopped. The pilot reported the propeller also struck the terrain while the engine was at idle. The right elevator and trim tab were damaged. In his report the pilot stated, "In hindsight, it might have been better to either continue to the next field at Macon, landed and waited for the front passage or to do a go around and turn back into the wind. With the severe turbulence, I had serious doubts about maintaining altitude and chose to take the action I took." Weather observations reported by the IRK automated surface observing system (ASOS) were: At 1655 cdt, wind 270 degrees magnetic at 9 knots. At 1755 cdt, wind 320 degrees magnetic at 23 knots, gusting to 38 knots. The pilot reported that he had veered off of the runway "under positive control of the aircraft." He reported that he had performed such an action to avoid colliding with the approach lighting system off of the end of the runway. The pilot noted he steered the aircraft into the "grassy area to the right of runway 18 because it contained no obstacles". The airport manager reported that the aircraft "landed about 2/3 of the way down the runway." According to the airport manager, the distance from the aircraft's position when it left the runway to the end of the runway was 300 feet. The distance from the aircraft's position when it left the runway to the approach lighting system was 700 ft. The approach lighting system was 400 feet from the end of runway 18. The distance from the aircraft's position when it left the runway to the threshold lights was 310 feet. The distance from the aircraft's position when it left the runway to the VASI lights was 475 feet. The airplane sustained substantial damage when it ran off the runway while landing. At the time of departure, the automated surface observing system (ASOS) on the airport was reporting winds 270 degrees magnetic at 9 knots. The pilot reported receiving the ASOS report prior to departure. About 15 minutes into the flight the pilot reported he encountered "extreme vertical turbulence" while on downwind. The ASOS reported the wind as 320 degrees at 23 knots gusting to 38 knots at 1755 cdt. The pilot landed on runway 18 and reported having difficulty braking and subsequently veered the airplane off the right edge of the runway 300 feet from the runways end. The pilot stated his decision to steer the aircraft off the runway was due to his approximation that the aircraft would collide with the approach lighting system 400 feet from the end of runway. The nose landing gear collapsed and the left wing struck the terrain as the airplane slid sideways after exiting the runway. The pilot reported he realized that other options, such as continuing to another airport or landing on runway 36, might have prevented the accident. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2003_CHI03LA135.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (turbulence). All research papers
- arXiv 2026 · arXiv preprint Direct Numerical Simulations of Ice-Ocean Boundary Turbulence
Turbulent heat and freshwater transport at ice-ocean interfaces controls glacier and iceberg melt rates, yet the underlying physics remains poorly constrained.
- arXiv 2025 · arXiv preprint Explainable LiDAR 3D Point Cloud Segmentation and Clustering for Detecting Airplane-Generated Wind Turbulence
Wake vortices - strong, coherent air turbulences created by aircraft - pose a significant risk to aviation safety and therefore require accurate and reliable detection methods.
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER) Political Turbulence and Aviation Safety: A Cross-National Analysis of Political Stability's Effects on Aviation Accidents
To what extent does political stability affect aviation safety? This research aims to link domestic political conditions and public safety through the consideration of aviation accident frequency.
- arXiv 2024 · arXiv preprint Does small-scale turbulence matter for ice growth in mixed-phase clouds?
Representing the glaciation of mixed-phase clouds in terms of the Wegener-Bergeron-Findeisen process is a challenge for many weather and climate models, which tend to overestimate this process because…
- arXiv 2023 · arXiv preprint Effects of electrostatic interaction on clustering and collision of bidispersed inertial particles in homogeneous and isotropic turbulence
In sandstorms and thunderclouds, turbulence-induced collisions between solid particles and ice crystals lead to inevitable triboelectrification.
- SKYbrary (Eurocontrol) 2023 · SKYbrary article Wake Vortex Turbulence — SKYbrary Knowledge Base
SKYbrary wake vortex turbulence comprehensive article — generation mechanics, dissipation factors, separation standards (ICAO LIGHT/MEDIUM/HEAVY/SUPER + recategorisation RECAT-EU).