GAA18CA086

NTSB accident investigation · Halley KFT Apollo · North Las Vegas, NV · December 17, 2017

Accident · No injuriesData collectionFinal report
Date
December 17, 2017, 15:40 local (23:40 UTC)
Place
North Las Vegas, NV
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N15LUHalley KFT Apollo
Defining event
Taxi: Loss of control on ground
Weather
Visual (VMC) · Day
Status
Completed · report July 5, 2018
Report
Approved by Office Director
NTSB office
General Aviation Accidents
Parties
FAA
FAA report
20171217023249A
Case key
96497

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The pilot’s failure to stop the main rotor rotation before taxiing the gyroplane in gusting wind conditions, resulting in the main rotor striking the empennage.

Findings · 3

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotHalley KFT APOLLO AG-1: 1 caseAll aircraft: 9,295 casesProbable cause
Rotorcraft flight control: main rotor controlAircraft › Aircraft propeller/rotor · Incorrect use/operationHalley KFT APOLLO AG-1: 1 caseAll aircraft: 28 casesProbable cause
Wind: gustsEnvironmental issues › Conditions/weather/phenomena · Effect on equipmentHalley KFT APOLLO AG-1: 1 caseAll aircraft: 1,199 cases

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

According to the pilot of the experimental amateur-built gyroplane, he landed on a taxiway and taxied to the runway intersection. The intersection was on the right side of runway 30R. The ramp where the pilot wanted to park, was across both runways, on the left side of runway 30L. Unfamiliar with the capabilities of the gyroplane, the tower controller asked the pilot to air taxi to the ramp. The pilot informed the tower controller that he could either ground taxi or takeoff and land on runway 30L then taxi to the ramp. The controller and the pilot agreed to the latter. The pilot further reported that, in anticipation of taxiing to parking, he had allowed the gyroplane's rotor speed to decrease; when he turned the gyroplane back onto the taxiway in the gusting wind, the main rotor struck the empennage and the pusher-propeller. The gyroplane sustained substantial damage to the empennage and rotor system. The METAR at the accident airport reported that about the time of the accident, the wind was from 330° at 14 kts and gusting to 19 kts. The pilot reported that this accident could have been prevented if he had waited for the rotor blades to stop completely before repositioning the gyroplane for taxi. The pilot reported that there were no preaccident mechanical malfunctions or failures with the gyroplane that would have precluded normal operation.

Factual narrative

According to the pilot in the experimental amateur-built gyroplane, he landed on a taxiway and taxied to the runway intersection. The intersection was on the right side of runway 30R. The ramp where the pilot wanted to park, was across both runways, on the left side of runway 30L. Unfamiliar with the capabilities of the gyroplane, the tower asked the pilot to air taxi to the ramp. The pilot informed the tower that he could either ground taxi, or takeoff and land on runway 30L, then taxi to the ramp. Tower and the pilot agreed to the latter. He further reported that in anticipation of taxiing to parking, he had allowed the Gyroplane's rotor speed to decrease, and when he turned the gyroplane back onto the taxiway in the gusting wind, the main rotor struck the empennage and the pusher-propeller. The gyroplane sustained substantial damage to the empennage and rotor system. The METAR at the accident airport reported that about the time of the accident, the wind was from 330° at 14kts and gusting to 19kts. Per the National Transportation Safety Board's Pilot Aircraft Accident Report, the pilot identified in the Owner Safety Recommendation section, that this accident could have been prevented if he had waited for the rotor blades to stop completely before repositioning the gyroplane for taxi. The pilot reported that there were no preaccident mechanical malfunctions or failures with the gyroplane that would have precluded normal operation.

Aircraft

Registration
N15LU
Reported as
Halley KFT Apollo (AG-01)
Category
Gyroplane
Serial number
010416
Built
2016
Airframe hours
13.4
Engine
Rotax 912ULS, 100 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Special, Experimental (Special)
Last inspection
Unknown · December 1, 2017
Departed
VGT · North Las Vegas, NV
Destination
VGT · North Las Vegas, NV
Airport
VGT · North Las Vegas
Equipment
None

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew · 2

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
56
Injuries
None
Certificates
Foreign, Private
Airplane ratings
Single-engine land
Medical
Class 1, Without waivers/limitations
Seat
Front
Restraint
4-point
Flight hours
10,151 total · 938 in this make and model · 9,901 as pilot in command · 31 in the last 90 days · 13 in the last 30 days · 0.1 in the last 24 hours
Role
Pilot-rated passenger
Age
48
Injuries
None
Certificates
Flight instructor, Commercial
Medical
Class 2
Last flight review
January 17, 2018
Seat
Rear
Restraint
4-point

Weather

Conditions
Visual (VMC) · Day
Wind
330° at 14 knots, gusting 19
Visibility
10 statute miles
Lowest ceiling
None
Temperature
55 °F, dew point 16 °F
Altimeter
30.04 inHg
Observed at
KVGT

Docket · 3

The files NTSB released with the investigation on May 14, 2018, on NTSB’s docket system: statements, records, photos and specialists’ reports. 7.1 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.