GFS Pride Sinks Near Hormuz: How to Identify Containers at Risk

Two Singapore-registered container ships operated by Global Feeder Shipping (GFS) were struck by unidentified projectiles near the Strait of Hormuz on 13 and 14 October. The 2,824 TEU GFS Pride caught fire and sank, while the 4,350 TEU GFS Giselle sustained hull damage before reaching a safe anchorage under its own power. Singapore’s Maritime and Port Authority (MPA) said on 14 October that all 43 crew members across the two vessels were safe.

For cargo owners, the immediate question is which containers were aboard the two vessels. A shipment record with no recent update cannot, on its own, distinguish cargo lost at sea from cargo delayed on a damaged ship or still waiting for a feeder connection. Teams need the vessel and voyage associated with each container’s latest confirmed movement, not just the vessel named on the original booking.

What Happened to GFS Pride and GFS Giselle

	GFS Pride	GFS Giselle
Size and build year	2,824 TEU, 2008	4,350 TEU, 2015
Published GFS service description	Khor Fakkan–Fujairah–Karachi	Fujairah–Khor Fakkan–Nhava Sheva
Incident and status reported 14 October	Struck 13 October; fire and sinking; floating containers reported nearby	Struck 14 October; hull damage; reached safe anchorage under own power
Crew	21, all safely evacuated	22, all safe

Sources: MPA, 14 October; The Loadstar, 14 October; Reuters reporting on floating containers. Service descriptions come from the GFS website as reported by The Loadstar; they do not establish the actual incident-voyage port calls or cargo aboard.

The cause of the sinking remains disputed. Maritime security sources cited by Reuters reported a projectile strike, while Iran’s Islamic Revolutionary Guard Corps Navy said an unnamed container ship had struck a mine on what it called an unauthorised route. That mine account has not been independently confirmed as the cause of the GFS Pride casualty. The bulk carrier Cape Dao also sank in the region this week following an earlier attack, underscoring the wider danger to commercial shipping.

GFS is an independent feeder operator in which AD Ports Group holds an 81% stake. The published service descriptions link UAE ports with Pakistan and India. But a service description is not a cargo manifest: it does not establish where either ship had called on the incident voyage, which mainline carriers bought slots, or whose containers were on board. Those facts require shipment- and voyage-level confirmation.

A Tracking Gap Cannot Tell You Whether Cargo Is Lost or Delayed

Carrier tracking systems record events such as gate-in, loading, discharge and gate-out. When a feeder is struck, the container record may remain at its last reported event while the vessel’s status changes dramatically. An outdated ETA or a missing movement update is a reason to investigate, but it does not establish what happened to the cargo.

The distinctions matter. A container confirmed aboard GFS Pride when it sank faces a potential total-loss claim, although individual container status still requires confirmation. Cargo aboard GFS Giselle may be delayed, damaged or rerouted; the MPA statement did not confirm the condition of individual containers. Boxes awaiting onward loading at a transshipment port present a third situation, even if their shipment timelines have also stopped advancing.

Start by separating the last confirmed container event from the actual vessel and voyage. A box already on a feeder might show a loading event; one waiting at the hub might show its last discharge. Compare those records with vessel movements, carrier or feeder-operator notices, and direct written confirmation before classifying cargo as lost or delayed.

The Vessel on Your Paperwork May Not Be the One at Sea

A transshipment booking can involve several vessels. Booking confirmations and bills of lading (B/Ls) differ in how much vessel detail they show, and an onward feeder can be assigned or changed after the original booking. Many carrier terms permit transshipment or substitution of vessels. Mainline carriers also purchase capacity on independent feeder services, so the ship physically carrying a container may be operated by a company the cargo owner has never dealt with directly.

This is a particular weakness when shipment teams rely on a single carrier portal or the originally published schedule. In a Tradlinx analysis of 508,055 ocean shipments, carrier ETAs were blank for 8.43% of shipments, and 30,929 of the 42,832 missing-ETA cases concerned an intermediate transshipment-port ETA. The study measured ETA gaps, not missing vessel assignments, but it illustrates how frequently visibility deteriorates around a handover.

Gulf contingency routings can involve additional handovers. As our 9 October review of Hormuz bypass routes explained, some workarounds still depend on feeder movements within the Gulf. The latest GFS incidents also bring attention to the vessels serving east-coast UAE gateways. A route marketed as a workaround still needs to be checked leg by leg.

