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 During bunkering operations alongside, there was a spillage of around 3 litres of fuel when the hose coupling was loosened during fault-finding. The incident occurred when a vessel took bunkers supplied by five tanker trucks, one after the other. The bunker hose was connected to the manifold from the first truck. Bunkering was started and after about four minutes, the truck driver complained of back pressure and bunkering was stopped.<\/p>\n To investigate the reason for the back pressure, suspecting that the manifold valve was not functioning properly, the Chief Engineer instructed the Fitter to open the hose coupling at the manifold. As soon as the coupling was loosened, fuel oil sprayed out onto the pier due to pressure in the pipe. Disconnection was stopped immediately, and the spilt oil was contained in the save-all at the manifold.<\/p>\n The local Coast Guard were informed and arrived at the site for an investigation. They instructed crew to clean up the spilt oil on the pier and retain the sweepings onboard. Clean-up on deck and pier was done using the vessel’s SOPEP equipment. Reports were made to all concerned parties as required. No restrictions were placed on the vessel by the Coast Guard or the port.<\/p>\n What were the causes?<\/strong><\/p>\n What action was taken? <\/strong><\/p>\n A full review of bunkering procedures took place. <\/p>\n Members may wish to refer to:<\/p>\n What happened? During bunkering operations alongside, there was a spillage of around 3 litres of fuel when the hose coupling was loosened during fault-finding. The incident occurred when a vessel […]<\/p>\n","protected":false},"template":"","tags":[],"safety_event_tag":[97],"class_list":["post-17452","safety-events","type-safety-events","status-publish","hentry"],"acf":[],"yoast_head":"\n\n
\n
\n