What happened
On September 10, 2009, at approximately 1415 EDT, a Hawker Beechcraft Corporation A36, registration N888WD, collided with trees and terrain in a residential area near Flat Rock, North Carolina. The flight originated from Asheville Regional Airport (AVL) at 1403 EDT for a local personal flight.
Prior to departure, the pilot informed the Asheville Air Traffic Control Tower that he intended to fly locally and perform approaches, though he specifically stated he did not want to perform any ILS approaches. The pilot was cleared for takeoff and instructed to fly a left pattern at or below 3,600 feet. During the flight, the pilot transitioned to Asheville Approach Control, stating he intended to fly toward Hendersonville and noted he was going to "stay under these clouds if I can."
At approximately 1413, the controller provided a vector for a heading of 340 degrees to sequence the aircraft for landing. Radar data showed the aircraft was flying at 3,000 feet MSL and moving in a northwesterly direction. Shortly after, the controller noticed the pilot was not tracking the assigned heading and attempted to communicate, but the pilot did not respond. Radar contact was lost at 1416:11, approximately ten miles south of AVL. The aircraft struck trees and terrain at an elevation of 2,809 feet MSL. The pilot, the sole occupant, sustained 1 fatal injury.
The investigation
Investigators examined the wreckage and found the fuselage impacted upsloping terrain. Debris, including the right main landing gear, a section of the rudder, and part of a flap, was found along an energy path. The engine and propeller showed no evidence of preimpact failure, though the propeller blades exhibited various forms of impact damage.
Examination of the cockpit revealed the throttle, propeller, and mixture controls were in the full forward position. While the "TRIM" warning lights for the autopilot components were found to have illuminated at the moment of impact, the left pitch trim actuator was in a neutral position, and the autopilot was not activated at the time of the crash. The investigation also found that the aircraft was operating under a transponder code (0210) that inhibited the Minimum Safe Altitude Warning (MSAW) system.
Findings
- The pilot attempted to maintain visual flight while operating in instrument meteorological conditions (IMC).
- The pilot failed to advise air traffic control of the actual weather conditions encountered during the flight.
- The pilot did not request MSAW monitoring prior to departure.
- The use of a specific transponder code prevented the generation of low altitude or MSAW warnings by the controller.