• Learn more about our technology and shipping tools andstart your free trial now
  • Produkte
  • Schiffe
  • Häfen
  • News
  • Über
    • Über
  • Community
  • Log in
    • English
    • German
  • Log in
    EN / DE

News

  • Produkt updates
  • News
  • Schiffsmeldungen
  • Hafenmeldungen

Category

Accident/Casualty41688Misc. for Ports and Vessels37813Scrapped/Beached/Broken Up22520Sold/Decommissioned8500Charter Changed6733Pirate attack1986

ELYANA

Misc. for ports and Vessels

The sanctioned 'Elyana', which in the past is likely to have been involved with shipping arms to Syria, has just completed a northerly passage up the Red Sea and was located on May 3, 2025, underway and entering the southern end of the Suez Canal. As of the end of the day, the AIS signal showsed it has completed the Suez Canal transit. The vessel set off from the Bandar Abbas commercial port on April 18, making a port call in Jebel Ali, and departed on April 21. The vessel is not known to have made any port call en route and hence has taken much longer to complete the Jebel Ali to Suez leg of its voyage than would a normal commercial vessel. The 'Elyana' is listed by name and is subject to secondary sanctions by the U.S. Treasury’s Office of Foreign Assets Control (OFAC). It is linked to the Islamic Republic of Iran Shipping Lines (IRISL), which is sanctioned as an entity.Equipped with deck davit cranes, the 'Elyana' would be capable of off-loading cargo at unsophisticated ports en route, potentially being able to do so in Houthi-controlled areas of Yemen without using the closely monitored (and recently demolished) ports of Hodeida and Ras Isa. In June 2024, the 'Elyana' had unloaded cargo in Latakia, which had been taken on in Bandar Abbas. While closely aligned with the doomed Assad regime in Syria, the IRGC are known to have used Latakia as a hub for their arms imports destined for Hezbollah and the Syrian regime, using shipping to the port of Latakia and flying Boeing 747 cargo aircraft directly into Latakia International Airport.

Timsen
2025-05-13

RIX SAPPHIRE

Casualty

On April 16, 2025, the ' Rix Sapphire' way detained in Port Sutton Bridge with 16 deficiencies, two of which being refarded as seriouslyand gronds for a detention. The ship had attempted to enter the port on the afternoon tide on April 14, but ran aground in pos. 52°50,57.32 N 000°12,47.53 E. It was refloated and berthed in port on April 15 at 08.10hr a.m. to unload the cargo of bulk sand from Esbjerg, During the subsequent inspections, two ofcdefiencies were found, causing the detention: 1) Fire safety - Remote Means of control (Machinery spaces) Inoperative 2) Emergency systems - Emergency source of power - emergency generator Not as required The vessel was released again on April 24 and left the port enroute to Rostock, where it arrived on April 27.

Timsen
2025-05-12

CAPTAIN RALEIGH

Casualty

On the morning of May 9, 2025, the 'Captain Raleigh' sank in Grays Harbor off Westport, Washington. The captain contacted the U S Coast Guard that the vessel had sprung a leak, and requested assistance. The Coast Guard rescued three of the four crew members. The 'Captain Raleigh' continued to flood until it capsized and sank. One crew member was reported missing. The Coast Guard conducted a search for the crew member with an aircraft from Astoria, while divers searched the sunken vessel. The Coast Guard called off the search the following morning without finding the man. The Washington State authorities have also deployed a response team to manage the pollution. Ab oil pollution was spotted where the 'Captain Raleigh' sank, as diesel fuel was leaking out. Due to strong currents and the search operation, no booms were deployed to contain the spill. Authorities stated there were no traces of pollution along the shoreline .

Timsen
2025-05-12

SAMOA

Casualty

Thanks to the rapid response of various emergency services, the 'Samoa', 1000 tons of corn on board as cargo, was prevented from sinking in the outer harbour of Hansweert on the afternoon of Ma 12, 2025. While entering the harbour, the vessel had hit the stones. This caused a leak, and the vessel took on water. The crew managed to manoeuvre the vessel to the nearby fender under their own power and moor there. In the meantime, they raised the alarm, and the KNRM lifeboat 'Jan van Engelenburg', the Kruiningen fire brigade, the salvage company Polderman and Rijkswaterstaat were alerted. Because the vessel was moored next to the KNRM lifeboat, the volunteer rescuers, who were present quickly, were able to immediately start pumping the vessel out. The salvage company Polderman was also quickly on site to assist. A total of five pumps were deployed to keep the vessel afloat Fire engines from Kruiningen, the KNRM, the patrol boat 'RWS 79' of Rijkswaterstaat and the tug 'Bravo' jointly stabilised the ship in time. While the pumping was underway, divers were called in to carry out an emergency repair to the hull. After approximately two hours, the situation was under control and the KNRM deployment could be terminated. Reports with photos and video: https://www.knrm.nl/nieuws/knrm-reddingstation-hansweert/snelle-inzet-hulpdiensten-voorkomt-zinken-binnenvaartschip https://www.schuttevaer.nl/nieuws/actueel/2025/05/13/knrm-en-rijkswaterstaat-voorkomen-zinken-binnenvaartschip-hansweert/ https://www.hvzeeland.nl/nieuws/64054-lekkage-binnenvaartschip-in-voorhaven-bij-hansweert/?utm_source=hvzeeland&utm_medium=website&utm_campaign=home

