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

November 13, 1999 · Piper PA18 · N82553

Malheur City, OR

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
November 13, 1999
Injury Outcomes
1 injury (1 minor injury)
Location
Malheur City, OR
Aircraft
Piper PA18
Tail Number
N82553
Injuries
Minor
Aircraft Damage
Destroyed
NTSB Number
SEA00LA018

For about two months prior to the accident, the aircraft's electrical system had been operating improperly and failing to charge the battery. Although two maintenance shops had attempted to correct the problem, as of the date of the accident, the system was still not functioning correctly. During this two-month period, the pilot had continued to operate the aircraft, turning on the master switch only during engine start and for brief periods of radio transmission. On the day of the accident, he turned on the master switch to start the engine, and then not realizing that he had not turned it off, headed for his destination. About 10 minutes after takeoff, the pilot smelled what he thought was either smoke or fumes from a malfunctioning heater, and elected to make a precautionary landing. While attempting to land in an open area near a county road, the aircraft collided with a power line that the pilot was trying to go under in order to get to the point where he wanted to touch down. After hitting the power line, and with the fumes getting stronger, the pilot tried to get the aircraft on the ground as quickly as possible. As a result, the aircraft touched down at an excessive descent rate, and both main gear collapsed. Immediately after exiting the aircraft, the pilot noticed a small fire in the right wing root. He elected not to approach the aircraft to attempt to put out the fire, and it was eventually consumed by the flames.

NTSB Probable Cause

The pilot's excessive descent rate during an attempted precautionary landing. Factors include the pilot's intentional operation of his aircraft with a known electrical system deficiency, a malfunction of the electrical system while in flight, the pilot's failure to maintain clearance from an electrical transmission line while attempting a precautionary landing, and rough terrain conditions at the location where the landing was attempted.

Full Narrative

On November 13, 1999, approximately 1120 Pacific standard time, a Piper PA18, N82553, landed hard after clipping a power line during an emergency landing on the Crowley Ranch, near Malheur City, Oregon. The airline transport pilot, who was the sole occupant, received minor injuries, and the aircraft, which was owned and operated by the pilot, was destroyed by a post-crash fire. The 14 CFR Part 91 personal flight, which had been airborne for about 10 minutes, was being operated in visual meteorological conditions. No flight plan had been filed, and there was no report of an ELT activation. According to the pilot, while en route to Ontario Airport, he spent some time flying over his ranch to look at water lines. While maneuvering near the water lines, he smelled what he thought was either smoke or fumes from a heater problem. He turned off his master switch, but the smell continued to get worse, so he elected to make an emergency landing on a county road. After getting lined up for an approach to the road, he changed his mind and decided to land in an open area alongside the road. He determined that in order to land in the open area, he would have to fly under a set of power lines, so he set up an approach to do so. But, just as he got to the power lines, he realized that one was hanging down lower than the others. He said that "without thinking" he pulled up to miss it, and the left wing of the aircraft clipped a line that was above the one that was sagging. This sequence of events, along with the pilot's "fear of fire," resulted in him attempting to get the aircraft on the ground as quickly as possible. During this attempt, the aircraft landed hard, and both main gear collapsed. After the pilot exited the aircraft, he noticed a small fire had initiated in the right wing root area. Because he was afraid of an explosion, the pilot stayed away from the aircraft, which was ultimately consumed by the fire. During the investigation, it was determined that the pilot had been having trouble with the aircraft's electrical system for about two months, and during that time, the alternator system had not been charging the battery. He had taken the aircraft to two separate maintenance shops in order to have the problem fixed, but as of the date of the accident, neither shop had been able to successfully fix the problem. According to the pilot, work had been performed on the alternator, voltage regulator, circuit breaker panel, battery box area, and the master switch, and additional parts were on order. Discussions with the pilot revealed that during the period of time the electrical system was malfunctioning, he continued to fly the aircraft, and continued to turn on the master switch for short periods when the electrical system was needed to start the engine or for radio transmissions. According to the pilot, at the beginning of the flight in which the accident occurred, he elected to use the electrical system to start the engine, but had meant to turn off the master switch after the start. When he smelled the smoke/fumes in flight, he looked down and saw the master switch was still on, and realized he had forgotten to turn it off after starting the engine. The pilot had not labeled the electrical system/master switch as inoperative, and in his written statement to the NTSB, he said that he felt he "... made a mistake by flying this aircraft with an existing electrical problem."

Flight

Event TypeAccident
Event Time11:20 PST
Nearest Airport0nm
Runway0
Flight Plan FiledNone
Aircraft FireGrd
Aircraft ExplosionGrd

Aircraft

AircraftPiper PA18
Tail NumberN82553
Aircraft CategoryAir
DamageDestroyed
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320-A2B · Reciprocating · 160
Seats2

People & Injuries

Injury Summary1 injury (1 minor injury)
Fatal0
Serious0
Minor1
Uninjured0
Total1
Crew 1Age 69 · Second Class

Conditions

ConditionsVMC
LightDaylight
WindCalm
Visibility50 sm
CeilingNone
Temperature / Dew Point45 C / 0 C
Altimeter0
Weather SourcePILO

Appendix: Source Data