Accident Cirrus SR20 N223CD,
ASN logo
ASN Wikibase Occurrence # 140087
 
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:Saturday 26 November 2011
Time:10:26
Type:Silhouette image of generic SR20 model; specific model in this crash may look slightly different    
Cirrus SR20
Owner/operator:Private
Registration: N223CD
MSN: 1110
Year of manufacture:2000
Total airframe hrs:1759 hours
Engine model:Continental IO-360-ES
Fatalities:Fatalities: 4 / Occupants: 4
Aircraft damage: Substantial
Category:Accident
Location:West of Crystal Lake, IL -   United States of America
Phase: En route
Nature:Private
Departure airport:Marion, IN (MZZ)
Destination airport:West Chicago, IL (DPA)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The noninstrument-rated pilot was conducting the accident flight under visual flight rules (VFR) without a flight plan. The pilot contacted the tower air traffic controller at the intended destination airport and inquired about landing. The controller informed him that the airport was currently under instrument flight rules (IFR). About 30 seconds later, the pilot informed the controller that he had inadvertently flown over the airport. The controller ultimately cleared the flight to land; however, the pilot decided not to land, informing the controller that he did not want to get delayed at the airport due to the weather. The pilot subsequently told the controller that the flight was “in and out of the clouds.” After asking the pilot if he was IFR qualified (and learning that the pilot was not), the controller transferred the flight to the local radar-equipped approach control facility for further assistance. That controller advised the pilot of several airports in the vicinity that were under VFR. After initially indicating that he would divert to one of those airports, the pilot told the controller that he did not want to “mess with the weather” and did not want to “get stuck in here,” and he declined to proceed to that airport. Radar data depicted that, shortly after the pilot’s radio transmission, the airplane entered a gentle right turn. About 90 seconds later, the right turn tightened abruptly, consistent with the airplane entering a steep spiral. The last 19 seconds of radar data depicted the airplane entering a climb of about 2,500 feet per minute (fpm) followed by an approximate 3,600-fpm descent. Witnesses reported hearing an airplane overhead, but they were not able to see it due to the cloud cover. They described the sound as similar to an airplane performing aerobatics. The witnesses subsequently observed the airplane below the clouds in a steep, nose-down attitude before it struck the ground. Based on reported weather conditions in the vicinity of the accident site, the flight encountered instrument meteorological conditions. A postaccident examination of the airplane did not reveal any anomalies consistent with a preimpact failure or malfunction.
Probable Cause: The noninstrument-rated pilot's decision to continue flight in instrument meteorological conditions, which resulted in the pilot’s spatial disorientation and loss of control of the airplane.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: CEN12FA083
Status: Investigation completed
Duration: 5 months
Download report: Final report

Sources:

NTSB

Location

Media:

Revision history:

Date/timeContributorUpdates
26-Nov-2011 11:58 RobertMB Added
26-Nov-2011 12:25 PC12 Updated [Registration, Cn, Operator]
26-Nov-2011 12:37 Alpine Flight Updated [Time, Operator]
26-Nov-2011 12:43 RobertMB Updated [Source, Narrative]
26-Nov-2011 12:44 RobertMB Updated [Narrative]
26-Nov-2011 13:57 Anon. Updated [Source]
27-Nov-2011 11:06 PC12 Updated [Source]
29-Nov-2011 09:28 flyflyfly Updated [Departure airport, Destination airport, Source, Narrative]
29-Nov-2011 20:09 RobertMB Updated [Departure airport, Destination airport, Source]
07-Dec-2011 10:48 Geno Updated [Time, Source, Narrative]
17-May-2012 12:46 Anon. Updated [Narrative]
11-Jan-2016 18:40 Anon. Updated [Departure airport, Narrative]
21-Dec-2016 19:26 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
23-Sep-2017 20:00 Iron_Hell Updated [Embed code, Damage]
27-Nov-2017 17:23 ASN Update Bot Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Embed code, Damage, 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