Timsen
2025-05-12

HEBRIDEAN ISLES

Sold/Decommissioned

Sold to Breakers

BerndU
2025-05-11

NIRVANA

Sold/Decommissioned

Sold to Breakers

BerndU
2025-05-10

DAEWON

Sold/Decommissioned

Sold to Breakers

BerndU
2025-05-10

NEWNEW POLAR BEAR

Casualty

Wan Wenguo, aged 43, the Chinese captain of the 'NewNew Polar Bear' has been remanded in custody by a Hong Kong court over accusations that his vessel caused serious damage to the Balticconnector gas pipeline and a nearby telecoms cable while passing through the Gulf of Finland on Oct 8, 2023. He appeared in Eastern Court in Hong Kong on May 8, 2025, where he was charged with one count of criminal damage and two charges related to marine safety violations under Hong Kong laws The pipeline damage occurred within Finland’s economic zone, while the telecommunications cable was damaged in Estonia’s waters. The prosecutors in Hong Kong accused Wan of being responsible for the damage caused during the ship’s voyage between October and December 2023. They claimed thatr he failed to ensure the vessel had enough anchors and also failed to submit required daily reports to the ship’s owner.These actions have violated safety provisions under the Merchant Shipping (Safety) Ordinance, including regulations concerning navigational equipment and vessel maintenance. The court hearing concluded with the captain being remanded in custody, as he did not submit a bail application. The next court session has been scheduled for early July, giving the authorities more time to continue investigations. The case has drawn global attention due to the strategic importance of the damaged infrastructure and ongoing tensions in the Baltic Sea. The Finnish police is believing that the pipeline was damaged by a dragged anchor and later confirmed that the vessel was missing one of its front anchors. The Chinese authorities have conducted their own investigation and concluded that the damage was accidental, caused by a strong storm. The Estonian officials have stated that China’s findings were not legally valid as official evidence in their case. China’s Foreign Ministry, in a statement issued in May 2024, acknowledged that the 'NewNew Polar Bear' was involved in the incident, but denied that the damage was intentional. They also said that China was willing to cooperate with Estonia. The Estonian prosecutors reported they had not received any response to a formal request for legal assistance from the Chinese authorities. The Prosecutor’s Office in Tallinn stated that they could not yet determine what data China might have collected or how it could influence further legal steps. After the incident, the ship had switched from the Hong Kong flag to the Panamanian flag. ´It s operated by the Hainan Yangpu NewNew Shipping and is insured by the Longon P&I Club. Under Hong Kong law, authorities have the power to prosecute crimes committed on board Hong Kong-registered ships even if the incidents occur in international waters,

Timsen
2025-05-13

KMP.MUCHLISA

Casualty

After the sinking of the 'Muchlisa', surface search efforts continued on May 7, and a Basarnas dive team was deployed to the site for a search and recovery mission within the vessel's interior. Both missing crew members were recovered deceased, and the search has been suspended, The ferry Muchlisa was under way on a short voyage from Balikpapan to Penajam and approaching its destination when the port engine failed. The crew discovered that the vessel's propeller shaft had broken, resulting in hull damage, and it was taking on water. Attempts at an emergency patch repair were not successful. The 'Muchlisa' contacted another nearby ferry and requested help in intentionally grounding the vessel to prevent it from fully sinking. The 'Muchlisa' successfully stranded on a sandbar, but later drifted free and sank about 600 feet offshore. The passengers were evacuated, with assistance from first responders. Police have questioned the crew, including the captain and the helmsman, and an investigation is underway. The precise number of passengers and crewmembers on board was not immediately known, and the official count grew as the response operation went on. Initially, local authorities believed that there were no casualties. After assembling a list of 23 passengers and 21 crew members who were aboard on the voyage, the rescue agency Basarnas identified two missing crew members.

Timsen
2025-05-12

BAYESIAN

Casualty

