• Learn more about our technology and shipping tools andstart your free trial now
  • Products
  • Vessels
  • Ports
  • News
  • About
    • About
  • Community
  • Log in
    • English
    • German
  • Log in
    EN / DE

News

  • Product updates
  • News
  • Vessel news
  • Port news

Category

Accident/Casualty42183Misc. for Ports and Vessels37965Scrapped/Beached/Broken Up22589Sold/Decommissioned8538Charter Changed6734Pirate attack2021

CUAUHTEMOC BE 01

Casualty

The 'Cuauhtémoc' has formally begun its repair phase at the Brooklyn Naval Shipyard. Since the weekend of June 8/9, security personnel from the GMD company, which manages the shipyard, have confirmed the start of work. Access to the area remains restricted to the public. The repairs could take one to two months, depending on the extent of the ship's internal damage. The Mexican government will assume all costs, including the occupation of the shipyard and the necessary repair work. The manoever to move the vessel from Pier 36 in Manhattan to the Brooklyn shipyard took three weeks of preparation and sought to prevent any additional incidents, working closely with the ship's captain and crew, marine inspectors, and experts in tall ships to ensure a safe operation. The move on June 6 was supervised by two helicopters that monitored the operation from 7:00 a.m. The transfer lasted approximately 75 minutes, during which ferry operations on the East River were suspended to ensure safety. In parallel with the repairs, the investigation into the causes of the May 17 accident remains active. The U.S. National Transportation Safety Board (NTSB) will coordinate additional oversight at the shipyard. The NTSB has reported that the investigation was progressing. The causes of the apparent mechanical failure that prevented the ship from reversing the inertia of the tide and wind, leading it to allide with the bridge, were being analyzed. The manner in which the ship was maneuvered by both the pilots and the New York Harbor pilot, as well as by personnel from the Navy, is also being investigated. Additionally, the assistance operations the vessel should have received from the company operating the only tug that assisted it at the time of the incident are being reviewed. The NTSB is expected to hold another press conference in approximately a week and a half to present a preliminary report on the causes of the accident. However, the full investigation and final recommendations were expected in approximately one year. Report with photo: https://www.meganoticias.mx/index.php/tuxpan/noticia/inicia-reparacion-del-buque-cuauhtemoc/630906

Timsen
2025-06-10

CANARIAS EXPRESS

Casualty

The 'Canarias Express', en route from Santa Cruz de Tenerife to Arrecife, Lanzarote, suffered an engine breakdown and went adrift north of Isla de Lobos between Lanzarote and Fuerteventura on June 10, 2025 (Lat. 28.8017 Lng. -13.8350), approaching it dangerously. The vessel is currently accompanied by the SAR vessel 'Guardamar Polinmia' (IMO: 9541679) from Arrecife, which was notified at 7.49 a.m. (Canary Islands time) and the tug 'VB Achaman' (IMO: 8615617), based in Puerto del Rosario, was heading to the casualty at full speed. The weather on scene was relatively calm, The vessel was not carrying dangerous goods,

Timsen
2025-06-10

BARCAROLE

Misc. for ports and Vessels

Israel has expelled the 12 activists from the Gaza solidarity ship 'Barcarole', which the army intercepted onon the morning of June 9 around 200 kilometers from the Gaza Strip's coast in international waters. They have arrived at Ben Gurion Airport to leave Israel and return to their home countries and scheduled to leave on June 10. The activists were met at the airport by consuls from their respective home countries. On board the "Madleen" were people from Germany, France, the Netherlands, Spain, Turkey, and Brazil. Eight of them refused to sign the necessary expulsion documents. Among them was French MEP Rima Hassan. In addition to Thunberg, three other activists signed the exit forms against this and were told to return to their home countries. Those who refused to sign the expulsion documents will be brought before a judicial authority in accordance with Israeli law to have their expulsion approved. The ship arrived in the port city of Ashdod on the evening of June 9. Reports with photos: https://www.westernslopenow.com/news/ap-israel-says-greta-thunberg-is-being-deported-after-gaza-bound-ship-she-was-on-was-seized/ https://www.abc.net.au/news/2025-06-10/greta-thunberg-boat-interception-latest-doran/105397110 https://edition.cnn.com/2025/06/08/middleeast/freedom-flotilla-gaza-aid-ship-thunberg-intl-hnk

