N150XCirrus Design SR22 · 2004

On March 17, 2020, about 1550 eastern daylight time, a Cirrus SR22, N150X, was substantially damaged when it was involved in an accident near Conway, South Carolina. The private pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot stated that he had owned the airplane for about 2.5 years and was selling it. On the day of the accident, he was delivering it to the new owner for an acceptance flight, departing from Hammond, Louisiana, about 1215 on an instrument flight rules clearance. He proceeded towards the destination airport, which was Columbus County Municipal Airport (CPC), Whiteville, North Carolina. According to Federal Aviation Administration (FAA) air traffic control information, while en route, the pilot discussed the weather conditions at CPC with the controller and elected to divert to Myrtle Beach International Airport (MYR), Myrtle Beach, South Carolina, which was reporting a higher ceiling than CPC. The controller cleared the flight direct to MYR and instructed the pilot to descend and maintain 3,000 ft mean sea level (msl).

At 1540:39, when the flight was north-northwest of MYR flying on a southeasterly heading at 6,370 ft pressure altitude (PA) and descending about 500 ft-per-minute (fpm), the controller cleared the flight to UXDEP, which was the initial approach fix (IAF) for the instrument landing system (ILS) or localizer runway 18 approach at MYR. The pilot stated that he entered the UXDEP waypoint into the GPS. The airplane turned to a southerly heading towards UXDEP and continued to descend about 500 fpm.

The pilot reported that the airplane was in instrument meteorological conditions and that he flew towards UXDEP with the autopilot possibly in “NAV” mode. (Recorded data downloaded from the airplane’s cockpit displays confirmed that the autopilot was in “NAV’ mode.) As the flight continued towards UXDEP, the airplane was not descending as fast as the pilot wanted, and the airplane “was not as stable as he wanted [it] to be.”

The downloaded data indicated that at 1544:07, autopilot course capture occurred. About 7 seconds later, the airplane was about 4,500 ft PA and 8 nautical miles northwest of UXDEP, when the controller instructed the pilot to cross UXDEP at or above 2,000 ft msl and cleared the flight for the ILS runway 18 approach (see figure 1).

Figure 1 – Flight track plot (purple) with selected moments overlaid on the MYR runway 18 ILS instrument approach procedure.

The flight continued towards UXDEP and continued to descend until about 1546 when it leveled off about 3,000 ft PA. At 1547:15, when the flight was about 1.4 nautical miles north-northwest of UXDEP on a south-southeasterly heading at about 3,000 ft PA, autopilot course captured occurred again, followed 1 second later by a turn to the left. It could not be determined from the available evidence what autopilot course was selected; the recorded data showed that the approach mode of the autopilot was never engaged and that autopilot failure did not occur.

At 1547:20, with the autopilot altitude bug set at 2,000 ft msl, the autopilot vertical speed mode engaged, and the autopilot vertical speed bug set to 500 fpm descent, the airplane climbed less than 10 ft over the course of 4 seconds then began slowly descending with the altitude rate decreasing to -1,000 feet-per-minute, and pitch trim-in-motion occurring several times until 1547:45. About this time, the flight was near UXDEP and crossed the center of the localizer course heading in an east-southeasterly direction, and the waypoint changed from UXDEP to KCPC.

Between 1547:45 and 1547:59, with the autopilot vertical speed mode engaged, multiple short duration pitch trim-in-motion engagements occurred resulting in the airplane climbing. At 1547:59, as the flight passed outside of the outer edge of the localizer, the autopilot turned off (see figure 2). The pilot could not recall turning the autopilot off, and the reason for the autopilot turning off could not be determined from the available evidence.

Figure 2 - Flight track plot with selected events annotated.

Beginning at 1548:00 and lasting about 1 minute, a series of altitude excursions occurred during which the airplane repeatedly climbed and descended. At 1548:04, the controller advised the pilot that he was going through the localizer, and 11 seconds later, the pilot advised the controller that he was aborting the procedure and would “climb out.”

The pilot reported that he added power to maintain altitude or climb and intended to “re-shoot the approach.” When he added power, it felt “like it was harder and harder to keep the instruments centered,” “like it was less stable than more,” and “like he was fighting it.” He saw the chevrons, which display on the primary flight display (PFD) when the pitch value is greater than +50° or less than -30°, and decided to deploy the Cirrus Airframe Parachute System (CAPS).

