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
Failure to report hydraulic leak subsea - DEV imca
Skip to content

Failure to report hydraulic leak subsea

A member has reported an incident in which crew failed to appropriately report a hydraulic leak subsea. The intent of this report is to highlight key learnings from that failure and to understand the reasons why the incident had not been reported at the time of occurrence.

The incident occurred during subsea operations which involved divers monitoring a manifold valve. A hydraulic release occurred when a valve was operated by the client FPSO. This leak was not detailed on the Dive Log or as an anomaly within the Management of Change (MoC) step of the operation. It was not reported to the Offshore Management Team nor to the client representative on board at the time. The client became aware of the leak some four months later following a review of as-built video footage, and onshore project management were notified of the incident. In the regulatory framework within which the vessel was operating, it is a requirement that any such releases to sea are reported by the client within 6 hours of such an event occurring.

No personnel were harmed or equipment damage sustained; however, an unknown volume of fluid was discharged to the environment which was not reported at the time of the incident.

Our member noted the following:

  • The requirement to report all subsea leaks was not followed. Personnel were not familiar with company procedures in place to ensure compliance with local regulations;
  • Project process to manage implementation of client site instructions for additional works were not clearly defined.

The following lessons were learnt:

  • Ensure that pollution reporting process requirements are understood by all key personnel both onshore and offshore;
  • Dive Plans should clearly reflect requirement to notify both client, master and project engineer of any discharge observed from subsea infrastructure.

Members may wish to refer to the following incident (search word: pollution):

Safety Event

Published: 6 December 2016
Download: IMCA SF 33/16

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.