Timsen
2025-06-10

LAUGA

Misc. for ports and Vessels

The cargo m/v 'HAV Dolphin' (IMO: 9073854) with a full Russian crew that was stopped at the Volkerak locks near Willemstad in mid-May, being suspected of having deployed drones over European territory. German investigation services had warned the Coast Guard a few hours earlier that the ship had behaved suspiciously off the coast of Kiel in early May, exactly at the time that drones were spotted there. The ship was inspected by a team from Customs, the Royal Marechaussee and the police, but no drones were found. On the night June 17 May, 2025, drones appeared again, this time above the German patrol ship 'Potsdam', which at that time shadowed the Russian 'Lauga' in the German Exclusive Economic Zone (EEZ),. The drones followed the patrol ship for three hours, until just before Dutch waters. The German police were unable to determine whether the drones came from the 'Lauga', but asked the customs in Belgium, where the ship was en route, to inspect it. No drones were found there either. German investigation services have seen an increase in drone sightings over critical infrastructure, such as ports, chemical parks and military installations, for years. The German authorities have informed European investigative bodies of the events. The ships have been closely monitored since then. Both cargo ships were showing a striking behaviour. The ''HAV Dolphin' has spent a month in the port of Kaliningrad, Russia, near a naval base, and temporarily disabled the mandatory AIS during its journey. The 'Lauga' also did this during its journey across the North Sea. In addition, the cargo ship previously had visited the Russian naval base in Syria, which indicates possible ties with the Russian Ministry of Defence. The 'HAV Dolphin' left Rotterdam on May 16 and berthed in Papenburg on June 3. The 'Lauga' arrived in St. Petersburg, Russia, on June 4.

Timsen
2025-06-10

BERGE FUJI

Sold/Decommissioned

sold to Chittagong Breakers 440 USD/TO

BerndU
2025-06-10

MESHKA

Casualty

The 'Meshka' has been refloated by the tugs 'Svitzer Thor' (IMO: 9548366) and ' Frigga' (IMO: 9175250) on the morning of June 7 at around 8 a.m. The salvage began at 3 a.m. by emptying the ballast tanks. Before that, the two tugs had been connected to the 'Meshka's stern and bow. At 8.30 a.m., the vessel was floating freely and, after assistance from the tugs, was able to proceed to Landskrona under its own power. Pilots from the Swedish Maritime Administration and officials from the Coast Guard were on board during the salvage. The salvage work and the voyage to the harbour took just over eight hours in good weather conditions and were supervised by the Coast Guard. The bulk carrier was moored at the Öresund Drydocks Ship Repair Yard in Landskrona for investigations and inspections. Report with photos: https://www.kustbevakningen.se/nyheter/bargningen-av-meshka-avslutad/

Timsen
2025-06-10

ARGYLE

Casualty

On June 8, the 'Argyle', serving on the route Wemyss Bay-Rothesay, suffered technical issue with the aft main engine, which needed to be investigated. As a consequence, the scheduled departures from Rothesay at 1:00 p.m., 3:00 p.m. and05:00 p.m. and fromtWemyss Bay at 2:05 p.m., 4:05 p.m. and 6:05 p.m. had to be cancelled. After the issue was resolved and folliowing a sea trial, the vessel finally resumed its service with the scheduled 7:00 p.m. sailing departing from Rothesay.

Timsen
2025-06-10

PEGAL

Casualty

