17 Jan 2010: CESSNA 177RG — FISHER PHILIP

17 Jan 2010: CESSNA 177RG (N53120) — FISHER PHILIP

No fatalities • Cedar Rapids, IA, United States

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.

— NTSB Determination

Accident narrative

On January 16, 2010, at 1940 central standard time, a Cessna 177RG, N53120, collided with the terrain approximately one-half mile west of the airport while on the instrument landing system (ILS) runway 09 approach at the Eastern Iowa Airport (CID), Cedar Rapids, Iowa. The private instrument rated pilot and two passengers were seriously injured. The airplane received substantial damage to the fuselage and left wing. The 14 Code of Federal Regulations Part 91 personal flight was operating on and instrument flight plan in instrument meteorological conditions. The flight originated from the Clermont County Airport (I69), Batavia, Ohio, at 1705 eastern standard time.

The original destination for the flight was the Monticello Regional Airport (MXO), Monticello, Iowa. While en route, it was determined that MXO was below weather minimums so the flight diverted to CID. The pilot reported the airplane had two Garmin 530s, a Wide Area Augmentation System (WAAS), and the global positioning system (GPS) steering was slaved to the autopilot. He stated he had one receiver/navigation unit tuned to the GPS runway 9 approach and the other tuned to the ILS runway 9 approach. He stated that with the autopilot he can select course via the GPS or the heading bug. The pilot stated that during the approach he began receiving conflicting information between the GPS and the ILS. He then noticed that he lost the receiver autonomous integrity monitoring (RAIM) system. The pilot initiated a missed approach and climbed back into visual meteorological conditions where he received vectors for a second approach.

The pilot reported he began the inbound leg of the second approach with both the GPS and the ILS in agreement. He stated he had trouble maintaining the glideslope and he had to keep adding power to maintain a proper descent rate. The pilot stated the top glideslope indicator began displaying erratic information with the glideslope needle rapidly changing from a full up deflection to a full down deflection. The pilot stated he was at full power at this point, so he did not have additional power in order to climb for a missed approach. He stated the bottom ILS indication was more stable, but it too began showing “…oscillating vertical deflections.”

The pilot stated that at an altitude of approximately 600 feet above the ground, he felt the right wing rise, which he believes was a result of the left wing stalling. He stated the directional gyro then indicated that he was in a left turn, which he tried to correct, but could not. He stated he was in “some kind of spin” or unusual attitude with the “nose slightly downward and tilted slightly to the left.” The pilot reported the last memory he has prior to impact was pulling up. The airplane impacted the terrain in an open field.

Air traffic control radar data indicated 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 pilot received his instrument pilot rating approximately 2 weeks prior to the accident. He reported having about 5 hours of actual instrument experience and 72 hours of simulated instrument experience.

Following the accident both the ILS and GPS approaches were flight checked by the Federal Aviation Administration and no discrepancies were found.

Contributing factors

  • cause Pilot
  • Effect on operation
  • factor Pilot
  • cause Performance/control parameters — Not attained/maintained

Conditions

Weather
IMC, wind 170/05kt, vis 3sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.