6 Oct 2012: CIRRUS DESIGN CORP SR22 — Billy Sprague

6 Oct 2012: CIRRUS DESIGN CORP SR22 (N80KW) — Billy Sprague

No fatalities • Birmingham, AL, United States

Probable cause

The pilot's failure to maintain airplane control during a missed approach in instrument meteorological conditions. Contributing to the accident was the pilot's overreliance on the autopilot system and his inability to hand-fly the airplane once the autopilot was disconnected.

— NTSB Determination

Accident narrative

On October 6, 2012, at 1217 central daylight time, a Cirrus SR22, N80KW, operated by a private individual, was substantially damaged during impact with terrain, after deployment of the Cirrus Airplane Parachute System (CAPS), following a loss of control during a missed approach at Birmingham International Airport (BHM), Birmingham, Alabama. The private pilot incurred minor injuries and the passenger was seriously injured. The personal flight was conducted under the provisions of 14 Code of Federal Regulations Part 91. Instrument meteorological conditions prevailed and an instrument flight rules flight plan was filed for the flight that departed Charles B Wheeler Downtown Airport (MKC), Kansas City, Missouri; destined for BHM.

The pilot stated that while on the instrument landing system approach to runway 6 at BHM, he reported missed approach at 2,000 feet mean sea level (msl) to the BHM air traffic control tower. The tower controller instructed the pilot to fly the runway heading; however, the pilot reported to the controller that he was unable due to weather. The tower controller then instructed the pilot to fly a heading of 180 degrees and climb to 4,000 feet. The pilot acknowledged the instruction and during the turn, lost control of the airplane. He then observed the altimeter indicating a descent through 1,700 feet and elected to deploy the CAPS. The airplane subsequently descended via parachute and came to rest in a commercial parking lot, about 2 miles south of BHM.

Review of Federal Aviation Administration (FAA) recorded radio communications between N80KW and BHM tower revealed that after the pilot declared a missed approach, the tower controller instructed the pilot to fly runway heading and climb to 4,000 feet. The pilot replied "Okay, I'm way off of runway heading…" and did not make any mention of not being able to turn due to weather. The controller then instructed the pilot twice to climb to 4,000 feet and make a left turn to 360 degrees as the airplane was approaching an antenna to the south. After a third query, the pilot replied that he was "going, trying to get around." About 20 seconds later, the pilot reported that he was "going down."

Examination of the airplane by an FAA inspector revealed substantial damage to the fuselage and a puncture of the left wing near the left main landing gear.

The airplane was equipped with an Avidyne primary flight display (PFD), which was forwarded to the NTSB Vehicle Recorder Laboratory, Washington, DC. The unit contained non-volatile memory, which was successfully downloaded. Review of the data revealed that the autopilot was engaged shortly after takeoff and remained on until 1215. At 1213, the autopilot approach mode was armed as the airplane was descending to 2,600 feet msl and had intercepted the localizer course. The autopilot was selected to vertical speed (VS) mode with the altitude armed, rather than the altitude mode. At 1214, the VS mode was automatically cancelled (and the autopilot automatically switched to altitude mode) as the airplane reached 2,600 feet; however, at that time the airplane was above the glideslope (GS) by 53 percent needle deflection. The airplane remained above the GS until the autopilot was disconnected at 1215 and the CAPS was deployed about 1217. According a representative from the PFD manufacturer, the autopilot would automatically arm the GS mode, provided seven criteria were met. Two of the seven criteria were altitude mode engaged and airplane no more than 10 percent needle deflection below GS (airplane above GS). Review of the data did not reveal any preimpact mechanical malfunctions with the airplane, nor did the pilot report any. The pilot reported a total flight experience of 1,944.7 hours; of which, 1,450 hours were in the same make and model as the accident airplane. He reported 17 and 75 total hours of actual and simulated instrument experience, respectively.

The recorded weather at BHM, at 1153, included an overcast ceiling at 700 feet above ground level (1,350 msl).

Contributing factors

  • cause Pilot
  • cause Altitude — Not attained/maintained
  • cause Directional control — Not attained/maintained
  • factor Pilot
  • factor Incorrect use/operation

Conditions

Weather
IMC, wind 330/09kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.