23 Jul 2008: Beech 35-C33A — Brian Higley

23 Jul 2008: Beech 35-C33A (N7965M) — Brian Higley

No fatalities • Longmont, CO, United States

Probable cause

A total loss of engine power for reasons undetermined. Contributing to the accident was the unsuitable terrain on which to make a forced landing.

— NTSB Determination

Accident narrative

On July 23, 2008, at 1008 mountain daylight time, a Beech 35-C33A, N7965M, registered to and piloted by the pilot, was substantially damaged when the engine lost power and the airplane landed short of runway 29 at Vance Brand Municipal Airport (LMO), Longmont, Colorado. Visual meteorological conditions prevailed at the time of the accident. The personal flight was being conducted under the provisions of Title 14 Code of Federal Regulations (CFR) Part 91, and a visual flight rules (VFR) flight plan had been filed and activated. There were no injuries to the pilot and his passenger. The cross-country flight originated from Wendover (ENV), Nevada, approximately 0750.

According to the pilot's accident report, he descended from 17,000 feet under partial power and entered a 45-degree entry for a left downwind to runway 29. The landing gear was extended and he completed the pre-landing checklist. On final approach with 20-degrees of flaps extended, the pilot noticed he was slightly below the glidepath and added power to compensate. The engine did not respond. He was forced to land in a barley field. The nose and main landing gear attach points were damaged, the firewall was buckled, and both wings were dented and punctured.

The airplane and engine were later examined at the facilities of Beegles Aircraft Service, Greeley, Colorado. Power train continuity was noted. There was thumb compression on all cylinders. The throttle arm was found fractured in two places. It was sent to NTSB's metallurgical laboratory for analysis. According to their report, "Fracture features generally showed tear ridges and dimples intermixed with casting voids consistent with overstress fracture. No evidence of preexisting cracking such as fatigue features was observed."

Contributing factors

  • cause Engine (reciprocating) — Failure
  • factor Contributed to outcome

Conditions

Weather
VMC, wind 040/03kt, 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.