• 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/Casualty42694Misc. for Ports and Vessels38127Scrapped/Beached/Broken Up22698Sold/Decommissioned8580Charter Changed6736Pirate attack2063

EVER FEAT

Casualty

On the afternoon of July 29, 2025, the 'Ever Feat', en route from Navegantes, berthed in the port of Montevideo with two container bays being heavily affected, with between 30 and 40 units crushed, bent, or dislodged. At least two 40-foot containers were left hanging precariously over the vessel’s port side, risking loss overboard, after encountering forceful winds and high waves near Rio Grande do Sul. The structural damage included twisted lashing bars, crushed container walls, and visibly distorted fittings on deck. Work was started in order to secure the cargo to allow the ship to sail again. The National Port Authority (ANP) was in charge of the planning, along with the shipping company and the corresponding port operators. The Coast Guard issued a series of recommendations for prevention during the handling of containers, due to the fact that they contain fertilizers, which are classified as toxic or polluting. The cargo was being handled by the company Monteco. It was currently unknown if any of the containers fell into the water. Due to the damaged containers, each client's insurance policies were activated. As a precaution, containment and clean-up protocols were triggered alongside a full cargo review. The nature of the collapse suggested internal system stress caused by extreme rolling and pitching, possibly exceeding the vessel’s designed stability limits. Classification society surveyors boarded the ship early on July 30. Their work included verifying hull integrity, checking for leaks of hazardous materials, and examining damaged lashing equipment. The 'Ever Feat' remained stationary in Montevideo as of Aug 8. Reports with photos and video: https://www.subrayado.com.uy/buque-contenedores-danados-y-punto-caer-esta-el-puerto-montevideo-accidente-brasil-n983820 https://www.elobservador.com.uy/nacional/llego-al-puerto-montevideo-barco-que-sufrio-danos-una-tormenta-mas-20-contenedores-resultaron-danados-n6010550 https://www.elpais.com.uy/maritimas/buque-se-accidento-frente-a-rio-grande-y-llego-a-montevideo-con-los-contenedores-a-punto-de-caer-al-agua

Timsen
2025-08-08

SEA LADY II

Casualty

The salvage operations was underway to refloat the 'Sea Lady II' in Port de Saint-Tropez by the Dutch maritime services provider HEBO Maritiemservice, The 'Hebolift 2' had arriving on site on the evening of Aug 5. The salvage effort was being supported by the DUC Diving from Urk, whose team was deploying lift bags and carrying out underwater operations. The recovery was utilising HEBO’s dedicated yacht lift set, including a large spreader beam designed to minimise further damage to the hull. If all goes according to plan, the 'Sea Lady II' will finally float under her own buoyancy. The operation is expected to be completed by the end of Aug 7 or the early morning of Aug 8. Report with photos: https://www.superyachttimes.com/yacht-news/sea-lady-ii-yacht-refloated-saint-tropez-fire

Timsen
2025-08-07

EVER LUNAR

Casualty

