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":18703,"date":"2019-07-16T14:58:17","date_gmt":"2019-07-16T13:58:17","guid":{"rendered":"https:\/\/www.imca-int.com\/?post_type=alerts&p=18703"},"modified":"2019-07-16T14:58:17","modified_gmt":"2019-07-16T13:58:17","slug":"near-miss-dropped-magnet-during-dry-docking","status":"publish","type":"safety-events","link":"https:\/\/dev.imca-int.com\/blog\/safety-events\/near-miss-dropped-magnet-during-dry-docking\/","title":{"rendered":"Near miss: dropped magnet during dry docking"},"content":{"rendered":"
What happened?<\/strong><\/p>\n
There was a dropped object near miss incident involving a magnet which was used by subcontractors during hot work operations. The incident occurred during a dry docking. Part of the scope of work involved hot work, grinding and gouging, to be carried out from scaffolding put up against the ships funnel. As a dropped object prevention measure, the scaffolding had been partially enclosed on three sides, with the fourth side being against the funnel.<\/p>\n
During an inspection of ongoing work, it was noted that sparks were escaping the fire protection and it was requested that the gap in the protection was closed. It was at this time, while the fire protection was being adjusted, that an object fell from the scaffold to the dock; a drop of 32m. The object was later identified as being a magnet which had been used to hold fire protection against the ships funnel. There was no damage and no injuries.<\/p>\n
<\/p>\n
What went wrong? What were the causes?<\/strong><\/p>\n
\n
The worksite was directly above the dock and no barriers had been placed on the dock to prevent workers from gaining access to the area directly below the worksite;<\/li>\n
Sub-contractors were using magnets on site and at height without any secondary retention in place. This was not known to the vessel crew;<\/li>\n
The magnets in use had been engineered to allow fitting of eyelets for secondary retention, but the fitting of secondary retention eyelets had not been considered by the shipyard.<\/li>\n<\/ul>\nA magnet used to secure fire protection<\/figcaption><\/figure>\nThe dropped magnet – note hole for retention eyelet<\/figcaption><\/figure>\nSimilar magnet with secondary retention eyelet fitted<\/figcaption><\/figure>\n
What lessons learned <\/strong><\/p>\n
\n
Our member noted that there was anecdotal evidence that magnets are routinely used in shipyards for securing against the ship superstructure. This should be taken into account on future worksites;<\/li>\n
Ensure that all equipment being used at height is identified and suitable dropped object prevention controls are in place.<\/li>\n<\/ul>\n