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
Uncontrolled movement of crane block and pennant during lifting operations at sea - DEV imca
Skip to content

Uncontrolled movement of crane block and pennant during lifting operations at sea

What happened?

During bunkering operations between two vessels at sea, there was an uncontrolled movement of a crane block, resulting in a pennant striking a supply vessel, placing personnel in the line of fire. The receiving vessel’s crane was positioned along the supply vessel’s port side where deck crew were waiting to secure and connect the hose to the rigging. The supply vessel rolled to Port due to sea swell. This caused the crane’s auxiliary hoist block to make contact with the supply vessel’s ROV launch and recovery system platform, which in turn caused the hoist block and attached pennant to swing.

While swinging, the pennant and hook made contact with the work station close to where the supply vessel’s deck crew were stationed. Following the incident, an All Stop was called. After the task was reassessed, the supply vessel proceeded to re- route the hose along the main deck. The operation was successfully completed.

What went wrong? What were the causes?

  • Before starting the operation, the following requests were made:
    • route the hose along the main deck aft instead of the port side – rejected by the supply vessel crew
    • use a longer pennant to increase the distance between block and the intended load – rejected by receiving vessel crew who felt the longer pennant would increase potential swing
    • before transferring the bunker hose, the supply vessel requested that the receiving vessel make a heading change to reduce thruster wash as it was making it difficult to maintain station. The heading was changed, station keeping stabilized, and control of the operation was handed to the receiving vessel’s deck crew;
  • The two vessels had never previously conducted bunkering operations together;
  • There was minimal communication between the vessels before the job started. The only discussion was regarding the length of the hose (60m required by receiving vessel, as opposed to supply vessel’s suggested 30m);
  • There was no comprehensive planning or control of work between departments on board the receiving vessel:
    • engine control room raised a permit to work with a risk assessment covering the operation, no deck officers or deck crew were included in the toolbox talk or signed onto the permit
    • the permit to work was generic for cargo operations.

What lessons were learnt? What actions were taken?

  • Activities involving different departments should be jointly and thoroughly planned with clearly defined roles and responsibilities;

Operations involving crews unfamiliar with one another (as on visiting supply vessels, etc.) should be fully planned in advance.

Members may wish to review the following incidents:

Safety Event

Published: 23 August 2017
Download: IMCA SF 21/17

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.