FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC22FA018 · Sikorsky S-61N

22 Feb 2022 · Kekaha, HI, United States

Croman Sikorsky S-61N · Accident: loss of control in flight during landing

Report a problem

Event

NTSB case
ANC22FA018
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
4 · 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

Sikorsky S-61N

Aircraft type
Sikorsky S-61
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
N615CK
Operator
Croman
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 60 years (built 1962)
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 133: Rotorcraft Ext. Load
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
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Organizational issues › Support/oversight/monitoring
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The accident helicopter was under contract to the United States Navy. The mission for the accident flight involved locating a training torpedo in the open waters, retrieving the torpedo using a recovery basket/cage system, then returning the torpedo to Pacific Missile Range Facility (PMRF) by sling load. According to automatic dependent surveillance-broadcast (ADS-B) data, after the helicopter departed, it proceeded north-northwest to an area about 44 miles away. After maneuvering in the area, the helicopter proceeded south-southeast to return to PMRF. As the helicopter approached the facility, it crossed the shoreline and began a shallow left turn as it maneuvered to the north, into the prevailing wind. As the helicopter neared the predetermined drop-off site, the left turn stopped, and the helicopter proceeded in a northeasterly direction. Multiple witnesses located near the accident site reported that as the helicopter continued the left turn towards the drop-off site, the turn stopped, and it began to travel in a northeast direction. The witnesses noted that as the helicopter flew about 200 ft above the ground, it gradually pitched nose down and impacted nose first, in a near-vertical attitude. An examination of the wreckage revealed the flight control fore/aft servo input link remained connected at its clevis end to the flight control fore/aft bellcrank, located adjacent to the main gearbox. However, the rod end was partially connected to the fore/aft servo input clevises and its bolt had mostly backed out of its normally installed position. The bolt exhibited no evidence of fractures or visible deformation and its threads exhibited no unusual wear. Therefore, the bolt likely backed out of its normally installed position during the accident flight due to the absence of its nut and cotter pin. This would have caused an uncommanded input to the fore/aft servo, resulting in the helicopter’s nose-down attitude, and the inability of the crew to control the pitch attitude of the helicopter. The fore/aft primary servo was installed on December 28, 2021. About 7.5 flight hours had elapsed from the time the fore/aft primary servo was installed until the day of the accident. The mechanic who installed the fore/aft servo input link to the fore/aft primary servo likely failed to correctly install the attaching hardware. The company’s certified inspector and who oversaw and inspected all of the work at completion, failed to ensure the hardware attaching the fore/aft servo input link to the fore/aft primary servo was installed correctly.

Probable cause

The improper installation of the fore/aft primary servo by maintenance personnel, which resulted in the attaching hardware backing out and which subsequently rendered the helicopter uncontrollable. Contributing to the accident was the company’s quality control personnel to identify the improper installation before certifying the helicopter for flight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC22FA018
Event ID
20220222104681
Case number
ANC22FA018
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, cause areas. 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: b62a64710f1fc85906e8250c006a9b8a4587d5fde7778fdcdd4c0e0a90bf1b05; retrieved 2026-09-15T07:41:21.894Z.