• 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/Casualty42170Misc. for Ports and Vessels37959Scrapped/Beached/Broken Up22586Sold/Decommissioned8538Charter Changed6734Pirate attack2021

CEUTAMAR CINCO

Casualty

The 'Ceutamar 5', with seven crew members on board, caught fire in the Bay of Algeciras at Punta del Rinconcillo, near the Refinery dock, heading towards the town of Palmones, on June 25, 2025, s Shortly after 5:30 p.m. The vessel operating alongside a container ship, which was anchored in the area, providied logistical support services at that time, Minutes after the fire broke out, two Boluda tugs intervened to extinguish the flames and to separate both ships. The crew members had to jump into the water and were rescued. Most of them were divers. They were transferred to the dock in good condition. No serious injuries have been reported. Two of them were treated for smoke inhalation, while neither of them required hospitalisation. The San Roque City Council activated its municipal Emergency Plan. Besides Salvamento Marítimo, also a Civil Guard vessel and the patrol boat 'Isla de León', based in Ceuta, participated in the joint operation to reinforce containment efforts and secure the area while the fire was extinguished. The Spanish Navy ship used a water cannon in this effort.The fire was extinguished, assisted by the Algeciras Fire Department, which responded, after being requested by the port authority, to cool the burning vessel. Six firefighters and three vehicles were dispatched to the scene. After the fire was extinguished, the 'Ceutamar 5' was towed to a nearby pier in the port of Algeciras. The vessel's wheelhouse had almost completely burned down with only the supporting frames left standing. Local officials have assured that the incident did not result in any pollution. Reports with photos and video: https://www.diarioarea.com/algeciras/juan-jesus-rodriguez-ruiz-velasco-toros-feria-algeciras-puerta-grande/ https://www.lavozdelsur.es/ediciones/provincia-cadiz/campo-gibraltar/preocupacion-por-enorme-columna-humo-barco-durante-repostaje-en-estrecho-reportan-explosiones_336949_102.html https://www.lavozdelsur.es/ediciones/provincia-cadiz/campo-gibraltar/siete-tripulantes-se-lanzan-mar-escapar-llamas-barco-incendiado-en-bahia-algeciras_336962_102.html https://www.8directo.com/puerto/puerto-desactiva-plan-autoproteccion-incendio-embarcacion-servicio_626379_102.html https://www.bairdmaritime.com/security/incidents/accidents/video-fire-ignites-on-supply-boat-near-spains-algeciras-port-all-seven-crew-rescued

Timsen
2025-06-27

MSC ELSA 3

Casualty

MSC has started talks with the Boskalis subsidiary Smit Salvage about the salvage of the 'MSC Elsa 3', after the shipping company terminated the contract with the the American T&T Salvage after delays in removing oil from the wreck. The new salvage contract was allegedly nearing completion. According to MSC, the company T&T Salvage did not have the necessary expertise, although great progress had already been made in sealing leaks in the fuel lines by divers. The removal of the more than 450 tons of marine fuel had been delayed because the installation for saturation diving was still at the customs.

Timsen
2025-06-27

SILVER CLOUD

Casualty

On June 26, 2025, a tour operator has rescued dozens of passengers of the 'Silver Cloud', who were stranded on an atoll off northern WA's Kimberley coast. They were exploring the waters near Adele Island, a small, low-lying island 150 kilometres north of Cape Leveque, in small boats, but got caught by the outgoing tide. The cruise, was four nautical miles away, when tthe boats were caught by the rapid outgoing tide . They had to get out and make their way across coral beds to make it to new zodiacs and get to the ship. Several of them suffered twisted ankles andlots of scrapes, when crossing coral-filled shallows to reach safety. A small group of passengers had to wait hours into the night for the tide to turn. The 'Silver Cloud' has 20 inflatable boats, which were used to ferry some passengers to safety. Others had to wait hours in the small boats, in darkness, before the water rose enough to make it back. Report with photo: https://www.abc.net.au/news/2025-06-27/silversea-cruises-passengers-stranded-at-adele-island-off-wa/105468440

Timsen
2025-06-27

WAN HAI 503

Casualty

