• 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/Casualty42013Misc. for Ports and Vessels37910Scrapped/Beached/Broken Up22564Sold/Decommissioned8529Charter Changed6734Pirate attack2009

ALI AYKIN

Casualty

As of June 10, the 'Ali Aykin' remained stationary in Malmö, while the investigations were still going on, why it deviated from the shipping channel. and grounded on the soft bottom of sand and stone near Klagshamn. The authorities have served notice and detained one crew member on suspicion of gross negligence in maritime traffic. One crew member was being investigated for drunkenness. The Swedish Coast Guard had feared an oil leakage from the 69 tons of fuel oil aboard the ship, after a breach was discovered in one of theballast tanks. The flooding of the tank had complicate the salvage efforts. On June 3, the salvage company hired by the owners began offloading a portion of the cargo of scrap to an adjacent barge.The salvage operation was supervised by hree Coast Guard vessels. The vessel will undergo a further inspection while the prosecutors were proceeding with the investigation regarding the actions of the crew.

Timsen
2025-06-10

PHOENIX JAMNAGAR

Casualty

On June 5, 2025, at around midnight, the 'Phoenix Jamnagar' disconnected from an offshore pipeline connection in the Si Racha District southeast of Bangkok in the Gulf of Thailand, due to unexpected severe weather conditions, including high waves and sudden strong winds. Oil dispersants, booms, and skimmers were being deployed to contain the spill. The Thai Oil company initiated a process to stop the oil transfer but during the sudden storm, the breakaway coupling worked as designed to prevent damage to the ship or pipeline. It disengaged causing the spill which took 30 minutes to stop. Thai Oil along with multiple government agencies worked to contain the oil slick. The National Maritime Interests Protection Center (ThaiMecc) reported that an estimated 20 cubic meters or approximately of oil had spilled . Oil booms were strung at 399 and 600 meters but the spill spread to create a slick covering an area estimated at 10 meters by 10 meters and drifted southwards at a speed of 1 to 2 knots. Boats and helicopters with dispersants were crossing the area, and a skimmer had also been deployed. The goal was to complete the skimming operation by the afternoon of June 6. No damage was apparent to the tanker or the pipeline.

Timsen
2025-06-08

OT-2439

Casualty

On June 8, 2025, at around 6:00 p.m. LT the 'OT 2439' suffered a hull damage and ran aground on the Kazachinsky rapids of the Yenisei River in central Siberia, while the towing two empty barges downstream. It had struck an underwater obstacle, which caused a breach in the hull and partial flooding. Subsequently, an oil leakage occurred from the ship, which had its strrn submerged and was listing to port side. Containment measures, including an oil barrier and sorbent booms, were deployed to prevent the spread of the oil slick, which drifted downstream and affecting riverbanks. A state of emergency has been declared in Kazachinsky district. There were 14 crew members on board at the time of the incident. Two of them were evacuated to shore, while the others remained to help contain the spill. The heads of the Pyatkovsky, Galaninsky, Momotovsky, Mokrushinsky, Kazachinsky, and Zakharovsky village councils have been ordered to monitor the appearance of oil spills, Russia’s Eastern Regional Transport Investigation Department has launched an investigation into the cause of the incident. Report with photos and video: https://www.fontanka.ru/2025/06/09/75566087/

Timsen
2025-06-09

MESHKA

Casualty

On June 3, the Swedish Transport Agency received a document for a salvage plan for the 'Meshka',which ran aground off Landskrona. The ship can be salvaged this week. but the first priority was that the fuel tanks must not be damaged. The ship was empty of cargo, when it ran onto a shoal on its way to Vysotsk in Russia on May 31 and has remained stuck since in pos. 55° 52' N 012° 46' E. On June 6, the patrol vessel 'KBV 001' (IMO: 9380441) was monitoring the bulk carrier. Report with photos: https://www.nyteknik.se/farkost/brottsmisstanke-efter-grundstotning-i-oresund-inga-lackor-hittade/4366188?fbclid=IwQ0xDSwKxMVxleHRuA2FlbQIxMQABHhqseqy93B7GLSFusyLT00iX-bwzBYXhxrQmZaJ-nbHQezZuLbcPA8ovsCBR_aem_DhFr6b_2iYk0-7YtU4ukpw

Timsen
2025-06-07

PHOENIX JAMNAGAR

Casualty

On June 5, 2025, at 12.54 a.m., the 'Phoenix Jamnagar' disconnected from an offshore pipeline connection in the Sri Racha District southeast of Bangkok, in the Gulf of Thailand in pos. 13°04.225′ N, 100°46.815′ E. The accident happened due to unexpected severe weather conditions, including high waves and sudden strong winds. Oil dispersants, booms, and skimmers were being deployed to contain the spill. The Thai Oil company initiated a process to stop the oil transfer but during the sudden storm, the breakaway coupling worked as designed to prevent damage to the ship or pipeline. It disengaged, causing the spill which took 30 minutes to stop. Thai Oil along with multiple government agencies worked to contain the oil slick. The National Maritime Interests Protection Center (ThaiMecc) reported that an estimated 20 cubic meters or approximately of oil had spilled . Oil booms were strung at 399 and 600 meters but the spill spread to create a slick covering an area estimated at 10 meters by 10 meters and drifted southwards at a speed of 1 to 2 knots. Boats and helicopters with dispersants were crossing the area, and a skimmer had also been deployed. The goal was to complete the skimming operation by the afternoon of June 6. No damage was apparent to the tanker or the pipeline. Report with photos: https://www.nationthailand.com/news/general/40050889

Timsen
2025-06-08
  • «
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • »

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