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 burning of sludge in the vessel incinerator, there was a high exhaust gas temperature alarm. Smoke appeared from the incinerator exhaust gas manifold, followed by a fire inside the exhaust pipe.<\/p>\n 19:34: the alarm sounded, and the crew mustered. The vessel course was altered to prevent the spread of smoke. Boundary cooling of the funnel was started; the fire team entered the incinerator room with extinguishers to fight the fire but were unable to extinguish it.<\/p>\n 19:41: the fire team left the incinerator room and sealed the door. Minutes later, the sprinkler system for the incinerator room was activated.<\/p>\n 20:01: the fire extinguished and the sprinkler system was stopped.<\/p>\n Smoke and high temperatures remained for over an hour; boundary cooling continued until the situation was stabilized at around 21:00. A fire watch was maintained until midnight. There were no injuries but there was some damage to the equipment in the incinerator room.<\/p>\n The incinerator was only used for burning sludge, at a temperature somewhere between 810-850\u00c2\u00b0C. For some reason the flame extinguished. <\/p>\n Detailed Sequence of Cause of Fire<\/strong><\/p>\n What went wrong? <\/strong><\/p>\n What lessons were learned?<\/strong><\/p>\n Have a full, detailed and comprehensive understanding of what happens to incinerators and other similar equipment when the EMERGENCY STOP<\/strong> button is pressed, and\/or when power fails and restarts. This applies not only to incinerators but to all complex machines. Ensure that incinerator flame failure devices are tested as part of the vessels’ planned maintenance system.<\/p>\n Members may wish to refer to the following three incidents, none of which are fires. Two have as a cause, lack of understanding of the technicalities of how certain equipment works. In the third, a serious incident arose from poor understanding of the consequences of a power outage.<\/p>\n What happened? During burning of sludge in the vessel incinerator, there was a high exhaust gas temperature alarm. Smoke appeared from the incinerator exhaust gas manifold, followed by a fire […]<\/p>\n","protected":false},"template":"","tags":[],"safety_event_tag":[97],"class_list":["post-18972","safety-events","type-safety-events","status-publish","hentry"],"acf":[],"yoast_head":"\n\n
\n
\n