20 Mar 2008: Beech F90 — Kreg Davis

20 Mar 2008: Beech F90 (N124BK) — Kreg Davis

No fatalities • Idaho Falls, ID, United States

Probable cause

the pilot's misjudged distance and airspeed that led to a failure to attain the proper touchdown point and a runway overrun. Contributing factors were the snow and muddy conditions off the runway.

— NTSB Determination

Accident narrative

On March 20, 2008, about 0100 mountain daylight time, a Beech F90, N124BK, had the nose gear collapse during a landing overrun at Idaho Falls, Idaho. The pilot/owner was operating the airplane under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The certificated private pilot and five passengers were not injured. The airplane sustained substantial damage to the airframe in the nose wheel well. The personal cross-country flight departed Salt Lake City, Utah, with a final destination of Idaho Falls. Visual meteorological conditions prevailed, and an instrument flight rules (IFR) flight plan had been filed.

The pilot stated that he flew IFR from Salt Lake City to Idaho Falls. He cancelled IFR about 25 miles from Idaho Falls, and proceeded under visual conditions. He decided to land on runway 35.

The pilot stated that he was high and fast as he crossed the numbers. At touchdown and reverse thrust, he didn't like what he was experiencing, so he added power to abort the landing. It took the engines 1 to 2 seconds to spool up, and he decided that it would be better to roll off the end of the runway than to attempt a takeoff with so little runway left. He went back into reverse thrust. He did not apply full brakes, as he was concerned that the airplane might flip over. The airplane went off the end of the runway, and slid to a stop in snow and mud. The nose gear collapsed in the process.

The pilot shut the engines down, and verified that his passengers were not injured. They evacuated the airplane, and went to the hangar.

The pilot stated that he had planned for the late hour arrival by resting during the day. He was alert and in good health. The runway was clear and dry, with excellent braking conditions. The airplane had come out of a phase check recently, and there were no squawks; the engines ran great.

Contributing factors

  • cause Incorrect use/operation
  • cause Incorrect use/operation
  • factor Wet/muddy
  • factor Snowy/icy
  • cause Incorrect use/operation
  • cause Pilot

Conditions

Weather
VMC, wind 200/11kt, 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.