Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

March 2, 2013 · Hughes 369HS HS · N471M

Latangai Island, PO, PG

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
March 2, 2013
Injury Outcomes
2 injuries (1 fatality, 1 serious injury)
Location
Latangai Island, PO, PG
Aircraft
Hughes 369HS HS (1974)
Tail Number
N471M
Operator
Jerrys Helicopter Service
Injuries
Fatal
Aircraft Damage
Substantial
NTSB Number
WPR13LA137

The pilot reported that, as he was flying toward a school of fish, he observed a nearby fishing vessel moving in the same general direction. He flew over the vessel then continued toward a fish aggregating device (FAD), which is a floating object designed and strategically placed to attract fish; it was located about 0.7 mile away from the vessel. As the pilot approached the FAD, he circled twice and then descended the helicopter into a low hover over the FAD. The helicopter was positioned into the wind, and the vessel was approaching the helicopter from behind. With the helicopter still in a low hover, the fish spotter reached out of the helicopter to attach a radio buoy to the FAD. Shortly after, the helicopter was struck from behind by the vessel. The helicopter subsequently plunged into the ocean. The fish master, who was at the controls of the vessel, reported that he observed the helicopter circle twice before it appeared to fly out of the area. He was slowing the vessel when it was about 500 meters (0.3 mile) from the FAD when he observed the helicopter in front of the vessel. The captain of the vessel reported that he was on the vessel's helicopter deck when he noticed the helicopter circle twice and then descend to a hover. He stated that he was unsure what the helicopter was doing until he saw the fish spotter reach for the FAD. At this time, he felt the fish master reverse the vessel; however, it still impacted the helicopter's tail. The Federal Aviation Administration Model Civil Aviation Regulations, Version 2.7, Part 11 states, "Each operator shall conduct operations so as not to endanger persons or property on the surface nor aircraft in flight." The U.S. Department of Homeland Security, United States Coast Guard Navigation Rules state, "every vessel shall at all times maintain a proper look-out by sight and hearing...as to make a full appraisal of the situation and of the risk of collision." Both the pilot and the fish master of the vessel should have been adequately monitoring their environment and their failure to do so resulted in a collision.

NTSB Probable Cause

The failure of both the pilot and the fish master of the vessel to adequately monitor their environment, which resulted in a collision.

Full Narrative

On March 2, 2013, about 1320 Universal coordinated time (UTC), a Hughes 369HS, N471M, impacted the Pacific Ocean after being struck by a commercial fishing vessel in international waters near Latangai Island, Papua New Guinea. The airline transport pilot sustained serious injuries, and the one fish spotter (passenger) sustained fatal injuries. The helicopter's main rotor assembly and tail rotor assembly were substantially damaged. The aircraft was registered to and operated by Jerry's Helicopter Service, Inc. under the provisions of 14 Code of Federal Regulations Part 91. Day, visual meteorological conditions prevailed for the flight and no flight plan had been filed. The flight originated from the helicopter's designated vessel (MV FK 869) at approximately 1220 UTC. The pilot reported that while flying the fish spotter found a fish formation. The pilot was flying towards it when he observed a fishing vessel motoring nearby, and in the general direction of, where the fish were spotted. The pilot circled over the vessel and identified it as the Pacific Ranger before it proceeded to circle over the fish formation. When the fish spotter found the fish aggregating device (FAD), which are floating objects designed and strategically placed to attract fish, the pilot approached the FAD and hovered over it at a low altitude about 0.7 miles away from the Pacific Ranger. During this time, the helicopter was positioned into the wind, with the Pacific Ranger approaching from behind. The fish spotter reached out of the helicopter and attempted to attach a radio buoy to the FAD when the helicopter suddenly shook violently and plunged into the ocean, coming to rest upside down. The fish master of the Pacific Ranger was at the controls at the time of the accident. He reported that prior to seeing the helicopter he observed it on radar when it was about 20 miles away. The helicopter approached the Pacific Ranger and circled around it twice. The fish master reported that it appeared that they did not find the FAD and flew out of the area. When the vessel was about 500 meters from the FAD he was slowing down the vessel when he observed the helicopter in front of them. The captain of the Pacific Ranger reported that he was on the helicopter deck of the Pacific Ranger watching for tuna and FADs when he noticed the helicopter circle twice and descend to a hover about five ship lengths in front of, and facing away from, the Pacific Ranger. He was unsure what the helicopter was doing until he observed the fish spotter climb onto the float of the helicopter and reach for the FAD. At this time, he felt the fish master reverse the Pacific Ranger, however, they still impacted the tail of the helicopter. A GPS, which contained waypoints the pilot created during the flight, was recovered from the helicopter and taken to the manufacturer for analysis. The GPS data indicated that when the helicopter initially flew in front of the Pacific Ranger, the helicopter was about 1.7 nautical miles (nm) (about 2 miles) away from the FAD and the Pacific Ranger was about 1.9 nm (2.3 miles) away. The helicopter continued toward the FAD and made one large circle, followed by a smaller circle, before descending to a low hover. The GPS did not indicate time nor did it show the speed of the helicopter or Pacific Ranger. According to The Federal Aviation Administration's Model Civil Aviation Regulations (MCARS), Version 2.7, Part 11 states under Fish Spotting Operating Rules, "Each operator shall conduct operations so as not to endanger persons or property on the surface nor aircraft in flight." According to the U.S. Department of Homeland Security, United States Coast Guard Navigation Rules state "every vessel shall at all times maintain a proper look-out by sight and hearing as well as by all available means appropriate in the prevailing circumstances and conditions so as to make a full appraisal of the situation and of the risk of collision."

Flight

Event TypeAccident
Event Time13:20 UTC
Nearest Airport0nm
Flight Plan FiledCvfr
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftHughes 369HS HS
Tail NumberN471M
Aircraft CategoryHeli
DamageSubstantial
OperatorJerrys Helicopter Service
Operating RulePart 91
Engines1
Engine TypeTurboshaft
Engine DetailsAllison · 250-C18 · Turboshaft · 317
Seats5

People & Injuries

Injury Summary2 injuries (1 fatality, 1 serious injury)
Fatal1
Serious1
Minor0
Uninjured0
Total2
Crew 1Age 50 · First Class · Serious

Conditions

ConditionsVMC
LightDaylight
Wind80° @ 15 kt, gusting 20 kt
Visibility20 sm
CeilingNone
Temperature / Dew Point0 C
Altimeter29.84 inHg
Weather SourcePILO

Appendix: Source Data