Skip to content Skip to footer

Who we are

Our website address is: https://shipip.com.

What personal data we collect and why we collect it

Comments

When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.

An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.

Media

If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.

Contact forms

Cookies

If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.

If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.

When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select "Remember Me", your login will persist for two weeks. If you log out of your account, the login cookies will be removed.

If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.

Embedded content from other websites

Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.

These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.

Analytics

Who we share your data with

How long we retain your data

If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.

For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.

What rights you have over your data

If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.

Where we send your data

Visitor comments may be checked through an automated spam detection service.

Your contact information

Additional information

How we protect your data

What data breach procedures we have in place

What third parties we receive data from

What automated decision making and/or profiling we do with user data

Industry regulatory disclosure requirements

Lessons to be learned from fatality during STS transfer

The incident happened at Kavkaz anchorage when Teal Bay was loading grain from Kavkaz V in a ship-to-ship transfer; Kavkaz V was at anchor with Teal Bay alongside.

A mooring line was being used to pull Teal Bay forward and was therefore under significant tension, but the STS transfer had created a difference in height (freeboard) between the two vessels. The vessels’ freeboards were similar when loading start, but as it progressed Teal Bay dropped lower relative to Kavkaz V creating an upward lead angle on the mooring line.

The fatal incident happened around 80% through the loading of the vessel when the vessel had to be moved forward to continue the loading operation.

KavKaz V’s deck was around 8 m higher than Teal Bay’s, and as the line had been secured through an open fairlead roller it sprang from the roller and struck the chief officer as it snapped tight. The Chief Officer was standing in a hazardous area close to the mooring line, and was struck in the head, falling unconscious to the deck.

After some delay in securing evacuation for the chief officer, he was pronounced dead by a paramedic at 0045 aboard a tugboat in the port of Taman.

“A postmortem examination determined he had sufered closed blunt force trauma to the head, traumatic swelling of the brain and a brain haemorrhage,” said the report.

“Chief Officer, Yuriy Maslov, was a 54-year-old experienced seafarer and had been with the company for over 20 years. He was wearing shorts, a T-shirt, safety boots, gloves and a hard hat.”

In its conclusions, MAIB said that the number of crew assigned to carry out the warping operation was insufficient and almost certainly influenced the Chief Officer’s decision, which went unchallenged, to stand in a hazardous area.  Ahead of the incident, the master had decided not to wake the of watch crew to assist, as this would disrupt their hours of rest.

MAIB also found that crew unfamiliarity with STS transfers and a lack of available time led to insufficient planning for the mooring and warping.

“Despite the crew’s efforts and the assistance of the tug Dobrynya, it took over 2 hours for the casualty to be seen by a medical professional. Given the severity of his injuries, it is unknown whether the delays in the Chief Officer receiving medical attention had any bearing on his death; however, the lack of co-ordination by the parties involved in organising the medical response created delays that lessened his chances of survival,” said the report.

MAIB has recommended that Isle of Man Ship Registry distribute the lessons from the report to owners and operators on its register. The UK Maritime and Coastguard Agency is set to issue guidance on the use of open fairleads.

Teal Bay’s management company V.Ships Ship Management (India) has taken a number of steps, including:

• Commissioned and overseen the production of a human factors analysis of the accident.

• Sent a fleetwide safety alert to highlight the safety issues raised by this accident.

• Conducted additional safety training with Teal Bay’s crew, including modules on safe mooring operations and STS.

• Issued a work instruction setting out a plan to remove open fairleads from the fleet and replace them with a closed type or universal type of fairlead and directed managers to make allowance for this within the dry dock specification for vessels scheduled to dry dock.

• Reviewed SMS procedures to include guidance on STS operations for bulk carriers with a specific bulk carrier checklist and ofce involvement in the STS approval process.

• Amended the company risk assessments to include a generic risk assessment for bulk carrier STS operations.

• Amended the SMS to include detailed guidance on warping operations.

Source: https://www.seatrade-maritime.com/regulation/lessons-be-learned-fatality-during-sts-transfer