FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Bering Air Robinson Helicopter Company R44 II accident

3 Aug 2017 · Solomon, AK, United States

Robinson Helicopter Company R44 II · Accident: low altitude operation/event while maneuvering

From Nome Airport (OME) to Nome Airport (OME)

Report a problem

Event

NTSB case
ANC17LA040
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 Helicopter Company R44 II

Aircraft type
Robinson R44
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
N4138M
Operator
Bering Air
Onboard fatalities
Unknown
Route
From Nome Airport (OME), Nome, AKTo Nome Airport (OME), Nome, AK
Aircraft age
About 9 years (built 2008)
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
Maneuvering · low-altitude flying
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
Low altitude operation/event
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
  • Personnel issues › Psychological
  • Personnel issues › Task performance

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

NTSB narrative

The pilot was conducting a commercial charter flight for the passenger to place mineral claim markers. He stated that, while flying over a lagoon at an altitude lower than he "should have been," while making inputs to the GPS unit, he likely inadvertently applied forward cyclic and allowed the helicopter to descend into the water below. The pilot reported that there were no mechanical malfunctions or anomalies with the helicopter that would have precluded normal operation. Although helicopters operated under 14 CFR Part 135 are required to be equipped with radar altimeters, the accident helicopter was not, as the operator had been authorized by the Federal Aviation Administration (FAA) to operate the helicopter without one. It is likely that if a radar altimeter was installed in the helicopter at the time of the accident, was functioning properly, and was set to provide an aural warning at a predetermined altitude, the pilot may have had adequate time to recognize and stop the inadvertent descent before impact with water.

Probable cause

The pilot's failure to maintain adequate altitude above water, and his loss of situational awareness, which resulted in an inadvertent descent and collision with water.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC17LA040
Event ID
20170807X63537
Case number
ANC17LA040
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: e3f431dbefdc00881c0d57e6bbb6a19f70f665327d59c0435ce6593e3b923516; retrieved 2026-09-16T05:40:32.811Z.