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
Anchor drag near-miss incident - DEV imca
Skip to content

Anchor drag near-miss incident

A member has reported a near-miss incident in which a barge anchor was dragged approximately 300 metres along the seabed and came within metres of a live export pipeline. Following a visual survey of the pipe 100m either side of the anchor location, it was confirmed that there was no apparen’t structural damage to the pipeline.

The following causal factors were identified:

  • Failure to identify that available monitoring information indicated a potential anchor drag;

Following investigation further causes were identified:

  • Training and competence
    • There was no competency defined for the anchor winch operator position
    • There were no properly identified training requirements for the anchor winch operator position;
  • Procedures
    • Anchor operating procedures were available on the vessel. However, the anchor winch operators were not aware of the location or content of the current procedure
    • The anchor winch operators were unaware of the existence and contents of anchor operating procedures which contained monitoring requirements and contingencies in the event of an anchor dragging
    • Enforcement of operating procedures in the past had not been thorough and failure to follow procedures has gone uncorrected;
  • Management systems
    • Pay-out counting devices were not used as a standard operating practice despite requirement under the procedures
    • A monitoring tool had been reported as broken four days earlier; the defect had been reported to maintenance but the person in charge was not informed. The anchor winch operators continued the operation without fixing the tool
    • There was no record of any management system compliance audit having taken place on the barge;
    • Safe systems of work
    • Despite one of the anchor winch operators having over 12 months’ experience, the two anchor operators were the least experienced on shift at the same time.

The company involved has put the following actions into place:

  • Develop competency matrix for all job roles and monitor competency;
  • Implement mentoring system for inexperienced staff;
  • Ensure shift schedules are properly balanced to ensure experienced personnel teamed with less experienced personnel;
  • Make operating procedures accessible to the crew and ensure crew are aware of operating procedures through ongoing communication;
  • Conduct safety management system audit of barge to confirm compliance with standard operating procedures;
  • Ensure all crew members are appropriately supervised;
  • Ensure all crew members are involved in the daily pre-start meetings;
  • Ensure safety critical equipment is repaired prior to activities commencing.

Safety Event

Published: 16 January 2009
Download: IMCA SF 01/09

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.