FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN10LA103 · Cessna 177RG

16 Jan 2010 · Cedar Rapids, IA, United States

Cessna 177RG · Accident: loss of control in flight on approach

From Clermont County Airport (I69) to The Eastern Iowa Airport (CID)

Report a problem

Event

NTSB case
CEN10LA103
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 177RG

Aircraft type
Cessna 177
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
N53120
Onboard fatalities
Unknown
Route
From Clermont County Airport (I69), Batavia, OHTo The Eastern Iowa Airport (CID), Cedar Rapids, IA
Aircraft age
Not recorded
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 final 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
Loss of control in flight
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 › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot's original destination was below weather minimums so he diverted to another airport. He flew the approach to runway 9 with one receiver/navigational unit tuned to the global positioning system (GPS) approach and one tuned to the instrument landing system (ILS) approach. He reported that he began getting conflicting information between the GPSs so he executed a missed approach. The pilot reported that during the second approach he had trouble maintaining the glideslope and he had to keep adding power to maintain a proper descent rate. He then received erratic information and needle oscillations on both glideslope indicators. The pilot stated that he was at full power, so he did not have additional power in order to climb for a missed approach. The pilot believes that the left wing stalled about 600 feet above the ground. He stated that he was in “some kind of spin” or unusual attitude with the “nose slightly downward and tilted slightly to the left.” The pilot reported that the last memory he has prior to impact was pulling up. The airplane impacted the terrain in an open field, which resulted in substantial damage to the fuselage and left wing. Radar data indicated that from the time the airplane was established on the approach up until the last minute of data available, the aircraft’s ground track varied from 97 degrees to 70 degrees, with a descent rate of approximately 500 feet per minute. The airplane’s rate of descent during the last 46 seconds of radar data increased to about 800 feet per minute and the heading changed from 95 degrees to 119 degrees, then to 13 degrees. The approaches were checked after the accident with no anomalies found. The pilot received his instrument rating two weeks prior to the accident. He reported having about 5 hours of actual instrument flight time and about 72 hours of simulated instrument flight time.

Probable cause

The pilot's failure to maintain aircraft control while flying an instrument approach. Contributing to the accident was the pilot's lack of experience in actual instrument conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN10LA103
Event ID
20100120X85827
Case number
CEN10LA103
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 2010-01-17.
  • API snapshot SHA-256: 56c007637509bcfd13b64b66d6749b0f57b72ab12732590c9c99d8454ea41802; retrieved 2026-09-15T13:38:25.782Z.