ASN Wikibase Occurrence # 22817
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | 11-SEP-2008 |
| Time: | 19:15 |
| Type: |  Cirrus SR22 |
| Owner/operator: | Bluesky Taxi Inc |
| Registration: | N193BS |
| MSN: | 2761 |
| Fatalities: | Fatalities: 3 / Occupants: 3 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Near Lakeland Airport, Minocqua-Woodruff, Wisconsin. -
 United States of America
|
| Phase: | Approach |
| Nature: | Passenger - Non-Scheduled/charter/Air Taxi |
| Departure airport: | Milwaukee, WI (MKE) |
| Minocqua/woodru, WI (ARV) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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.
Sources:
NTSB
Accident investigation:
 |
|
Images:
(c) NTSB
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 12-Sep-2008 22:44 | angels one five | Added |
| 13-Sep-2008 11:18 | RobertMB | Updated |
| 13-Jan-2010 11:11 | harro | Updated [Time, Operator, Nature, Departure airport, Destination airport, Source, Narrative] |
| 21-Dec-2016 19:14 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 21-Dec-2016 19:16 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 21-Dec-2016 19:20 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 03-Dec-2017 12:06 | ASN Update Bot | Updated [Cn, Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2023 Flight Safety Foundation