{"id":1006,"date":"2026-10-15T03:33:52","date_gmt":"2026-10-15T03:33:52","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/singapore-confirms-gfs-pride-sank-and-gfs-giselle-took-a-hormuz-hit\/"},"modified":"2026-10-15T03:34:53","modified_gmt":"2026-10-15T03:34:53","slug":"singapore-confirms-gfs-pride-sank-and-gfs-giselle-took-a-hormuz-hit","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/singapore-confirms-gfs-pride-sank-and-gfs-giselle-took-a-hormuz-hit\/","title":{"rendered":"Singapore confirms GFS Pride sank and GFS Giselle took a Hormuz hit"},"content":{"rendered":"

The Maritime and Port Authority of Singapore published a 14 October statement naming two Singapore-registered container vessels, GFS Pride and GFS Giselle, as struck by unknown projectiles while transiting the Strait of Hormuz. The flag-state product dates the Pride hit to 13 October and the Giselle hit to 14 October, both in Singapore time. GFS Pride sustained damage and a fire on board and has since sunk. All 21 crew members were safely evacuated. No injuries have been reported. GFS Giselle sustained hull damage and arrived under its own propulsion at a safe anchorage. All 22 crew members are safe, with no injuries reported. MPA said there are no Singaporeans on board either ship, that it is in contact with the vessels’ management company, and that it is monitoring the situation closely.<\/p>\n

This is a flag-state naming of two feeder hulls, not a UKMTO warning and not a JMIC numbered update. It is not a rewrite of Tuesday’s dedicated Warning 170-26 unnamed Hormuz container ship or of Wednesday’s dedicated Warning 172-26 and Warning 173-26, which remain unnamed 50,000-tonne inbound and 19,000-tonne outbound container Attacks that continued on passage with minor damage and no casualties. Do not assign GFS Pride or GFS Giselle to those numbered PDFs. Do not brief Wednesday as UKMTO naming a Singapore liner, as a confirmed mine, or as a Hormuz reopen.<\/p>\n

What Singapore actually printed<\/h2>\n

MPA’s immediate-release note, dated Singapore, 14 October 2026, is six numbered paragraphs. Paragraph 1 is the information line: two Singapore-registered container vessels, GFS Pride and GFS Giselle, were reportedly struck by unknown projectiles while transiting the Strait of Hormuz on 13 and 14 October 2026 (Singapore Time), respectively. Paragraph 2 is the Pride outcome: damage, fire on board, and the ship has since sunk; 21 crew evacuated; no injuries reported. Paragraph 3 is the Giselle outcome: hull damage; arrived under its own propulsion at a safe anchorage; 22 crew safe; no injuries reported. Paragraph 4 states there are no Singaporeans on board both vessels. Paragraph 5 is the management contact and monitoring line. Paragraph 6 is the legal line. MPA is deeply concerned about the continued attacks on commercial shipping in the Strait of Hormuz, including the latest incidents involving two Singapore-registered vessels. It calls the attacks unprovoked, unjustifiable, and a breach of international law, and says all actions affecting international shipping must fully comply with international law, in particular the United Nations Convention on the Law of the Sea, and must not endanger the safety of seafarers and ships at sea.<\/p>\n

The statement does not print IMO numbers, a projectile type, a fire compartment, an attacker, a wreck position, a pollution volume, a cargo count, a service string, or the nationality of the 43 seafarers. It does not say whether Pride was inbound or outbound. It does not name the safe anchorage that Giselle reached. It does not print general average, salvage, or a class note. Stay with those blanks. BBC, Channel News Asia and Loadstar restated the MPA lines on 14 October. They are newspaper colour on the same flag-state product, not a second primary.<\/p>\n

The wreck warning is a separate instrument<\/h2>\n

The Hydrographer of Pakistan issued NAVAREA IX 373\/26 at 141045 UTC on 14 October for the Strait of Hormuz, charts BA 3172 and Oman charts OM302, OM509 and OM1219. The text reports commercial vessel GFS Pride sunk with floating containers in 26-16.8N 056-08.6E, approximately 4 nautical miles northwest of Ras Shaykh Masud, and cautions mariners. It cancels NAVAREA IX 371\/26. That is a wreck-and-debris product. It is not MPA’s crew line, and it is not a UKMTO Attack PDF. Masters transiting the southern Omani corridor now have a named wreck, a named position, and a floating-container caution on a current NAVAREA. IMO’s highlighted-incidents board, as at 14 October, prints GFS Pride, IMO 9349045, dated 13 October, Strait of Hormuz, sunk, no pollution, and GFS Giselle, IMO 9704661, dated 13 October, 6 nautical miles from the coast of Oman, damaged, no pollution. The IMO dates sit on the UTC side of MPA’s Singapore-time split. They do not convert either hull into a numbered UKMTO product. The dedicated 14 October IMO-board piece on this desk carries the wider 113-count; this file stays with the flag-state naming and the wreck warning.<\/p>\n

Iran’s Revolutionary Guard Corps navy said on 14 October that a cargo ship sank after striking a naval mine on an unauthorised route in the Strait of Hormuz, and that it was the first time Iran had reported a ship sinking after hitting a mine during the war. AP carried that line the same day. MPA printed unknown projectiles, not mines. UKMTO has not issued a mine product against GFS Pride. Do not collapse the IRGC mine claim onto Singapore’s projectile line. Do not brief a confirmed minefield in the TSS on the back of that statement.<\/p>\n

Open-register colour, not a class survey<\/h2>\n

Open-register colour only on GFS Pride: IMO 9349045, MMSI 563115400, call sign 9V6902, Singapore, container ship, built 2008, about 222 by 30 metres, about 28,340 gross tons and 39,446 deadweight, about 2,824 TEU on the GFS fleet list. VesselFinder’s last public AIS before the wreck warning was on the order of 11 days stale, last port Fujairah anchorage on 3 October, draught about 11.9 metres. That is tracker colour, not a class survey and not an MPA position. Loadstar placed Pride on a Khor Fakkan\u2013Fujairah\u2013Karachi service and said the ship had been due in Khor Fakkan on Friday. Reuters\/gCaptain identified the United Arab Emirates-based manager as GFS Ship Management FZE and said the company could not be immediately reached for comment. Those lines are industry colour. They are not in the MPA note.<\/p>\n

Open-register colour only on GFS Giselle: IMO 9704661, MMSI 566456000, call sign 9V2812, Singapore, container ship, built 2015, about 240 by 37 metres, about 44,887 gross tons and 54,117 deadweight, about 4,350 TEU on Flexport Atlas and 4,400 TEU on the GFS fleet list. VesselFinder’s last public AIS was on the order of 7 days stale, destination Fujairah, draught about 12.6 metres. Loadstar placed Giselle on a Fujairah\u2013Khor Fakkan\u2013Nhava Sheva service, also due Khor Fakkan on Friday, and noted that Abu Dhabi-based AD Ports owns 81 per cent of Global Feeder Shipping after the 2018 Simatech liner acquisition. Stay with MPA’s hull-damage and own-propulsion snapshot. Do not invent a TEU cargo count, a reefer loss, or a named refuge berth.<\/p>\n

Safeen Prestige, IMO 9593517, remains the dedicated March sink on this tape, printed on the IMO board as sunk with an oil slick detected. Reuters\/gCaptain’s 14 October analysis treating GFS Pride and Cape Dao as the second and third vessels to have sunk since 28 February is newspaper colour against that earlier named wreck. Cape Dao’s delayed sinking is wrap on the dedicated 14 October IMO-board piece, not this flag-state file. Do not add Pride’s 21 evacuated crew to any missing-seafarer tally. MPA printed no injuries.<\/p>\n

Operational implications<\/h2>\n

The Hormuz threat is no longer a tanker-only briefing item for this week. UKMTO’s Monday cluster already included an inbound container Attack on Warning 167-26. Tuesday’s dedicated 170-26 was an unnamed container. Wednesday’s dedicated 172-26 and 173-26 were unnamed container Attacks that continued. Singapore has now put a flag, two named hulls, a fire, a sink, a wreck position, and 43 seafarers onto that same week. Feeder operators on the Khor Fakkan, Fujairah, Karachi and western-India strings are inside the same projectile geometry as the VLCC shuttle. A master’s pack that still treats container ships as a residual risk behind tanker routing will under-brief the current week.<\/p>\n

The wreck is a navigation problem as well as a casualty file. NAVAREA IX 373\/26 puts floating containers at 26-16.8N 056-08.6E, about 4 nautical miles northwest of Ras Shaykh Masud, on the southern corridor charts. That is inside the Musandam approaches, not a far-field Gulf of Oman note. Night transits, restricted-visibility transits, and any AIS-off routing through that box now carry a named debris field. CSOs should put the NAVAREA on the passage plan beside BMP and the current JMIC note, which remains Update 104, ICOD 111500 UTC 11 October, Hormuz SEVERE. Update 104’s information cut-off sits before these 13\u201314 October container files. Do not replace it with the MPA statement.<\/p>\n

Do not recast Wednesday as a UKMTO naming of GFS Pride or GFS Giselle, a confirmed IRGC mine, a rewrite of Warning 170-26, 172-26 or 173-26, a JMIC Update 105, or a Hormuz reopen. UKMTO 172-26 remains a time-late 13 October 1640 UTC unnamed 50,000-tonne inbound container, minor damage, no casualties, continued on passage. UKMTO 173-26 remains a time-late 13 October 1700 UTC unnamed 19,000-tonne outbound container, minor damage, no casualties, continued on passage. Pride sank. Giselle reached a safe anchorage under its own power. Those outcomes do not match the continued-on-passage lines. Leave the numbered PDFs unnamed.<\/p>\n

What Operators Should Note<\/h2>\n