Cirrus SR22 accident near Conway, South Carolina, March 17, 2020
On March 17, 2020 at about 7:50 pm local time, a 2004 Cirrus SR22, registered N150X, was substantially damaged in an accident during approach near Conway, South Carolina. It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
The pilot’s incorrect use of the autopilot while approaching the initial approach fix and his subsequent improper primary pitch control input while a pitch mode of the autopilot was engaged, which resulted in pitch excursions and subsequent departure from controlled flight.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 17, 2020 · about 7:50 pm local time
- Place
- Conway, South Carolina · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Cirrus SR22 Undesignat, built 2004 · all SR22s on the register
- Registration
- N150X · no longer on the register · serial 0813
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot was on a cross-country, instrument flight rules flight, and while en route to the destination airport, he diverted to an alternate airport with a higher ceiling. The flight was operating in instrument meteorological conditions and was vectored by the controller to the initial approach fix (IAF) for an instrument landing system approach. The pilot was instructed to cross the IAF at or above 2,000 ft mean sea level (msl); however, with the vertical speed mode of the autopilot off the airplane did not descend much below 3,000 ft pressure altitude as it approached the IAF. When the flight was less than 2 miles from the IAF, an autopilot course capture with a corresponding heading change to the left occurred. Over the next 25 seconds, with the autopilot altitude bug set at 2,000 ft msl, which was 1,000 ft below the airplane’s current altitude, the autopilot vertical speed mode engaged, and the autopilot vertical speed bug set initially to 500 fpm descent and then subsequently to greater than 750 fpm descent, the airplane climbed less than 10 ft over the course of 4 seconds then began slowly descending, with pitch trim-in-motion occurring numerous time over the course of 15 seconds. The slight increase in altitude initially was likely due to environmental conditions since the airplane then began to descend at a rate of about -1,000 feet-per-minute. The delay in descending was likely the result of the increased start up voltage of the pitch servo. As the airplane neared the IAF, a waypoint change from the IAF to the original destination airport occurred. It is likely that this erroneous waypoint change was the result of pilot input. The airplane flew through the localizer course, and as it passed outside of the outer edge of the localizer, the autopilot turned off. 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. Over the next minute, a series of altitude excursions occurred during which the airplane repeatedly climbed and descended. During this time, the controller advised the pilot that he had flown through the localizer, and the pilot advised the controller that he was aborting the procedure. The pilot reported that when he added power, he had difficulty maintaining control of the airplane and that it was unstable. Subsequently, the pilot sensed that he was fighting the airplane and in an unusual attitude, with the pitch trim near full nose-down position and the airplane in a corresponding -42° nose-low and 13° left-roll attitude, he deployed the airframe’s parachute system. The airplane descended under canopy and touched down in the backyard of a house. The airplane's nose gear collapsed and the rudder partially separated during the landing, resulting in substantial damage to the airframe. While off course with the autopilot engaged and the vertical speed mode selected, the pilot likely applied and held pitch control input that was sensed by the autopilot auto trim system as an out-of-trim condition. The autopilot auto trim system responded by trimming the airplane, resulting in the corresponding altitude excursions. Postaccident operational testing of the autopilot components revealed a slight malfunction of the pitch servo that would have resulted in a small delay in the servo reacting to commands from the computer; the delay would have potentially resulted in small pitch oscillations of about 1° to 2°. However, these low magnitude pitch oscillations would likely have presented no flight hazard. No significant discrepancies were noted during testing of the remaining autopilot components. Therefore, it is likely that the pilot manually changed course when near the IAF and then intentionally applied control pressure on the control yoke for longer than 3 seconds with the vertical speed mode engaged. Those actions resulted in a heading change, altitude excursions, and the subsequent departure from controlled flight.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Course deviation during approach (IFR initial approach)
- Altitude deviation during approach (IFR initial approach)
- Loss of control in flight during approach defining event
The NTSB's findings
- Aircraft › Aircraft systems › Auto flight system › Autopilot system › Incorrect use/operation
- Aircraft › Aircraft systems › Flight control system › Elevator control system › Incorrect use/operation
- Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 350 hours in all; 269 in this make and model; 17 in the last 90 days; 9 in the last 30 days; 274 as pilot in command
- Last flight review: February 27, 2019
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 1,912.6 hours
- Last inspection: annual inspection, December 20, 2019; 12 hours since
- Maximum gross weight: 3,400 lb
- Seats: 4
- Landing gear: fixed
- Engine: Continental IO-550N (piston); 1,913 hours total
The flight
- Departed from: HDC Hammond LA at 4:15 pm
- Destination: MYR Myrtle Beach SC
- Flight plan: IFR
Weather at the time
- Light: daylight
- Wind: from 210° at 3 knots
- Visibility: 10 statute miles
- Sky: overcast at 1,600 ft
- Temperature: 63°F (17°C), dew point 57°F (14°C)
- Altimeter: 30.20 inHg
- Observation at 8:56 pm from KMYR, 13 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
12 documents, released by the NTSB on October 20, 2022. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
