Accident Cirrus SR22 GTS X G3 Turbo N847C,
ASN logo
ASN Wikibase Occurrence # 121544
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Monday 4 April 2011
Time:11:58
Type:Silhouette image of generic SR22 model; specific model in this crash may look slightly different    
Cirrus SR22 GTS X G3 Turbo
Owner/operator:Windy City Flyers
Registration: N847C
MSN: 3218
Year of manufacture:2008
Total airframe hrs:654 hours
Engine model:Continental IO-550-N
Fatalities:Fatalities: 1 / Occupants: 1
Aircraft damage: Substantial
Category:Accident
Location:South Bend, Indiana -   United States of America
Phase: Landing
Nature:Private
Departure airport:Wheeling, IL (PWK)
Destination airport:South Bend, IN (SBN)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The pilot was performing a landing approach with a known, gusting crosswind present. A witness stated that the airplane was being “bounced around” by the wind gusts and that it “stalled and rolled to the left.” Another witness heard the accident airplane go to full power. The airplane was then in a 15- to 30-degree left bank with a nose-down attitude before it impacted the ground. The airplane’s left wing impacted the ground first, then the airplane cartwheeled one-half turn. A postaccident examination of the airplane revealed no preimpact airframe or engine anomalies that would have precluded normal operation of the airplane.

About 8 months before the accident, the airplane's annual inspection was completed, and 2 days later the airplane's recoverable data module (RDM) stopped recording data due to a failed transient voltage suppressor (TVS) and did not record data during the accident flight. The airplane underwent a 100-hour inspection about midway through the 8 month period, and the failed RDM was not detected at that time. The system does not provide a failure indication to the pilot, and there is no requirement during the 100-hour inspection to check the RDM. A likely cause of the TVS failure could have been electrical overstress: the airplane was tied down overnight, and lightning was present when the RDM stopped recording. A similar airplane sustained substantial lightning strike airframe and avionics damage while tied down and at least two other airplanes sustained lightning strikes at that time. An Air Force Research Lab report recommended that a “review of the system design be conducted to determine if a cockpit indicator could be installed to alert the pilot when data logging is not functioning."


Probable Cause: The pilot’s failure to maintain airplane control while on final approach with a gusting crosswind and the subsequent aerodynamic stall and spin during the attempted go-around.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: CEN11FA267
Status: Investigation completed
Duration: 1 year and 7 months
Download report: Final report

Sources:

NTSB

Location

Media:

Revision history:

Date/timeContributorUpdates
05-Apr-2011 11:21 bijzets101 Added
05-Apr-2011 14:26 harro Updated [Source, Embed code]
05-Apr-2011 20:41 RobertMB Updated [Aircraft type, Embed code]
03-May-2011 07:26 RobertMB Updated [Time, Embed code, Narrative]
03-May-2011 11:29 gerard57 Updated [Source, Embed code, Narrative]
21-Dec-2016 19:25 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
27-Nov-2017 16:49 ASN Update Bot Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org