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

December 26, 2002 · Piper PA-28-181 · N75337

Spanish Fork, UT

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
December 26, 2002
Injury Outcomes
2 injuries (1 serious injury, 1 minor injury)
Location
Spanish Fork, UT
Aircraft
Piper PA-28-181
Tail Number
N75337
Operator
Million Air Salt Lake City
Injuries
Serious
Aircraft Damage
Substantial
NTSB Number
DEN03LA026

The pilot departed, with full fuel tanks, to visit family members for Christmas. During his return trip aircraft preflight, he visually checked the fuel tanks and fuel gauges. "One registered just under 20 gallons and the other 15 gallons." He did not take on additional fuel before departure. The pilot said the engine lost power approximately half way home. He said he enriched the mixture, activated the electric fuel pump, and switched fuel tanks. The engine's power increased. The pilot said he decided to head toward Spanish Fork Canyon. Shortly thereafter, with the Spanish Fork Airport in sight, the engine again lost power. The pilot performed a forced landing to an open field. During the landing roll, the airplane nosed over. Postaccident examination of the terrain revealed that it was frozen hard. An FAA inspector retrieved approximately 1/4 cup of fuel from one fuel tank, and he reported the other tank was empty. The inspector also said the fuel strainers were clean, but dry.

NTSB Probable Cause

the pilot's inadequate preflight planning and preparation and his in-flight decision/planning resulting in fuel exhaustion. A contributing factor was the rough, frozen terrain at the landing site.

Full Narrative

On December 26, 2002, at approximately 0945 mountain standard time, a Piper PA-28-181, N75337, was substantially damaged when it nosed over during a forced landing in an open field near Spanish Fork, Utah. The instrument rated private pilot was seriously injured, and his passenger received minor injuries. Keystone Aviation, Salt Lake City, Utah, was operating the airplane under Title 14 CFR Part 91. Visual meteorological conditions prevailed for the personal cross-country flight that originated from Blanding, Utah, approximately 2 hours before the accident. No flight plan had been filed. The pilot said he had the airplane topped off with fuel prior to departure from Salt Lake City 2 days before the accident. He flew to Blanding, Utah, for Christmas celebrations with family members. The flight lasted approximately 2 hours and 15 minutes. Prior to departure from Blanding, the pilot said he visually checked the fuel tanks and fuel gauges. "One registered just under 20 gallons and the other 15 gallons." The pilot said he calculated his fuel burn at 9 gallons per hour. He did not take on additional fuel before departure. The pilot said that about half way between Price and Provo, Utah, the engine lost power. He said he enriched the mixture, activated the electric fuel pump, and switched fuel tanks. The engine's power increased. The pilot said he decided to head toward Spanish Fork Canyon. Shortly thereafter, with the Spanish Fork Airport in sight, the engine again lost power. The pilot performed a forced landing to an open, plowed field. During the landing roll, the airplane nosed over bending both wings, the vertical stabilizer, and the firewall. Postaccident examination of the terrain revealed that it was frozen hard. An FAA inspector retrieved approximately 1/4 cup of fuel from one fuel tank, and he reported that other tank was empty. The inspector also said the fuel strainers were clean, but dry. According to the Pilot's Operating Handbook, the airplane has 48 gallons of usable fuel capacity. The Hobbs meter in the airplane reflected a total time from Salt Lake City to Blanding, and from Blanding to the accident site, as 5.2 hours. This results in an average fuel burn rate of approximately 9.3 gallons per hour.

Flight

Event TypeAccident
Event Time09:45 MST
Nearest Airport0nm
Flight Plan FiledUnknown
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-28-181
Tail NumberN75337
Aircraft CategoryAir
DamageSubstantial
OperatorMillion Air Salt Lake City
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsTextron Lycoming · O-360-A4M · Reciprocating · 180
Seats4

People & Injuries

Injury Summary2 injuries (1 serious injury, 1 minor injury)
Fatal0
Serious1
Minor1
Uninjured0
Total2
Crew 1Age 22 · First Class · Serious

Conditions

ConditionsVMC
LightDaylight
Wind170° @ 9 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point21 C / 16 C
Altimeter30.30 inHg
Observation Time16:55
Weather SourceWFAC

Appendix: Source Data