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 20, 1999 · Hammond Twinstar Gyroplane Twinstar G · N6364H

Bloomsburg, PA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
May 20, 1999
Injury Outcomes
2 injuries (1 serious injury, 1 minor injury)
Location
Bloomsburg, PA
Aircraft
Hammond Twinstar Gyroplane Twinstar G
Tail Number
N6364H
Injuries
Serious
Aircraft Damage
Substantial
NTSB Number
NYC99LA115

The pilot was attempting a takeoff in his gyroplane when the rotor rpm decreased. The pilot continued the takeoff roll to try to increase the rotor rpm. However, the rotor blades began flapping, and finally struck the ground to the left of the gyroplane, causing it to roll over to the left. Winds at the time were from the left, about 90 degrees, at 7 to 10 knots, with reported gusts in the area. The private pilot had 87 hours of flight time in model. He was rated in airplane category aircraft, but not in rotorcraft category aircraft. According to 49 CFR Part 61.31(k)(2)(i), a rotorcraft category rating and the gyroplane class rating were not required, even though a passenger was onboard, since the gyroplane was not type-certificated. In addition, the operating limitations for the gyroplane did not require the pilot to have an appropriate category or class rating, as well.

NTSB Probable Cause

The pilot's failure to maintain sufficient takeoff rpm. Factors included crosswind gusts, and the FAA's lack of category and class rating requirements for pilots flying non-type-certificated experimental aircraft.

Full Narrative

On May 20, 1999, about 1930 Eastern Daylight Time, a homebuilt Twinstar Gyroplane, N6364H, was substantially damaged while attempting a takeoff from Bloomsburg Municipal Airport (N13), Bloomsburg, Pennsylvania. The certificated private pilot was seriously injured, and the passenger received minor injuries. Visual meteorological conditions prevailed at the time of the accident. No flight plan was filed for the local flight, which was conducted under 14 CFR Part 91. According to a Federal Aviation Administration (FAA) Inspector, the gyroplane was taking off from Runway 08. The pilot stated that the rotor "began to flop," and that rotor rpm decreased to below the rpm necessary for flight. The pilot said he attempted to increase the rotor rpm by applying aft cyclic, but the cyclic began to move without the pilot's input due to rotor system feedback. The rotor struck the ground below the aft left side of the rotor disk plane several times. The fuselage then made an uncommanded 120-degree left roll, and came to a stop on the left side of the runway. In a later statement, the pilot wrote that during the takeoff roll, his finger slipped off the pre-rotate button at 80 rpm. He continued down the runway to increase the rpm, and about 90 rpm, encountered a severe stick shake, or "violent rotor flapping." It was at that point that he believed that part of the airframe broke, and part of it struck him. Winds, about 25 minutes after the accident, were recorded at an airport about 25 nautical miles to the northwest as being from 340 degrees magnetic, at 7 knots. At the same time, winds were recorded at another airport, about 35 nautical miles to the northeast, as being from 360 degrees magnetic, at 11 knots. Witnesses stated that the winds had been gusting during the time of the accident. Other airports in the region had recorded wind gusts up to 21 knots throughout the day. The pilot made an additional statement regarding the accident: "I believe this accident and many other gyro accidents were caused by 'dynamic rollover' - a rollover on the ground caused by severe rotor flapping caused by insufficient rotor rpm combined with excessive ground speed." He further stated: "This is a serious flaw in gyros which should no longer be covered up or pushed aside as unimportant." Further research on the subject failed to revealed any association between gyroplane operations and dynamic rollover. However, FAA Advisory Circular AC 90-87, Helicopter Dynamic Rollover, addressed how dynamic rollover could occur if a critical rollover angle was exceeded by a helicopter that pivoted about one skid or wheel, and which was still in contact with the ground. The private pilot had 87 hours of flight time in the accident gyroplane. He was rated in airplane category aircraft, but not in rotorcraft category aircraft. According to 49 CFR Part 61.31(k)(2)(i), the rotorcraft category rating was not required, even though a passenger was onboard, since the gyroplane was not type-certificated. In addition, the operating limitations for the gyroplane did not require the pilot to have an appropriate category or class rating.

Flight

Event TypeAccident
Event Time19:30 EDT
Nearest AirportBloomsburg Municipal (0nm)
Runway8
Runway Length2800 ft
Runway Width50 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftHammond Twinstar Gyroplane Twinstar G
Tail NumberN6364H
Aircraft CategoryGyro
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO-320 · Reciprocating · 160
Seats2

People & Injuries

Injury Summary2 injuries (1 serious injury, 1 minor injury)
Fatal0
Serious1
Minor1
Uninjured0
Total2
Crew 1Age 58 · Third Class

Conditions

ConditionsVMC
LightDaylight
Wind340° @ 7 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point43 C
Altimeter30.00 inHg
Observation Time23:54
Weather SourceWFAC

Appendix: Source Data