• 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

  • News
  • Schiffsmeldungen
  • Hafenmeldungen

Category

Accident/Casualty48299Misc. for Ports and Vessels40861Scrapped/Beached/Broken Up23626Sold/Decommissioned9057Charter Changed6781Pirate attack2200

MYRA

Casualty

The 'Myra', with 21 crew members on board, enroute from Ust-Luga to Port Said with an ETA as of Nov 7, issued an Inmarsat-C distress alert approximately 270–290 nautical miles west of Northern Ireland and the Outer Hebrides in pos. 56°18' N, 015°25' W on Oct 24, 2026, at 2.06 p.m. UTC, while sailing around 350 nautical miles off the Isle of Mull. The tanker maintained a speed of nine knots despite extreme sea conditions with 8.8 metres swell and gusts of 70 knots. The UK Coastguard coordination continued, as nearby traffic monitored the vessel. All vessels in the vicinity able to assist were requested to contact UK Coastguard immediately. The Royal Air Force deployed a P8 Poseidon Submarine Hunter to the vessel. Possibly the HM 'Coastguard S92' was also to be tasked. The RAF aircraft established contact with the 'Myra', and the crew reported that the distress signal had activated as they left an area of large swells. Following an assessment, the vessel continued its passage. The tanker has since entered Irish waters. The Irish Coast Guard dispatched its Beechcraft aircraft also on the morning of oct 25, made contact with the vessel and took images. It, too, was told that the emergency broadcast had been a false alarm and that there were no problems onboard. The Irish Coast Guard continues to provide support to the UK Coastguard and continued to monitor the vessel’s onward track. The distress alert from the 'Myra' was no longer active on Inmarsat and the tanker sailing south at a speed of 9 knots on Oct 25. Ukrainian intelligence linked the 'Myra' to Fractal Marine DMCC, a company registered in the United Arab Emirates, one of the three largest international operators transporting Russian oil and petroleum products, alongside Radiating World Shipping Services and Gatik Ship Management in 2023. Britain sanctioned Fractal Marine DMCC in February 2024 for activity in Russia’s energy sector. The company operated a fleet of 28 tankers, acting as an intermediary between shipowners and charterers. After sanctions were imposed, management of the vessels was transferred to other affiliated entities. The IMO listed its flag as 'Cameroon False', indicating a suspected fraudulent use of the Cameroonian flag. In the Ukrainian intelligence database, the vessel’s current flag was listed as unknown. The registered owner of the tanker was the Fleet Armada Pvt Ltd. Recently, the 'Myra' has been used to export Russian oil and petroleum products to third countries, while the G7 and EU oil embargoes and the price cap on Russian crude were in effect. The 'Myra' has repeatedly called at the Russian ports of Ust-Luga and Primorsk and has also visited ports in Turkey, Brazil, Senegal, Estonia, and Denmark. Inrecorded instances the vessel switched off its AIS system. The tanker was under sanctions from six jurisdictions. The United States sanctioned it on July 30, 2025, followed by the European Union on Oct. 24, 2025, and Switzerland and Ukraine on Dec. 13, 2025. The United Kingdom added the vessel to its sanctions list on Feb. 24, 2026, and Canada followed on March 25. The 'Myra' was part of a shipping network controlled by Mohammad Hossein Shamkhani, the son of Ali Shamkhani, a former secretary of Iran’s Supreme National Security Council and an adviser to Iran’s supreme leader. The network generates billions of dollars in revenue from oil trading and takes steps to conceal its links to Russia, Iran, and the Shamkhani family. Among the companies Ukrainian intelligence linked to the 'Myra' were the BPT Shipping Co. LLC., the Fractal Marine DMCC, the Wanta Shipping LLC-FZ, and The Zulu Ships Management and Operation — Sole Proprietorship LLC, all registered in the United Arab Emirates. https://www.aol.co.uk/articles/raf-scrambled-sanctioned-russian-linked-215655000.html

Timsen
2026-10-27

SEAHORSE

Casualty

