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 A potential fire hazard was discovered, caused by a failed fuel pipe connection on the supply line to the main engines. The Chief Engineer was called to engine room with a report of a leak on a low pressure fuel supply line supplying both main engines. Upon arriving in the engine room and assessing the situation, a temporary repair was effected, due to being unable to isolate the pipe. Self-amalgamating tape was used to reduce the leak to a weep and then fibre-glass resin and bandage was applied, to try and seal the weep.<\/p>\n At the time, both main engines were running with the starboard engine on load, although the port propeller was declutched. Three auxiliary engines and all the thrusters were on load.<\/p>\n What were the causes?<\/strong><\/p>\n The immediate cause<\/strong> was found to be a failed weld on a T-piece of the pipe. The root cause<\/strong> is believed to be the age of the pipe, an original fit from the vessel’s construction, incurring natural degradation over time.<\/p>\n Actions taken and lessons learnt<\/strong><\/p>\n In this case, a trend in the failure of fuel supply piping was noticed; this was the 4th<\/sup> failure within 4 months.<\/p>\n Members may wish to refer to the following incidents:<\/p>\n What happened? A potential fire hazard was discovered, caused by a failed fuel pipe connection on the supply line to the main engines. The Chief Engineer was called to engine […]<\/p>\n","protected":false},"template":"","tags":[],"safety_event_tag":[97,109],"class_list":["post-12112","safety-events","type-safety-events","status-publish","hentry"],"acf":[],"yoast_head":"\n\n
\n