ANC17LA040

NTSB accident investigation · Robinson Helicopter R44 · Solomon, AK · August 3, 2017

Accident · No injuriesClass 3 · LimitedFinal report
Date
August 3, 2017, 10:32 local (18:32 UTC)
Place
Solomon, AK
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Maneuvering
Aircraft
N4138MRobinson Helicopter R44
Defining event
Maneuvering-low-alt flying: Low altitude operation/event
Weather
Visual (VMC) · Day
Status
Completed
Report
Approved by Office Director
Investigation class
Class 3
NTSB office
Alaska Regional Office
Parties
FAA Anchorage FSDO, Robinson Helicopter Company
FAA report
20170803017929A
Case key
95762

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

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.

Findings · 4

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

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.

Factual narrative

On August 3, 2017, about 1032 Alaska daylight time, a Robinson Helicopter Company R-44 helicopter, N4138M, was substantially damaged when it was involved in an accident near Solomon, Alaska. The commercial pilot and passenger were not injured. The helicopter was operated as a Title 14 Code of Federal Regulations (CFR) Part 135 on-demand charter flight. The pilot reported that the purpose of the flight was to place mineral claim markers, which involved maneuvering the helicopter over a designated GPS location, after which the passenger would drop the marker from the rear left seat of the helicopter. Some of the mineral claim corners were in water, and the placement of those markers had to be offset to the nearest land mass. The pilot departed Nome Airport (OME), Nome, Alaska, and flew to the passenger's residence about 4 miles east, where the passenger boarded the helicopter and they departed on the accident flight. After reaching the destination and while placing the markers, helicopter was operating about 10 to 15 ft above the water over a lagoon between the mainland and a sand barrier. The pilot reported that he was "lower than he should have been" and lost situational awareness while programming the GPS. He inadvertently allowed the helicopter to descend into the water "in a more level or slight nose-low attitude." He further reported that he must have pushed forward on the cyclic as he leaned forward to manipulate the GPS. Upon impact, the helicopter rolled and came to rest on its right side in about 4 ft of water. After egressing, the pilot and passenger waded about 200 ft to the shore with the helicopter occupant survival bag and a satellite telephone. The pilot contacted the operator with the satellite telephone and a second company helicopter was dispatched to pick up the pilot and passenger about 1200. The pilot reported that there were no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation and stated that the accident could have been prevented by maintaining a higher altitude and not fixating on the GPS unit. The helicopter sustained substantial damage to the main rotor system, the fuselage, the tail boom, and the tail rotor system.

Aircraft

Registration
N4138M
Reported as
Robinson Helicopter R44 (II)
Category
Helicopter
Serial number
12159
Built
2008
Airframe hours
2,053.8
Engine
Lycoming IO-540 Series, 205 horsepower, reciprocating
Damage
Substantial damage
Flight
Part 135
Operator
Bering Air, Inc., doing business as Bering Air, Inc.
Registered owner
Bering Air, Inc.
Airworthiness certificate
Standard, Normal
Last inspection
100 hour · July 8, 2017
Departed
OME · Nome, AK
Destination
OME · Nome, AK
Flight plan
Company VFR
Equipment
Satellite tracking device, Handheld GPS

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
48
Injuries
None
Certificates
Commercial, Flight instructor
Instrument ratings
Helicopter
Medical
Class 1, With waivers/limitations
Last flight review
May 9, 2017
Seat
Right
Restraint
4-point
Flight hours
3,818 total · 266 in this make and model · 742 as pilot in command · 184 in the last 90 days · 90 in the last 30 days · 3 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
310° at 4 knots
Visibility
10 statute miles
Lowest ceiling
5,000 ft overcast
Temperature
57 °F, dew point 54 °F
Altimeter
29.84 inHg
Observed at
PAOM, 30 nm away

Docket · 10

The files NTSB released with the investigation on January 5, 2021, on NTSB’s docket system: statements, records, photos and specialists’ reports. 7.3 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.