Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the the-events-calendar domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the broken-link-checker domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-eu-vat-number domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php on line 6114
Loss of rig anchor wire from vessel Karm Fork - DEV imca
Skip to content

Loss of rig anchor wire from vessel Karm Fork

What happened?

There was an unplanned retraction of the Karm Fork on an Anchor Handling vessel, leading to an anchor tow wire and chain to be dropped.  The incident occurred during a rig move.  The Anchor Handling vessel was following the rig with the anchor line secured in the Karm Fork on deck with 300m of wire and 150m of chain between the rig and vessel.  During the transit to the new location, the vessel accidentally retracted its Karm fork, allowing the wire and chain between the vessel and rig to slip over the vessel stern roller into the sea.  Water depth at the time was 370m.  No subsea assets were in the vicinity, no personnel were in the line of fire.

What went wrong?

Our member noted that the preliminary investigation revealed that the causes were lack of communication, failure to follow company procedures and failure to follow the Masters’ instructions:

  • The Chief Engineer raised the port side Karm Fork with no command from the Master – the company procedure states “All instructions for operation of the anchor handling plant will be disseminated directly from the Master“;
  • Ignoring the Masters’ request and lack of attention — even after the Masters’ second command to lower the port side Karm Fork, the Chief Engineer delayed the task implementation and then in a rush accidentally pushed the emergency release buttons of the wrong Karm Fork.

What actions were taken?  What lessons were learnt?

  • Revision of operations manual and task risk assessment;
  • Relocation of CCTV camera to cover deck area;
  • Reiteration of need for strict compliance to manual requirements and specifically, the need to follow the requirement that such commands or actions should come from the Master only.

Members may wish to refer to:

Safety Event

Published: 30 September 2019
Download: IMCA SF 23/19

Relevant life-saving rules:
IMCA Safety Flashes
Submit a Report

IMCA Safety Flashes summarise key safety matters and incidents, allowing lessons to be more easily learnt for the benefit of all. The effectiveness of the IMCA Safety Flash system depends on Members sharing information and so avoiding repeat incidents. Please consider adding safetyreports@imca-int.com to your internal distribution list for safety alerts or manually submitting information on incidents you consider may be relevant. All information is anonymised or sanitised, as appropriate.

IMCA’s store terms and conditions (https://www.imca-int.com/legal-notices/terms/) apply to all downloads from IMCA’s website, including this document.

IMCA makes every effort to ensure the accuracy and reliability of the data contained in the documents it publishes, but IMCA shall not be liable for any guidance and/or recommendation and/or statement herein contained. The information contained in this document does not fulfil or replace any individual’s or Member's legal, regulatory or other duties or obligations in respect of their operations. Individuals and Members remain solely responsible for the safe, lawful and proper conduct of their operations.