Cessna 172M N9853Q
3 December 2012 · Rochester, Minnesota, United States · Minor injuries
Summary
On 3 December 2012 at about 00:33 local time, a Cessna 172M registered N9853Q, operated by Southeastern Minnesota Flying Club, Inc., was involved in an accident near Rochester, Minnesota, United States. 4 people were on board and 4 had minor injuries. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 00:33
- Classification
- Accident
- Location
- Rochester, Minnesota, United States
- Nearest airport
- Rochester International (RST)
- Coordinates
- 43.9189, -92.5256
- Aircraft
- Cessna 172M
- Registration
- N9853Q
- Category
- Airplane
- Year built
- 1975
- Engines
- 1
- Operator
- Southeastern Minnesota Flying Club, Inc.
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Green Bay → Rochester
- Aircraft damage
- Substantial
- Weather
- IMC
- Light
- Night/Dark
- NTSB number
- CEN13LA088
People
4 people had minor injuries.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 4 | 0 | 0 | 4 | 0 |
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.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
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.
Quoted verbatim from the NTSB record.
Other Cessna 172 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 9 Sep 2012 | Cessna 172N | Acreúna Municipality, Brazil | - | Fatal | 4 |
| 9 Jul 2012 | Cessna 172S | Allentown, Pennsylvania, United States | Gateway Aviation | No injuries | - |
| 19 Apr 2012 | Cessna 172R | Richmond, Kentucky, United States | Eastern Kentucky University | No injuries | - |
| 17 Feb 2012 | Cessna 172N | Flat Rock, Virginia, United States | - | No injuries | - |
| 16 Nov 2012 | Cessna 172 | Ostermaima, Sweden | Arbra Flygklubb Hovsatter | Fatal | 1 |
| 22 Sep 2012 | Cessna 172S | Land O'Lakes, Florida, United States | - | Fatal | 1 |
All 12,209 records for this type
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 12 Jul 2012 | Mikoyan Gurevich MIG 21MF | Minneapolis, Minnesota, United States | Ward William E | Minor injuries | - |
| 11 Jun 2012 | Airbus A320-212 | Minneapolis, Minnesota, United States | Delta Air Lines Inc | Serious injuries | - |
| 20 Jul 2012 | Mooney M20K | Hutchinson, Minnesota, United States | - | No injuries | - |
| 27 Aug 2012 | Top Dog TD2 | Bemidji, Minnesota, United States | - | Fatal | 1 |
| 2 Oct 2012 | Cirrus SR20 | Eden Prairie, Minnesota, United States | Hummingbird Ventures LLC | No injuries | - |
| 8 Jun 2012 | Piper PA-31-325 | Duluth, Minnesota, United States | - | Fatal | 1 |