While the vessel was still listing, the 'Seahorse' was moved to the Port of Beirut to offload the cargo and thus stabilise the ship. After the list occurred, it was thought that the cargo had shifted on the vessel. When the authorities contacted the captain, he said the situation was under control and that they did not require assistance. Later reports said the ship had possibly grounded as it was approaching Sidon. When the list increased, seven crew members panicked and chose to jump into the water. The captain called for assistance, and the seven men were rescued. The authorities meanwhile came to tge conclusion that the vessel had malfunctioned and the crew had failed to detect a water ingress, primarily in cargo hold no. 5. When they boarded the vessel, they reported it was nearly impossible to walk due to the angles, and they detected 3.5 to 4 metres of water in the hold. An emergency pumping operation commenced, and they were able to lower the water level to between 50 and 60 centimetres. Following the salvage, the crew members returned on board, with the exception of one injured sailor, who was taken to the hospital. Civil Defense and army teams assisted in pumping out the water that had caused the vessel to become unstable, in coordination with the Lebanese Armed Forces and the JRCC, which was inaugurated on Oct. 2, 2025, at the Beirut Naval Base. The authorities did not indicate what had malfunctioned on the vessel. The ship, however, had a long history of deficiencies reported during port state inspections going back to 2013. It had listed deficiencies on its last six inspections dating back to December 2025. Reports with photos and video: https://maritime-executive.com/article/seven-panicked-crew-jump-from-listing-cargo-ship-off-lebanon https://de.nachrichten.yahoo.com/sieben-besatzungsmitglieder-%C3%BC-bord-frachter-093046819.html https://today.lorientlejour.com/article/1552124/civil-defense-escorts-a-drifting-ship-between-saida-and-beirut.html

Timsen
2026-10-27

JOHANNA ENGELINA

Casualty

The 'Johanna Engelina' struck a breakwater in the Wadden Sea near Kornwerderzand on the early evening of Oct 26, 2026, and subsequently became stuck. The crew requested assistance, after which salvage company Rederij Noordgat from Terschelling arrived on the scene with the fast rescue boat 'Hurricane'. The ship was pulled free from the breakwater. Howeve, it then became apparent that more water was entering the vessel than initially thought. Pumps were immediately brought on board. Noordgat's second fast boat, the 'Skua', was also deployed and headed towards the ship with additional pumping equipment and support. Because the situation on board was deteriorating, the KNRM Harlingen was also alerted on behalf of the Coast Guard. The rescuers arrived quickly and assisted in locating the leak. Subsequently, an attempt was made to seal the leak as best as possible using an emergency solution. At that moment, there was a significant amount of water inside the ship. To minimise the risk of sinking, it was intentionally grounded with the assistance of the vessels involved. After working for several hours to seal the leak and pump out the ship, the course was set towards the port of Harlingen around 11:00 p.m. Rijkswaterstaat, with the patrol boat 'RWS 76', was also on site to monitor and provide support. Upon entering the harbor, the ship also received assistance from the 'BDS Supporter', a salvage vessel from Harlingen. The salvors assisted to safely move the ship with its own power into the Industrial Harbour and moor it at the quay at BDS on Oct 27 at 1 a.m. In the run of the day, the ship was taken ashore using the ship lift, so that the damage could be further investigated and the exact extent of the leak and other damage be determined. The extent of the damage was yet unknown. Report with photos: https://112fryslan.nl/schip-botst-op-strekdam-en-raakt-lek-hulpdiensten-in-actie/

Timsen
2026-10-27

MSC ANNE F

Casualty

