CHI06LA078 · Cirrus Design Corporation SR22
Cirrus Design Corporation SR22 · Accident: loss of control in flight en route
From Wagner Municipal Airport (AGZ) to Schaumburg Regional Airport (06C)
Event
- NTSB case
- CHI06LA078
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cirrus Design Corporation SR22
- Aircraft type
- Cirrus SR22
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N751CD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Wagner Municipal Airport (AGZ), Wagner, SDTo Schaumburg Regional Airport (06C), CHICAGO/SCHAUMB, IL
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · climb to cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Aircraft control, not maintained
- Pilot in command › Stall, inadvertent
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane, piloted by an instrument rated private pilot, sustained substantial damage on impact with terrain following an in-flight loss of control during climb in instrument meteorological conditions. The pilot stated, "The flight plan was entered on the GPS [Global Positioning System] direct to function. Took off on runway 26 at about 1320 and a right turning climb was made to the east. When we were heading in the general direction and a climb was established, I place the plane on autopilot. I switched the frequency to 128.0 and immediately heard the frequency buzzing and saw the radio was in the RX mode and would not quit, my first distraction. I contacted Minneapolis center and reported a 3700 ft altitude and climbing, they replied to report back at 7000 or 9000 ft, I don't remember. I then noticed that the autopilot had me in a left hand standard rate turn, even though I was heading east at the time the autopilot was engaged, my next distraction. I then took over the controls to try to get up to the required altitude. In doing so I obviously misread the vertical speed indicator and eventually got the plane into a stall, then into a spin that I could not recover from. At that moment the parachute was engaged and we floated safely to the ground." An examination of the wreckage revealed no pre-impact anomalies.
Probable cause
The pilot not maintaining airplane control and the inadvertent stall encountered during the climb. A factor was the instrument meteorological conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI06LA078
- Event ID
- 20060208X00182
- Case number
- CHI06LA078
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 701d2af310b0ce70be350cb53c4249d77e4eaead86041252e45f1d5d5f47f88a; retrieved 2026-09-22T05:07:15.611Z.