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 vessel lost control of its steering gear due to leakage through the Karm fork seals, leading to uncontrolled flooding in the steering compartment. The engine room received a steering gear compartment bilge high level alarm and the bilge pump was started. After fifteen minutes of pumping out, the alarm was still active, and only then were the Chief Engineer and Captain informed. The Chief Engineer went to the steering gear compartment and found water below the floor plates.<\/p>\n The vessel was facing heavy seas and rolling heavily. After thirty minutes, the bilge alarm went off, the bilge pump lost suction, and it was stopped. On the bridge, there was a power failure alarm on the steering control panel, and vessel steering was lost. The steering gear compartment was found flooded to 30cm above the floor plates. The bilge pump was started again and the equipment in the steering gear compartment isolated.<\/p>\n An announcement was made on the PA system regarding the steering gear failure; the client was informed and vessel assistance was requested. The Chief Engineer also found the bilge alarm float level-arms in broken condition (see rightmost image). A submersible pump was used to pump out water from the flooded compartment. Also, steps were taken to lighten the vessel by pumping out a number of freshwater tanks.<\/p>\n What went wrong? What were the causes?<\/strong><\/p>\n The main cause of the flooding was found to be the worn-out condition of the towing pin\/Karm fork seal. Due to the rough weather, water was coming onto the deck and entered the steering compartment through the leaking seal.<\/p>\n What lessons were learnt?<\/strong><\/p>\n What actions were taken?<\/strong><\/p>\n The operation of the bilge level sensors was checked, as per PMS recommendations.<\/p>\n Members may wish to review the following incidents:<\/p>\n What happened? A vessel lost control of its steering gear due to leakage through the Karm fork seals, leading to uncontrolled flooding in the steering compartment. The engine room received […]<\/p>\n","protected":false},"template":"","tags":[],"safety_event_tag":[97],"class_list":["post-13703","safety-events","type-safety-events","status-publish","hentry"],"acf":[],"yoast_head":"\n<\/p>\n
<\/p>\n
<\/p>\n
\n
\n
\n