Cirrus Design CORP SR-22 accident near South Bend, Indiana, April 4, 2011
On April 4, 2011 at about 3:58 pm local time, a 2008 Cirrus Design CORP SR-22, registered N847C, was substantially damaged in an accident during approach (VFR go-around) near South Bend, Indiana (South Bend Regional Airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 4, 2011 · about 3:58 pm local time · cases in 2011
- Place
- South Bend, Indiana · South Bend Regional Airport · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Cirrus Design CORP SR-22 NO SERIES, built 2008
- Registration
- N847C · registry record · serial 3218
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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."
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
- Other weather encounter during approach (VFR pattern final)
- Loss of control in flight during approach (VFR go-around) defining event
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- Environmental issues › Conditions/weather/phenomena › Wind › Crosswind › Contributed to outcome
- Environmental issues › Conditions/weather/phenomena › Wind › Gusts › Contributed to outcome
- Aircraft › Aircraft systems › Indicating/recording systems › Data recorders (flight/maint) › Failure other cases naming the instruments and avionics
- Aircraft › Aircraft systems › Indicating/recording systems › (general) › Design other cases naming the instruments and avionics
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › (general) › Not attained/maintained
Pilot
- Certificate: private
- Ratings: single-engine land; single-engine sea; instrument: airplane
- Flight time: 372 hours in all; 17 in the last 90 days; 6 in the last 30 days
- Last flight review: March 15, 2011
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 654 hours
- Last inspection: 100-hour inspection, December 15, 2010
- Seats: 4
- Landing gear: retractable
- Engine: Cont Motor IO-550-N (piston); 0 hours total
The flight
- Departed from: PWK Wheeling IL at 3:06 pm
- Destination: SBN South Bend IN
- Flight plan: IFR
- Runway 27L, 8,418 ft by 150 ft
Weather at the time
- Light: daylight
- Wind: from 310° at 16 knots, gusting 24
- Visibility: 7 statute miles
- Sky: overcast at 1,500 ft
- Temperature: 45°F (7°C), dew point 39°F (4°C)
- Altimeter: 29.40 inHg
- Observation at 3:54 pm from SBN
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
29 documents, released by the NTSB on August 24, 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.
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
- N847C on the register today · the tail number may have moved to another aircraft since
- Engine: Cont Motor IO-550-N 2,794 aircraft carry this series today · as the NTSB recorded it
- South Bend International · nearest airport
- Chicago Executive · departed from
- Accidents and incidents in Indiana 1,367 since 1982 · 179 in the last ten years
- Indiana 5,705 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CEN11FA267.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.
