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 6121The United States Coast Guard (USCG) has published Marine Safety Alert 06-17<\/a> to bring attention to ‘yet another fuel spray fire’. The USCG notes that “these types of incidents, involving fuel leakages contacting hot surfaces and igniting, happen too frequently and have been a focus of various marine safety organizations such as the IMO for many years.”<\/em><\/p>\n What happened?<\/strong><\/p>\n On a 194 GRT offshore supply vessel with an unmanned engine room, a main engine low fuel pressure alarm occurred on the bridge, and was investigated by the crew.<\/p>\n The crew member on watch entered the engine room and identified a high-pressure fuel leak spraying over and upon the port engine’s turbocharger. He also reported a large quantity of diesel fuel in the bilge.<\/p>\n The Master then went down into the engine room and witnessed the ignition of the fire. Using a hand held portable fire extinguisher he quickly attempted to extinguish the fire without success. The Master activated the general alarm, secured the hatches, had crew members secure the ventilation dampers and closed the remote fuel shut-off valves to the engine room. The fire then quickly self-extinguished. No-one was harmed, but this engine room fire led to significant damage, operational down-time of the vessel and lost company revenues.<\/p>\n What went wrong? What were the causes?<\/strong><\/p>\n The source of the fuel leak was identified to be a rupture on a flexible fuel hose connected to the fuel filter assembly. <\/strong>The USCG recommendations can be summarised thus:<\/p>\n Please refer to the fuller report and recommendations on the USCG website<\/a>.<\/p>\n Members may wish to review the following incidents:<\/p>\n The United States Coast Guard (USCG) has published Marine Safety Alert 06-17 to bring attention to ‘yet another fuel spray fire’. The USCG notes that “these types of incidents, involving […]<\/p>\n","protected":false},"template":"","tags":[],"safety_event_tag":[97,109],"class_list":["post-12379","safety-events","type-safety-events","status-publish","hentry"],"acf":[],"yoast_head":"\n
<\/p>\n
\n
\n