25 Mar 2010: PIPER PA-22-150 — Daniel Miller

25 Mar 2010: PIPER PA-22-150 (N3351Z) — Daniel Miller

No fatalities • Terry, MT, United States

Probable cause

The pilot's failure to maintain directional control during the landing roll in gusting winds. Contributing to the accident was a loss of engine power on final approach due to fuel exhaustion as a result of the pilot having to divert due to deteriorating weather conditions.

— NTSB Determination

Accident narrative

On March 24, 2010, about 2330 mountain daylight time, a Piper PA-22-150 Pacer, N3351Z, ground-looped at Terry Airport, Terry, Montana, after experiencing fuel exhaustion while on final approach. The private pilot and his passenger were not injured, but the airplane, which was owned by DEM Cattle Company, sustained substantial damage to the left side lower longeron. The 14 Code of Federal Regulations Part 91 business flight, which departed Billings, Montana, about four hours prior to the accident, was en route to New Town, North Dakota. The landing was being made in night visual meteorological conditions (VMC). No flight plan had been filed.

According to the pilot, he did not seek a weather briefing from a Federal Aviation Administration (FAA) Flight Service Station or a DUAT (Direct User Access Terminal) provider prior to departure. Instead he called an acquaintance at his destination in order to find out what the current weather was, and what the forecast for the area was expected to be around the time of his arrival. While en route he contacted Flight Watch, the FAA's en route flight advisory service, to get an update on the weather at New Town. Flight Watch advised him that the weather around the New Town area was marginal VFR, with a current visibility of 10 miles, but with broken ceilings between 700 and 1,000 feet above ground level (agl). Once he got to a point about 20 to 25 miles east of Miles City, Montana, he began flying over a scattered to broken layer of clouds, which he eventually discovered reached all the way to his destination. As he continued on toward his destination, the clouds below him became a solid overcast, so he elected not to continue on to New Town, but instead asked Flight Watch to direct him to an airport that had visual meteorological conditions (VMC). Flight watch advised him that the weather in Dixon, North Dakota was still VFR, so the pilot started flying in that direction. But, by the time he got to within about 30 miles of Dixon, the weather had deteriorated there as well. At that time Flight Watch advised the pilot that his next best option was Bismarck, North Dakota, but the pilot decided to turn back toward the west to see if he could find an open airport in the direction he had originally come from.

As he headed back toward the west, the pilot was able to make contact with Minneapolis Center, whereupon he advised them of his "low fuel" conditions, and his desire to find an airport with VMC. The pilot was eventually able to descend through a hole in the clouds near Glendive, Montana, and although he initially thought about trying to land at Dawson Community Airport in Glendive, because of the weather conditions there, he elected to follow State Highway 94 further to the west. As he neared Terry, Montana, which is located about 35 miles southwest of Glendive, the weather conditions had improved enough that he decided to land at Terry Airport, which is located within one-quarter mile of State Highway 94.

While on a straight-in to runway 26, and still about one-half mile east of the runway threshold, the airplane ran out of fuel, and the engine stopped producing power. The pilot was able to stretch his glide to reach the threshold, but during the night downwind flare/touchdown on the unlighted runway, the airplane encountered a significant wind gust resulting in a ground-loop.

A post-accident inspection confirmed that there was no fuel left in the airplanes fuel system.

Contributing factors

  • factor Pilot
  • Contributed to outcome
  • cause Directional control — Not attained/maintained
  • factor Fluid management
  • Contributed to outcome

Conditions

Weather
VMC, wind 000/25kt, 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.