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

March 10, 2005 · Rotorway Exec 162F · N20539

Coos Bay, OR

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
March 10, 2005
Injury Outcomes
1 injury (1 minor injury)
Location
Coos Bay, OR
Aircraft
Rotorway Exec 162F
Tail Number
N20539
Injuries
Minor
Aircraft Damage
Destroyed
NTSB Number
SEA05LA058

While in cruise flight, the pilot detected a burning rubber smell and heard "strange loud noises" just as both the engine and rotor rpm began to fluctuate. Soon thereafter, the engine began to lose power, and the pilot elected to make an autorotational landing. He headed for a nearby opening, which turned out to be a cemetery, and as he touched down among the gravestones with zero forward speed, the aircraft rolled over onto its right side. Immediately after it rolled to the side, flames appeared in the cockpit, but the pilot was able to escape out of the left side of the helicopter. A post-accident teardown inspection of the engine and drive assembly revealed that the upper main drive pulley bearing, a double ball bearing assembly, had partially disintegrated, leading to the decoupling of the main rotor shaft drive from the engine output drive shaft. The upper ball bearings were loose in the assembly, and their retaining cage had been destroyed. All of the subject bearings displayed excessive wear, flat spots, and significant thermal damage. Although there was very little grease remaining in the assembly, and the lower drive belt sheave grease passage set screw was found backed half way out, it could not be positively determined whether a lack of lubrication initiated the sequence of events leading to the failure of the bearing assembly, or whether the grease had been consumed by the heat generated by an internal failure resulting from other factors. According to the pilot/builder of the helicopter, he had adhered to the required 25 hour grease service intervals since the aircraft had been built, approximately 115 hours prior to the accident.

NTSB Probable Cause

The disintegration, for undetermined reasons, of the upper main drive pulley assembly bearing, while in cruise flight, leading to the decoupling of the main rotor drive assembly from the engine drive assembly. Factors include the absence of any suitable forced landing area, leading to a landing between the gravestones of a cemetery.

Full Narrative

On March 10, 2005, approximately 1220 Pacific standard time, an experimental Garner RotorWay Exec 162F, N20539, collided with the terrain during an emergency autorotation near Coos Bay, Oregon. The commercial pilot, who was the sole occupant, received minor injuries, and the aircraft, which is owned and operated by the pilot, was destroyed by the post-crash fire. The 14 CFR Part 91 personal pleasure flight, which departed North Bend Municipal Airport, North Bend, Oregon, about 10 minutes prior to the accident, was being operated in visual meteorological conditions. No flight plan had been filed for the intended flight to Norway, Oregon. According to the pilot, while in cruise flight, he detected a burning rubber smell and heard "strange loud noises" just as both the engine and rotor rpm began to fluctuate. Soon thereafter, the engine began to lose power, and the pilot elected to make an autorotational landing. He headed for a nearby opening, which turned out to be a cemetery, and as he touched down among the gravestones with zero forward speed, the aircraft rolled over onto its right side. Immediately after it rolled to the side, flames appeared in the cockpit, but the pilot was able to escape out of the left side of the helicopter. A post-accident teardown inspection of the engine and drive assembly revealed that the upper main drive pulley bearing, a double ball bearing assembly, had partially disintegrated, leading to the decoupling of the main rotor shaft drive from the engine output drive shaft. The upper ball bearings were loose in the assembly, and their retaining cage had been destroyed. All of the subject bearings displayed excessive wear, flat spots, and significant thermal damage. Although there was very little grease remaining in the assembly, and the lower drive belt sheave grease passage set screw was found backed half way out, it could not be positively determined whether a lack of lubrication initiated the sequence of events leading to the failure of the bearing assembly, or whether the grease had been consumed by the heat generated by an internal failure resulting from other factors. According to the pilot/builder of the helicopter, he had adhered to the required 25 hour grease service intervals since the aircraft had been built, approximately 115 hours prior to the accident.

Flight

Event TypeAccident
Event Time12:20 PST
Nearest Airport0nm
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireGrd
Aircraft ExplosionNo

Aircraft

AircraftRotorway Exec 162F
Tail NumberN20539
Aircraft CategoryHeli
DamageDestroyed
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsRotorway · 162F · Reciprocating · 150
Seats2

People & Injuries

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

Conditions

ConditionsVMC
LightDaylight
Wind330° @ 7 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point63 F / 0 C
Altimeter30.14 inHg
Weather SourcePILO

Appendix: Source Data