The U.S. aircraft register, updated daily
Accidents · NTSB WPR24FA150 · Final report

Piper PA-18-150 accident near Thurlow, Montana, May 14, 2024

On May 14, 2024 at about 1:20 pm local time, a Piper PA-18-150, registered UNREG, was substantially damaged in an accident during maneuvering (low-alt flying) near Thurlow, Montana. It was an other work-use flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s exceedance of the airplane’s critical angle of attack while maneuvering at low altitude, resulting in an aerodynamic stall and subsequent impact with terrain. Contributing to the accident was the pilot’s distraction by his cell phone use while maneuvering.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
May 14, 2024 · about 1:20 pm local time
Place
Thurlow, Montana · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Piper PA-18-150 · all PA-18-150s on the register
Registration
UNREG · no longer on the register · serial 18-7409083
Damage
Substantial damage
Flight
Other work-use flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot of the tandem seat, non-registered airplane and a passenger were conducting a predator control flight that targeted coyotes on private land. A wildlife control officer on the ground near the designated hunting area was communicating with the pilot via through cell phone and could hear gunfire when the call ended. The control officer attempted to call the pilot back after he expected the flight to have ended but did not determine a need to search for the airplane. A ranch hand located the wreckage later in the day. GPS data recovered from a handheld device found in the airplane wreckage showed that most of the flight was conducted at low altitudes. While engaging wildlife targets, the pilot slowed the airplane to as low as 36 kts groundspeed and performed multiple turns. During the last period of circling maneuvers the airplane slowed to about 25 kts groundspeed while about 113 ft above ground level (agl). The manufacturer’s Pilot’s Operating Handbook for a similar model of airplane indicated that the stall airspeed was 43 mph (37 kts). Examination of the wreckage revealed the airplane impacted terrain in a nearly vertical, nose-down attitude while rotating clockwise. The wreckage signatures and very small debris area were consistent with an aerodynamic stall/spin. While maneuvering at low altitudes and low airspeed, the pilot likely exceeded the airplane’s critical angle of attack, which resulted in an aerodynamic stall/spin at an altitude too low for recovery. The pilot’s use of his cell phone, even with the aid of a hands-free device, likely distracted him from piloting duties. The pilot’s toxicological testing revealed medications that had the potential to cause performance impairment and other medications that were commonly used to treat cold and allergy symptoms; however, toxicological testing did not establish that the pilot was impaired by the medication, nor that he was experiencing cold or allergy symptoms at the time of the accident.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Aerodynamic stall/spin during maneuvering (low-alt flying) defining event
  2. Low altitude operation/event during maneuvering (low-alt flying)

The NTSB's findings

  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
  • Personnel issues › Psychological › Attention/monitoring › Task monitoring/vigilance › Pilot

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; single-engine sea; instrument: airplane
  • Flight time: 26,735 hours in all; 1,000 in this make and model; 25,000 as pilot in command
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: frt
  • Injury: fatal

Passenger

  • Seat: rear
  • Injury: fatal

The aircraft

  • Airframe total time: 2,139.1 hours
  • Last inspection: annual inspection, February 4, 2022; 1,036.4 hours since
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming O-320-A2B (piston); 21,391 hours total

The flight

  • Departed from: Miles City MT
  • Flight plan: none
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 220° at 9 knots
  • Visibility: 10 statute miles
  • Sky: scat at 8,000 ft
  • Temperature: 55°F (13°C), dew point 46°F (8°C)
  • Altimeter: 29.89 inHg
  • Observation at 7:53 am from KBIL, 107 miles away

Weather report (METAR): KBIL 141353Z 22009KT 10SM SCT080 SCT220 13/08 A2989 RMK AO2 SLP102 SHRA DSNT E-SE T01330078 $

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Photographs from the investigation 3 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

15 documents, released by the NTSB on July 29, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Accident Site Survey PDF, 12 pages · our copy View Download
2 GPS Device Specialist's Factual Report PDF, 5 pages · our copy View Download
3 Attachment 1 to GPS Device Specialist's Factual Report data file · our copy Download
4 GPS Track for the Accident Flight map file · our copy Download
5 GPS Track for Accident Flight Excel File data file · our copy Download
6 Pilot's Cell Phone Screen Shots PDF, 7 pages · our copy View Download
7 County Sheriff Events Log PDF, 2 pages · our copy View Download
8 Interviews PDF, 9 pages · our copy View Download
9 Airframe and Engine Examination Report PDF, 11 pages · our copy View Download
10 Photos PDF, 4 pages · our copy View Download
11 Maintenance Logbook Excerpts PDF, 3 pages · our copy View Download
12 Pilot's Operating Handbook Excerpt PDF, 1 page · our copy View Download
13 Toxicological Report, Pilot PDF, 1 page · our copy View Download
14 Toxicological Report Pilot-rated-passenger PDF, 1 page · our copy View Download
15 Party Member Certificates PDF, 2 pages · our copy View Download

The same docket at the NTSB.

Other NTSB records under UNREG the same tail number, which may have belonged to a different aircraft at the time

2026-07-07CEN26LA246 · accident near Hooker, OK · substantial damage · minor injuries
2026-02-28CEN26LA131 · accident near Van Burensburg, IL · substantial damage · no injuries
2025-10-13ERA26LA017 · accident near Gaffney, SC · substantial damage · serious injuries
2025-09-27CEN25LA397 · accident near Harvard, IL · substantial damage · no injuries
2025-09-12CEN25LA385 · accident near Rossville, IN · substantial damage · serious injuries
2025-07-07CEN25LA242 · incident near Ingram, TX · minor damage · no injuries
2025-06-18DCA25WA305 · accident near N/A · serious injuries
2025-05-01OPS25LA034 · incident near Washington, DC
2025-04-11CEN25LA155 · accident near Brady, TX · substantial damage · serious injuries
2025-01-30DCA25MA108 · accident near Washington, DC · destroyed · fatal

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.