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

May 9, 1999 · Piper PA-18-150 · N7483L

Salem, OR

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
May 9, 1999
Injury Outcomes
No injuries (1 uninjured)
Location
Salem, OR
Aircraft
Piper PA-18-150
Tail Number
N7483L
Injuries
None
Aircraft Damage
Substantial
NTSB Number
SEA99LA056

The pilot, who had been cleared for a straight-in approach, began a reduced-power descent from approximately 2000 feet above ground level (AGL) while about five miles from the runway. About half way through the descent, the pilot retarded the throttle to idle but did not apply carburetor heat. When he reached 400 feet AGL, the pilot realized he was getting too low on the approach, so he pushed the throttle forward in order to add power and arrest his descent. Upon moving the throttle forward, the engine did not respond. The pilot then applied full carburetor heat, but he could not get the engine to restart. It was ultimately determined that his descent had been made under conditions where severe carburetor icing could be expected at glide power. Although the PA-18 Owners Handbook did not call for the use of carburetor heat during all approaches, it did require it when '... icing conditions prevail.'

NTSB Probable Cause

The pilot's improper decision not to apply carburetor heat during a reduced power descent in conditions conducive to carburetor icing. Factors include weather conditions conducive to carburetor icing, and high vegetation and a fence post in the area where the forced landing was attempted.

Full Narrative

On May 9, 1999, approximately 1420 Pacific daylight time, the pilot of a Piper PA-18-150, N7483L, collided with tall brush while attempting a forced landing in a field about 1/2 mile short of the runway at McNary Field, Salem, Oregon. The private pilot was not injured, but the aircraft, which was owned and operated by the pilot, sustained substantial damage. The local 14 CFR Part 91 flight, which was being conducted in visual meteorological conditions, began about one hour and 30 minutes prior to the accident. No flight plan had been filed, and there was no report of an ELT activation. According to the pilot, as he was returning from the pleasure flight, he contacted Salem Tower and was cleared for a straight-in VFR approach to runway 34. While about five miles from the airport, he reduced the engine power to a setting less than it had been at during cruise flight, and started a descent from about 2,000 feet above the ground (AGL). About half way through the descent, the pilot pulled the throttle to idle but did not apply carburetor heat. When he was about 400 feet AGL, the pilot realized he was getting low on the approach, so he moved the throttle forward, but there was no response from the engine. He applied carburetor heat, but was unable to get the aircraft to restart. He therefore made a forced landing in a field about 1/2 mile from the end of runway. During the landing roll, the pilot maneuvered to miss a fence post he had not seen from the air, but in so doing, the aircraft collided with tall shrubs and sustained substantial damage. Subsequent to the accident, the aircraft was moved to McNary Field where the engine was test run and inspected. The inspection revealed no anomalies, and during the test run, the engine operated normally with proper responses to magneto and carburetor heat checks. The investigation revealed that the surface weather observation (METAR) taken at Salem Airport at the time of the accident (2120 UTC) showed a temperature of 54 degrees Fahrenheit and a dew point of 36 degrees. According to the Carburetor Icing Probability Chart obtained from DOT/FAA/CT-82/44 (see attached chart), the pilot was making the approach in conditions where serious carburetor icing could be expected at glide power. A review of the PA-18 Owners Handbook revealed that, although carburetor heat is not required for all approaches and landings, it is required when "...icing conditions prevail."

Flight

Event TypeAccident
Event Time14:20 PDT
Nearest Airport0nm
Runway0
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-18-150
Tail NumberN7483L
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320-A1 · Reciprocating · 150
Seats2

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 53 · Second Class

Conditions

ConditionsVMC
LightDaylight
Wind120° @ 4 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point54 / 36 C
Altimeter30.00 inHg
Observation Time21:20
Weather SourceWFAC

Appendix: Source Data