During the salvage work of the 'Bayesian', a diver died on May 9. The deceased is a 39-year-old Dutch diver who died during the work on board the wreck. Divers were in the process of removing the giant boom on the 72-meter-high mast when the accident occurred. The details have not yet been clarified. Around 60 salvage specialists and several ships and barges are involved in the $ 30 million salvage operation over the next three weeks. The cause of the superyacht capsizing is still under investigation. Report with photo: https://www.maritimedanmark.dk/kaentret-superyacht-koster-endnu-et-menneskeliv

Timsen
2025-05-12

OLIWIA

Casualty

Due to the tide, the 'Oliwia' ran aground off the coast of Stavenisse on the morning of Ma 10, 2025. At around 08:00 a.m., Rijkswaterstaat was notified tha due to the low tide, the vessel could not continue under its own power. A patrol boat of Rijkswaterstaat and the rescue and salvage vessel 'Mistral' attended. It was decided that the vessel skipper would wait until there was enough water again, and the vessel refloated under his own power. Report with photo: https://www.omroepzeeland.nl/nieuws/17461886/binnenvaartschip-loopt-aan-de-grond-bij-stavenisse

Timsen
2025-05-12

EVENTIN

Casualty

The Finance Court of Mecklenburg-Western Pomerania, based in Greifswald (Vorpommern-Greifwald district), has suspended the confiscation order of the' Eventin', issued by German customs authorities. This is an interim judicial step and does not mean that the "Eventin" can set sail again. The Finance Court will continue to hear the case; until then, the federal government is not permitted to do anything with the ship — neither pump out the oil nor sell the vessel, due to ongoing appeal proceedings against the confiscation of the tanker by the customs authorities. According to the Finance Court, there are reasonable doubts as to whether the shipowner can invoke an "exceptional circumstance applicable to cases of distress at sea." However, this review must be reserved for the main proceedings. A date for this has not yet been set.

Timsen
2025-05-11

WOODS

Scrapped

arrived Chittagong Anchorage 08.05.25

BerndU
2025-05-10

SMS CAYENNE

Scrapped

Beached at Aliaga 02.05.25 https://www.instagram.com/p/DJda16Woe0f/

BerndU
2025-05-10

CAPTAIN RALEIGH

Casualty

A commercial salvage team from Seattle is on scene developing a plan to recover the 'Captrain Raleight' from a water depth of 40 feet near the bar at the entrance to Grays Harbor, after the Coast Guard suspended a search for its missing captain, who was last seen inside the ship. The Coast Guard immediately issued an “Urgent Marine Information Broadcast” and actively searched for the captain for several hours, but called off the search at 8:40 p.m. Rescuers transported the three crew members to Station Grays Harbor for evaluation by EMS .On May 10, a dredging ship operated by the U.S. Army Corps of Engineers also arrived to help locate the sunken ship. At around 11:45 a.m., they pinpointed the location of the wreck. A U.S. Navy dive team brought in by Navy helicopter from Air Station Whidbey Island was also deployed to the area of the sunken vessel. Divers were unable to access the wreck site until around 6 p.m. They attempted to approach the vessel, but failed to penetrate it due to debris, poor visibility, and strong currents. The Coast Guard was working with the Washington Department of Ecology to monitor pollution and mitigate impact to wildlife. So far there ws no damage from fuel to the shoreline around Westport and Grays Harbor.

Timsen
2025-05-13

ENDURANCE

Casualty

Worn-out mooring lines that were not replaced on time were the reason that the 'Endurance' broke free from its dock and hit a pier and dry dock at the Port of Bremerhaven on March 13, 2021,, the Federal Bureau of Maritime Casualty Investigation (BSU) found out. The investigators have determined that the main cause of the line breakage was the worn mooring lines that were not replaced in good time due to an inadequate safety management system. Owing to the conditions of the mooring lines, coupled with offshore winds with gusts reaching speeds of up to 50 knots, the accident was most likely to happen despite preventive efforts by the ship’s master. The 'Endurance' was moored starboard side when the lines parted at about 09 45 a,m,. Investigators were able to establish that the master was aware of the weather forecast and conscious of the potential danger of mooring line failure. For this reason, he had taken appropriate precautionary measures against line failure by requesting tugs. 19 minutes before the incident at 09.24 a.m., the master had gone to the bridge because of the prevailing wind conditions at the berth. At 09.30 a.m., he requested tug assistance and instructed two of his deck officers to inspect the lines. When the lines failed, he issued instructions to drop the starboard anchor, start the main engine, and raise the lowered vehicle ramp. Before the arrival of the tugs, the 'Endurance' had drifted toward the Lloyd Werft dockyard. The first two tugs arrived about eight minutes after the line failures and before the main engine was running, but could not prevent the allision. It was determined that the vessel was only about 120 meters, meaning the tugs did not have enough time and space to prevent the contact. The damage on the ship included a crack above the waterline in the shell plating on the port side, a hole in the bulbous bow, and a dent and paint abrasions at the stern on the starboard side. The vessel’s operator, ARC, had also arrived at the same conclusion in its internal investigation, determining that the condition of the lines may not have been consistent with requirements. The lines were damaged to such an extent that only two of the 14 lines met the requirements for mooring lines. Following the BSU investigation, actions have been taken to prevent similar occurrences. They included the procurement of berth analysis software by the Port of Bremerhaven. Expected to be deployed this year, the software is designed to trigger alerts that would help the port inspect a vessel's mooring arrangement. As of Jan 1, 2024, new internationally binding guidelines for the inspection and maintenance of mooring equipment, including lines, came into force. In particular, the vessel operator is now required to introduce a procedure for mooring operations, as well as the inspection and maintenance of mooring equipment, including mooring lines. A maintenance procedure must be implemented on ships so that worn lines are identified in good time before they fail. Maintenance must be carried out and documented on board.

