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 18, 2000 · Cessna 150H · N50348

Spangle, WA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
February 18, 2000
Injury Outcomes
No injuries (2 uninjured)
Location
Spangle, WA
Aircraft
Cessna 150H
Tail Number
N50348
Injuries
None
Aircraft Damage
Substantial
NTSB Number
SEA00LA045

While on a long cross-country flight, the pilot noticed that the aircraft had used considerably more fuel than it should have, and that he was then low on fuel. While attempting to get to an airport for a precautionary landing, the engine lost power. The pilot lined up to land in an open field, but as he got lower, he realized it was full of large rocks and was too bumpy. He therefore tried to land on a dirt road which sat between a power line on one side and a barbed wire fence on the other. During the landing flare, the aircraft contacted the fence resulting in a yaw that brought it in contact with a series of fence posts. An investigation revealed that the aircraft's fuel storage and distribution system had leaked considerable fuel, and that the fuel quantity sensing system was very unreliable.

NTSB Probable Cause

Exhaustion of the fuel supply due to a leaking fuel tank system. Factors contributing to the accident were, inaccurate fuel quantity sensors, the lack of suitable terrain in the area of the forced landing, and a fence alongside the dirt upon which the pilot attempted the forced landing.

Full Narrative

On February 18, 2000, approximately 1440 Pacific standard time, a Cessna 150H, N50348, collided with a series of fence posts during a forced landing after a loss of power near Spangle, Washington. The airline transport pilot and his passenger were not injured, but the aircraft, which was owned and operated by the pilot, sustained substantial damage. The 14 CFR Part 91 personal pleasure flight, which departed Albany, Oregon, about three hours prior to the accident, was being operated in visual meteorological conditions. The pilot was on a VFR flight plan, and there was no report of an ELT activation. According to the pilot, the aircraft was fitted with long-range tanks, and at the time of departure there was enough fuel on board for a six hour flight (28.5 gallons). He had planned that during the 3.5 hour flight the aircraft would use approximately 16 gallons of fuel. But while en route the fuel quantity diminished at a considerably higher rate than he planned for. He said he was not aware of this situation until well into the flight because the fuel quantity indicator system had given erratic and inconsistent quantity indications and one of the fuel gauges may have temporarily stuck. Once he realized that the indicator system had malfunctioned and that he was low on fuel, he headed for the airport at Spangle. So as to avoid flight over rugged terrain while low on fuel, the pilot decided to take a more indirect route to Spangle that would keep him over more hospitable terrain. While trying to reach the airport, the engine experienced a complete loss of power, and the pilot lined up to make a forced landing in an open field. But as he got lower, he realized that the field contained some large rocks and was too bumpy. Therefore, while at low altitude he switched his landing point to a dirt road that sat between a set of power lines on one side and a barbed wire fence on the other. As he was making a final low-level turn to line up with the road, the horizontal stabilizer hooked a strand of the barbed-wire fence, resulting in the aircraft yawing and coming in contact with a series of fence posts. A post-accident investigation revealed fuel stains that indicated there had been significant leakage from the fuel tanks and fuel distribution system. Bench testing of the fuel quantity sensor/sender units revealed that both were "very erratic" between the full and empty extremes. Disassembly of the transmitter units revealed that the electrical contact surface that normally rides up and down on the rheostat windings were almost completely worn away on both units.

Flight

Event TypeAccident
Event Time14:40 PST
Nearest Airport0nm
Runway0
Flight Plan FiledVFR
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 150H
Tail NumberN50348
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsContinental · O-200A · Reciprocating · 100
Seats2

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 62 · Second Class

Conditions

ConditionsVMC
LightDaylight
WindCalm
Visibility20 sm
CeilingNone
Temperature / Dew Point30 C / 0 C
Altimeter0
Weather SourcePILO

Appendix: Source Data