On June 25 at 6 p.m. the 'Wan Hai 503' remained under tow approximately 88 nautical miles off the Indian coastline, positioned at Lat. 09°16.73'N Long. 074°49.96' E, proceeding west-southwest at speeds between 1.2 to 3 knots with heavy rolling and pitching due to persistent rough sea conditions. Approximately 90 miles have been covered so far, with the vessel expected to exit the Indian EEZ by late June 27th or early on June 28 weather permitting. The fire situation in cargo hold no. 4 remained critical. Structural failures, including a partial hatch collapse and container stack collapse in the forward section, have increased ventilation, allowing strong winds to exacerbate the smouldering fire, particularly in containers storing plastic resin. Thermal imaging indicatedhotspots at frames 83, 93, and 103 with temperatures peaking at 228°C. Dense black smoke continued to emit from hold no. 4, with boundary cooling being conducted continuously by tugs 'Saksham' and 'Water Lily' from both port and starboard sides. Despite multiple boarding attempts, salvage teams have been unable to safely access the vessel due to deteriorating weather and safety risks, including unknown contaminants in the flooded engine room. Searches for the missing crew member remained a top priority during each boarding attempt, though no remains have been found to date. The port midship draft markings remained obscured due to heat-related paint damage, not submersion. Stability remained a concern due to flooding in the engine room and limited dewatering capability at present. Salvage resources currently deployed included the 'Offshore Warrior', 'Saksham', 'Water Lily' and 'Saroja Blessing', carrying additional equipment and independent pumps. Pyrocool firefighting material was en route aboard the 'Virgo', scheduled to arrive by June 29. A complete suite of salvage equipment, including independent pumps with 800-900 cubic meters per hour capacity, power packs, compressors, hot-tapping units, de-fuelling gear, and fast-response firefighting kits were staged aboard the tugs. Salvage divers with contaminated water dive suits were present on site, but have not been cleared to enter the flooded engine room pending water quality testing to assess chemical hazards from compromised container cargo. The VDR remains secured aboard the 'Offshore Warrior', with transfer to the 'Water Lily' planned at the earliest opportunity for subsequent delivery to MMD Kochi. CO₂ reserves were confirmed available, with 198 bottles on site. However, CO₂ deployment in cargo hold no. 4 remained unfeasible due to structural breaches. The salvors planned to deploy CO₂ in the holds 5 and 6 once the structural integrity checks have been completed. The WAN HAI Lines continued to pursue a Port of Refuge approval, with agency coordination and harbour master engagement underway. Crew members injured during the initial incident remain stable, with ICU cases showing signs of recovery. The vessel remains exposed to compounded risks from ongoing fires, uncertain hazardous cargo, and rough weather conditions hampering onboard operations. The presence of over 280 containers with incomplete manifest data continued to pose a significant hazard to firefighting teams, though updated information has now been received from WAN HAI Lines and is under ITOPF review for hazardous material classification. Firefighting teams were facing substantial challenges due to open ventilation in hold no. 4, which continueds to feed the smouldering fires despite boundary cooling efforts. Inaccessible sections and unknown cargo content restricted direct firefighting options. Salvors have confirmed that excessive water application remained constrained to avoid worsening the engine room flooding, which currently contributed to the compromised vessel stability. Towing operations towards international waters were a critical priority to mitigate coastal environmental risks. The Directorate has directed T&T Salvage to maintain course and speed to expedite the vessel's exit from the EEZ. A replacement of the 'Boka Winger' remained pending following the owner's refusal to extend deployment beyond contractual obligations. The salvors were coordinating alternative tug resources from Sri Lanka and anticipated the 'Atlantis Virgo's arrival to supplement the towing and firefighting operation. Weather conditions were expected to improve temporarily, providing a narrow window for critical actions. The Directorate has instructed that, weather permitting, salvage teams must prioritise boarding to commence dewatering of the engine room, conduct necessary fire suppression within accessible areas, and assess hull and pipeline integrity before CO₂ deployment. The Directorate also emphasised that salvors must test the engine room water for contamination prior to diving operations to safeguard personnel. Should conditions permit, divers may seal internal pipe leaks to isolate the engine room and enable effective dewatering. Immediate focus remains on stabilising the vessel, maintaining fire control, and securing a safe tow beyond Indian jurisdiction. Coordination with all stakeholders were continued, with clear directives issued to WAN HAI Lines to provide comprehensive container manifest data and assist with expediting all approvals for Port of Refuge access. T&T Salvage has been instructed to finalise plans for ETV replacement, initiate hard wire towline installation when feasible, and prepare contingency measures for all salvage operations. The Directorate reiterates that environmental protection, crew safety, and vessel stabilisation remain paramount, with all available resources to be deployed toward achieving these objectives in the shortest possible timeframe.

Timsen
2025-06-27

REM PROVIN DL AZUAY

Casualty

On June 26, salvors started to recover the 'Provincia de Azuay', that sank on March 17 at Pier 2 in Veracruz. At around 6:00 p.m. that personnel from the Veracruz National Port System Administration (ASIPONA) started the work using a specialized crane.After the sinking, and as part of the environmental protocol, the Ministry of the Navy (SEMAR) hadimplemented containment barriers from the outset to prevent the spill of hydrocarbons or other polluting substances in the area. The authorities have not specified an estimated completion date for the salvage, but assured that vigilance will be maintained to minimize risks to navigation and the marine ecosystem of the port of Veracruz. Report with photos: https://imagendeveracruz.mx/policiaca/Inician-el-rescate-del-remolcador-que-se-hundio-frente-al-Malecon-de-Veracruz-20250626-0091.html

Timsen
2025-06-27
  • «
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • »

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