• 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

  • News
  • Vessel news
  • Port news

Category

Accident/Casualty48318Misc. for Ports and Vessels40884Scrapped/Beached/Broken Up23627Sold/Decommissioned9057Charter Changed6781Pirate attack2200

TUGBERK IMAMOGLU

Casualty

On Oct 2, search teams have found an unidentified man’s body off Silivri, Istanbul, 56 days after the 'Tuğberk İmamoğlu' sank in the Sea of Marmara collision. Forensic Medicine Institute tests will establish his identity, cause of death and any crew link. Captain Yaşar Kayhan’s body was found 5 kilometers from the collision site on Sep 14 and identified on Sep 15. The nine other crew members had remained missing. The ship, carrying 4,199 tons of steel coils from southern İskenderun to the Black Sea port Karadeniz Ereğli, collided with the tanker 'Alsu' on Sep 2 at around 3 a.m., while the tanker was sailing from northwestern Kocaeli to western Aliağa. The Navy vessel TCG Akın located the wreck at a depth of 720 meters on Sep 4. The 'Alsu’s captain Ahmet Erarslan and the 3rd officer Murat Evciman were remanded on Se. 3. A preliminary report cited failures of supervision and collision avoidance, respectively. Four other suspects were facing judicial supervision.

Timsen
2026-10-29

COMMANDANT CHARCOT

Casualty

The 'Le Commandant Charcot' ran aground one meter from the quay in Breivika in Tromsø on the morning of Oct 29, 2026. The ship was scheduled to arrive in Leknes on Oct 30 and in Narvik on the weekend of Oct 31/Nov 1. Photo: https://livecenter.norkon.net/frame/lofotposten/23033/default?p=lc-12726387-23033-lofotposten

Timsen
2026-10-29

CONTSHIP JET

Casualty

The 'Contship Jet', enroute from Haifa to Constanța with 421 containers on board, was hit by three sea drones on Oct 28, 2026, at noon, while sailing off Bulgaria’s northern Black Sea coast. The attack took place approximately 21 nautical miles off the coastal town of Shabla, 16 nautical miles off Cape Kaliakra, which would place it in Bulgaria’s exclusive economic zone in the Black Sea, but four miles outside the country’s territorial waters. The ship caught fire and developed a list to starboard side, and the 18 crew members - among them 14 Filipinos and four Ukrainians - took to the life rafts. A tanker was also dispatched to provide assistance. Meanwhile, another drone approached over the water, endangering the lives of the sailors. Before the incident, the Navy received a signal from a French Navy's Atlantic maritime patrol aircraft. The aircraft crew initially observed two unmanned aerial vehicles, and then another, which were heading towards several ships north of Cape Kaliakra. It was assumed that the ships would be attacked, the information was immediately disseminated to the Maritime Traffic Management with a request to warn vessels of the danger of a drone attack. The corvette 'Resolute', the SAR ship 'Proteo“ and a 'speedboat with the ship number 223 were sent to the risk zone. The first strike was carried out at around 12:00, followed by two more. After a signal that the crew was starting to leave the container vessel, rescue teams were directed to the site. All 18 sailors were taken aboard the 'Proteo'. During the inspection, it was found that the ship was hit on the starboard side in the waterline area. The vessel remained afloat and continued to drift at the site of the attack. The attacking drones were moving at a speed of about 26 knots. The attack took place within about an hour and was carried out in international waters. The incident was the latest in a series of drone attacks on merchant ships off the coasts of Bulgaria and Romania, and came as the defence ministers of Bulgaria, Romania and Türkiye were meeting on Oct 28 to discuss maritime security in the Black Sea. It was widely believed that Russia was behind the attacks. Bulgaria, Romania and Turkey adopted a joint statement strongly condemning attacks against civilian shipping. The Bulgarian defence minister Stoyanov emphasised the shared responsibility of the three Black Sea countries, all NATO allies, to ensure the safety of maritime transport. The three defence ministers also agreed to organise further meetings in the near future to continue their cooperation. The tanker 'Khoryv' had caught fire after an attack on Oct 23. There were 13 people on board, including 10 Ukrainian and three Azerbaijani citizens. Nine sailors were rescued, one was killed and three remained missing. Other ships attacked during the recent days included the 'Alfa Watan', 'Able', 'Chelsea 3' and 'HS Dignity'. The 'Alfa Watan' and 'Able' were struck inside Bulgaria’s EEZ on Oct 6, 2026, at around 3 a.m. Report with video: https://www.novinite.com/articles/241335/Sea+Drone+Attack+on+CONTSHIP+JET+Captured+on+Video