At 1549:01, the airplane was in about a -42° nose-down and 13° left-roll attitude, which the pilot described as an unusual attitude, when the CAPS was deployed. The pilot informed the controller of the CAPS deployment, and while descending under canopy, he cracked open both doors, secured the engine, and prepared for the touchdown, which occurred on all three landing gear. During the landing the airplane's nose landing gear collapsed, and the rudder partially separated.

The airplane was equipped with a Genesys-Aerosystems (formerly S-TEC) Fifty Five X autopilot system, an Avidyne PFD, and an Avidyne multi-function display (MFD). According to the autopilot Pilot’s Operating Handbook (POH), when the remote autopilot on switch has been selected and both a roll mode and a pitch mode engaged, the autopilot will provide an annunciation whenever it is automatically trimming the airplane. The POH also indicated that should the pitch servo loading exceed a preset threshold for a period of 3 seconds (such as a pilot input), the autopilot will annunciate “TRIM” followed by an up or down symbol as an advisement that it is automatically trimming the aircraft in the indicated direction. If the autopilot is still in the process of automatically trimming the aircraft after 4 more seconds, the annunciation will flash. Once the aircraft has been sufficiently trimmed, the annunciation with extinguish. The handbook also included a check of the autotrim system as part of the preflight check.

The airplane was equipped with a Genesys-Aerosystems (formerly S-TEC) Fifty Five X autopilot system, an Avidyne PFD, and an Avidyne multi-function display (MFD). According to the autopilot Pilot’s Operating Handbook (POH), when the remote autopilot on switch has been selected and both a roll mode and a pitch mode engaged, the autopilot will provide an annunciation whenever it is automatically trimming the airplane. The POH also indicated that should the pitch servo loading exceed a preset threshold for a period of 3 seconds (such as a pilot input), the autopilot will annunciate “TRIM” followed by an up or down symbol as an advisement that it is automatically trimming the aircraft in the indicated direction. If the autopilot is still in the process of automatically trimming the aircraft after 4 more seconds, the annunciation will flash. Once the aircraft has been sufficiently trimmed, the annunciation with extinguish. The handbook also included a check of the autotrim system as part of the preflight check.

A picture of the cockpit taken by a first responder depicted the roll trim indicator in a right roll condition, and a picture of the pitch trim actuator taken by the recovery crew depicted the pitch trim in a near full nose down condition. The PFD and the memory card from the MFD were sent to the manufacturer’s facility for read-out. The data was provided to the National Transportation Safety Board’s Vehicle Recorder Division and was the source for the Cockpit Displays – Recorded Flight Data report (contained in the public docket for this investigation).

The wing was removed from the airframe, and the airplane was shipped to the manufacturer’s facility for a repair estimate. Genesys-AeroSystems autopilot components consisting of the turn coordinator, pitch servo, autopilot processor/computer, and altitude transducer were removed and shipped to the manufacturer’s facility for testing and examination by NTSB. Additionally, the Globe Motors autopilot roll servo motor was removed and shipped to the manufacturer’s facility for testing and examination by NTSB.

The Genesys-AeroSystems turn coordinator passed the acceptance test procedure (ATP) for all tests except test point 2.6(a), which was a test checking across the gyro signal and gyro reference signal or checking the gyro when level for centering. To allow for ATP testing of the Genesys-AeroSystems pitch servo, the electrical wires that were cut to remove it from the airplane were spliced. Following splicing of the wires, at initial startup, the motor voltage was 4 volts, which was greater than the cutoff value of 2 volts. A representative of the manufacturer reported that the startup voltage being higher than their cutoff value would result in a small delay in the servo reacting to commands from the computer and that this delay would potentially cause small pitch oscillations of about 1° to 2°. The technician also reported that these low magnitude pitch oscillations would present no flight hazard. The pitch servo passed all subsequent test points. The Genesys-AeroSystems autopilot processor/computer and altitude transducer passed all ATP tests, and it was noted that the back lighting of the autopilot processor was dim. Examination of the Globe Motors autopilot roll servo motor at the manufacturer’s facility revealed it passed the ATP tests.