The 'Pegal', with two crew members on board, suffered a leak six nautical miles southwest of Corrubedo in Ribeira. on June 9, 2025. The two sailors, José María Santiago Franco, from Ribeira, and Abel García Lestón, from Muros, issued a distress signal, abandoned the fishing vessel and wenr aboard a raft. AT 9.30 a.m. they were rescued by another f/v, the 'Día de Reyes' (MMSI: 224202860). The SAR boat 'Salvamar Sargadelos' was mobilized by the CCS of Salvamento Marítimo to take on board the castaways and bring them ashore.According to Maritime Rescue, they are in good health and did not require medical assistance. After the fishing vessel sank, the SAR boat remained in the area to check for any floating debris that could pose a danger to navigation. No objects were found floating in the area after the sinking.The Sasemar 308 aircraft was diverted to inspect the area and monitor the environmental situation. The operation was coordinated by the Fisterra Maritime Rescue Center, under the direction of the Villagarcía Maritime Captaincy. Report with photos: https://www.elcorreogallego.es/barbanza-muros-noia/2025/06/09/rescatados-ilesos-marineros-hundirse-pesquero-118401722.html

Timsen
2025-06-10

PANNENKOEKENBOOT

Casualty

On the late afternoon of June 8, 2025, the 'Pannekoekenboot'' suffered engine trouble on the IJ got out of control and was in danger of alliding with the Jan Schaefer Bridge in Amsterdam. The master requested tut assistance. Another passenger ship, the 'De Jordaan', came to the rescue before the harbour service arrived, and took the ship in tow. The manoever was not easy due to the strong wind, but the ship eventually managed to establish a towing connection. A municipal boat also helped out: The 'Pannekoekenboot' was safely moored at the head of Java Island. The municipal boat and a police have also moored alongside. Later the casualty was taken to its own berth in Noord by a push boat. A mechanic arrived around 8:30 p.m. to see if the main engine could be repaired quickly. Report with photo and video: https://www.nhnieuws.nl/app/nieuws/349362/pannenkoekenboot-op-het-ij-opeens-stuurloos-had-heel-anders-kunnen-aflopen

Timsen
2025-06-10

DHARMA KARTIKA 2

Casualty

