somdn-pro
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 6121woocommerce-services
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 6121woocommerce-conditional-shipping-and-payments
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 6121woocommerce-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 6121woocommerce-memberships
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 6121woocommerce-order-status-control
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 6121woocommerce-sequential-order-numbers-pro
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 6121imca-website-2020
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 6121What happened?<\/strong><\/p>\n An ROV system had just completed a test dive to 3000m and was being returned to deck. Upon lifting the system out of the water, the umbilical became detached from the TMS bullet. The ROV and TMS fell to the seabed and landed upside down on a firm seabed at 3276m water depth. The vehicle was located by another ROV system from the same vessel. The system (ROV and TMS) was inspected on the seabed. Based on that information and the sea conditions (1.5m significant wave height), a risk assessment and a toolbox talk (TBT) were carried out which determined that recovery was both safe and possible. The spare bullet was terminated onto the ROV umbilical to allow it to be used to recover the system with the emergency recovery rigging on the TMS. The ROV, TMS and umbilical termination were damaged in the incident. No personnel were injured.<\/p>\n What went wrong?<\/strong><\/p>\n The parted umbilical termination was analysed by a third-party specialist laboratory. Following a detailed engineering examination and internal investigation, it was concluded that the umbilical failed because its termination had been conducted in a very poor fashion with a number of clear defects observed.<\/p>\n What actions were taken? What lessons were learned?<\/strong><\/p>\n Members may wish to refer to: <\/p>\n What happened? An ROV system had just completed a test dive to 3000m and was being returned to deck. Upon lifting the system out of the water, the umbilical became […]<\/p>\n","protected":false},"template":"","tags":[],"safety_event_tag":[97],"class_list":["post-16596","safety-events","type-safety-events","status-publish","hentry"],"acf":[],"yoast_head":"\n<\/p>\n
\n
\n
\n