29 Mar 2013: CIRRUS SR22T — Hamid Abbasi

29 Mar 2013: CIRRUS SR22T (N1967N) — Hamid Abbasi

No fatalities • Alexandria, MN, United States

Probable cause

The failure of maintenance personnel to install a safety wire during reinstallation of the right flap, which led to the separation of the right flap rod from the right flap actuation fitting during flap extension. Contributing to the accident were inadequate inspections of the right flap during subsequent annual, prebuy, and preflight inspections.

— NTSB Determination

Accident narrative

**This report was modified on 9/20/2013. Please see the public docket for this accident to view the original report.**

On March 29, 2013, about 1045 central daylight time, a Cirrus SR22T airplane, N1967N, was substantially damaged after impact with terrain (frozen lake) near the Chandler Field Airport (AXN), Alexandria, Minnesota. The private pilot and one passenger sustained minor injuries, and two passengers were not injured. The airplane was registered to MWBS Holdings LLC and operated by the pilot under the provisions of 14 Code of Federal Regulations Part 91 with no flight plan filed. Day visual meteorological conditions prevailed for the flight, which originated from the Marv Skie-Lincoln County Airport (Y14), Tea, South Dakota about 0904.

While on pattern downwind to AXN, the pilot reported a loud noise during flap extension. The pilot initiated a climb as he struggled to maintain roll control. He attempted to reduce the airplane’s rolling tendency by adjusting flap position. As his control of the airplane worsened, the pilot pulled the ballistic recovery system handle. The parachute deployed and the airplane descended onto a frozen lake.

The flight recording device was recovered from the accident airplane and forwarded to the National Transportation Safety Board’s Vehicle Recorder Laboratory for evaluation. While on pattern downwind, the recorder indicated that the flaps were adjusted from up to half and the airplane made several left bank turns, with a maximum of 30 degrees of left bank. About 18 seconds after initial flap movement, the flaps were briefly adjusted to up and returned to half.

About 36 seconds after initial flap movement, the flaps were adjusted from half to full and the airplane began a right roll to a steep right bank attitude. A stall indication was recorded 38 seconds after the flaps were adjusted to full. The Cirrus Airframe Parachute System (CAPS) was deployed two seconds after the stall indication. The CAPS handle pull occurred at a pitch of 22 degrees nose down, a roll attitude of 86 degrees right bank, and an altitude of about 519 feet above ground level.

The airplane was examined at the accident site by Federal Aviation Administration (FAA) inspectors and a representative of Cirrus Design Corporation. The right flap rod end was found disconnected from the right flap actuation fitting. The right flap rod end mounting bolt and washer were found lying on the snow under the airplane. No evidence of a safety wire was present on the mounting bolt or on the right flap actuation fitting.

An examination of the CAPS Rear Harness assembly revealed that both reefing line cutters had fired but the rear harness remained “snubbed.” The impact scars on the snow and Ice, and the damage to the aircraft indicated that touch-down occurred while the airplane was in a 40-50 degree nose-down attitude. This nose-down attitude is consistent with a touch-down prior to “tail drop.”

A review of maintenance records indicated that the right flap was reinstalled on August 3, 2011, at a Hobbs time of 66.4. According to maintenance manual procedures, the mounting bolt and washer hardware were to be torqued to a measured 50-70 inch pounds, then safety wired to the flap actuation fitting. An annual inspection was conducted on July 10, 2012 (163.9 Hobbs), a pre-buy inspection was conducted on November 5, 2012 (177.2 Hobbs) and the accident occurred with a Hobbs time of 278.0.

According to the Cirrus SR22T pilot operating handbook, the preflight checklist states to "inspect flap hinges, actuation arm, bolts, and cotter pins.....secure."

Contributing factors

  • cause Incorrect service/maintenance
  • cause Maintenance personnel
  • factor Maintenance personnel
  • factor Pilot

Conditions

Weather
VMC, wind 150/06kt, vis 5sm

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.