WPR10LA180

NTSB accident investigation · Piper PA-22-150 · Terry, MT · March 25, 2010

Accident · No injuriesLimited investigationFinal report
Date
March 24, 2010, 23:30 local (Mar 25, 2010, 05:30 UTC)
Place
Terry, MT
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N3351ZPiper PA-22-150
Defining event
Approach: Loss of engine power (total)
Weather
Visual (VMC) · Night/dark
Status
Completed · report August 12, 2010
Report
Approved by Office Director
NTSB office
Western Pacific Region
Parties
FAA (Helena FSDO)
FAA report
20100324031219A
Case key
75583

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

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.

Findings · 5

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Ceiling/visibility/precip: low ceilingEnvironmental issues › Conditions/weather/phenomena · Contributed to outcomePiper PA-22-150: 2 casesAll aircraft: 190 cases
Performance/control parameters: directional controlAircraft › Aircraft oper/perf/capability · Not attained/maintainedPiper PA-22-150: 38 casesAll aircraft: 3,958 casesProbable cause
Fluids: fuelAircraft › Fluids/misc hardware · Fluid managementPiper PA-22-150: 9 casesAll aircraft: 1,695 casesProbable cause
Wind: gustsEnvironmental issues › Conditions/weather/phenomena · Contributed to outcomePiper PA-22-150: 7 casesAll aircraft: 1,199 cases

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

The pilot, who elected to make a nighttime visual-flight-rules, cross-country business flight, did not acquire a Federal Aviation Administration (FAA) or Direct User Access Terminal weather briefing prior to departure. Instead he gathered his weather information by making a phone call to an acquaintance who was located at his destination and by checking with the FAA's Flight Watch while en route. As he proceeded toward his destination the pilot began flying over a scattered-to-broken cloud layer, which eventually turned to overcast as he neared his destination. After realizing that he would not be able to get into his planned destination, he attempted to get to another airport, but the weather also deteriorated at that airport as well. The pilot then reversed course and headed back in the direction he had come from in the hopes of finding an airport that had visual meteorological conditions (VMC). He was eventually able to descend through a hole in the clouds, but had to pass up the nearest airport because of the bad weather there. He eventually located an airport with VMC, but his airplane ran out of fuel while on a half-mile final. Although he was able to glide to the approach end of the runway, the pilot reported that he landed on the threshold and the airplane bounced once, then settled on the runway. As the tail came down, a gust of wind hit the airplane, which subsequently ground-looped and resulted in substantial damage to the lower left side longeron.

Factual 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.

Aircraft

Registration
N3351Z
Reported as
Piper PA-22-150
Category
Airplane
Serial number
22-7291
Engine
Lycoming O-320 SERIES, 150 horsepower, reciprocating
Damage
Substantial damage
Flight
Business · Part 91
Operator
Daniel Miller
Registered owner
Dem Cattle Co Lp
Airworthiness certificate
Standard, Normal
Last inspection
Annual · May 20, 2009
Departed
KBIL · Billings Logan, MT
Destination
05D · New Town, ND
Airport
8U6 · Terry Airport, runway 26, 4,300 × 75 ft, asphalt

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
38
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Without waivers/limitations
Last flight review
June 8, 2008
Seat
Left
Flight hours
754 total · 230 in this make and model · 700 as pilot in command · 36 in the last 90 days · 16 in the last 30 days · 4 in the last 24 hours

Weather

Conditions
Visual (VMC) · Night/dark
Wind
Variable at 25 knots, gusting 35
Visibility
10 statute miles
Lowest ceiling
10,000 ft overcast
Temperature
30 °F, dew point 27 °F
Altimeter
30.12 inHg

Docket · 2

The files NTSB released with the investigation on May 13, 2010, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.2 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.

Other investigations on N3351Z · 1

Matched to the same aircraft by N-number and date.