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

NTSB: Poor BRM Caused Allision With Uncharted Offshore Platform

The NTSB has released its final report on the allision of a bulker with a decommissioned offshore platform off the coast of Louisiana last year. Its investigators determined that poor bridge resource management and a charting error were the root causes of the casualty.

On Jan. 7, 2021, the bulker Ocean Princess struck the oil and gas platform SP-83A some 24 miles south of Pilottown, Louisiana. No pollution or injuries were reported, and damage to the vessel and platform came to about $1.5 million.

The Ocean Princess offloaded a cargo of ore and steel in New Orleans in late December. On January 6, she was drifting in the Gulf of Mexico before heading back up river to load a cargo of grain. The master planned to drift through the night with the engine on 15-minute standby, keeping clear of traffic and the three platforms located in the area.

In order to give the crewmembers some rest time after a long day of cleaning cargo holds, the master scheduled himself on the bridge, joining the second officer. The vessel was drifting at about 2-3 knots in a northerly direction, with on and off rain showers periodically limiting visibility.

As the watch went on into the early hours of January 7, the master and second officer worked on administrative tasks on the bridge. At about 0100 hours, the vessel drifted towards a fairway, and they called the engine room to prepare to maneuver. With the master at the helm, they headed away from the fairway at a slow bell. At 0113, as he maneuvered away, the master saw a dim yellow light and checked the radar, which was set at a range of about 1.5-3 miles. The second officer had a look and confirmed that the contact was a platform, but could not determine the range visually. It looked like an ENC-charted platform some 5-6 miles away, and they concluded that it was not a hazard.

They were mistaken, and the master only fully appreciated the risk about 40 seconds before contact. Last-minute maneuvers were not successful and the bulker allided with the platform at four knots. The starboard anchor lodged in the platform structure, and the bulker swung on the anchor chain until morning when it could be safely cut free.

Ocean Princess’ trackline in the hours leading up to the allision (NTSB)

The master and second officer told NTSB that they never saw SP-83A on the radar. After the contact, they found that the platform was properly marked on the paper chart (an Admiralty product) – but SP-83A did not appear on their ECDIS ENC (a NOAA product).

NTSB verified that platform SP-83A was not charted on the official U.S. charts that fed Ocean Princess’ ECDIS. It had been charted correctly at platform commissioning in 1990 but was removed from the NOAA charts in 2010 for unknown reasons. Its absence went unnoticed and uncorrected until the allision. (After the accident, NOAA added it back in.)

A photo of the British Admiralty chart 3857 (left) and ECDIS screenshot from the Ocean Princess fed by NOAA ENCs (right), which were up to date at the time of the casualty. The British Admiralty chart shows SP-83A, but the ECDIS image shows nothing at that position. (NTSB)

NTSB determined that poor BRM was the probable cause of the casualty, since the bridge team noticed the platform’s lights 10 minutes in advance but failed to take timely and effective action. The platform’s absence from the ENC was a contributing factor.

“Technology, such as an ECDIS, can result in operator overreliance and overconfidence that degrades sound navigation practices and negatively affects situational awareness,” advised NTSB. “When identifying hazards, bridge teams should avoid overreliance on a single data source.”

Source: https://www.maritime-executive.com/article/ntsb-poor-brm-caused-allision-with-uncharted-offshore-platform

 

CREWEXPRESS STCW REST HOURS SOFTWARE - Paris and Tokyo MoU have announced that they will jointly launch a new Concentrated Inspection Campaign (CIC) on Standards of Training, Certification and Watchkeeping for Seafarers (STCW) from 1st September 2022 to 30th November 2022