Probable cause
A malfunction of the flight controls for undetermined reasons.
NTSB analysis
About one minute after takeoff, the pilot reported to the air traffic controller that the airplane's control wheels were locked. The controller subsequently cleared the pilot to land on any runway. No further transmissions were received from the pilot and the airplane continued straight ahead. Witnesses observed the airplane in a slow, level descent, until it impacted wires and then the ground. During a postaccident examination of the airplane, flight control continuity was confirmed to all the flight controls. Due to the impact and post-crash fire damage, a cause for the flight control anomaly, as reported by the pilot, could not be determined; however, several unsecured cannon plugs and numerous unsecured heat damaged wire bundles were found lying across the control columns forward of the firewall. Examination of the airplane logbooks revealed the most recent maintenance to the flight controls was performed about four months prior to the accident. The airplane had flown 91 hours since then.
Text from the NTSB. Open the NTSB docket for ERA10FA195 for the full record.
Event
- Date
- Mar 30, 2010
- Type
- Accident
- Place
- Roanoke, Virginia
- Nearest airport
- Roanoke Regional/Woodrum Field (ROA)
- Highest injury
- Fatal
- Fatal injuries
- 1
- Serious injuries
- 1
- Weather
- Visual (VMC)
- Light
- Day
Piper PA46
- N-number
- N6913Z
- Category
- Airplane
- Damage
- Destroyed
- Operating rule
- Part 91 (general aviation)
- Purpose of flight
- Personal
Other records under this N-number
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.