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
Vessel made contact with rig legs - DEV imca
Skip to content

Vessel made contact with rig legs

What happened?

A vessel came into contact with the legs of a rig – however, there was no damage to the vessel. The incident occurred when the vessel was moving astern down the prevailing current, to approach the starboard side of the rig. Because the cargo was located on the vessel’s forward deck, the vessel had to approach within two meters of the rig in order to allow the hook to reach the load. When the vessel reached her offload/snatch position below the crane’s hook, the vessel’s bow turned slightly to port, which allowed the current to catch the vessel’s starboard side. The Master observed the vessel drifting towards the rig’s starboard side aft leg and he immediately decided to abort the operation. The vessel was manoeuvred forward with both engines to escape; unfortunately, the port quarter slightly touched the rig’s starboard side aft leg.

What went wrong? What were the causes?

The findings noted were as follows:

  • The Master permitted the operation to take place on the starboard or weather side of the rig and did not request to have the work done from the rig’s port or lee side;
  • The effect of wind and current played a vital role in vessel’s approach to and hitting the rig’s leg;
  • The Master’s decision to approach was not properly risk assessed – he misjudged the direction and effect of the current during manoeuvring;
  • It was not evident that the lifting operation was covered in a specific risk assessment for that particular project;
  • The Master had no robust plan for escape manoeuvring and did not plan when to abort manoeuvring.

What actions were taken? What lessons were learned?

  • A better understanding was needed of the risks and hazards of manoeuvring against the current;
  • A more detailed prior agreement should have been made between the vessel Master and the offshore installation manager (OIM) with regard to cargo and lifting operations;
  • Escape routes and plans should be considered before starting any critical manoeuvring;
  • The vessel Master – rather than the OIM or the client – has the overriding authority to accept or reject the operation based on judgment about the weather limitations and circumstances.

Members may wish to refer to the following incidents:

Safety Event

Published: 9 May 2018
Download: IMCA SF 10/18

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.