WPR18FA260 · Robert L Coons RotorWay RW 1
Robert L Coons RotorWay RW 1 · Accident: controlled flight into terrain/object (CFIT) while maneuvering
From Billings Logan International Airport (BIL) to Billings Logan International Airport (BIL)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR18FA260
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Robert L Coons RotorWay RW 1
- Aircraft type
- Robert L Coons ROTORWAY RW 1
- Category
- Helicopter
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N166LC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Billings Logan International Airport (BIL), Billings, MTTo Billings Logan International Airport (BIL), Billings, MT
- Aircraft age
- About 3 years (built 2015)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Maneuvering
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Controlled flight into terrain/object (CFIT)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Physical environment
- Personnel issues › Psychological
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The pilot, who did not hold a helicopter rating, was maneuvering his experimental amateur-built helicopter around the airport area. An acquaintance of the pilot stated that the accident pilot would regularly hover-taxi around the airport area testing the helicopter. The acquaintance also stated that, on the day of the accident, the pilot mentioned that the helicopter was flying well and that he did not have any issues with it. Afterward, the pilot started the helicopter and departed to the west and hover-taxied around the row of hangars back to his hangar. The acquaintance reported that he did not see the accident but that he heard the sound of the helicopter impacting a hangar.
Postaccident examination of accident site showed that the helicopter's main rotor blades had collided with the top section of the hangar and that the helicopter came to rest oriented upward on an angle of about 30° and against the front of the hangar on a westerly heading. It is likely that, during the hover-taxi, the accident pilot ascended above a hover to the height of the hangars before colliding with one.
The left anti-torque pedal for the pilot's right-seat position had failed where the horizontal and vertical tubes met. Notwithstanding the failed anti-torque pedal, examination of the airframe and engine found no mechanical anomalies that would have precluded normal operation of the helicopter.
A metallurgical examination of the fractured horizontal and vertical components of the pilot's right seat's left anti-torque pedal assembly revealed that they failed from a lack of complete fusion at a fillet joint, which led to an overstress fracture. The fractured pedal tube assembly consisted of two aluminum tubes joined together with a filler metal that was consistent with a zinc solder alloy. However, the right anti-torque pedal tube assembly, which was intact, consisted of alloy steel tubes that were welded together with an alloy steel filler metal. The intact tube assembly had a much stronger quality due to the welding process and the inherent higher mechanical properties of the steel than those of the fractured tube assembly.
A build ledger for the helicopter revealed that the anti-torque pedals had been fabricated in December 1996 by the previous owner, almost 20 years before the accident pilot purchased the helicopter. However, the ledger did not detail the fabrication differences among the anti-torque pedals.
The investigation could not determine if the left anti-torque pedal for the right-seat position failed before the impact with the hangar or during the impact sequence. Although the pilot might have been able to control the helicopter after the pedal failed, that possibility would be unlikely given the pilot's minimal experience in helicopters.
Probable cause
The pilot's failure to maintain clearance with a hangar while maneuvering to his hangar. Contributing to the accident was the pilot's limited experience in helicopters.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR18FA260
- Event ID
- 20180912X65838
- Case number
- WPR18FA260
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: b7664f075a7f343c3e48ba7009118d5518eb97a7d1b18cd36df3f2dc5e9dad0f; retrieved 2026-09-15T06:48:00.778Z.