ERA10LA204
2010-04-03 · Princeton, Kentucky, United States · Minor · 1 aircraft · Status: Completed
Airport 2M0
N29WD has since been reassigned. It is now registered to a different aircraft (GLASAIR GLASTAR GS-1, built 2023), which was not involved in this event.
Aircraft involved
Probable cause & findings
The pilot's failure to maintain directional control during landing roll for undetermined reasons, resulting in a runway excursion.
Factual narrative
On April 3, 2010, about 1330 central daylight time, a Mitsubishi MU-2B-26A, N29WD lost directional control and veered off the runway while landing at the Princeton-Caldwell County Airport, Princeton, Kentucky. The private pilot received minor injuries and the airplane sustained substantial damaged. Visual meteorological conditions prevailed and an instrument flight rules flight plan was filed for the 14 Code of Federal Regulations Part 91 business flight from Garfield County Regional Airport, Rifle, Colorado, to Princeton, Kentucky.The pilot stated that as he turned from base to final to land on runway 23, the windsock showed little to no wind and his approach speed was 95-100 knots. After crossing the threshold, the rear tires touched down on centerline about 800 feet down the runway. He stated that the landing and position on the runway was textbook perfect and that there was no crosswind during the final approach or touchdown. The pilot further stated that approximately 100-200 feet after touchdown during the landing roll at about 70 knots, the airplane made a sharp veer (30 degrees) to the right, the right wing dropped suddenly and the airplane exited the right side of the runway. The pilot thought that that he could not stop the airplane before going into a ditch so he applied full power in an attempt to fly over the ditch, but the airplane collided with a fence. After the accident, the pilot reported that he believed that something caused the power to drop or the propeller changed pitch on the right engine which resulted in the sharp veer to the right. A Federal Aviation Administration inspector reported that the airplane's wings and fuselage were buckled. Examination of the runway by the inspector showed tire marks approximately 400 feet down the runway from the initial touchdown point and the marks continued approximately 1,500 feet off of the right side of the runway through grass until the airplane collided with the fence. The left main tire was found inflated, and the right main tire was impact damaged and separated from the rim bead. The nose wheels were inflated and there were no signs of tire failures. The nose wheel steering linkages were intact and no anomalies were noted. All landing main landing gear linkages were intact with some impact damage. Examination of the engine power and propeller controls revealed no anomalies. Flight control continuity was established throughout the flight controls to their respective control surfaces, and the flaps were found set in the 20-degree position. According to the pilot, after landing on the centerline about 800 feet beyond the runway threshold, the airplane veered sharply to the right and exited the right side of the runway. Observation of the windsock by the pilot during final approach showed negligible wind. After exiting the runway, the pilot added full power in an attempt to fly over a ditch and collided with a fence. Examination of the accident site by a Federal Aviation Administration inspector revealed tire marks approximately 400 feet down the runway from the initial touchdown point and the marks continued approximately 1,500 feet off of the right side of the runway through grass until the airplane collided with the fence. After the accident, the pilot reported that he believed something caused the power to drop or the propeller changed pitch on the right engine which resulted in the sharp veer to the right. A postaccident examination of all landing gear linkages, engine power, and propeller controls did not reveal anomalies other than impact damage. Flight control continuity was established through all flight controls to their respective control surfaces, and no other mechanical anomalies were noted. No physical evidence was found to conclusively determine the reason for excursion. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Not determined-Not determined-(general)-(general)-Unknown/Not determined - C
Verbatim from NTSB's published report. Source file
NTSB_2010_ERA10LA204.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 (runway excursion). All research papers
- SKYbrary (Eurocontrol) 2024 · SKYbrary article Runway Excursion — SKYbrary Knowledge Base
SKYbrary runway excursion review — RE-OE (overruns) + RE-LO (lateral). Risk drivers: long landing, high approach speed, contaminated surface, tailwind, mis-set autobrakes.
- NTSB Aircraft Accident Reports 2019 · Accident report Embraer ERJ 175 Runway Excursion at Charlotte Douglas
Republic Airline ERJ-175 runway excursion CLT, January 2018. Examines a low-energy runway excursion involving misuse of autobrakes + thrust reverser response after a high-crosswind landing on a contam…
- NASA NTRS 2025 · Presentation Uncovering Resilient Behavior in the Aviation Safety Reporting System Using Large Language Models
Resiliency is present in everyday life, both in system design and exhibited by the operators that function within these systems.
- NASA NTRS 2025 · Conference Paper Uncovering Resilient Behavior in the Aviation Safety Reporting System Using Large Language Models
Resiliency is present in everyday life, both in system design and exhibited by the operators that function within these systems.
- Flight Safety Foundation 2024 · FSF / AeroSafety World Runway Safety Initiative Final Report (RSI)
Foundation Runway Safety Initiative final report — comprehensive analysis of runway excursion + incursion risk drivers worldwide.
- Semantic Scholar 2020 · Article Towards online prediction of safety-critical landing metrics in aviation using supervised machine learning
Abstract In recent years, due to the increased availability of data and improvements in computing power, application of machine learning techniques to various aviation safety problems for identifying,…