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 stand-by diver on a light daughtercraft (LDC) was nearly hit by a flying block and tackle, which was thrown towards him by an unplanned release of tension during mooring operations. The incident occurred when a team of divers were carrying out a familiarisation diver rescue drill in preparation to work from an LDC alongside a floating production storage and offloading unit (FPSO). In preparing to return to the mother vessel, the LDC was disconnected from two mooring lines suspended from the FPSO. The forward FPSO mooring line caught under the T section of a removable diver rescue davit arm installed on the LDC. This created a tension on the arm which self-released, causing the arm to move very suddenly. Attached to the end of the arm was a block and tackle weighing approx. 1.5kg. This was jettisoned at head height and flung towards a bulkhead adjacent to the stand-by diver.<\/p>\n What went wrong?<\/strong><\/p>\n Investigation concluded that the incident occurred as a result of the LDC drifting forward whilst being made ready for transit, with the diver rescue davit in the deployed position. The deck crew on the LDC were preoccupied in the stowage of equipment and did not notice the LDC had drifted forward to the point where the forward mooring line was midships with the LDC. When the coxswain engaged the motor to depart the worksite, the mooring line had caught under the T-section of the diver rescue davit; when the LDC turned to starboard, the davit arm forcefully recoiled to its stowage position.<\/p>\n What were the causes?<\/strong><\/p>\n Lessons learnt<\/strong><\/p>\n Actions taken<\/strong><\/p>\n Members may wish to review the following incidents:<\/p>\n What happened A stand-by diver on a light daughtercraft (LDC) was nearly hit by a flying block and tackle, which was thrown towards him by an unplanned release of tension […]<\/p>\n","protected":false},"template":"","tags":[],"safety_event_tag":[97,108],"class_list":["post-13796","safety-events","type-safety-events","status-publish","hentry"],"acf":[],"yoast_head":"\n\n
\n
\n
\n