FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI08FA282 · Cirrus Design Corporation SR22

11 Sept 2008 · Woodruff, WI, United States

Cirrus Design Corporation SR22 · Accident: loss of control in flight on approach

From General Mitchell International Airport (MKE) to Lakeland Airport Noble F Lee Memorial Field (ARV)

Report a problem

Event

NTSB case
CHI08FA282
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
3 · 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
Charter & commuter
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument 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
N193BS
Operator
Unknown
Onboard fatalities
Unknown
Route
From General Mitchell International Airport (MKE), Milwaukee, WITo Lakeland Airport Noble F Lee Memorial Field (ARV), MINOCQUA/WOODRU, WI
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 135: Air Taxi & Commuter
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
Approach · IFR missed approach
Defining eventThe 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
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

  • Organizational issues › Management
  • Organizational issues › Support/oversight/monitoring
  • Personnel issues › Experience/knowledge

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot was attempting a non-precision instrument approach at dusk in instrument meteorological conditions (IMC) that were below the required approach minimums without an alternate airport. Near the missed approach point, the airplane entered a climb and the airspeed decreased. The airplane gave a stall warning and it subsequently crashed. Recorded flight data revealed that pilot was utilizing the autopilot intermittently and then about two minutes before the accident he turned it off, indicating that he was either not proficient in flying in IMC in the accident airplane make and model and/or utilizing its autopilot. This was further supported by the pilot previously failing his initial airman examination flight and his lack of experience in non precision approaches in such conditions. Furthermore, the postaccident investigation determined that the Part 135 certificate holder had used an unapproved airplane training program paid for by the airplane owner and had falsified air carrier records in order to meet air carrier flight training requirements.

The assignment of the flight shows a loss of operational control due to the attempted approach in below approach minimums; the lack of an alternate airport; the assignment of a pilot that lacked proficiency and/or experience in the weather conditions that were encountered during the flight; and pilot’s lack of explicit authorization for use of an autopilot in lieu of a second-in-command, which was due to the Federal Aviation Administration (FAA) Principal Operation Inspector's (POI) failure to complete the appropriate form. Additionally, the airplane’s registered owner had placed their airplanes on a previous Part 135 certificate but that certificate holder removed those airplanes from the certificate after the owner improperly exercised operational control instead of the certificate holder. The airplanes were then placed on the current certificate holder’s certificate during which time there are indications that the airplane owner was exercising operation control. At least one inspector from the FAA’s Flight Standard District Office (FSDO) was aware of the history of improper exercise of operational control of flights by the airplane owner (not the certificate holder) and no action was taken to stop this practice. Additionally, the FAA FSDO surveillance records revealed that the certificate holder was rated as satisfactory with no comments noted, although throughout the investigation numerous discrepancies were found that within the company that did not comply with Part 135 operations. A postaccident examination revealed no mechanical anomalies that would have precluded normal airplane operation.

Probable cause

The pilot’s failure to maintain airspeed during a missed approach leading to the inadvertent stall. Contributing to the accident were the pilot’s lack of experience in the type of operation conducted, the certificate holder’s loss of operational control, and the lack of adequate oversight of the operation by the Federal Aviation Administration.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI08FA282
Event ID
20080925X01531
Case number
CHI08FA282
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2008-09-12.
  • API snapshot SHA-256: 79c89a13706d0d0d21c3965a9c5fcfde16a6a713f582d311e553e315446ef87d; retrieved 2026-09-13T19:29:25.955Z.