Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the 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 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-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 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-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 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-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 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-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 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-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 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-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 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the imca-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 6121

Warning: Cannot modify header information - headers already sent by (output started at /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php:6121) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php:6121) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php:6121) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php:6121) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php:6121) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php:6121) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php:6121) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/rest-api/class-wp-rest-server.php on line 1896

Warning: Cannot modify header information - headers already sent by (output started at /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php:6121) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/rest-api/class-wp-rest-server.php on line 1896
{"id":17156,"date":"2019-04-05T08:43:20","date_gmt":"2019-04-05T07:43:20","guid":{"rendered":"https:\/\/www.imca-int.com\/?post_type=alerts&p=17156"},"modified":"2019-04-05T08:43:20","modified_gmt":"2019-04-05T07:43:20","slug":"near-miss-crewman-struck-on-head-by-crane-hook-marine-safety-forum","status":"publish","type":"safety-events","link":"https:\/\/dev.imca-int.com\/blog\/safety-events\/near-miss-crewman-struck-on-head-by-crane-hook-marine-safety-forum\/","title":{"rendered":"Near miss: crewman struck on head by crane hook (Marine Safety Forum)"},"content":{"rendered":"

The Marine Safety Forum (MSF) has published Safety Alert 18-26<\/a>, in which an AB was struck on the head by a crane hook during routine deck cargo transfer operations.<\/p>\n

A platform supply vessel (PSV) was carrying out the routine deck cargo operations at an offshore installation.  Two crew on deck were routinely hooking on and off cargo as it was being discharged and back loaded to and from the vessel.  Shift change was due, so after discharge of the cargo carrying unit (CCU), the crew moved to the forward end of the cargo deck for shift change.  However, before departing from deck, there was no routine check of the next CCU to ensure it was ready for discharge; this critical step was overlooked.<\/p>\n

The crane was landing the previous CCU on the installation deck whilst the crew completed their handover on the PSV’s deck.  The oncoming crew were waiting in the ‘safe area’ for the crane hook to return to vessel in order to attach the next CCU.  As the crane hook was being lowered, the new crew noticed that the lifting bridle was snagged; their attention was immediately drawn away from the approaching crane hook as they freed the lifting bridle.  This took only a matter of seconds; they then stood back to look up for the crane hook, which had continued its descent to the deck unchecked by the crane operator.<\/p>\n

As one of the crew looked up at the crane hook, it struck his hard hat before continuing its descent to the vessel deck.  Luckily, his hard hat did the job and he was uninjured.<\/p>\n

What went wrong?  What were the causes? <\/strong><\/p>\n

Several critical factors were identified from this incident:<\/p>\n