FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Ridgeline Aviation Robinson R66 accident

19 Jun 2018 · Cordova, AK, United States

Robinson R66 · Accident during landing

From Cordova Municipal Airport (CKU) to Cordova, AK

Report a problem

Event

NTSB case
GAA18CA366
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
0 · 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
Charter & commuter
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

Robinson R66

Aircraft type
Robinson R66
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
N7040P
Onboard fatalities
Unknown
Route
From Cordova Municipal Airport (CKU), Cordova, AKTo Cordova, AK
Aircraft age
About 6 years (built 2012)
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 135: Air Taxi & Commuter
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
Landing
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
Miscellaneous/other
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tower/antenna (incl guy wires)
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

  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The helicopter pilot reported that, after multiple attempts to find a suitable landing site on a mountain ridgetop, the tail rotor impacted brush during landing. The helicopter pivoted, the main rotor contacted a communications tower, and the helicopter then rotated 180° and rolled onto its left side.

The helicopter sustained substantial damage to the windscreen and main rotor mast.

The pilot reported that there were no preaccident mechanical failures or malfunctions with the helicopter that would have precluded normal operation.

Probable cause

The pilot’s selection of unsuitable terrain for landing, which resulted in impact with brush and a loss of helicopter control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA18CA366
Event ID
20180620X21155
Case number
GAA18CA366
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. 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: a5bf1b52e992ab7527e4ef40e99988e80d3de72bde210dd111c56154d0aedb60; retrieved 2026-09-16T07:35:23.798Z.