ASN Wikibase Occurrence # 150971
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: | Sunday 2 December 2012 |
| Time: | 18:33 |
| Type: |  Cessna 172M Skyhawk |
| Owner/operator: | Southeastern Minnesota Flying Club, Inc. |
| Registration: | N9853Q |
| MSN: | 17265797 |
| Year of manufacture: | 1975 |
| Total airframe hrs: | 13143 hours |
| Engine model: | Lycoming O-320-E2D |
| Fatalities: | Fatalities: 0 / Occupants: 4 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Rochester International Airport - KRST, Rochester, MN -
 United States of America
|
| Phase: | Landing |
| Nature: | Private |
| Departure airport: | Green Bay, WI (GRB) |
| Rochester, MN (RST) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The commercial pilot was conducting a personal cross-country flight. According to recorded air traffic control (ATC) transmissions and radar track data, the pilot attempted an instrument landing system (ILS) approach to an airport where the reported weather conditions were below published minimums for the approach. The pilot reported that the airplane descended on the glideslope into fog where there was limited to no forward visibility and that he initiated a missed approach at 1,600 ft mean sea level (msl) because he could not see the runway environment. The airplane impacted terrain shortly after the pilot increased engine power to transition into a climb for the missed approach. A review of the pilot’s flight logbook established that he had not maintained his instrument currency, as required by federal regulations, during the 6 months preceding the accident.
According to radar track data, the airplane made multiple course corrections on both sides of the localizer centerline as it proceeded inbound toward the runway. The airplane eventually flew through the right localizer limit about 1.2 miles from the runway threshold. The airplane continued to fly away from the localizer and descended below the published decision height of 1,480 ft msl. The airplane impacted terrain about 1/2 mile right of the localizer centerline and about 3/4 mile from the runway threshold while in a descending right turn.
Postaccident testing revealed that there were no anomalies with the airplane’s altimeter that would have prevented its normal operation. Additionally, the pilot had selected a Kollsman window setting that would have minimized any indication errors during the instrument approach. Further avionic testing identified no anomalies with the airplane’s primary navigation radio and its associated course deviation indicator. According to ATC documentation, all components of the ILS approach were fully functional at the time of the accident. Further, 12 minutes before the accident, another airplane had completed the same ILS approach to the runway without any reported issues or anomalies.
In conclusion, the weather and light conditions at the time of the accident and the pilot’s maneuvering during the approach were conducive to the development of spatial disorientation. Therefore, it is likely that the pilot became spatially disoriented during the instrument approach, which resulted in the airplane descending below decision height and impacting terrain outside the lateral limits of the localizer. The pilot’s lack of recent instrument flight experience likely contributed to him becoming spatially disoriented during the instrument approach.
Probable Cause: The pilot’s spatial disorientation during the instrument approach in night, instrument meteorological conditions, which resulted in the airplane descending below decision height and impacting terrain outside the lateral limits of the localizer. Contributing to the accident was the pilot's lack of recent instrument flight experience.
Accident investigation:
 |
|
Sources:
NTSB
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=9853Q
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 03-Dec-2012 06:10 | gerard57 | Added |
| 03-Dec-2012 06:15 | harro | Updated [Location] |
| 03-Dec-2012 06:16 | harro | Updated [Aircraft type, Registration, Cn, Operator, Source] |
| 03-Dec-2012 15:23 | Geno | Updated [Time, Aircraft type, Operator, Location, Departure airport, Destination airport, Source, Narrative] |
| 21-Dec-2016 19:28 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 28-Nov-2017 14:01 | ASN Update Bot | Updated [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