Jump to Content

Cargo handling procedures

Issue number: MO-2015-005-SI-01
Who it affects: All owners and operators of offshore support vessels
Issue owner: DOF Management, Norway (DOF Management)
Operation affected: Marine: Shipboard operations
Background: Investigation Report 322-MO-2015-005
Date: 23 November 2016

Safety issue description

Skandi Pacific’s safety management system (SMS) procedures for cargo handling in adverse weather conditions were inadequate. Clearly defined weather limits when cargo handling operations could be undertaken and trigger points for suspending operations were not defined, including limits for excessive water on deck.

Proactive Action

Action organisation: DOF Management
Action number: MO-2015-005-NSA-003
Date: 23 November 2016
Action status: Closed

Following the accident, DOF management submitted a ‘safety flash’ to the offshore industry organisation, International Marine Contractors Association. The safety flash summarised key safety matters and the accident, allowing wider dissemination of lessons learned to the industry. The company also undertook to review the adverse weather working guideline and the cargo loading procedure to include cargo lashing arrangements, and risk assessment for securing cargo.

Subsequently, DOF Management advised the ATSB that the existing working in adverse weather procedure had been reviewed and updated. The procedure now includes weather limits related to specific wind speeds, sea state, tidal streams, visibility and vessel movement. The precautions to be taken are directly related to each of the trigger points. In addition, working parameters for vessels with open sterns include a trigger point in the event that water is shipped on deck over the stern. The master is to be informed, who is then required to have a risk assessment conducted.

   
Current issue status: Adequately addressed
Status justification:

The revised procedures for working in adverse weather and cargo handling, and the additional safety action taken has adequately addressed the safety issue.

 
Share this page Comment
Last update 23 November 2016