If your team would only discover that a container was aboard a casualty vessel after a consignee asks, see how ops teams can match containers to the vessels carrying them across each leg.

Sunk or Damaged: The Claim Routes Differ

Once a container is linked to the affected vessel and voyage, the next steps depend on the cargo’s confirmed condition, the applicable B/L and the insurance policy. Preserve the event history and seek written confirmation from the contractual carrier. A casualty report establishes what happened to the vessel; it does not automatically settle the cargo claim.

	Vessel sank (GFS Pride)	Vessel damaged, at anchorage (GFS Giselle)
Cargo status	Cargo confirmed aboard at the time of sinking may be lost; individual exposure and any recovery remain to be established	Cargo condition unconfirmed; may be delayed, damaged or discharged at another port
Carrier liability	Where the Hague or Hague-Visby Rules apply, an act-of-war defence may be available; its application depends on the facts and governing terms	The same possible defence and other applicable carriage rules require case-specific assessment
Insurance	Notify cargo insurer; check whether war-risk cover applies and whether the incident falls within its insured perils	Notify cargo insurer; check war-risk cover for physical damage and separate any general average or salvage requirements from ordinary delay
Evidence to gather	Container number, last loading record, actual vessel/voyage, B/L, commercial invoice and carrier confirmation	Same records, plus inspection findings, any revised discharge arrangements and dates

General principles based on Hague-Visby Rules Article IV(2)(e), Institute Cargo Clauses (A) clause 6 and Institute War Clauses (Cargo) 1/1/2009. These provisions are not a determination of liability or cover for either casualty; individual contracts and policies control.

The war-risk exclusion applies to both incidents. Standard Institute Cargo Clauses (A) exclude loss caused by war or hostile acts, while separate Institute War Clauses can cover specified war-related physical loss or damage. Coverage depends on the cause, the policy wording and whether the relevant transit was insured. Standard Institute War Clauses also exclude loss or expense caused by delay, even when the delay follows an insured peril, subject to the wording’s general-average provision. A delayed container is therefore not necessarily an insured loss.

War cover has a timing condition that shipment events can help verify. Under clause 5.2 of the Institute War Clauses (Cargo) 1/1/2009, if goods are discharged at an intermediate port for onward carriage, cover generally continues for up to 15 days counted from midnight on the day the carrying vessel arrives there, subject to the clause’s conditions and any additional premium. After that period, cover reattaches when the goods are loaded onto the onward overseas vessel or aircraft. At the final port, cover generally ends upon discharge or 15 days after vessel arrival, whichever occurs first, subject to the stated exceptions. Check the arrival, discharge and onward-loading dates against the actual policy rather than calculating the period from discharge alone.

If general average or salvage is declared for GFS Giselle, the cargo-release process may involve security, including an insurer’s average guarantee and a cargo owner’s average bond; uninsured interests may be asked for a deposit. The requirements depend on the declaration and the adjuster’s instructions. See our general average explainer. Do not assume a declaration has been made without an operator or adjuster notice.

What to Check This Week

Identify the actual vessel and voyage. For shipments moving through Khor Fakkan, Fujairah and other affected Gulf connections, retrieve the container’s last loading and discharge events. Check the vessel/voyage against GFS Pride and GFS Giselle rather than relying on the initial booking vessel.
Get written confirmation. Ask the contractual carrier or forwarder whether each relevant container was loaded aboard either vessel, including through purchased feeder slots. Preserve the response for any insurance or contractual claim.
Investigate stalled records. Flag shipments with overdue events around affected feeder legs, but distinguish last-loaded from last-discharged containers. A missing update should trigger investigation, not an automatic loss classification.
Notify insurers promptly. For potentially affected cargo, give notice and confirm the policy’s war-risk provisions, territorial terms, notice requirements and any deadlines.
Check transshipment arrival and dwell. Record when the inbound vessel arrived, when the container was discharged and whether it has been loaded onward. Compare these dates with any applicable 15-day war-cover clause.
Monitor Giselle cargo instructions. Watch for revised discharge plans, inspection arrangements and any formal general average or salvage notice. Keep B/Ls, invoices and packing lists available.
Test another feeder hub. At a regular transshipment port such as Singapore or Colombo, check whether your team can identify the actual onward vessel for each waiting container before an exception occurs.