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 6121Incident 1: Life-Raft Inadvertently Deployed<\/strong><\/p>\n During monthly inspection of the life-raft, the port side life-raft was accidentally released into the water and activated. The incident was reported to the bridge, vessel made a MOB manoeuvre and crew were mustered. FRC was lowered to retrieve the life-raft, which was recovered without incident.<\/p>\n What went wrong?<\/strong><\/p>\n The second mate was doing the monthly inspection of the life-raft. He inspected how to release the life-raft and checked if it was lashed properly. In doing so he accidentally opened up the clip that launched the life-raft into the water, and because the painter line was still connected, the life-raft was activated.<\/p>\n The second mate was inexperienced with this type of release system and on his first job on this kind of vessel, made his first contract on this type vessel.<\/p>\n What actions were taken? What lessons were learnt?<\/strong><\/p>\n Incident 2: Lifeboat Davit Failed During Test Deployment<\/strong><\/p>\n A vessel was at anchor in a quiet bay and the suggestion was made to take out both lifeboats for tests. Whilst the port side boat was being lowered, with crew inside, a hydraulic part failed, and the forward davit arm fell down to the horizontal. The chief mate (operating the levers) continued to deploy the lifeboat to water, calling down not to release the hooks yet. Crew inside the lifeboat noticed something was wrong because during lowering, the lifeboat tipped bow down by approx. 0.5m. There were no injuries.<\/p>\n The lifeboat was recovered using the forward crane and stored on deck as a quick repair was not possible.<\/p>\n What went wrong? <\/strong><\/p>\n Investigation revealed that there was a damaged\/worn thread and broken bearing in the davit hydraulic equipment.<\/p>\n What actions were taken? <\/strong><\/p>\n Members may wish to refer to:<\/p>\n Incident 1: Life-Raft Inadvertently Deployed During monthly inspection of the life-raft, the port side life-raft was accidentally released into the water and activated. The incident was reported to the bridge, […]<\/p>\n","protected":false},"template":"","tags":[],"safety_event_tag":[97],"class_list":["post-18480","safety-events","type-safety-events","status-publish","hentry"],"acf":[],"yoast_head":"\n\n
\n
\n