Cirrus SR22 accident near Concord, North Carolina, January 8, 2016
On January 8, 2016 at about 8:38 pm local time, a 2003 Cirrus SR22, registered CGXXJ, was substantially damaged in an accident during approach (IFR initial approach) near Concord, North Carolina. It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were 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 inadequate management of the airplane’s automated systems, which resulted in a loss of control during an instrument approach and necessitated his subsequent deployment of the airplane’s parachute system.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- January 8, 2016 · about 8:38 pm local time
- Place
- Concord, North Carolina · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Cirrus SR22, built 2003 · all SR22s on the register
- Registration
- CGXXJ · no longer on the register · serial 0729
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The instrument-rated private pilot was conducting a cross-country instrument flight rules flight in instrument meteorological conditions. The pilot reported that, during an instrument landing (ILS) approach, he engaged the autopilot with the intent of flying an autopilot-coupled approach, but the airplane subsequently flew below the glideslope and off course. Review of recorded data revealed that the airplane's automated systems were not properly configured to automatically transition from GPS waypoint navigation mode to the navigation (NAV) mode; therefore, the autopilot did not capture the ILS. After the airplane passed the final approach fix (FAF), the pilot disengaged and then re-engaged the autopilot in the attitude hold mode, at which time, the roll attitude was about 15° left. The airplane drifted left of course and subsequently flew below the glideslope. The air traffic controller subsequently canceled the approach clearance and provided radar vectors to another airport about 15 miles away. Based on this information, it is likely the pilot’s mismanagement of the airplane’s automated systems (autopilot, GPS, and navigation radios) led to its failure to capture the ILS and necessitated the missed approach. About 5 minutes after the missed approach, the controller provided the pilot with radar vectors to the FAF for a GPS approach at the diversionary airport. The pilot reported that, he thought he had engaged the autopilot to fly directly to the FAF and that the airplane subsequently began to climb and bank sharply right. The data showed that the pilot had mistakenly programmed the GPS/autopilot to fly to the initial approach fix (IAF), which was behind and right of the airplane, instead of the FAF. Due to the pilot’s mismanagement of the airplane’s automated systems (GPS and autopilot), when he attempted to activate the approach near the FAF, the autopilot attempted to turn the airplane right toward the IAF, contrary to the pilot’s intent. After air traffic control canceled the second approach clearance, they provided the pilot with radar vectors for a third instrument approach attempt. The recorded data showed that the pilot made a series of inputs to the autopilot that resulted in the airplane climbing when he expected it to descend, and shortly thereafter, the autopilot’s underspeed envelope protection mode activated in order to avoid entering an aerodynamic stall. When queried about the airplane’s altitude by air traffic control, the pilot appeared to be confused as to why the airplane was climbing. Further, when the controller queried the pilot about which direction the airplane was headed, he indicated that he thought the autopilot was navigating to a fix, when in reality it was in a mode to follow a prescribed heading. During the final minutes of the flight, after air traffic control provided the pilot a low altitude alert, the autopilot modes changed several times while the airplane began maneuvering to extreme roll and pitch attitudes. During this time, the pilot attempted to activate the autopilot’s straight and level mode three times. The first time the pilot activated the mode, he deactivated it six seconds later. He then attempted to activate the straight and level mode again, but the pilot held the button down, delaying its activation. After the mode activated, the roll returned to level, but the airplane increased its pitch to 20° nose up. As the pitch attitude increased, the autopilot commanded nose down trim, an indication that the autopilot was opposing the pilot’s nose up forces to the control stick. This evidence indicates that the pilot continued to exhibit confusion about the way the airplane’s automated systems worked together with the autopilot. The pilot then disconnected the autopilot and reactivated the straight and level mode for the third and final time after the pitch attitude reached 60° nose up and about 120° left roll. After the activation, the pitch and roll began to decrease toward a wings level attitude. About that time, the pilot activated the airplane’s parachute system. The airplane subsequently descended into a residential area and during the landing, the left wing was substantially damaged. The pilot and passenger were not injured. Postaccident review of all recorded data showed that the airplane and its automated systems performed as expected given the inputs provided by the pilot. It is likely that the pilot’s continuous mismanagement of the airplane’s automated systems ultimately led to his loss of airplane control during the third instrument approach attempt, which necessitated his eventual activation of the airplane’s parachute system.
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
- Loss of control in flight during approach (IFR initial approach) defining event
- Collision with terrain or object (not controlled flight into terrain) during emergency descent
The NTSB's findings
- Personnel issues › Action/decision › Info processing/decision › Understanding/comprehension › Pilot
- Aircraft › Aircraft systems › Auto flight system › Autopilot system › Incorrect use/operation
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 1,372 hours in all; 900 in this make and model; 12 in the last 90 days; 6 in the last 30 days; 1,372 as pilot in command
- Last flight review: September 11, 2015
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 1,503 hours
- Last inspection: annual inspection, September 21, 2015; 26 hours since
- Maximum gross weight: 3,600 lb
- Seats: 4
- Landing gear: fixed
- Engine: Continental Motors IO550N27B (piston); 1,503 hours total
The flight
- Departed from: ERI Erie PA at 4:00 pm
- Destination: CLT Charlotte NC
- Flight plan: IFR
Weather at the time
- Light: daylight
- Wind: from 340° at 5 knots
- Visibility: 3 statute miles
- Sky: overcast at 500 ft
- Temperature: 45°F (7°C), dew point 43°F (6°C)
- Altimeter: 30.07 inHg
- Observation at 8:40 pm from JQF, 7 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
18 documents, released by the NTSB on April 9, 2021. 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.
