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

February 10, 2024 · Piper PA-32R-301T · N989SR

Spanish Fork, UT

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
February 10, 2024
Injury Outcomes
2 injuries (2 minor injuries)
Location
Spanish Fork, UT
Aircraft
Piper PA-32R-301T (2002)
Tail Number
N989SR
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
WPR24LA088

The pilot reported that, during the local flight, he switched fuel tanks several times. While descending for landing at the conclusion of the flight, he conducted the before-landing checklist, switched fuel tanks, and turned on the electric fuel pump. On the downwind leg of the traffic pattern, he conducted the landing checklist and switched to the fullest fuel tank; however, he did not specifically recall if the fuel selector was placed in the detent of the fuel tank selected. While abeam the runway threshold, the engine lost partial power. The pilot attempted to troubleshoot by switching the fuel selector to the opposite fuel tank and cycled the electric fuel pump off and back on. Despite his attempts to troubleshoot, the engine lost total power. The pilot determined that the airplane would not reach the runway and initiated a forced landing to an open field, during which the airplane sustained substantial damage. Examination of the recovered airframe and engine revealed no preaccident mechanical malfunctions or failures that would have precluded normal operation. Continuity of the fuel system was established from the main fuel tanks throughout the system to the fuel servo. A test run of the engine revealed no anomalies. Data retrieved from an onboard engine monitor indicated that, before the loss of power, the fuel flow decreased from about 15 gallons per hour to 0 gallons per hour, with corresponding reductions in engine rpm, horsepower, oil pressure, and oil temperature values. The total amount of fuel onboard the airplane before the flight could not be determined; however, fuel was found in the tanks after the accident. Based on the available information, it is likely that the pilot failed to ensure proper placement of the fuel selector, which resulted in fuel starvation and a total loss of engine power.

NTSB Probable Cause

The pilot's failure to ensure proper placement of the fuel selector, which resulted in a total loss of engine power due to fuel starvation.

Full Narrative

On February 10, 2024, about 1430 mountain standard time, a Piper PA-32R-301T, N989SR, was substantially damaged when it was involved in an accident near Spanish Fork, Utah. The pilot and passenger sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that he planned on conducting two flights on the day of the accident. Upon arrival at Spanish Fork Municipal Airport/Woodhouse Field (SPK), Spanish Fork, Utah, he conducted a preflight inspection of the accident airplane. According to the airplane’s fuel totalizer, the airplane had about 47 gallons of fuel, which he visually confirmed. The pilot reported that, during the local flight, he switched fuel tanks several times. While descending toward the airport’s traffic pattern for landing at the conclusion of the flight, the pilot completed the before-landing checklist, switched fuel tanks, and turned on the electric fuel pump. While on the left downwind leg for runway 30, he conducted the landing checklist and switched to the fullest fuel tank; however, he did not recall if the fuel selector lever was rotated and placed in the detent of the fuel tank selected. While abeam the runway threshold, the engine lost partial power. The pilot attempted to troubleshoot by switching the fuel selector lever to the opposite fuel tank and cycled the electric fuel pump off and back on. Despite his attempts to troubleshoot, the engine lost total power. The pilot turned toward the runway and transmitted a mayday call on the airport’s common traffic advisory frequency. He realized that the airplane would not reach the runway and initiated a forced landing to an open field. During the landing, the airplane impacted power lines and terrain before it came to rest upright. Postaccident examination of the airplane identified crushing of the forward fuselage. Flight control continuity was established from all primary flight control surfaces to the cockpit controls. All areas of separation within the flight control cables were consistent with overload or separation by recovery personnel. According to the airport manager, when he arrived at the accident location, the left wing was partially separated from the fuselage at the wing root due to impacting a tree. Fuel was observed leaking from the left wing fuel tank. Several large bags of fuel absorbent were utilized to contain the leaking fuel. When cleared to relocate the airplane, onto airport property, the left wing was separated and substantial amounts of fuel began leaking. He estimated the tank in the left wing was about 1/4 to 1/2 full. Wreckage recovery personnel reported that about 15 gallons of fuel was drained from the right wing. Examination of the recovered airframe and engine revealed no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. Fuel system continuity was established from the main fuel tanks throughout the system to the fuel servo. All areas of separations within the fuel system were consistent with impact separation or separation by recovery personnel. The fuel selector valve appeared undamaged and functioned normally when rotated. A small amount of fuel was observed in the airframe fuel strainer. An external fuel tank was attached to the electric fuel pump inlet port. The engine started during the initial attempt. Due to the engine instruments being removed, the engine rpm was not observed. The engine ran throughout various power settings uneventfully for about five minutes. A functional check was conducted of the magnetos, and a change in engine in noise was noted during the left and right magneto checks. Due to the damage to the propeller, the throttle was not advanced to the full forward position. The airplane was equipped with a J. P. Instruments EDM-930 engine monitor. The engine monitor was removed and sent to the National Transportation Safety Board Vehicle Recorder Laboratory. Examination of the engine monitor revealed no visible damage to the exterior of the unit. The device powered on normally and data was extracted using the manufacturer’s procedures. The data revealed that, about 1429, the fuel flow decreased from about 15 gallons per hour to 0 gallons per hour, with corresponding reductions of engine rpm, horsepower, oil pressure, and oil temperature values.

Flight

Event TypeAccident
Event Time14:30 MST
Nearest AirportSpanish Fork Muni/Woodhouse Fl (1nm SE)
Runway30
Runway Length6500 ft
Runway Width100 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-32R-301T
Tail NumberN989SR
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · TIO-540-AH1A · Reciprocating · 300
Seats6

People & Injuries

Injury Summary2 injuries (2 minor injuries)
Fatal0
Serious0
Minor2
Uninjured0
Total2
Crew 1Age 54 · Third Class · Minor
Crew 2Minor

Conditions

ConditionsVMC
LightDaylight
Wind160° @ 4 kt
Visibility10 sm
CeilingOvercast 4200 ft
Temperature / Dew Point34 F / 21 F
Altimeter30.05 inHg
Observation Time14:56
Weather SourceWFAC

Appendix: Source Data