The 'Dharma Kartika II' was in collision with the barge 'Bomas Galante' on June 5, 2025, at 7.48 a.m. WITA, while sailing out of the Banjarmasin Estuary en route to Surabaya, in pos. 03°36.800' S 114°28.800' E. The 'Dharma Kartika II'. under the guidance of pilot Capt. Efendi Sutiono (ID No. 254), communicated withthe tugs 'MBP 3208' and 'Bomas Galante', requesting them to shift to the 2 West track (approximately 36 meters from the AS track. Despite the captain having reduced the vessel's speed, the 'MBP 3208' remained too close in the 1 West track (18 meters), causing its barge to veer into the 1 East track. To avoid a collision, the captain of the 'Dharma Kartika II' steered the vessel to the 3 East track using slow speed on the port engine and half speed on the starboard engine. However, at around 07:57 a.m. WITA, the bow of the vessel brushed against the eastern embankment and ricocheted westward, approaching the position of the Bomas Galante barge, which was approximately 370 meters from the 'MBP 3208'. The limited distance left no room for evasive maneuvers, and although the captain attempted to stop and reverse the engines to reduce the impact, the collision could not be avoided. After clearing from the barge, the vessel proceeded to the OB Taboneo anchorage area and dropped anchor at 08:46 a.m. for an inspection, which revealed damage to the hull above the waterline, specifically in the bow visor area. Despite the minor damage, the vessel was deemed seaworthy and safe to continue its voyage to Surabaya for further repairs. Report with photos: https://hubla.dephub.go.id/Indonesianmaritimesafetyinformation/page/news/read/25398/km-dharma-kartika-ii-mengalami-tubrukan-dengan-tongkang-bomas-galante-di-muara-banjarmasin-km-dharma-kartika-ii-collides-with-bomas-galante-barge-in-banjarmasin-estuary

Timsen
2025-06-10

HAV DOLPHIN

Misc. for ports and Vessels

The 'HAV Dolphin' with a full Russian crew that was stopped at the Volkerak locks near Willemstad in mid-May, being suspected of having deployed drones over European territory. German investigation services had warned the Coast Guard a few hours earlier that the ship had behaved suspiciously off the coast of Kiel in early May, exactly at the time that drones were spotted there. The ship was inspected by a team from Customs, the Royal Marechaussee and the police, but no drones were found. On the night June 17 May, 2025, drones appeared again, this time above the German patrol ship 'Potsdam', which at that time shadowed the Russian freighter 'Lauga' (IMO: 9111060) in the German Exclusive Economic Zone (EEZ),. The drones followed the patrol ship for three hours, until just before Dutch waters. The German police were unable to determine whether the drones came from the 'Lauga', but asked the customs in Belgium, where the ship was en route, to inspect it. No drones were found there either. German investigation services have seen an increase in drone sightings over critical infrastructure, such as ports, chemical parks and military installations, for years. The German authorities have informed European investigative bodies of the events. The ships have been closely monitored since then. Both cargo ships were showing a striking behaviour. The ''HAV Dolphin' has spent a month in the port of Kaliningrad, Russia, near a naval base, and temporarily disabled the mandatory AIS during its journey. The 'Lauga' also did this during its journey across the North Sea. In addition, the cargo ship previously had visited the Russian naval base in Syria, which indicates possible ties with the Russian Ministry of Defence. The 'HAV Dolphin' left Rotterdam on May 16 and berthed in Papenburg on June 3. The 'Lauga' berthed in St. Petersburg, Russia, on June 4.

Timsen
2025-06-10

MSC ANSHIKA VI

Casualty

On April 4, 2025, the 'Marus' (IMO: 9110559), enroute from Rotterdam, alllided with the 'MSC Anshikia IV', which was anchored off Ramsgate, enroute from Abidjan. The freighter suffered severe bow damage and entered the Emder Shipyard for repairs on April 26, where it remained stationary as of May 5. The 'MSC Anshika VI' entered the drydock of the EDR Shipyard in Antwerp on April 26 too and remained stationary as of May 10 Photos: x.com/Ht9bPSU3cN https://www.shipspotting.com/photos/3848220?navList=gallery&category=39&page=1&viewType=normal&sortBy=newest https://www.shipspotting.com/photos/3848221?navList=gallery&category=39&page=1&viewType=normal&sortBy=newest https://www.shipspotting.com/photos/3848222?navList=gallery&category=39&page=1&viewType=normal&sortBy=newest

Timsen
2025-06-10

CGC ROBERT WARD

Casualty

The 'Robert Ward (WPC-1130)' interdicted seven migrants aboard a 20-foot white center console boat, approximately eight miles south of Point Loma, on June 9, 2025. At 8:42 a.m. the Coast Guard Sector San Diego watchstanders at the Joint Harbor Operations Center directed the launch of a boarding team from the Coast Guard Cutter to interdict the vessel two miles south of the maritime boundary line heading north. The boarding team was able to interdict the Chaparral boat without any use of force and found seven people aboard the vessel, all claiming Mexican nationality. They were transferred to the custody of the U.S. Border Patrol at Ballast Point on the afternoon. Report with photos: https://www.news.uscg.mil/Press-Releases/Article/4210969/coast-guard-interdicts-7-aliens-off-the-coast-of-point-loma-calif/

Timsen
2025-06-10

GLEN SANNOX

Casualty

The 'Glen Sannox', serving on the route Troon-Brodick, suffered a technical issue with the passenger gangway on June 5, which was currently unavailable. As a result foot passengers were required to embark and disembark via the car deck at Troon. This meant a delay for foot passengers disembarking the vessel. Bus connections in Troon have been made aware and were awaiting passengers. Contractors will be attending on June 9, after service, to look at carrying out a temporary repair to the gangway, with plans for a permanent fix made a priority. Due to an issue with the 'Glen Sannox' starboard main engine the sane foremidday, the vessel had to operate at reduced speed. The issue has since been resolved, and the vessel was operating at full speed again, but arrival in to Brodick was at risk to be delayed. On June 8, the issue has been resolved, and traffic was loaded for the 12:40 p.m. sailing departing Troon.

Timsen
2025-06-10

PIANA

Casualty

A fire broke out on a trailer aboard the 'Piana' on the morning of June 7, 2025, at berth 70 of the Arenc ferry terminal in the port of Marseille, just as the ship's passengers from Ajaccio had finished disembarking. The attending fire fighters of the Marseille fire brigade deployed one of their two fireboats in addition to a tug from Boluda, which cooled the hull from outside. The fire could be brought under control quickly, and no injuries nor pollution were reported, but the ship had to cancel its departure for Corsica. The ferry resumed its rotations on June 9 and headed to Ajaccio. Report with photo: https://lemarin.ouest-france.fr/shipping/le-piana-de-la-meridionale-reste-a-quai-a-marseille-apres-lincendie-dune-remorque-9aec3f10-43b2-11f0-b321-9f4333574570

Timsen
2025-06-10

NADIR

Casualty

Italian authorities detained th "Nadir" in the port of Lampedusa on Jujne 9. The vessel, belonging to the German non-governmental organization (NGO) Resqship, had previously rescued 112 people from an unseaworthy wooden boat in the Mediterranean. The rescue took place during the night of June 5-6. After the Italian authorities designated Lampedusa as a safe port for the "Nadir," the sailing vessel was detained for 20 days upon its arrival on June 8. The Coast guard also launched an investigation. Resqship was accused of ailing to promptly inform the relevant authorities in Tunisia and Libya and failing to follow instructions regarding the designated safe harbour. The NGO denies the allegations: "In fact, the Nadir followed the instructions of the Italian authorities and repeatedly contacted the MRCCs in Tunisia and Libya – without receiving a response, The allegations also ignore the fact that neither Libya nor Tunisia can be considered a safe haven for people on the move due to serious and well-documented human rights violations." During the voyage to Lampedusa, the "Nadir" was also requested to hand over some of the rescued people to an Italian patrol vessel. Since no written confirmation of this order was provided, and the "Nadir's" crew did not want to separate families, they refused this handover for safety reasons. Resqship condemned the detention of the civilian sailing vessel and described it as illegal: "This detention is not about right or wrong, but about politics. The allegations are completely unfounded, and the decision to detain the Nadir is arbitrary. Civilian sea rescue is being deliberately obstructed in order to push a political agenda."

Timsen
2025-06-10

LOMAIVITI PRINCESS 2

Casualty

After the 'Lomaiviti Princess 2' capsized and partially sank in Walu Bay at Suva Harbour on the night of June 1, while it was towed away from the jetty without proper checking and monitoring, The Fiji authorities have placed booms around the vessel. However, a diesel fuel pollution could not be totally contained. A visible sheen of diesel fuel could be seen in Suva harbour. Oil dispersants were applied to minimise damage and reduce harm to the surrounding marine ecosystem. The authorities have issued a coastal warning and placed yellow buoys to indicate the boundary of the oil pollution. The ferry had been moored at the jetty since 2019 and had been used as a dumping ground. The Minister for Public Works, Meteorological Services and Transport, Ro Filipe Tuisawau, has ordered an investigation on the sinking. The Government was actively undertaking all necessary measures to contain the oil spill and mitigate any environmental damage. The next steps in the response operation include plans to refloat and reposition the LP II to clear the navigation channel, followed by the removal of the wreck. Further actions, including the possible referral to the National Disaster Management Office (NDMO), will be considered as the situation evolves. Report with photo: https://www.fijitimes.com.fj/minister-slams-sheer-recklessness-in-lomaiviti-princess-ii-sinking/

Timsen
2025-06-10

PO YANG HU

Sold/Decommissioned

Sold to Breakers

BerndU
2025-06-10

MARUS

Casualty

On April 4, 2025, the 'Marus' alllided with the 'MSC Anshikia IV' (IMO: 925848), which was anchored off Ramsgate, enroute from Abidjan. The freighter suffered severe damage to the foreship and the bulbous bow. The vessel entered the Emder Shipyard for repairs on April 26, where it remained stationary as of May 10. The 'Anshika VI' entered the drydock of the EDR Shipyard in Antwerp on April 26 too and remained stationary as of May 5. Photos: x.com/Ht9bPSU3cN https://www.shipspotting.com/photos/3848220?navList=gallery&category=39&page=1&viewType=normal&sortBy=newest https://www.shipspotting.com/photos/3848221?navList=gallery&category=39&page=1&viewType=normal&sortBy=newest https://www.shipspotting.com/photos/3848222?navList=gallery&category=39&page=1&viewType=normal&sortBy=newest

Timsen
2025-06-10

MORNING MIDAS

Casualty

On the afternoon of June 9, the first salvage crews arrived at the still burning 'Morning Midas' approximately 350 kilometers south of Adak. The salvors were on board the tug 'Gretchen Dunlap' (IMO: 9804021) of the Dunlap Towning Company from the Seattle area and have begun assessing the overall situation. Two other vessels are expected to arrive on site on various dates within the next two weeks. One of those vessels is a firefighting tug. The British ship manager Zodiac Maritime appointed the American salvage and firefighting specialist Resolve Maritime on June 5 to ‘respond’ to the fire, the cause of which was still unknown, According to the ship’s manager, the first smoke was spotted on a deck with electric vehicles. Of the total of 3048 vehicles on the carrier, 70 were fully electric, 681 hybrid. As of June 8, the fire has spread across several decks. The bow, side and stern showed extensive heat damage from the waterline to the upper deck on the port side. Black smoke clouds were visible from the front of the ship on June 9. The crew of a HC-130J Super Hercules from the Kodiak Air Base observed no signs of pollution. On June 5, a narrow trail of at least a few hundred meters length could be seen on the water from the bow of the 'Morning Midas'. The ship is carrying 1,530 tons of very low sulfur fuel oil (VLSFO). The Coast Guard was closely monitoring the weather conditions to support the relief effort. As of Junde 9 at 12:20 p.m. LT, winds increased to 45-50 knots. The Coast Guard was monitoring the ship's position and condition through regular overflights, information from on-site salvage crews, and drift analyses, were performed in conjunction with information from the National Oceanic and Atmospheric Administration's (NOAA) Office of Response and Restoration. Report with photos;: https://www.news.uscg.mil/Press-Releases/Article/4211030/update-2-coast-guard-responds-to-vessel-fire-offshore-adak-alaska/

Timsen
2025-06-10
  • «
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • »

Location + Contact

vesseltracker.com GmbH
Rödingsmarkt 20,
20459 Hamburg, Germany

+49-(0)40-970786-10
info@vesseltracker.com

About

Privacy NoticeGeneral Terms and ConditionsTerms of useImprintContact

Explore

ProductsVesselsPortsNewsAboutCommunity

Social

 

© vesseltracker 

Log in

Lost password? Reset

Don't have an account? Register

Phishing Attack Warning

There are some links in social media, promising a free trial for vesseltracker.com. The linked website is being used for phishing and attempting to collect login data from vesseltracker users.

In order to keep you safe:

  • Please make sure that you only enter your login data on the real websites www.vesseltracker.com or cockpit.vesseltracker.com
  • Make sure your browser shows a green lock in the address bar, indicating that it is a secure connection
  • Should you have entered login data somewhere else already, please change your password on the real website. To do this, please log in at www.vesseltracker.com, click on your username and then on "My vesseltracker". There you will find the option to change the password