17 Oct 2012: BEECH A36

17 Oct 2012: BEECH A36 (N121VP) — Unknown operator

No fatalities • Wausau, WI, United States

Probable cause

The pilot's decision to attempt an instrument approach in meteorological conditions below approach minimums and his failure to properly execute a missed approach.

— NTSB Determination

Accident narrative

On October 17, 2012, about 0800 central daylight time, a Beech model A36 airplane, N121VP, sustained substantial damage when it impacted trees and terrain short of the runway during an instrument approach to runway 12 at the Wausau Downtown Airport (AUW), Wausau, Wisconsin. The pilot received serious injuries. The aircraft was registered to and operated by the pilot under the provisions of 14 Code of Federal Regulations Part 91 as a business flight. Instrument meteorological conditions prevailed for the flight, which operated on an instrument flight rules flight plan. The flight originated from The Waukesha County Airport (UES), Waukesha, Wisconsin, about 0720.

The pilot reported that as he neared AUW, the airport automated weather observing system was reporting conditions that were below approach minimums. He stated that he thought the early morning fog would be clearing, decided to attempt the approach, and if necessary perform a missed approach and hold until conditions improved. His written report indicated that he attempted an instrument landing system approach to runway 12. As he descended there was considerable glare reflecting off the tops of the low cloud layer below.

Once he had descended into the clouds it became very dark and very turbulent. He stated that his usual practice was to set the decision altitude (DA) and lower the landing gear at the final approach fix. He stated that he believed that he accomplished this on the accident approach. He stated that he did not remember hearing the aural DA warning. He decided to execute a missed approach and began to configure the airplane. He then saw the hills and trees immediately prior to impact.

In his written report, the pilot indicated that there were no mechanical malfunctions or failures of the airplane. No mention was made regarding instrumentation failure or anomalies related to the instrumentation or avionics within the airplane.

Contributing factors

  • cause Pilot
  • cause Compliance w/ procedure
  • Low ceiling

Conditions

Weather
IMC, wind 120/04kt, vis 1sm

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.