# NTSB WPR13LA099: Goetz Helicycle, N143PG, Mesa, AZ, January 22, 2013 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: January 22, 2013, 14:00 local (21:00 UTC) - Place: Mesa, AZ - Coordinates: 33.45639, -111.723609 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=33.4564&lon=-111.7236&mi=10 - Phase of flight: [Emergency descent](https://openairdocs.org/ntsb-phases/600) (OpenAirDocs' grouping) - Defining event: [Autorotation: Hard landing](https://openairdocs.org/ntsb-events/092) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report January 13, 2014 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 86062 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR13LA099 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/86062/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=86062 - Page: https://openairdocs.org/ntsb/WPR13LA099 ## Probable cause The pilot's failure to properly install and secure the wire connecting the electronic speed controller unit to the fuel controller actuator motor, which resulted in the wire’s disconnection in flight and the resultant partial loss of engine power. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Engine fuel and control](https://openairdocs.org/ntsb-findings/01057300): Aircraft › Aircraft power plant · Malfunction (probable cause); cases with it: [Goetz Joe HELICYCLE, 1 case](https://openairdocs.org/ntsb-findings/01057300/cases.md?model=05620NO), [All aircraft, 49 cases](https://openairdocs.org/ntsb-findings/01057300/cases.md) - [Misc hardware: misc wiring](https://openairdocs.org/ntsb-findings/01071497): Aircraft › Fluids/misc hardware · Incorrect service/maintenance (probable cause); cases with it: [Goetz Joe HELICYCLE, 1 case](https://openairdocs.org/ntsb-findings/01071497/cases.md?model=05620NO), [All aircraft, 3 cases](https://openairdocs.org/ntsb-findings/01071497/cases.md) - [Maintenance: installation](https://openairdocs.org/ntsb-findings/02062035): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Goetz Joe HELICYCLE, 1 case](https://openairdocs.org/ntsb-findings/02062035/cases.md?model=05620NO), [All aircraft, 371 cases](https://openairdocs.org/ntsb-findings/02062035/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Prior to flight: Aircraft maintenance event](https://openairdocs.org/ntsb-events/040); cases with it: [Goetz Joe HELICYCLE, 1 case](https://openairdocs.org/ntsb-events/040/sequence.md?model=05620NO), [All aircraft, 484 cases](https://openairdocs.org/ntsb-events/040/sequence.md) - [Enroute-cruise: Loss of engine power (partial)](https://openairdocs.org/ntsb-events/342); cases with it: [Goetz Joe HELICYCLE, 1 case](https://openairdocs.org/ntsb-events/342/sequence.md?model=05620NO), [All aircraft, 1,858 cases](https://openairdocs.org/ntsb-events/342/sequence.md) - [Approach: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Goetz Joe HELICYCLE, 1 case](https://openairdocs.org/ntsb-events/440/sequence.md?model=05620NO), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) - [Autorotation: Hard landing](https://openairdocs.org/ntsb-events/092) (defining event); cases with it: [Goetz Joe HELICYCLE, 1 case](https://openairdocs.org/ntsb-events/092/sequence.md?model=05620NO), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) ## Analysis The pilot reported that while in cruise flight the helicycle's engine lost partial power. Unable to maintain altitude he maneuvered to find a safe landing area, and autorotated onto a residential street. A witness reported that before the helicycle landed, it was oscillating and sounded as if the engine was cutting in and out. Postaccident examination of the helicycle revealed that the "B" wire, which runs between the electronic speed controller unit and fuel controller actuator motor, separated from the connection during cruise flight. The pilot reported that if the fuel controller actuator motor loses power, the engine would automatically go to a minimum fuel stop position and flight idle. The pilot further reported that there were no parts failures, but that he had installed the "B" wire without an additional strain relief at the connector, which allowed the wire to disconnect from the system during normal operations. The pilot reported that the accident can be prevented by installing a second parallel wire between the fuel controller actuator motor and the electronic speed controller unit. ## Factual narrative On January 22, 2013, about 1400 mountain standard time, a Goetz Helicycle, N143PG, experienced a hard landing following an off airport autorotation about 4 miles southeast of Falcon Field Airport (FFZ), Mesa, Arizona. The commercial pilot, the sole occupant, was not injured. The helicycle was registered to, and operated by the pilot under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed, and no flight plan had been filed for the flight that originated from Chandler Municipal Airport (CHD), Chandler, Arizona. The pilot reported that he had hovered the helicycle for about 15 minutes prior to a normal takeoff. During the flight, the engine suddenly lost partial power. The pilot initiated an emergency landing onto a residential road. A witness reported that his attention was first drawn to the helicycle when he heard an engine cutting in and out. Once the helicycle came into view, he noticed that it was also oscillating. The helicycle made a circle over his neighborhood before it initiated an autorotation to the ground. The helicycle landed hard and came to rest in a bush. During the accident sequence, the tailboom and tail rotor assembly were substantially damaged. Post-accident examination of the airframe and engine by a Federal Aviation Administration Inspector revealed that the fuel controller actuator motor arm was in the minimum fuel position. The electronic speed controller unit was damaged and separated from the helicycle. Several of the wires from this system were pulled from their ring terminals, including the "B" wire, which runs to the fuel controller actuator motor. All of these wires showed signs of being mechanically pulled from the ring terminal with the exception of the "B" wire, which did not have the same rough and tension markings. The pilot reported that the "B" wire had come loose at the connection while inflight. He further reported that when there is a loss of power to the fuel controller actuator motor the engine automatically goes to a minimum fuel stop position and flight idle. The pilot further reported that there were no parts failures, but that he had installed the "B" wire without an additional strain relief at the connector, which allowed the wire to disconnect from the system during normal operations. The pilot reported that the accident can be prevented by installing a second parallel wire between the fuel controller actuator motor and the electronic speed controller unit. ## Aircraft - Registration: [N143PG](https://openairdocs.org/aircraft/N143PG), registered now, S/N 3-27, built 2007 (OpenAirDocs) - Reported make and model: GOETZ HELICYCLE - Registry model: [Goetz Joe HELICYCLE](https://openairdocs.org/model/goetz-joe-helicycle) (registry code 05620NO) (OpenAirDocs) - Registry engine: [Amateur-built UNKNOWN ENG](https://openairdocs.org/engine/amateur-built-unknown-eng) (registry code 99999) (OpenAirDocs) - Category: Helicopter, amateur-built - Serial number: 3-27 - Airframe hours: 371 - Engines: Solar T62-32 turbo shaft - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Goetz Joe - Registered owner: Goetz Joe - Airworthiness certificate: Special, Experimental (Special) - Last inspection: Condition, March 15, 2012 - Departed: CHD, Chandler, AZ - Destination: FFZ, Mesa, AZ - Airport: FFZ, Falcon Field Airport ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 65; injuries: none; commercial; airplane ratings: single-engine sea, single-engine land, multi-engine sea; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review January 14, 2012; seat: single; flight hours: 1,500 total, 370 in this make and model, 1,400 as pilot in command, 18 in the last 90 days, 11 in the last 30 days, 0 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 340° at 8 knots - Visibility: 40 statute miles - Lowest ceiling: none - Temperature: 77 °F, dew point 46 °F - Altimeter: 30.07 inHg - Observed at: FFZ, 4 nm away ## 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 20130122000769A](https://openairdocs.org/incident/20130122000769A), Jan 22, 2013: Goetz Joe HELICYCLE, Mesa, AZ, Substantial damage. On 01/22/2013 N143PG, experimental helicopter was enroute to falcon field (ffz) and lost engine power and entered autorotation. The aircraft came to rest in… ## Docket (6 files) The files NTSB released with the investigation on November 15, 2013, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=86062. 6.6 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 580 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40386067&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Record of Conversation - Witness (item 2, .PDF, 28 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40403857&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Witness-Master.PDF - Record of Email - FAA (item 3, .PDF, 103 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40403880&FileExtension=.PDF&FileName=Record%20of%20Email%20-%20FAA-Master.PDF - Weather Reports and Records (item 4, .PDF, 15 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40403869&FileExtension=.PDF&FileName=Weather%20Reports%20and%20Records-Master.PDF - Photo 1: On Scene Photo of the Helicycle (item 5, .PDF, 5.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40403864&FileExtension=.PDF&FileName=Photo%201%3A%20On%20Scene%20Photo%20of%20the%20Helicycle-Master.PDF - Photo 2: On Scene Photo of the Helicycle tailboom and tailrotor (item 6, .PDF, 846 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40403867&FileExtension=.PDF&FileName=Photo%202%3A%20On%20Scene%20Photo%20of%20the%20Helicycle%20tailboom%20and%20tailrotor-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.