# NTSB GAA18CA086: Halley KFT Apollo, N15LU, North Las Vegas, NV, December 17, 2017 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: December 17, 2017, 15:40 local (23:40 UTC) - Place: North Las Vegas, NV - Coordinates: 36.210556, -115.194442 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=36.2106&lon=-115.1944&mi=10 - Phase of flight: [Taxi](https://openairdocs.org/ntsb-phases/250) (OpenAirDocs' grouping) - Defining event: [Taxi: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report July 5, 2018 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 96497 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA18CA086 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/96497/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=96497 - Page: https://openairdocs.org/ntsb/GAA18CA086 ## 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 NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Halley KFT APOLLO AG-1, 1 case](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=130087A), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Rotorcraft flight control: main rotor control](https://openairdocs.org/ntsb-findings/01046710): Aircraft › Aircraft propeller/rotor · Incorrect use/operation (probable cause); cases with it: [Halley KFT APOLLO AG-1, 1 case](https://openairdocs.org/ntsb-findings/01046710/cases.md?model=130087A), [All aircraft, 28 cases](https://openairdocs.org/ntsb-findings/01046710/cases.md) - [Wind: gusts](https://openairdocs.org/ntsb-findings/03034045): Environmental issues › Conditions/weather/phenomena · Effect on equipment; cases with it: [Halley KFT APOLLO AG-1, 1 case](https://openairdocs.org/ntsb-findings/03034045/cases.md?model=130087A), [All aircraft, 1,199 cases](https://openairdocs.org/ntsb-findings/03034045/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Taxi: Other weather encounter](https://openairdocs.org/ntsb-events/400); cases with it: [Halley KFT APOLLO AG-1, 1 case](https://openairdocs.org/ntsb-events/400/sequence.md?model=130087A), [All aircraft, 1,127 cases](https://openairdocs.org/ntsb-events/400/sequence.md) - [Taxi: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Halley KFT APOLLO AG-1, 1 case](https://openairdocs.org/ntsb-events/230/sequence.md?model=130087A), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) ## 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](https://openairdocs.org/deregistered/N15LU-2021-12-04), registration cancelled 2021-12-04, S/N 010416, built 2016 (OpenAirDocs) - Reported make and model: HALLEY KFT APOLLO (AG-01) - Registry model: [Halley KFT APOLLO AG-1](https://openairdocs.org/model/halley-kft-apollo-ag-1) (registry code 130087A) (OpenAirDocs) - Registry engine: [Rotax 912ULS series](https://openairdocs.org/engine/rotax-912uls-series) (registry code 55572, 4 cycle) (OpenAirDocs) - Category: Gyroplane - Serial number: 010416 - Year built: 2016 - Airframe hours: 13.4 - Engines: 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 ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 56; injuries: none; 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 - Pilot-rated passenger; age 48; injuries: none; 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 ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20171217023249A](https://openairdocs.org/incident/20171217023249A), Dec 17, 2017: Halley Kft APOLLO AG-01, North Las Vegas, NV, Substantial damage. On December 17, 2017, at 1638 PST, a 2016 Halley Kft, apollo AG-1, gyroplane (N15LU), sustained substantial damage when the rotor blades struck the propeller… ## Docket (3 files) The files NTSB released with the investigation on May 14, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=96497. 7.1 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 - Kantas (item 1, .PDF, 3.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40463128&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1%20-%20Kantas-Master.PDF - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 2, .PDF, 3.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40463129&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Photo (Courtesy of FAA) (item 3, .PDF, 1 photo, 87 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40463130&FileExtension=.PDF&FileName=Photo%20(Courtesy%20of%20FAA)-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.