FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA20LA129 · Cirrus SR22 Undesignat

17 Mar 2020 · Conway, SC, United States

Cirrus SR22 Undesignat · Accident: loss of control in flight on approach

From Hammond Northshore Regional Airport (HDC) to Myrtle Beach International Airport (MYR)

Report a problem

Event

NTSB case
ERA20LA129
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Cirrus SR22 Undesignat

Aircraft type
Cirrus SR22
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N150X
Operator
Unknown
Onboard fatalities
Unknown
Route
From Hammond Northshore Regional Airport (HDC), Hammond, LATo Myrtle Beach International Airport (MYR), Myrtle Beach, SC
Aircraft age
About 16 years (built 2004)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft systems
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

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.

Probable cause

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA20LA129
Event ID
20200317X65851
Case number
ERA20LA129
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 10291ce0546f7cef01fe06df289357d96598828a38cf7ee4d01b2273dfc3e37c; retrieved 2026-09-16T11:19:22.849Z.