Timsen
2025-05-12

GULF STREAM

Casualty

On the morning of May 12, 2025, at around 07:30 a.m., a fire broke out during welding works on the 'Gulf Stream', moored at the Kalkhaven near the Keizershof in Dordrecht. The fire brigade was called out and attended with two fire engines. The fire could be extinguished quickly. No one was injured; but there was damage to the ship. Reports with photos: https://www.bndestem.nl/dordrecht/brand-op-een-schip-op-keizershof-in-dordrecht~aca677d8/?referrer=https%3A%2F%2Fwww.google.com%2F&%3Bcb=8a2ba4a1-ccda-4c45-a4fb-a194532b8953&%3Bauth_rd=1&cb=2b5d213a-6e8d-4803-a5ca-ce7e3d8f9a1f&auth_rd=1 https://dordtcentraal.nl/1/opnieuw-brand-binnenvaartschip-in-kalkhaven/

Timsen
2025-05-12

CHARLENE

Scrapped

Beached at Chittagong 12.05.25

BerndU
2025-05-12

HEBRIDEAN ISLES

Scrapped

Until May 9. 2025, a small group of seafarers stayed with the 'Hebridean Isles' while she was berthed at King George V docks in Glasgow since mid-November 2024. CalMac continued to crew the vessel, at minimum manning levels, under charter until CMAL finalised arrangements to tow the vessel, dead ship, to a recycling facility at Esbjerg. Report with photos: https://www.hebrides-news.com/calmac-crew-farewell-hebridean-isle-leaves-scotland-scrapping-9525.html?fbclid=IwQ0xDSwKNVD1jbGNrAo1UM2V4dG4DYWVtAjExAAEe2pWbXh4VSjb7NHLM82oRsKwtW1qom991hwyOID68VVAopEugIqXuDRru33g_aem_k-4FgaYa0-6tM-760XrCQg

Timsen
2025-05-11

HU GANG YIN 2

Scrapped

arrived Chittagong Anchorage 05.05.25

BerndU
2025-05-10
  • «
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • »

Location + Contact

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

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

Über

DatenschutzerklärungGeneral Terms and ConditionsTerms of useImprintContact

Explore

ProdukteSchiffeHäfenNewsÜberCommunity

Social

 

© vesseltracker 

Log in

Haben Sie Ihr Passwort vergessen? Reset

Noch kein account? Registrieren

Phishing - Warnung:

In sozialen Medien sind Links aufgetaucht, die einen kostenlosen Trial-Zugang zu vesseltracker versprechen. Die verlinkte Webseite wird für phishing benutzt und versucht, Zugangsdaten von vesseltracker Usern zu stehlen.

Bitte beachten Sie die folgenden Hinweise:

  • Loggen Sie sich nur auf den Original-Seiten (www.vesseltracker.com und cockpit.vesseltracker.com) ein
  • Stellen Sie sicher, dass sie ein grünes Schloss in der Adresszeile des Browsers sehen und dass es sich um eine sichere Verbindung handelt
  • Sollten Sie bereits ihre Zugangsdaten auf der falschen Seite eingegeben haben, ändern Sie bitte ihr Passwort. Um das zu tun, loggen Sie sich auf www.vesseltracker.com ein und klcken dann auf Ihren Usernamen => My Vesseltracker. Dort finden Sie die Möglichkeit, das Passwort zu ändern
  • Falls Sie weitere Fragen haben oder Hilfe beim Ändern des Passworts benötigen, schreiben Sie bitte an support@vesseltracker.com