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

Real Life Incident: Two Anchors Are Not Always Enough

A loaded general cargo vessel had left berth but went to anchor in the river for repairs before proceeding to sea. The pilot showed the Master and Chief Officer his intended anchoring position on the ship’s ECDIS and informed them of his plan to use both anchors, establishing a ‘good spread’ between the port and starboard anchor chains. There were thunderstorms forecast for that afternoon that could bring strong and gusty winds to the area and river water levels were high, causing an outflow current of about four to five knots.

The starboard anchor was let go (position 1 in the diagram). The vessel then manoeuvred to port and, five minutes later, the port anchor was also let go (position 2). The starboard anchor was heaved to four shackles on deck and the port to three shackles in the water. About 15 minutes after the port anchor was let go the pilot informed the Master that the anchoring was finished. The pilot was satisfied with the situation (position 3), but recommended keeping the engine on short standby due to the inclement weather that was due to arrive and the strong river current. Another issue was that the vessel’s stern was only 150 metres from the bow of another ship anchored astern (shown in red in the diagram).

The pilot left the vessel a few minutes later. Unknown to him, the vessel was not in a stable condition and continued to yaw between the anchors.

Even though the vessel astern was only 150 metres away, the OOW set the anchor watch alarm on the ECDIS for a radius of 180 metres. Soon, the vessel was moving astern at a speed over the bottom of about 1.8 knots. At 1602 there was a watch handover; the relieving officer, unfamiliar with the vessel’s ECDIS because he was new, asked why the ship was not in the middle of the ECDIS ‘anchor watch’ circle.

The officer being relieved offered to help familiarise the relieving officer with the ECDIS, but they did not further discuss the vessel’s position at anchor as they went on to other business. About 10 minutes later, the OOW aboard the vessel anchored astern called on VHF radio giving a warning – he had noticed that the general cargo vessel was moving astern toward his vessel.

At 1639, the OOW became aware that they were now too close to the other anchored vessel. He contacted the engine room and engine control was received on the bridge nine minutes later. The Master began using full ahead engine, along with the bow thruster and rudder, to reduce the swing and bring the ship ahead. By this point, the ship was unable to turn to starboard away from the other anchored ship. At 1655, with the first vessel now broadside to the current and pushing on the bow of the other anchored vessel, both vessels were now dragging anchor.

Tugs were requested to help hold and stabilise the vessel. The first tug arrived on scene about 30 minutes later. A further 30 minutes passed before pilots arrived on both vessels, but more tugs were needed to extricate the vessels from their position. Although these arrived some time later, the vessel nonetheless hit a shore dock at a speed of 6 knots before its bow grounded on the river bank. Damage to the two vessels and the dock were estimated at $16.9 million.

Source: https://www.marineinsight.com/case-studies/real-life-incident-two-anchors-are-not-always-enough/