Mitsubishi MU-2B-26A N29WD accident near Princeton, Kentucky

Apr 3, 2010 · NTSB number ERA10LA204 · Final report

Probable cause

The pilot's failure to maintain directional control during landing roll for undetermined reasons, resulting in a runway excursion.

NTSB analysis

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.

Text from the NTSB. Open the NTSB docket for ERA10LA204 for the full record.

Event

Date
Apr 3, 2010
Type
Accident
Place
Princeton, Kentucky
Nearest airport
Princeton-Caldwell County Airp (2M0)
Highest injury
Minor
Minor injuries
1
Weather
Visual (VMC)
Light
Day

Mitsubishi MU-2B-26A

N-number
N29WD
Category
Airplane
Damage
Substantial
Operating rule
Part 91 (general aviation)
Purpose of flight
Business

From the NTSB aviation accident database: N-registered aircraft, events since 2008, data through Oct 28, 2026. The file is published monthly, so the latest weeks are incomplete and recent records can change. The official source is the NTSB aviation investigation search. CheckAero is independent and not affiliated with the NTSB.