Near miss – diving operations while alongside
What happened?
A vessel main engine was started while the divers were in the water, and the engine was immediately shut down again by the bridge. The diver was able to exit the water and was unhurt in the incident. The incident occurred during diving operations in a dockyard to remove debris from a bow thruster.
What went wrong?
- Engine room to bridge communications procedures were not followed. The engineers started the engine without consulting the bridge;
- There was a failure to follow the diving permit to work (PTW) procedures;
- There was a failure to implement lockout/tagout (LOTO) procedure;
- There was no risk assessment conducted.
What actions were taken? What lessons were learnt?
- Only the vessel Master should have the authority to start the vessel’s engines;
- Sometimes, isolation tags (LOTO) are not enough, and physical isolations and barriers should be put in in place;
- Our member recommended the following specific actions:
- before divers enter the water, all subsea equipment should be physically isolated including the auxiliary engines and HVAC system
- lifting operations on the main deck are to be stopped while divers are in the water
- control of work documentation to be completed in full before any tasks are started, including any associated documentation from the diving teams
- do not sign off on the control of work unless you have physically checked to ensure that the control measures listed in the risk assessment and associated PTW have been put in place
- any mistakes in any official logbook should be corrected by placing the mistake in brackets or a single line through it so that it is still eligible – scraping out and use of correction fluid not to be permitted.
Members may wish to refer to:
- Near-miss (HIPO): Engine started and running whilst crew member working on shaft generator
- Dropped object fell from crane – Poor communication/lack of awareness/control of work
- Lost time injury (LTI): Finger injury during main engine exhaust valve overhaul [root causes: no adequate system of communication and confirmation; no isolation (lockout/tagout); inadequate compliance – the risk in this routine, recurring task was seen as tolerable].
Safety Event
Published: 30 September 2019
Download: IMCA SF 23/19
IMCA Safety Flashes
Submit a Report
IMCA Safety Flashes summarise key safety matters and incidents, allowing lessons to be more easily learnt for the benefit of all. The effectiveness of the IMCA Safety Flash system depends on Members sharing information and so avoiding repeat incidents. Please consider adding [email protected] to your internal distribution list for safety alerts or manually submitting information on incidents you consider may be relevant. All information is anonymised or sanitised, as appropriate.
IMCA’s store terms and conditions (https://www.imca-int.com/legal-notices/terms/) apply to all downloads from IMCA’s website, including this document.
IMCA makes every effort to ensure the accuracy and reliability of the data contained in the documents it publishes, but IMCA shall not be liable for any guidance and/or recommendation and/or statement herein contained. The information contained in this document does not fulfil or replace any individual’s or Member's legal, regulatory or other duties or obligations in respect of their operations. Individuals and Members remain solely responsible for the safe, lawful and proper conduct of their operations.