12 Nov 2011: CESSNA 180

12 Nov 2011: CESSNA 180 (N3606C) — Unknown operator

No fatalities • Eau Claire, WI, United States

Probable cause

The pilot’s disorientation during a night flight, which resulted in an off-airport landing, and his inadequate directional control during the landing roll. Contributing to the accident was the loss of the airplane’s electrical system power.

— NTSB Determination

Accident narrative

On November 11, 2011, about 1900 central standard time, a Cessna 180, N3606C, impacted a pole during a precautionary landing on a highway near Eau Claire, Wisconsin. The pilot, the sole occupant, was not injured. The airplane sustained substantial damage. The airplane was registered to and operated by the private pilot under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Night visual flight rules conditions prevailed at the time of the accident, which operated without a flight plan. The flight departed the Chippewa Valley Regional Airport (EAU), near Eau Claire, Wisconsin, about 1640, and was destined for the Crystal Airport (MIC), near Minneapolis, Minnesota.

The pilot reported that he departed MIC about 1430 to 1500 for a sightseeing flight along the St. Croix River to La Crosse, Wisconsin. He stated that he did not intend to land at La Crosse. The pilot added he stopped to refuel at Rice lake, Wisconsin, before he started his return to MIC when dusk conditions began.

While en route during the return flight, the airplane had a loss of electrical power rendering the cockpit “virtually black.” The pilot used a flashlight to illuminate the cockpit as he looked for a diversion airport for over an hour. After not finding a nearby airport, he elected to perform a precautionary landing on roadway. The pilot reported that the “tailwheel castored”, it hit an obstacle, “and did a fair amount of damage to the airplane”. The pilot listed no other mechanical malfunctions in his report other than the loss of electrical power. The pilot was asked if he flown anywhere else and he reported that he did not land at any other airport other than Rice Lake.

However, the manager of the fixed base operator (FBO) at EAU reported that the accident airplane had landed there around 1620. The pilot asked an FBO employee which airport this was. The pilot was told he was at EAU. According to the manager, the pilot said that he had originated from the La Crosse area and that he was trying to get to Stillwater, Minnesota. The FBO staff pointed out the general direction toward Stillwater. According to the FBO manager, the pilot seemed shocked when he discovered that there was a control tower at the airport and realized that he had landed without any radio communication.

According to the manager, the pilot said that his airplane’s engine was flooded. He could not get his engine started and accepted the manager’s assistance to get the airplane started. The pilot asked which direction was north and the manager pointed west and replied that west was the direction to Stillwater. The manager stated that he reminded the pilot to contact the control tower and depart to the west. The pilot taxied the airplane out about 1640 without contacting the control tower and the next time the manager heard about the pilot was after the pilot landed the airplane on the highway.

A Federal Aviation Administration inspector examined the wreckage on-scene and confirmed the substantial damage to the left wing. A subsequent examination revealed that the airplane’s battery had a low power state.

At 1956, the recorded weather at EAU was: wind 190 degrees at 4 knots; visibility 10 statute miles; sky condition clear; temperature 3 degrees C; dew point -3 degrees C; altimeter 29.62 inches of mercury.

Contributing factors

  • Contributed to outcome
  • Contributed to outcome
  • cause Pilot
  • cause Pilot
  • factor Electrical power system — Failure

Conditions

Weather
VMC, wind 190/04kt, vis 10sm

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.