eFlight
Accidents · NTSB CEN12FA083 · Final report

Cirrus Design CORP SR20 accident near Crystal Lake, Illinois, November 26, 2011

On November 26, 2011 at about 4:26 pm local time, a Cirrus Design CORP SR20, registered N223CD, was substantially damaged in an accident during enroute near Crystal Lake, Illinois (Dupage Airport). It was a personal flight under general aviation rules (Part 91). 4 people were killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
November 26, 2011 · about 4:26 pm local time · cases in 2011
Place
Crystal Lake, Illinois · Dupage Airport · cases near this airport · map
Type
Accident
Injuries
4 people were killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Cirrus Design CORP SR20
Registration
N223CD · registry record · serial 1110
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. VFR encounter with IMC during enroute
  2. Loss of control in flight during enroute defining event
  3. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Personnel issues › Psychological › Perception/orientation/illusio › Spatial disorientation › Pilot
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Below VFR minima › Effect on operation

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 207 hours in all; 114 in this make and model; 27 in the last 90 days; 11 in the last 30 days; 153 as pilot in command; 0 on instruments
  • Last flight review: April 22, 2010
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 1,759 hours
  • Last inspection: annual inspection, April 5, 2011; 154 hours since
  • Maximum gross weight: 2,900 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Continental IO-360-ES (piston); 0 hours total

The flight

  • Departed from: MZZ Marion IN at 2:30 pm
  • Destination: DPA West Chicago IL
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 170° at 11 knots
  • Visibility: 2 statute miles
  • Sky: overcast at 900 ft
  • Temperature: 50°F (10°C), dew point 46°F (8°C)
  • Altimeter: 29.85 inHg
  • Observation at 4:29 pm from DPA, 22 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers3

Documents from the investigation the NTSB's docket: the evidence folder behind the report

27 documents, released by the NTSB on April 9, 2012. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Witness Statements PDF, 14 pages View Download
2 Accident Site Diagram PDF, 1 page View Download
3 Plot of radar Track Data PDF, 3 pages View Download
4 Transcript of Radio Communications -- Dupage Air Traffic Controltower PDF, 7 pages View Download
5 Transcript of Radio Communications -- Chicago Approach Control PDF, 5 pages View Download
6 Statement from Line Service Personnel PDF, 1 page View Download
7 Summary of On-scene Examination PDF, 5 pages View Download
8 Pilot's Logbook PDF, 38 pages View Download
9 Airplane Maintenance Logbook PDF, 9 pages View Download
10 Engine Maintenance Logbook PDF, 5 pages View Download
11 Propeller Maintenance Logbook PDF, 4 pages View Download
12 Meteorology -- Weather Depiction Chart PDF, 1 page View Download
13 Meteorology -- Satellite Image PDF, 1 page View Download
14 Electronic Devices 17 - Specialist's Factual Report PDF, 7 pages View Download
15 Toxicological Report PDF, 1 page View Download
16 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 5 pages View Download
17 Statement of Party Representatives to NTSB Investigation PDF, 2 pages View Download
18 Photo 1 -- Accident Site PDF, 1 page View Download
19 Photo 2 -- Accident Site PDF, 1 page View Download
20 Photo 3 -- Accident Site PDF, 1 page View Download
21 Photo 4 -- Accident Site PDF, 1 page View Download
22 Photo 5 -- Main Wreckage PDF, 1 page View Download
23 Photo 6 -- Main Wreckage PDF, 1 page View Download
24 Photo 7 -- Left Wing PDF, 1 page View Download
25 Photo 8 -- Vertical Stabilizer/rudder PDF, 1 page View Download
26 Photo 9 -- Propeller Assembly PDF, 1 page View Download
27 Photo 10 -- Engine Assembly PDF, 1 page View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/CEN12FA083.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.

Aircraft

By kindModelsMakersEnginesFleetsWhat changed

Fly

Plan a flightAirportsLive mapRoutes and flightsFuels

Training and work

TrainingFlight schoolsGround schoolsPilot examinersMedical examinersJobs

Companies

DirectoryCharter operatorsFBOsRepair stationsClaim your listing

Safety and data

AccidentsRecords checkAnalyticsSAFxCHANGEThe graphAbout

Colours follow your device's light or dark setting.