CEN13LA088 · Cessna 172M
Southeastern Minnesota Flying Club Cessna 172M · Accident: controlled flight into terrain/object (CFIT) on approach
From Austin Straubel International Airport (GRB) to Rochester International Airport (RST)
Event
- NTSB case
- CEN13LA088
- 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
- 0 · 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
- General aviation
- 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
Cessna 172M
- Aircraft type
- Cessna 172
- 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
- N9853Q
- Onboard fatalities
- Unknown
- Route
- From Austin Straubel International Airport (GRB), Green Bay, WITo Rochester International Airport (RST), Rochester, MN
- Aircraft age
- About 37 years (built 1975)
- 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 91: General Aviation
- 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
- Controlled flight into terrain/object (CFIT)
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Psychological
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN13LA088
- Event ID
- 20121203X62629
- Case number
- CEN13LA088
- 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 2012-12-03.
- API snapshot SHA-256: 0b55c9b38ce502a52aac038211c8433cb68c1f90d23d3faa62325fb6e4be3fc2; retrieved 2026-09-15T20:31:06.728Z.