Caroline Bezengi: The Sanctioned Tanker Nobody Owns Enough to Save, Breaking Up on Oman's Turtle Coast

What's Confirmed

Caroline Bezengi departed Novorossiysk, Russia, in May 2026 bound for India with a cargo of Russian crude reported at over 800,000 barrels. On 8 June, while transiting off the coast of Oman, the crew reported an explosion consistent with a suspected limpet mine attack — reporting has attributed this to a possible strike linked to the ongoing conflict involving Russian energy exports, though no formal attribution has been confirmed by any investigating authority. The crew was evacuated without injury on 12 June. Without anyone aboard to manage her, the damaged tanker subsequently drifted and was driven onto rocks at Jazirat Al Qibliyyah in the Hallaniyat Islands, off Oman's Dhofar coast.

Omani maritime authorities boarded the vessel for a survey on 12 July and issued a 24-hour removal directive on 23 July. By 2 August, satellite imagery showed an active oil plume spreading from the wreck. Salvage vessels have been reported in the area, but no confirmed unloading or salvage operation was underway as of early August — the tanker remains grounded, listing, and deteriorating through the region's monsoon season.

Why Nobody Has Simply Removed Her

This is the part of the story that matters most for anyone in the industry, not just the environmental headline. Caroline Bezengi is a genuine “shadow fleet” vessel — sanctioned by the EU, UK, and US Treasury (OFAC), flagged in Cameroon (a flag increasingly used by vessels shifted out of mainstream registries after sanctions), owned through a Shanghai-registered management structure, and previously associated with Sovcomflot, Russia's state shipping company. Vessels in this category typically operate outside the mainstream International Group of P&I Clubs — the insurance framework that, for 90% of the world's tonnage, would normally fund exactly this kind of wreck removal and spill response.

That gap is the real story. A conventional tanker casualty has a clear chain: flag state, class society, P&I club, and owner, all with defined obligations and the insurance to back them. A sanctioned shadow-fleet tanker can have all four of those either absent, obscured, or actively trying not to be found — which is exactly the situation Oman's authorities appear to be navigating in real time, weeks into a spill nobody has yet confirmed a funded plan to clean up.

What's at Risk

The coastline between Sharbithat and Ras Madrakah is deliberately remote — isolated beaches backed by cliffs, which is precisely what makes it valuable nesting ground for sea turtles undisturbed by human traffic. The wider Hallaniyat Islands Marine Buffer Zone is a strictly protected habitat for endangered Arabian Sea humpback whales, seabirds, and coral. An estimated 600km² slick from a cargo worth over $100 million puts all of it directly at risk, in a region with limited existing spill-response infrastructure.

The Lesson for Crew, Not Just Governments

Most seafarers will never crew a sanctioned vessel knowingly. But the shadow fleet has grown large enough — hundreds of vessels by most industry estimates — that manning agencies and individual seafarers increasingly need to know what to actually check before signing on: is the vessel's P&I cover a genuine International Group club, or a lesser-known non-Group insurer that may not fund a real casualty response? Is the flag state one with a functioning maritime administration, or one used specifically because its oversight is minimal? Those questions matter for exactly the reason Caroline Bezengi is illustrating right now — when something goes wrong on a vessel like this, the safety net an OOW or engineer would normally assume exists may simply not be there.

Test Your Knowledge

Think you've got this covered? Put it to the test in Crew Connect's free Knowledge Checker — try a quick MARPOL/compliance round and see how you score.

Related Reading

• Wind Orca / BG Orange – another developing environmental incident covered from confirmed facts only
• This week's full regulatory roundup