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 23, 2015 · Destiny 2000 NO Series · N3376

Eltopia, WA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
May 23, 2015
Injury Outcomes
2 injuries (1 serious injury, 1 minor injury)
Location
Eltopia, WA
Aircraft
Destiny 2000 NO Series (2001)
Tail Number
N3376
Injuries
Serious
Aircraft Damage
Substantial
NTSB Number
GAA15LA085

The flight instructor and student pilot were departing in the powered parachute during a fly-in event with the student pilot at the flight controls. The flight instructor reported that the powered parachute experienced left-to-right wing oscillations during the takeoff roll and initial climb and that, about 15 ft above ground level, it rotated sharply downward and to the right and then impacted terrain; this was corroborated by video footage provided by an observer on the ground, which also showed that the oscillations worsened during the initial climb. The flight instructor reported that he was monitoring all of the parachute lines during the takeoff roll and initial climb and that he observed no abnormalities that would have adversely affected the parachute's steering mechanism. According to Federal Aviation Administration guidance on powered parachute operations, the takeoff should be aborted if the parachute experiences severe wing oscillations. The guidance also states that "dual controls are required in the aircraft for training." However, the powered parachute was not equipped with dual flight controls. If the powered parachute had been equipped with dual flight controls, it is possible that the flight instructor would have taken control of the flight and aborted the takeoff. Regardless, the flight instructor should have told the student to abort the takeoff when he first noticed the wing oscillations.

NTSB Probable Cause

The flight instructor’s failure to tell the student pilot to abort the takeoff after the powered parachute experienced wing oscillations, which resulted in the student pilot’s loss of aircraft control during initial climb and subsequent impact with terrain. Contributing to the accident was the flight instructor's decision to conduct training in a powered parachute without dual flight controls.

Full Narrative

On May 23, 2015, about 1430 pacific daylight time, a Destiny 2000 powered parachute, N3376, impacted terrain during the initial climb from a field near Eltopia, Washington. The flight instructor sustained minor injuries, and the student pilot sustained serious injuries. Day visual meteorological conditions prevailed, and no flight plan was filed for the instructional flight, which was operated under the provisions of Title 14 Code of Federal Regulations Part 91. According to the flight instructor, the aircraft experienced left to right oscillations during the takeoff roll and initial climb, and about 15 feet above ground level, the parachute rotated sharply downward and to the right. The aircraft impacted terrain in a right bank and nose-low attitude. The student pilot was at the flight controls for the entire duration of the flight, and stated in a postaccident interview that he did not make any abrupt control inputs during the takeoff or initial climb. The flight instructor stated that dual flight controls were not installed, and he could not reach the throttle lever. The flight instructor provided a video recording of the accident sequence, which was filmed by an observer on the ground. The footage depicted the accident aircraft experiencing left to right wing oscillations throughout the takeoff roll and the rotation. During the initial climb, the oscillations continued and the aircraft rolled sharply downward and to the right, eventually moving out of the video recorders view. The flight instructor stated there were no mechanical malfunctions or failures with the powered parachute that would have precluded normal operation. In addition, he reported that he was monitoring all parachute lines during the takeoff roll and initial climb, and observed no line-overs or any other abnormalities that would have adversely affected the parachute's steering mechanism. The reported winds at an airport 11 nautical miles away about the time of the accident were from 210 degrees true at 7 knots. The flight instructor reported that he observed a steady direct headwind about 4 to 7 knots before takeoff. During the video, about one minute before the accident powered parachute lifted off, an observer could be heard stating, "The wind has basically come down to nothing." ADDITIONAL INFORMATION According to the Federal Aviation Administration Powered Parachute Flying Handbook (FAA-H-8083-29), "An oscillating wing forced into takeoff will most likely roll the airframe," and "if the oscillations become too severe, it is best to abort the takeoff and set up again." The handbook additionally states, "Dual controls are required in the aircraft for training."

Flight

Event TypeAccident
Event Time14:30 PDT
Nearest Airport0nm
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftDestiny 2000 NO Series
Tail NumberN3376
Aircraft CategoryPpar
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsRotax · 582DCDI · Reciprocating · 65
Seats2

People & Injuries

Injury Summary2 injuries (1 serious injury, 1 minor injury)
Fatal0
Serious1
Minor1
Uninjured0
Total2
Crew 1Age 64 · None · Serious
Crew 2Age 57 · None · Minor

Conditions

ConditionsVMC
LightDaylight
Wind210° @ 7 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point54
Altimeter29.95 inHg
Observation Time21:53
Weather SourceWFAC

Appendix: Source Data