Accident Summary
On January 8, 2016, at 1538 eastern standard time, a Cirrus SR22, Canadian registration C-GXXJ, was substantially damaged when it was involved in an accident near Concord, North Carolina. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.
Flight History
Near the end of a cross-country, instrument flight rules flight, the pilot was conducting an instrument landing system (ILS) approach to runway 36R at Charlotte/Douglas International Airport (CLT), Charlotte, North Carolina, in instrument meteorological conditions. According to the pilot, during the ILS approach, both flags on the primary flight display (PFD) were white and centered, indicating that the autopilot was engaged and the glideslope was captured. He then saw a "vertical flag drop" on the PFD, indicating the airplane was below the glideslope, but the autopilot did not correct. As the airplane broke through a cloud layer, the pilot noted that the runway was to his right despite the PFD showing lateral on-course indication.
Autopilot and Navigation Issues
Review of data from the PFD, multi-function display, autopilot, FAA air traffic control voice communications, and radar recordings revealed that at 1509:00, the airplane descended through 3,200 ft about 1.4 miles before the final approach fix (HAYOU) for the ILS. The autopilot mode changed from GPS Steering-Vertical Speed (GPSS-VS) to GPSS-Approach (APP)-VS mode. The primary navigation source was in VHF/VLOC 1 mode, which prevented the autopilot from automatically transitioning to NAV mode for the ILS approach and from arming the glideslope. After passing HAYOU, the GPS unit no longer provided steering guidance, and the PFD displayed a yellow "GPSS Invalid" message. The airplane drifted right of the localizer course, and the pilot disconnected and re-engaged the autopilot in various modes, leading to oscillations.
Approach and Missed Approach
At 1510:52, as the airplane descended through the glideslope, the tower controller advised the pilot that the airplane was left of course. The pilot acknowledged and attempted corrections. At 1511:20, the autopilot was disengaged, and the controller canceled the approach clearance, instructing the pilot to turn right to 090° and climb to 4,000 ft. The pilot initially responded that he had the airport in sight, but the controller reiterated the instructions. The pilot complied.
Following the missed approach, the controller provided radar vectors to Concord-Padgett Regional Airport (JQF) for a GPS approach to runway 2. The pilot experienced confusion regarding approach fixes and initially loaded the approach for runway 20. After clarification, he loaded the correct approach. While establishing inbound, the pilot engaged the autopilot, which caused the airplane to climb and turn sharply. Multiple autopilot mode changes and disconnections followed, with the airplane deviating from the approach course.
Parachute Deployment and Examination
During the final minutes, the pilot received "terrain" and "envelope protection" warnings. He attempted the autopilot's "straight and level" mode, but the airplane did not respond as expected. At 1536:54, the straight and level mode activated briefly but was deactivated. The pilot reported experiencing G forces and deployed the airplane's parachute system, securing the engine. The airplane descended into a residential area and came to rest on a chain link fence.
Postaccident examination by an FAA inspector revealed substantial damage to the underside of the left wing; the flaps were retracted. The parachute remained attached. The PFD, MFD, and autopilot were recovered for data analysis. Review of recorded data showed no evidence of autopilot or system anomalies. The pilot held a commercial pilot certificate with 1,372 total flight hours, including 900 hours in the accident airplane make and model.