Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the 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 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-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 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-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 6121

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 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-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 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-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 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-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 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the imca-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 6121

Warning: Cannot modify header information - headers already sent by (output started at /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php:6121) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php:6121) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php:6121) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php:6121) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php:6121) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php:6121) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php:6121) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php:6121) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/rest-api/class-wp-rest-server.php on line 1896
{"id":17452,"date":"2019-04-25T14:50:27","date_gmt":"2019-04-25T13:50:27","guid":{"rendered":"https:\/\/www.imca-int.com\/?post_type=alerts&p=17452"},"modified":"2019-04-25T14:50:27","modified_gmt":"2019-04-25T13:50:27","slug":"oil-spill-during-bunkering","status":"publish","type":"safety-events","link":"https:\/\/dev.imca-int.com\/blog\/safety-events\/oil-spill-during-bunkering\/","title":{"rendered":"Oil spill during bunkering"},"content":{"rendered":"

What 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

\"\"
Bunker hose connection at ship’s bunker manifold<\/figcaption><\/figure>\n
\"\"
Ship’s bunker manifold valve<\/figcaption><\/figure>\n

What were the causes?<\/strong><\/p>\n