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

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

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 6114
Robbery at anchor - vessel security - DEV imca
Skip to content

Robbery at anchor – vessel security

What happened?

A members’ vessel was robbed whilst at anchor. The incident occurred in Indonesian waters, in the hours of darkness, some three hours after anchoring. The duty officer, whilst on his rounds on the port side bridge wing, sighted a person on the poop deck. On being shouted at, the person tried to hide behind a ventilator.

The duty officer raised the alarm, alerting the Master and crew, and sent the duty AB down to check. While on the way down to the poop deck, the duty AB saw two more persons, armed with knives, who made threatening gestures to him. He immediately retreated back to the bridge.

On noticing that the crew were alerted and active, the intruders (5 in number) lowered some bags into boat, jumped overboard and escaped. A thorough search of the vessel was carried out for further unauthorised persons and for items lost. It was discovered that auxiliary engine spares to the value of around 12,000 USD, were missing. No crew were injured.

What were the causes?

Onboard investigation established that the intruders had boarded via the poop deck from a small boat, cut open the padlock securing the engine room entrance watertight door, and thus gained access to the engine room.

The incident was reported to concerned authorities. The Master and crew were aware of the risk of piracy in the waters through which the vessel was travelling and had implemented some counter-piracy measures. However, an effective deterrent – a deck piracy watch – had not been maintained.

What lessons were learned?

Our member recommended:

  • Pre-arrival security briefing should include anticipated threats and planning;
  • Vessel management should remain updated with world-wide maritime security concerns;
  • A deck piracy watch in locations known for piracy.

This is the first such security-based report passed to IMCA by members; there are no similar IMCA incidents to which members’ attention can be drawn.

Members are encouraged to submit incidents of this sort to IMCA in order to continue to raise awareness of vessel security.

Safety Event

Published: 2 October 2018
Download: IMCA SF 23/18

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 safetyreports@imca-int.com 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.