ASN Wikibase Occurrence # 48610
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: | Saturday 6 December 2008 |
| Time: | 15:13 |
| Type: |  Cessna 206H |
| Owner/operator: | Private |
| Registration: | N6053B |
| MSN: | 20608272 |
| Year of manufacture: | 2006 |
| Total airframe hrs: | 753 hours |
| Engine model: | Lycoming IO-540-AC1A5 |
| Fatalities: | Fatalities: 1 / Occupants: 1 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | About 18 miles east of Traverse City, just south of Kalkaska, MI -
 United States of America
|
| Phase: | Approach |
| Nature: | Private |
| Departure airport: | South St Paul, MN (SGS) |
| Glens Falls, NY (GFL) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The instrument-rated pilot departed on a cross-country flight from Minnesota to New York. While en route and in visual flight rules conditions above the clouds, the pilot elected to divert to a nearby airport due to adverse weather conditions. The pilot received an instrument-flight-rules clearance, radar vectors, and instrument approach information from air traffic control (ATC). However, he was unable to complete the approach due to trouble receiving the localizer signal for the instrument landing system (ILS) approach. The pilot requested that he be able to continue with only glideslope information and the controller informed the pilot that his current altitude (2,700 feet mean sea level) was the minimum altitude that ATC could authorize. The pilot informed ATC that he was going to descend and ATC reported that radar contact was lost. Over the next approximately 4 minutes, the controller instructed the pilot several times to climb. The pilot did not comply with these requests and radar data indicated that the airplane circled several times about 1.5 miles east of the airport during this time period. After several requests the pilot agreed to climb and accepted vectors for another approach. Transcripts indicated that the pilot was able to successfully tune his navigation equipment for the global-positioning-system approach to the airport. While the airplane was being vectored for another approach the controller instructed the pilot to climb and the pilot responded "I'm off," which was the last transmission received from the accident airplane. Radar data showed that the airplane remained airborne and maneuvered east of the airport for 36 minutes after the last radio transmission from the pilot. Witnesses on the ground reported seeing the airplane circling before it struck trees, the ground, and a residence. The last radar contact was within 0.1 miles of the accident location. Review of the pilot's flight records showed that he had accumulated about 8 hours of actual instrument flight time since he received an instrument rating about 10 months prior to the accident; however, the records do not indicate that the pilot had met the recent flight experience required by regulations to act as pilot in command in instrument flight conditions. The autopsy on the pilot revealed evidence of multiple previous and one very recent, possibly ongoing, heart attack. There were no indications that the pilot had been symptomatic with or was aware of his heart disease. The circumstances of the accident do not suggest incapacitation, and the pilot did not indicate any symptoms in discussions with air traffic controllers. It could not be determined whether distraction or impairment due to the pilot’s heart disease may have played a role in this accident.
Probable Cause: The pilot's failure to maintain clearance from trees and terrain during the instrument-flight-rules flight. Contributing to the accident was the pilot's failure to comply with instrument flight procedures and his lack of recent instrument flight experience.
Accident investigation:
 |
|
Sources:
NTSB
FAA register: 2. FAA: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?omni=Home-N-Number&nNumberTxt=6053B
5. https://flightaware.com/live/flight/N6053B/history/20081206/1610ZZ/KSGS/KTVC
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 08-Dec-2008 08:54 | angels one five | Added |
| 08-Dec-2008 12:16 | RobertMB | Updated |
| 18-Jul-2016 11:51 | Dr.John Smith | Updated [Time, Operator, Location, Nature, Departure airport, Destination airport, Source, Narrative] |
| 18-Jul-2016 11:58 | Dr.John Smith | Updated [Destination airport] |
| 03-Dec-2017 13:10 | ASN Update Bot | Updated [Time, 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:
©2024 Flight Safety Foundation