On Aug 1, 2025, the 'Ever Lunar' lost approximately 50 containers, while being anchored in pos. 12° 01' S 077° 12' W in the Callao Bay, approximately 3.9 nautical miles northwest of San Lorenzo Island. The container ship had been berthed in Callao for cargo operations, but left the port due to the tsunami warning issued, without all the containers being secured. It moored on anchorage 1, where it experienced severe rolling, causing the containers at the stern to fall into the sea. One of the containers was left with half of its structure hanging off the side of the ship, while three other units lay fallen on the ship's deck. Multiple containers were floating along, spilling some of the cargo they were storing, mostly cardboards. The incident prompted a temporary closure of the Port of Callao, which halted operations at the DP World terminals, APM Terminals, and other companies operating in the area. and stopping vessel traffic in the region. Maritime security advisories were issued, and vessel movements were halted throughout the bay. The weather conditions were dense fog, overcast skies, and high humidity associated with the South Pacific Anticyclone. The National Emergency Operations Centre (Coen) of the National Institute of Civil Defence (Indeci) confirmed that the containers did not contain hazardous goods. The National Port Authority (APN) reported that recovery operations would be undertaken by specialized salvage companies under the coordination of the Maritime Authority. Fishermen and onlookers mobilized in small boats to collect drifting boxes, many still sealed, that the sea had dragged ashore. Two patrol boats, the 'Costa Sama' and 'Río Chira' (MMSI: 760001220), were deployed to secure the area while tugs 'Ram Vigo' ((MMSI: 677900000)) and 'Tiamat' ((IMO: 8112184)) were deployed to the Callao Bay to assist in removing the floating containers. The relevant authorities have launched an investigation to determine the cause of the incident. The crew was safe on board. n the On the afternoon of the same day and following further technical assessments, the DICAPI announced a reduction in the alert level, establishing a partial closure (Level IV), restricting maritime traffic to the Central Zone: Callao Bay; North Zone "A": Pampilla 1, Pampilla 2, and Pampilla 3; North Zone "B": Solgas and Pure Biofuels; North Zone "C": Tralsa 1, Tralsa 2, Surfisa, Quimpac, and Zeta Gas; and South Zone: Conchán Multibuoys and Unacem Lima Docks, in addition to Ancón Bay. Later, operations throughout the port were fully restored. The recovery time for the lost boxes was expected to take between 15 and 20 days. The 'Ever Lunar' remained anchored off Callao as of Aug 8. Reports with photos: https://apam-peru.com/buque-de-evergreen-pierde-50-contenedores-en-bahia-del-callao/ https://m.youtube.com/watch?v=wNGoxpN5qpA https://informateperu.pe/peru/pescadores-del-callao-recogen-paquetes-flotantes-tras-caida-de-contenedores-al-mar/ https://splash247.com/evergreen-ship-loses-50-boxes-off-peru/ https://www.puentedemando.com/un-barco-de-evergreen-pierde-50-contenedores-y-provoca-el-cierre-del-puerto-de-el-callao/

Timsen
2025-08-08

CORUISK

Casualty

The 'Coruisk', serving on the route Mallaig-Lochboisdale, suffered a technical issue with the aft engine on Aug 7, which required the use of the berth at Mallaig. As a consequence, the scheduled 09:15 a.m. arrival at Mallaig and the 10:05 a.m. departure from Mallaig and the 10:15 a.m. sailing from Armadale, operated by the ferry 'Lochnevis' (IMO: 9209063), were cancelled. After the technical issue was successfully resolved, the previously cancelled 10:15 a.m. sailing from Armadale has been reinstated.

Timsen
2025-08-07

STRATFORD

Casualty

On July 28, 2025, a fire broke out aboard the 'Stratford' with 25 crew members on board, while sailing approximately 190 nautical miles northwest of the Yongshu Reef, northwest of Hongkong near the Nansha district, en route from Shenzhen to Nha Trang n its China–India Express 3 (CIX3) service. The distress call was forwarded by the Salvage Bureau to the South China Sea Rescue Bureau, which deployed the 'Nanhai Jiu 116', which was on a one of its ships of routine patrol nearby. A rescue helicopter was also launched for an aerial survey and in order to transmit real-time fire updates. The fire was initially located in four containers on the foreship. When the patrol boat reached the scene, it immediately used fire monitors to conduct high-intensity cooling and firefighting operations. Three professional rescue team members were dispatched aboard the container ship to conduct firefighting operations. By late that night, the flames were largely extinguished. From the night of July 30 to 31 some containers on board began to smoke and rekindle, and the area of the burning containers expanded. Rescue teams worked tirelessly day and night, repeatedly carrying out firefighting, water spraying, fire-retardant injections, and fire detection inspections. The visible flames were extinguished on July 30 at around 2 p.m. Following repeated inspections, rescue crews confirmed that no residual fire risks remained by the evening of Aug 1, securing the safety of the crew, vessel and cargo while preventing secondary disasters like marine pollution.On the afternoon of July 30, they reported the temperature in the containers had returned to normal levels, and the fire was declared extinguished. They continued to monitor for any signs of the fire reigniting. The 'Nanhai Jiu 116' escorted the vessel, which proceeded at a speed of 5.8 knots towards the port of destination, where it arrived on Aug 6. Aso f Aug 8, it remained anchored in pos. 12° 13' N 109° 13' E off Nha Trang. Report with photos: https://www.sdilogistics-shippings.com/news/another-ship-caught-fire-which-had-called-at-85172266.html

Timsen
2025-08-08
  • «
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • »

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