When the cruise ship 'Mein Schiff 3' (IMO: 9641730) embarked on a 20-day voyage to the Canary Islands from Bremerhaven on Oct 25 at around 5 p.m., with 2,428 guests and 922 crew members on board despite stormy weather conditions with wind gusts of 35 knots, assisted by tugs, the vessel ran into difficulties near the container terminal. Strong gusts of wind caught the 'Mein Schiff 3', making it impossible for the ship to maintain its course. While it still managed to pass the 'MSC Anne F' at the Strom Quay, though it was reported that it also suffered slight damage, short time later it allided with the 'MSC Victorine' (IMO: 946867), which was also berthed at the MSC Gate. The assistance tug 'Fairplay 91' (IMO 9932177) retreated in the last moment in the space between the two container ships, along with the tugs 'Svitzer Rota' (IMO (IMO 9760859) and 'VB Evolution' (IMO: 9691357), which was connected to the bow of the 'MSC Victorine', which was berthed at the MSC Gate in pos. 53° 35' N 008° 32' E. On the starboard side, the forward boat davits were torn off, and four lifeboats were destroyed. Their numbers were 1, 3, 5, and 7. Deck 5 and 6 as well as the bridge suffered damages too. A crack approximately ten meters long was torn into the hull of the container ship at the Strom Quay, and a cell guide was damaged at port side. Some containers also suffered damage. Following the impact, the 'Mein Schiff 3' returned to the Columbus Quay, where a thorough assessment of the damage to the cruise ship began. No one was injured in the accident. The cruise line has not yet disclosed the full extent of the damage. TUI Cruises stated that further information would be provided as soon as more definitive details were available. The Canary Islands cruise scheduled for Oct 25 to Nov 14 would not be able to take place, as the cruise ship no longer had a full complement of lifesaving equipment at its disposal. The vessel first had to undergo inspection and repairs, and subsequently receive clearance from both a classification society and the flag state. The destruction of the lifeboats was expected to present particular challenges. Both ships were banned from sailing. The Bremerhaven water police and the Federal Bureau of Maritime Casualty Investigation (BSU) have begun their investigation into the cause. The actual cruise was cancelled, and the cruise ship will have to enter a shipyard for permanent repairs. The passengers had to disembark the ship on Oct 26 until 6 p.m. The ship will have to enter a repair yard, and the shipping company must now order new rescue boats from the manufacturer. They will be built from fiberglass-reinforced plastic. The production, outfitting, and acceptance testing of each boat was expected to take one to two weeks in series production. Furthermore, the hull of the vessel has sustained significant damage. all of which must be repaired. The costs for this were expected to run into the millions. The police has launched an investigation against the captain. According to the current sailing plans, the 'Mein Schiff 3' was scheduled to begin its winter program in Kiel on Dec 2. This date was expected to be met. The ship could also be deployed with a reduced number of lifeboats following emergency repairs. However, in accordance with SOLAS regulations, the shipping company would then have to reduce the number of passengers on board. The 'MSC Anne F' was able to leave Bremerhaven on Oct 26 enroute to Haugesund with an ETA as of Oct 28. Report with photos and videos: https://www.youtube.com/watch?v=ZrRrbcEJYEc https://www.youtube.com/watch?v=4OfDlo8tMUQ https://www.nordsee-zeitung.de/bremerhaven/mein-schiff-3-kracht-in-containerschiff-425817.html https://bnn.de/nachrichten/deutschland-und-welt/mein-schiff-3-soll-nach-unfall-in-die-werft https://www.mopo.de/hamburg/mein-schiff-3-rammt-containerschiff-reederei-trifft-schwere-entscheidung/5054504 https://www.moz.de/nachrichten/panorama/kreuzfahrt-ist-abgesagt-mein-schiff-3-muss-zur-reparatur-79611230.html https://www.tagesspiegel.de/gesellschaft/panorama/dpa-video-zeigt-unfall-in-bremerhavenkreuzfahrtschiff-mein-schiff-3-kollidierte-mit-containerschiffen--polizei-nennt-ursache-16200745.html https://www.ndr.de/nachrichten/niedersachsen/oldenburg_ostfriesland/nach-kollision-reise-von-mein-schiff-3-abgesagt,meinschiff-110.html https://www.butenunbinnen.de/nachrichten/kreuzfahrtschiff-mein-schiff-drei-crash-lloyd-bremerhaven-100.html https://www.news5.de/news/news/read/43717 https://youtube.com/shorts/hP4LM2sqcBQ?si=_RfTeQs-JI2ZFeUK https://www.youtube.com/shorts/TXsdOEugkZI https://www.facebook.com/reel/1566601018604503

Timsen
2026-10-27

MMC-CHRISTIANE

Casualty

The 'Christiane', carrying approximately 350 tons of rapeseed, suffered a failure of the rudder system near Reibersdorf on the morning of Oct 25, 2026. The crew carrier out a repair after a brief stop at anchor. However, at the Straubing lock, at river kilometer 2322, the 57-year-old Ukrainian captain noticed hydraulic oil leaking from the ship. Both the Straubing volunteer fire department and the relevant authorities were notified. The fire department deployed oil booms as a precaution. To limit further hazards, the ship was prohibited from sailing. An expert was called in to inspect the ship, but found no further oil leakage. Only a small amount of hydraulic oil had leaked. There was no water pollution or property damage. The water police of the Deggendorf traffic police inspectorate launched further investigations against the captain. The ship was allowed to continue its voyage at midday and arrived in Regensburg on Oct 26 at 5 p.m. UTC.

Timsen
2026-10-27
  • «
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • »

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