WW/PORTSTERMI

Filed 671W3M read

Explosion aboard Russian ship at Benghazi after suspected drone attack

Libya’s government says a suspected drone attack caused an explosion aboard a Russian vessel at Benghazi. Injuries were reported, but no deaths; the ship, cargo and operator were not identified.

By
Marcus Bennett
Filed
Length
671 words
Read
3 min
Suspected Drone Attack Caused Explosion On Russian Ship At Benghazi Port
Suspected Drone Attack Caused Explosion On Russian Ship At Benghazi Portanalogicus / pixabay

Key points05

  • Nov. 22: A preliminary Libyan investigation indicated a suspected drone attack caused an explosion aboard a Russian vessel at Benghazi.
  • The vessel had stopped in Benghazi to refuel and resupply before returning to Russia under maritime cooperation agreements.
  • Two medical sources reported injuries but no deaths; the injured count and nationalities remained unknown.
  • No group had claimed responsibility, and Russian authorities had not reacted immediately.
  • Port and naval-base warehouses were reported safe; normal operations awaited fire control and site security.

Libya’s eastern-based government said on Sunday, Nov. 22, that a preliminary investigation indicated a suspected drone attack caused an explosion aboard a Russian vessel docked at Benghazi, Libya’s eastern port. The government placed the explosion at the Benghazi naval base in eastern Libya, aboard the ship at the city’s port.

Two medical sources said people had sustained injuries but that no deaths had been reported; they could not immediately establish the number or nationalities of those hurt.

The vessel had stopped at Benghazi to refuel and resupply while heading back to Russia, under maritime cooperation agreements between Libya and Russia.

What does the incident mean for port and voyage operations?

The immediate commercial exposure is an interrupted Russia-bound port call and its associated refueling and resupply work. The government did not report a cargo delay, sailing cancellation, bunker shortage or diversion, leaving shippers and forwarders without evidence of a broader network disruption.

The government said port and naval-base facilities, including warehouses, had remained safe. Normal operations would resume once the fire was under control and the site secured, but authorities gave no duration, berth count, throughput reduction or cargo-release timetable.

The report identified no vessel name, operator, flag, cargo type, TEU capacity, tonnage or sailing schedule for the Benghazi ship. The available evidence therefore supports no defensible calculation of affected boxes, tons, $/FEU rates or fleet-capacity percentage.

For shippers, the unresolved issue is access to any cargo already aboard the vessel. The report did not say whether the ship had been secured, its holds inspected or its cargo released, although it reported the port’s warehouses as safe.

For carriers and forwarders, the missing sailing time and vessel identity prevent a measured disruption estimate. The report links the incident only to the vessel’s Russia-bound call, so it offers no basis for converting the event into a fleet-capacity change or market-rate movement.

What is confirmed, and what remains unproven?

The government based its account on a preliminary investigation and described the attack only as suspected. No organization had claimed responsibility, and Russian authorities had not reacted immediately, leaving both the perpetrator and the precise mechanism unconfirmed.

Those omissions do not disprove an attack. They do mean commercial planners cannot treat attribution, blast damage or the vessel’s condition as settled facts.

Libya’s eastern government condemned the suspected attack as a violation of sovereignty and a threat to maritime safety. It said it would pursue legal and diplomatic measures against anyone found responsible.

It stated: “The Libyan government will not allow Libyan ports, territory or territorial waters to be turned into an arena for settling scores or exporting international conflicts.”

Do the related reports identify the vessel?

Related coverage did not resolve those gaps. One item described the Arctic Metagaz as a stricken Russian LNG tanker anchored off Libya after a two-month odyssey, with its future uncertain.

Another concerned a Russian cargo ship hit by drones in the Baltic Sea off Finland, with its fire continuing through the night; a linked headline placed a Russian military-linked cargo ship in the Gulf of Finland after a suspected drone strike.

Nothing in that material established any of those vessels as the ship involved at Benghazi. Identifying the affected vessel, cargo or operator from those references would go beyond the reported facts.

What happens next?

The next checkpoint is operational rather than market-wide: the fire must be brought under control, the site secured, and investigators must establish the vessel’s identity, condition, cargo status and responsibility for the suspected attack.

Injury reporting must also become more precise; on Nov. 22, the count and nationalities of the injured remained unknown, while the government’s only stated timing trigger was fire control and site security.

Any rate or capacity impact will depend on how quickly the fire is controlled, the site secured and the vessel’s condition established; until then, a forecast of higher rates or reduced capacity would exceed the source.

Source: gCaptain

Share this article:

More from Marcus Bennett

Marcus Bennett

Show full bio

Senior reporter covering regulation, policy and their impact on Ocean and air freight, container shipping at Waybill Wire.

1,006 articles

Related05

  1. Russian cargo flights link Benghazi to Bamako six times in six weeks

  2. Container Ship Contship Jet Sinks Off Bulgaria After Triple Naval Drone Strike

  3. Drone Strikes Sink Second Ship Off Bulgaria as Sofia Points at Moscow

  4. Suspected Drone Strike Hits Second Merchant Ship Off Bulgaria in 24 Hours

  5. Two Tankers Ablaze off Romania, Seven Crew Missing as Drone Strikes Reach Danube Gateway

« Prev