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 15, 2003 · Cessna 182J · N2913F

Salem, OR

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
May 15, 2003
Injury Outcomes
1 injury (1 minor injury)
Location
Salem, OR
Aircraft
Cessna 182J
Tail Number
N2913F
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
SEA03LA082

The pilot reported that while cruising at 11,500 feet in order to get over some clouds, the engine slowly started losing power. Because it appeared to him that it might be carburetor icing, the pilot applied carburetor heat, but the engine continued to lose more power. Eventually the engine lost enough power that the pilot was unable to hold altitude, and he therefore found it necessary to descend and attempt a forced landing in an open field. Although the touchdown was uneventful, during the landing roll the aircraft encountered some rough terrain, resulting in substantial damage. A post-accident engine teardown inspection found a large hole in the top of the crankcase, and numerous internal parts failures. There were also several components within the engine that displayed coloration signatures consistent with heat stress due to lack of lubrication, but an inspection of the oil filter, oil filter adapter, propeller governor, push rod seals, oil pressure line, dipstick tube, oil sump quick drain, oil pump, tachometer drive, and oil filler port/cap found no evidence of a pre-event oil leak. Ultimately, the initiating event leading to the sequence of events resulting in the catastrophic engine failure could not be determined.

NTSB Probable Cause

Loss of power in cruise flight due to a catastrophic engine failure for undetermined reasons.

Full Narrative

On May 15, 2003, approximately 1600 Pacific daylight time, a Cessna 182J, N2913F, collided with the terrain during the landing roll when the pilot attempted a forced landing in an open field about four miles east of Salem, Oregon. The commercial pilot, who was the sole occupant, was not injured, but the aircraft which is owned by a relative of the pilot, but operated primarily by the pilot, sustained substantial damage. The 14 CFR Part 91 personal pleasure flight, which departed Hillsboro, Oregon, about 40 minutes earlier, was being operated in visual meteorological conditions. No flight plan had been filed. There was no report of an ELT activation. According to the pilot, while cruising at 11,500 feet in order to get over some clouds, the engine slowly started losing power. Because it appeared to him that it might be carburetor icing, the pilot applied carburetor heat, but the engine continued to lose more power. Eventually the engine lost enough power that the pilot was unable to hold altitude, and he therefore found it necessary to descend and attempt a forced landing in an open field. Prior to reaching the field, the engine lost all power, but the pilot was able to reach the field he was aiming for. Although the touchdown was uneventful, during the landing roll the aircraft encountered some rough terrain, resulting in substantial damage. According to the FAA inspector who responded to the scene, the engine crankcase had fractured and although the oil filler cap was in place, all but a very small amount of engine oil was missing. During a post-accident engine inspection it was observed that there was a large hole in the top of the crankcase between cylinders #1 & #2. Connecting rods #1 & #3 were disassociated from their rod journals. Connecting rods #4, 5 and 6 were dry and brown in color. The crankshaft cheeks adjacent to these rods were discolored, as were the rod journals for #1 & #3 connecting rods. The four connecting rod bolts for rods #1 & #3 were all a dark blue color and separated at mid bolt with the points of separation severely necked down. All of the recovered parts of the connecting rods #1 & #3 were a dark blue color. Both pistons #1 & #2 had been broken up during the failure event. The tops of piston's #1, 3, 4, 5 and 6 all exhibited normal operating signatures. The top of piston #2 had been fragmented and was in the oil sump. The chrome cylinder walls were blue in color and heavily scored. All valves were found to be intact. The oil sump was removed and was found to contain most of the fragment engine parts and very little oil. The exterior of the engine was checked for oil leaks as well as the oil filter, oil filter adapter, propeller governor, push rod seals, oil pressure line, dipstick tube, oil sump quick drain, oil pump, tachometer drive, and oil filler port/cap, and no evidence of a leak was noted. According to the pilot, he added one quart of oil just prior to the flight, and this brought the oil level to a point about half way between the low-oil mark and the fully filled line. Although the engine displayed the aforementioned signs of catastrophic internal failure, the event initiating that failure sequence could not be determined.

Flight

Event TypeAccident
Event Time16:00 PDT
Nearest Airport0nm
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 182J
Tail NumberN2913F
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsContinental · O-470R · Reciprocating · 230
Seats4

People & Injuries

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

Conditions

ConditionsVMC
LightDaylight
Wind260° @ 11 kt, gusting 20 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point55 / 39 C
Altimeter30.13 inHg
Observation Time22:56
Weather SourceWFAC

Appendix: Source Data