Timsen
2026-10-29

EIDSVAAG MARIN

Casualty

The Norwegian Safety Investigation Authority has published its findings on Oct 27, 2026, into the death of a crew member aboard the 'Eidsvaag Marin' on Oct 29, 2025. The man was killed while replacing a hydraulic component on the vessel's cargo-handling machinery, while it sailed from Stavanger to Røvær. The investigators found out that disconnecting a hydraulic hose caused the machine's lifting frame and the operator's cab to move backwards, trapping the worker against a hydraulic oil tank. Other crew members attempted to free him, but were unsuccessful. The vessel returned to port of Dusavik, where emergency services released him. He subsequently died from his injuries. The investigation found that the machinery lacked a physical safeguard capable of preventing the uncontrolled movement. Although the manufacturer's operating manual specified a locking device to prevent crushing injuries during maintenance, the component was not included in the standard equipment supplied and was not available aboard the vessel. The investigators also found that Eidsvaag's safety management system did not adequately address the risks associated with hydraulic maintenance. There was no specific procedure, risk assessment or safety analysis for the work. Training was limited and depended heavily on individual crew members, while neither internal audits nor external inspections had identified the shortcomings. The authority also questioned the machinery's design, finding that its arrangement could make the safest maintenance position difficult to access. Following the accident, the Eidsvaag company, specialising in the transportation of fish feed from factories to salmon farms along the coast, ordered locking devices for vessels with similar equipment and introduced stronger training requirements and revised safety procedures. At the time of the accident, it operated 19 vessels, including four fitted with the same type of cargo-handling machinery. The Norwegian Maritime Authority has carried out an inspection, issued an order and announced plans for a safety notice covering vessels fitted with similar machinery. Proposed regulations covering lifting equipment and operations aboard ships were also under consultation, including more specific training requirements for cargo-handling equipment. The investigation did not identify a technical fault in the machinery itself. The Safety Investigation Authority issued no additional safety recommendations, citing the measures already introduced or planned by the operator and maritime authorities. Full report: https://havarikommisjonen.no/Sjofart/Avgitte-rapporter/2026-05

Timsen
2026-10-29

SARA KARIN

Casualty

The 'Sara Karin', with nine crew members on board, got its purse seine caught in the propeller amid bad weather in the Barents Sea 50 nautical miles northwest of Bjørnøya and had to be assisted by the Coast Guard on Oct 18, 2026. The patrol vessel 'Bjørnøya', which had been moored behind Bjørnøya with a crew consisting of 24 permanent employees and 35 conscripts, was deployed to assist by the Coastal Administration and took the 'Sara Karin' in tow towards the shore at a speed of 5-6 knots at 8.15 p.m. At 3.30 a.m., the towing connection failed, when the attachment points in the bow of the fishing boat gave way to the forces of the storm. In strong gales with around eight meters wave height, the Coast Guard vessel had to back up close to the casualty to shoot over a new tow line. Three hours later, the tow was finally secured again, and the course was set towards the east side of Bjørnøya. The conditions in the lee of Bjørnøya also presented challenges, with currents and swells from different directions that forced the Coast Guard to go in a continuous figure-eight pattern with the casualty in tow. Several other fishing boats in the area also sought refuge at the island to ride out the storm. On the night of Oct 20, when the storm center passed at its worst, thetowing wire broke once again. The 'Sara Karin' immediately began to drift eastward, out of the lee and towards the open sea with ten-meter waves and wind gusts of up to 60 knots. The casualty was drifting fast, and the margins were extremely small. If there would not have been the shielding from Bjørnøya astern, it could have developed even more worse. Once again, the crew managed to establish a new connection in the demanding conditions. On the way to the mainland, the tow cable broke for the fourth time, but reserve lines were quickly connected from the Coast Guard. North of Nord-Fugløya in Troms, the 'Sara Karin' was finally handed over to a civilian tug, which pulled the vessel the last distance to Hamnes in Lyngen for repairs to the propeller. By then the rescue mission had lasted four days. The response was coordinated via the Maritime Traffic Central Service in Vardø, which was following up on the incident. Report with photos: https://www.nrk.no/tromsogfinnmark/kystvakten-kjempet-i-fire-dogn-i-uvaer-i-barentshavet-for-a-berge-fiskebat-1.18064185

Timsen
2026-10-29
  • «
  • 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

About

Privacy NoticeGeneral Terms and ConditionsTerms of useImprintContact

Explore

ProductsVesselsPortsNewsAboutCommunity

Social

 

© vesseltracker 

Log in

Lost password? Reset

Don't have an account? Register