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
Pipe stacking incident - DEV imca
Skip to content

Pipe stacking incident

A member has reported a near-miss which could have been a potentially serious incident, which occurred during the stacking of lengths of pipe. The pipe joints were being off-loaded from the transport vehicle, and were being stacked pending further loading into U-frames for delivery to the pipelay vessel.

The procedure specified a stack with a maximum height of 8 layers of the 10″ pipe joints. When placing the seventh layer on a stack, the front end pipe joint in the bottom layer slipped out of the restraining chock, pushing the other chocks ahead of it. This was followed by a slow slippage of the entire base layer, causing the rest of the pipe stack to slump. The slippage of pipes continued until it came to rest against a fork lift truck that was parked in front of the stack.

The area in front of the stack was used as an inspection area, but at the time of the incident no people were in the area and, as a result, nobody was injured and there was only negligible damage.

The method employed for stacking the pipe had been used on several projects without any previously recorded incidents.

The investigation showed that the pipe coating was smooth, not sintered as expected, with little or no friction. This had been noted upon reception of the pipe joints, but not considered a problem. A subsequent sensitivity analysis, conducted as part of the investigation, revealed that the smooth surface more than doubled the forces that the wooden restraining chocks would have to withstand.

The discovery of the smooth pipe coating should have resulted in the initiation of a management of change process, which would have led to further engineering and a new risk assessment for the pipe stacking. This was not done.

As a result of this incident, a new method was employed to secure the bottom layer. Four lengths of pipe were inserted into pipe joints and these were secured with chains and turnbuckles (see photo below).

Original method
Original method
New method employed after the incident
New method employed after the incident

The company involved has noted the lessons learned from this incident as including:

  • Always use a management of change process when things are different than expected;
  • Pipe stacks should be located so that work in front of/or behind the stack is avoided;
  • The method of stacking pipe should be evaluated for each type of pipe, taking into account the coating, to determine if securing the stack with wooden chocks is sufficient or other methods have to be adopted.

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.