The U.S. aircraft register, updated daily
Accidents · NTSB WPR22LA045 · Final report

Amateur-built ROTORWAY EXEC 162F accident near Scio, Oregon, November 22, 2021

On November 22, 2021 at about 11:10 pm local time, a 2003 amateur-built ROTORWAY EXEC 162F (helicopter), registered N102LD, was substantially damaged in an accident during maneuvering (hover) near Scio, Oregon (Jack'S Heliport airport). It was a flight test under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s improper maintenance on the tail rotor assembly, which resulted in the loss of control and roll over.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
November 22, 2021 · about 11:10 pm local time
Place
Scio, Oregon · Jack'S Heliport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Amateur-built ROTORWAY EXEC 162F, built 2003
Registration
N102LD · no longer on the register · serial 1001
Damage
Substantial damage
Flight
Flight test · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot of the experimental helicopter reported that, he had performed maintenance on the tail rotor assembly. While checking the blade tracking and balance in a hover, a pitch change link retention bolt lost torque and separated from the tail rotor slide assembly, which resulted in the loss of control and subsequent rollover. The helicopter sustained substantial damage to the fuselage, tailboom, and main rotor system. The pilot reported that there were no preaccident mechanical failures or malfunctions with the helicopter and that he failed to ensure the maintenance was performed correctly.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Flight control sys malf/fail during maneuvering (hover) defining event

The NTSB's findings

  • Personnel issues › Task performance › Maintenance › Installation › Owner/builder

Pilot

  • Certificate: private, student
  • Ratings: single-engine land; instrument: airplane; rotorcraft: helicopter
  • Flight time: 1,550 hours in all; 350 in this make and model; 3 in the last 90 days; 3 in the last 30 days; 1,300 as pilot in command
  • Last flight review: April 7, 2006
  • Medical certificate: None
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 360 hours
  • Last inspection: condition inspection, August 25, 2021
  • Maximum gross weight: 1,600 lb
  • Seats: 1
  • Landing gear: fixed
  • Engine: Ama/Expr 162F (piston); 360 hours total

The flight

  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 330° at 3 knots
  • Visibility: 10 statute miles
  • Sky: overcast at 8,000 ft
  • Temperature: 48°F (9°C), dew point 43°F (6°C)
  • Altimeter: 30.08 inHg
  • Observation at 2:56 pm from KCVO, 21 miles away

Weather report (METAR): KCVO 222256Z AUTO 33003KT 10SM OVC080 09/06 A3008 RMK AO2 SLP189 T00890056

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

3 documents, released by the NTSB on July 21, 2022. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.