# NTSB CEN11FA267: Cirrus Design SR-22, N847C, South Bend, IN, April 4, 2011

- Type: NTSB accident investigation
- Classification: Accident · Fatal · Field investigation · Final report
- Date: April 4, 2011, 11:58 local (15:58 UTC)
- Place: South Bend, IN
- Coordinates: 41.708057, -86.317222 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=41.7081&lon=-86.3172&mi=10
- Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping)
- Defining event: [Approach-VFR go-around: Loss of control in flight](https://openairdocs.org/ntsb-events/240)
- Highest injury: Fatal
- Injuries: 1 fatal
- Status: Completed, report November 5, 2012
- Report: Approved by Office Director
- NTSB office: Central Region
- Parties: Teledyne Continental Motors, Heads Up Technologies, Inc., AMSAFE, Cirrus Aircraft Corporation, Federal Aviation Administration
- NTSB case key (mKey): 78761
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN11FA267
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/78761/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=78761
- Page: https://openairdocs.org/ntsb/CEN11FA267

## 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.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cirrus Design SR22, 94 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2130001), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Wind: crosswind](https://openairdocs.org/ntsb-findings/03034040): Environmental issues › Conditions/weather/phenomena · Contributed to outcome; cases with it: [Cirrus Design SR22, 9 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md?model=2130001), [All aircraft, 1,008 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md)
- [Wind: gusts](https://openairdocs.org/ntsb-findings/03034045): Environmental issues › Conditions/weather/phenomena · Contributed to outcome; cases with it: [Cirrus Design SR22, 13 cases](https://openairdocs.org/ntsb-findings/03034045/cases.md?model=2130001), [All aircraft, 1,199 cases](https://openairdocs.org/ntsb-findings/03034045/cases.md)
- [Indicating/recording systems: data recorders (flight/maint)](https://openairdocs.org/ntsb-findings/01023130): Aircraft › Aircraft systems · Failure; cases with it: [Cirrus Design SR22, 1 case](https://openairdocs.org/ntsb-findings/01023130/cases.md?model=2130001), [All aircraft, 17 cases](https://openairdocs.org/ntsb-findings/01023130/cases.md)
- [Indicating/recording systems](https://openairdocs.org/ntsb-findings/01023100): Aircraft › Aircraft systems · Design; cases with it: [Cirrus Design SR22, 1 case](https://openairdocs.org/ntsb-findings/01023100/cases.md?model=2130001), [All aircraft, 18 cases](https://openairdocs.org/ntsb-findings/01023100/cases.md)
- [Performance/control parameters](https://openairdocs.org/ntsb-findings/01062000): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cirrus Design SR22, 15 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md?model=2130001), [All aircraft, 1,269 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Approach-VFR pattern final: Other weather encounter](https://openairdocs.org/ntsb-events/400); cases with it: [Cirrus Design SR22, 8 cases](https://openairdocs.org/ntsb-events/400/sequence.md?model=2130001), [All aircraft, 1,127 cases](https://openairdocs.org/ntsb-events/400/sequence.md)
- [Approach-VFR go-around: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Cirrus Design SR22, 74 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=2130001), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md)
- [Uncontrolled descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cirrus Design SR22, 113 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2130001), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

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."

## Factual narrative

HISTORY OF FLIGHT On April 4, 2011, about 1158 eastern daylight time, a Cirrus Aircraft Corporation SR22, N847C, sustained substantial damage on impact with terrain during landing on runway 27L (8,414 feet by 150 feet, asphalt) at the South Bend Regional Airport (SBN), near South Bend, Indiana. The private pilot, the sole occupant, sustained serious injuries and was transported to a hospital. The pilot subsequently died from the injuries that he sustained. The airplane was registered to Canoecouple Inc. and was operated as a rental airplane by Windy City Flyers, Inc., under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual flight rules conditions prevailed for the flight, which operated on an activated instrument flight rules flight plan. The flight originated from the Chicago Executive Airport (PWK), near Wheeling, Illinois, about 1106, and was destined for SBN. Prior to the accident, as the pilot flying N847C approached SBN, he contacted the approach controller who issued N847C the current weather at SBN, which included the winds that were “3-0-0 at 1-5” and “gusts to 2-4.” After the weather brief, the pilot responded, “Roger.” The pilot was then vectored for and was cleared to conduct the instrument landing system runway 27L approach. The pilot changed to the tower frequency and the tower controller issued updated wind information and a landing clearance to land on runway 27L. The pilot did not ask for any further wind updates and the tower did not issue any prior to the airplane impacting terrain. About 1158, a witness, who worked at SBN, saw an airplane landing. He indicated that the airplane was being “bounced around” by wind gusts. He reported that the airplane “stalled and rolled to the left.” The airplane’s left wing impacted terrain first and then the airplane cartwheeled one-half turn. Another witness, who worked at a fixed base operator at SBN, stated that he heard the accident airplane go to “full” power and he looked out the line office window. The airplane was in a 15 to 30 degree left bank and it had a nose-down attitude. The airplane then impacted the ground and a puff of smoke was observed. PERSONNEL INFORMATION The pilot held a Federal Aviation Administration (FAA) private pilot certificate with an airplane single-engine land, single-engine sea, and instrument ratings. He had been issued a FAA third-class medical certificate on June 2, 2009, with a limitation for corrective lenses. The pilot reported on the application for that medical certificate that he had accumulated 217.8 hours of total flight time and 45.8 hours of flight time in the six months prior to that application. A copy of excerpts from the pilot’s logbook indicated the pilot’s last entry in his logbook was dated March 15, 2011. The pilot recorded that he had accumulated 372.1 hours of total flight time, 16.5 hours of flight time in the 90 days prior to the accident, and 5.7 hours of flight time in the 30 days prior to theaccident. The pilot’s logbook showed that the pilot received 259.4 hours of dual instruction. The logbook had a certified flight instructor’s (CFI) endorsement for a flight review and an endorsement for an instrument proficiency check, which were both dated March 15, 2011. According to a recovered certificate, also dated March 15, 2011 and endorsed by the CFI as an "Authorized Cirrus Aircraft Instructor," showed that the pilot completed the course requirements for Advanced Transition Training. The CFI was employed by the airplane operator. AIRCRAFT INFORMATION N847C, a 2007 model Cirrus Aircraft Corporation SR22, serial number 3218, was a four-place single engine low-wing airplane powered by a six-cylinder, 310-horsepower, Teledyne Continental Motors model IO-550-N51 engine, with serial number 691913, that drove a three-bladed Hartzell constant speed propeller. The airplane's airworthiness certificate was issued on August 21, 2008. The Cirrus Aircraft Corporation SR22 was certified under Part 23. The airplane owner flew the airplane the day before the accident. The owner, in part, stated: I flew Cirrus N847C from Georgetown, TX (KGTU) to Chicago Executive (KPWK) via Houston, MO (M48) on April 3, 2011. The vent fan was placarded as INOP. Other than a greatly reduced volume of fresh air into the cabin, the airplane functioned as expected during all phases of flight. An airplane logbook entry showed that on March 22, 2011, a mechanic removed the blower, sent it for repairs, and updated the airplane’s weight and balance to reflect the blower removal. Airplane logbook entries showed that last airplane annual inspection was completed on August 6, 2010, and a 100-hour inspection was completed on December 15, 2010. The airplane accumulated 556.9 hours of total flight time as of the annual inspection and 654.5 hours of total flight time at the 100-hour inspection. The airplane was equipped with a Garmin Primary Flight Display (PFD) and a Multi-Function Display (MFD) for the pilot’s flight instruments. Integrated avionics units, located behind the MFD and instrument panel, functioned as the main communication hub, linking all integrated avionics system components with the PFD. A secure data (SD) card, when inserted in the top SD card slot of the MFD, can have the MFD log flight data on the SD card at 1 Hertz, generating a text file for each power cycle. The accident airplane was also equipped with a Recoverable Data Module (RDM), which was a crash-hardened flight recording device installed in the tail of the aircraft and it recorded flight and aircraft information. The RDM recorded data at 1 Hz. The RDM was designed to record airplane performance, configuration data, and navigation data to include the flight's groundspeed and global positioning system track. The Cirrus Aircraft Corporation SR22 airplane maintenance manual (AMM), in part, stated: The Aircraft Data Logger (ADL) consists of the RDM. The RDM, located in the shear web of the aft vertical sparin front of the rudder, receives airplane data from the primary GIA 63W integrated avionics unit. The ADL system is powered by 28 VDC through the 2-amp STALL WARNING circuit breaker on the Essential Bus 2 and the 3-amp FUEL QTY circuit breaker on the Main Bus 1. ... (2) Operational Tests - Aircraft Data Logger System ... (a) Set BAT 1 switch to ON position. (b) Open center armrest console and remove glove box trim to access diagnostic LED [light emitting diode]. ... (c) Verify diagnostic LED indicates normal operation with several 0.03 flashes once per second. If diagnostic LED does not indicate normal operation, refer to the following troubleshooting table. ... (d) Install glove box trim. ... (e) Set BAT 1 switch to OFF position. The AMM required an annual operational test of the ADL system. Cirrus Aircraft Corporation initially issued service bulletin (SB) 2X-31-05 R2 on April 16, 2009 and issued a revised version on August 27, 2009. SB 2X-31-05 R2, in part, stated: PURPOSE Cirrus Design recently discovered a condition on aircraft with Perspective Avionics where the Aircraft Data Logger (ADL) fails to store data correctly. Upon investigation, it was determined that the condition is caused by the Recoverable Data Module (RDM) internal software. To correct this condition, the affected RDM must be replaced with an RDM with improved software. N847C had a RDM with improved software installed on September 10, 2009. Additionally, at the airplane’s last annual inspection, the required inspection of the ADL system, indicated that the RDM was operational. The airplane's flight manual indicated that the airplane's maximum demonstrated crosswind component was 20 knots. METEOROLOGICAL INFORMATION At 1154, the recorded weather at SBN was: Wind 310 degrees at 16 knots gusting to 24 knots; visibility 7 statute miles; sky condition overcast 1,500 feet; temperature 7 degrees C; dew point 4 degrees C; altimeter 29.41 inches of mercury. AIRPORT INFORMATION SBN was a public, towered airport, owned by the St Joseph County Airport Authority, located 3 miles northwest of South Bend, Indiana, at a surveyed elevation of 799 feet above mean sea level. The airport featured three runways, Runway 9R/27L, 18/36, and 9L/27R with asphalt surfaces. The airport listed 118.9 megahertz as its common traffic advisory frequency and reported that it meets the fire and rescue requirements of aircraft rescue and fire fighting index B. Runway 27L had a four-light precision approach path indicator (PAPI) on located on the left side of the runway and that PAPI provided a 3.00 degree glide path. Runway 27L obstruction remarks listed a 36-foot tree, located 1,741 feet from the runway, and 588 feet right of centerline, which indicated a 42:1 slope to clear that obstruction. FLIGHT RECORDERS The airplane's RDM was manufactured by Heads Up Technologies Inc. The module was installed in the airplane's empennage. The unit was designed to record airplane performance, configuration data, andnavigation data to include the flight's groundspeed and global positioning system track. The flight's data was stored on flash memory chips within the module. WRECKAGE AND IMPACT INFORMATION The wreckage and on-scene ground scars were examined and documented by FAA inspectors. Some of the ground scars, consistent propeller slashes, were observed along the path that the airplane took prior to coming to rest in the grass south of runway 27L. The wreckage was located approximately 2,500 feet from the runway’s approach end and a approximately 200 feet south of the its centerline. A safety representative from the airplane manufacturer assisted the FAA inspectors with the examination. Flight control continuity was established and no preimapct anomalies were detected during the postaccident examination of the wreckage. The cockpit avionics display units sustained damage. The display units’ recovered SD cards and the airplane’s RDM were retained for examination. MEDICAL AND PATHOLOGICAL INFORMATION An autopsy was performed on the 50-year-old pilot by the Cook County Medical Examiner's Office. The autopsy listed the date of death as May 1, 2011, and the cause of death as a result of multiple injuries due to an airplane crash. Samples for toxicological examination were not sent to the FAA Civil Aerospace Medical Institute and a Final Forensic Toxicology Accident Report was not produced. TESTS AND RESEARCH Three SD cards were recovered from the onboard Garmin MFD and were sent to the National Transportation Safety Board (NTSB) Vehicle Recorder Laboratory. Two of the SD cards had Garmin labels and contained various charting and navigation databases. The third was an unlabeled SanDisk 1 gigabyte SD card. When this accident SD card was inserted into a card reader connected to a PC, the SD card did not mount and became heated. The card was transported to the Federal Bureau of Investigation (FBI) Cryptologic and Electronic Analysis Unit for examination. The FBI lab was able communicate with the card, but was unable to read valid sector data. X-ray examination found no obvious defect in the packaging. The not-and (NAND) flash die was exposed using acid decapsulation and cracks were observed in a “T” shape on its die. No data was recovered from the damaged SD card. The RDM was sent to the National Transportation Safety Board (NTSB) vehicle recorder laboratory. A NTSB specialist subsequently powered the unit by the universal serial bus connection and downloaded the data from the RDM. The RDM contained over 145 hours of flight data. The most recent record was from August 8, 2010, at 1630 central daylight time when the aircraft was on the ground at Gogebic-Iron County Airport (IWD), near Ironwood, Michigan. The RDM was transported to its manufacturer, Heads Up Technologies, near Carrollton, Texas, for examination and an attempt to download additional data under NTSB supervision. The unit failed to power up and disassembly revealed its power supply had failed. Thefailed power supply was removed, an exemplar power supply directly powered the RDM, and the RDM’s data was downloaded. The data set matched the data set initially downloaded at the NTSB Vehicle Recorder Laboratory. The power supply unit was sent to the Air Force Research Laboratory (AFRL) at Wright-Patterson Air Force Base, Ohio, to determine the cause of power supply failure. Examination of the failed power supply showed charring on the top of the circuit card. Further x-ray analysis revealed a failed R9 resistor and shorted transient voltage suppressor (TVS). Both the R9 resistor and TVS are part of the power supply’s input protection and filtering section and found near the charred area of the power supply. According to the AFRL report, “the most likely cause of the TVS failure is either electrical overstress or possible manufacturing defect. … If lightning were the cause, one would normally expect to see additional damage to other electronics or structure.” According to the RDM manufacturer, this is the first observed TVS failure. ADDITIONAL INFORMATION The RDM data showed that on August 7, 2010, the accident airplane was flown from PWK, about 1344 central daylight time (CDT) and it landed at IWD about 1555 CDT. Data was consistent with electrical power being turned on a couple times on August 8, 2010, at IWD. The owner of the airplane indicated that he flew that flight to IWD and that he did not use any external power to start the airplane at IWD on August 8, 2010. A lighting strike report for the 5-mile radius around IWD was completed for the time period between August 7, 2010, 1100 CDT to August 8, 2010, 1059 CDT. The National Lightning Detection Network detected ten strikes during that period and location. The NTSB received a notification that on July 10, 2008, a Cirrus Aircraft Corporation SR22, N596CD, serial number 1710, sustained substantial damage consistent with a lightning strike while tied down on the ramp at PWK. The airplane also sustained damage to its avionics. A lighting strike report for the 5-mile radius around PWK was completed for the time period between July 10, 2008, 0200 CDT to July 11, 2008, 0159 CDT. The National Lightning Detection Network detected 31 strikes during that period and location. Two other Cirrus Aircraft Corporation SR22 airplanes, N616JG, serial number 0151, and N6053U, serial number 0621, were reported by Cirrus Aircraft Corporation as having been involved in lightning strikes. The strikes occurred on about March 6, 2003, for N616JG and on November 16, 2005, for N6053U. The AFRL Evaluation Report on the RDM power supply indicated that a “review of the RDM power supply design is recommended. A single point failure of the TVS, failing in an electrical short condition, will cause secondary damage to the RDM power supply.” The report found that there is no indication, visible to the pilot, that data logging has failed in the event of a power supply failure. It further recommended that a “review of thesystem design be conducted to determine if a cockpit indicator could be installed to alert the pilot when data logging is not functioning."

## Aircraft

- Registration: [N847C](https://openairdocs.org/deregistered/N847C-2013-04-17), registration cancelled 2013-04-17, S/N 3218, built 2008 (OpenAirDocs)
- Reported make and model: CIRRUS DESIGN CORP SR-22 (NO SERIES)
- Registry model: [Cirrus Design SR22](https://openairdocs.org/model/cirrus-design-sr22) (registry code 2130001) (OpenAirDocs)
- Registry engine: [Continental IO-550-N](https://openairdocs.org/engine/continental-io-550-n) (registry code 17215, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 3218
- Year built: 2008
- Airframe hours: 654
- Engines: CONT MOTOR IO-550-N 310 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Windy City Flyers
- Registered owner: Canoecouple Inc
- Airworthiness certificate: Standard, Normal
- Last inspection: 100 hour, December 15, 2010
- Departed: PWK, Wheeling, IL
- Destination: SBN, South Bend, IN
- Flight plan: IFR
- Airport: SBN, South Bend Regional Airport, runway 27L, 8,418 × 150 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 50; injuries: fatal; private; airplane ratings: single-engine land, single-engine sea; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review March 15, 2011; seat: left; flight hours: 372 total, 17 in the last 90 days, 6 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 310° at 16 knots, gusting 24
- Visibility: 7 statute miles
- Lowest ceiling: 1,500 ft overcast
- Temperature: 45 °F, dew point 39 °F
- Altimeter: 29.40 inHg
- Observed at: SBN

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20110404006099A](https://openairdocs.org/incident/20110404006099A), Apr 4, 2011: Cirrus Design Corp SR22, South Bend, IN, Destroyed, 1 fatal. Accident still under investigation. Recoverable data module and chips from the garmin 1000 were sent to Washington NTSB lab for analysis.

## Docket (29 files)

The files NTSB released with the investigation on August 24, 2012, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=78761. 18.7 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 4.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40363670&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- Witness Statements (item 2, .PDF, 624 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40346330&FileExtension=.PDF&FileName=Witness%20Statements-Redacted.PDF
- Witness Statement (item 3, .PDF, 282 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40363669&FileExtension=.PDF&FileName=Witness%20Statement-Redacted.PDF
- Witness Statement (item 4, .PDF, 122 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40370980&FileExtension=.PDF&FileName=Witness%20Statement-Redacted.PDF
- Retention / Release of Wreckage Form (item 5, .PDF, 149 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371018&FileExtension=.PDF&FileName=Retention%20%2F%20Release%20of%20Wreckage%20Form-Redacted.PDF
- Evidence Control Forms - Return of RDM Memory Section & Power Supply Section and Two Garmin SD Chips (item 6, .PDF, 524 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371787&FileExtension=.PDF&FileName=Evidence%20Control%20Forms%20-%20Return%20of%20RDM%20Memory%20Section%20%26%20Power%20Supply%20Section%20and%20Two%20Garmin%20SD%20Chips-Redacted.PDF
- Recoverable Data Module Factual Report (item 7, .PDF, 6 photos, 1.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40370317&FileExtension=.PDF&FileName=Recoverable%20Data%20Module%20Factual%20Report-Master.PDF
- FBI Laboratory SD Card Analysis Report (item 8, .PDF, 3 photos, 212 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40370352&FileExtension=.PDF&FileName=FBI%20Laboratory%20SD%20Card%20Analysis%20Report-Master.PDF
- AFRL RDM Evaluation Report (item 9, .PDF, 2.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40370616&FileExtension=.PDF&FileName=AFRL%20RDM%20Evaluation%20Report-Redacted.PDF
- Other Pertinent Forms and Reports - Airplane Logbook Excerpts (item 10, .PDF, 933 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40363820&FileExtension=.PDF&FileName=Other%20Pertinent%20Forms%20and%20Reports%20-%20Airplane%20Logbook%20Excerpts-Redacted.PDF
- Miscellaneous - Mechanic's Statement Excerpt (item 11, .PDF, 39 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40363665&FileExtension=.PDF&FileName=Miscellaneous%20-%20Mechanic%27s%20Statement%20Excerpt-Redacted.PDF
- Miscellaneous - Mechanic's Pitot/Static Check Statement (item 12, .PDF, 43 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40363666&FileExtension=.PDF&FileName=Miscellaneous%20-%20Mechanic%27s%20Pitot%2FStatic%20Check%20Statement-Redacted.PDF
- Miscellaneous - Pilot's Logbook Excerpts (item 13, .PDF, 2.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371228&FileExtension=.PDF&FileName=Miscellaneous%20-%20Pilot%27s%20Logbook%20Excerpts-Redacted.PDF
- Miscellaneous - Pilot's Advanced Transition Training Certificate (item 14, .PDF, 52 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371255&FileExtension=.PDF&FileName=Miscellaneous%20-%20Pilot%27s%20Advanced%20Transition%20Training%20Certificate-Redacted.PDF
- Miscellaneous - Statement from Windy City Flyer's Chief Pilot confirming the endorsing CFI (item 15, .PDF, 106 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371430&FileExtension=.PDF&FileName=Miscellaneous%20-%20Statement%20from%20Windy%20City%20Flyer%27s%20Chief%20Pilot%20confirming%20the%20endorsing%20CFI-Redacted.PDF
- Miscellaneous - Cirrus's list of CSIP instructors at Windy City Flyers (item 16, .PDF, 295 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371497&FileExtension=.PDF&FileName=Miscellaneous%20-%20Cirrus%27s%20list%20of%20CSIP%20instructors%20at%20Windy%20City%20Flyers-Redacted.PDF
- Miscellaneous - Cirrus Standardized Instructor Pilot details from Cirrus website (item 17, .PDF, 96 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371495&FileExtension=.PDF&FileName=Miscellaneous%20-%20Cirrus%20Standardized%20Instructor%20Pilot%20details%20from%20Cirrus%20website-Master.PDF
- Miscellaneous - Pilot's Medical Application Details (item 18, .PDF, 71 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40363836&FileExtension=.PDF&FileName=Miscellaneous%20-%20Pilot%27s%20Medical%20Application%20Details-Master.PDF
- Miscellaneous - Fuel Receipt (item 19, .PDF, 66 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40363668&FileExtension=.PDF&FileName=Miscellaneous%20-%20Fuel%20Receipt-Redacted.PDF
- Miscellaneous - Mechanic's E-mail Indicating RDM Was Operational At The Annual (item 20, .PDF, 29 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40363910&FileExtension=.PDF&FileName=Miscellaneous%20-%20Mechanic%27s%20E-mail%20Indicating%20RDM%20Was%20Operational%20At%20The%20Annual-Redacted.PDF
- Miscellaneous - Cirrus Service Bulletin SB 2X-31-05 R2 (item 21, .PDF, 258 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40363894&FileExtension=.PDF&FileName=Miscellaneous%20-%20Cirrus%20Service%20Bulletin%20SB%202X-31-05%20R2-Master.PDF
- Miscellaneous - Cirrus POH Excerpts (item 22, .PDF, 681 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40370994&FileExtension=.PDF&FileName=Miscellaneous%20-%20Cirrus%20POH%20Excerpts-Master.PDF
- Miscellaneous - RDM Operational Test Maintenance Manual Extract (item 23, .PDF, 806 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40372094&FileExtension=.PDF&FileName=Miscellaneous%20-%20RDM%20Operational%20Test%20Maintenance%20Manual%20Extract-Master.PDF
- Transcript of Radio Communications - SBN Approach (item 24, .PDF, 96 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40370949&FileExtension=.PDF&FileName=Transcript%20of%20Radio%20Communications%20-%20SBN%20Approach-Redacted.PDF
- Transcript of Radio Communications - SBN Tower (item 25, .PDF, 76 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40370950&FileExtension=.PDF&FileName=Transcript%20of%20Radio%20Communications%20-%20SBN%20Tower-Redacted.PDF
- Photo - Accident site (item 26, .PDF, 158 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371792&FileExtension=.PDF&FileName=Photo%20-%20Accident%20site-Master.PDF
- Photo - Ground Scar (item 27, .PDF, 157 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371793&FileExtension=.PDF&FileName=Photo%20-%20Ground%20Scar-Master.PDF
- Statement of Party Representatives to NTSB Investigation (item 28, .PDF, 283 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40371334&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation-Redacted.PDF
- Statement of Party Representatives to NTSB Investigation (item 29, .PDF, 1.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40363671&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation-Redacted.PDF

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.