Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

March 25, 2010 · Piper PA-22-150 · N3351Z

Terry, MT

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
March 25, 2010
Injury Outcomes
No injuries (2 uninjured)
Location
Terry, MT
Aircraft
Piper PA-22-150
Tail Number
N3351Z
Operator
Daniel Miller
Injuries
None
Aircraft Damage
Substantial
NTSB Number
WPR10LA180

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.

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

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

Flight

Event TypeAccident
Event Time23:30 MDT
Nearest AirportTerry Airport (0nm)
Runway26
Runway Length4300 ft
Runway Width75 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-22-150
Tail NumberN3351Z
Aircraft CategoryAir
DamageSubstantial
OperatorDaniel Miller
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320 SERIES · Reciprocating · 150
Seats4

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 38 · Third Class · None

Conditions

ConditionsVMC
LightDark Night
Wind25 kt, gusting 35 kt
Visibility10 sm
CeilingOvercast 10000 ft
Temperature / Dew Point30 C / 27 C
Altimeter30.12 inHg
Weather SourcePILO

Appendix: Source Data