Incident archive

Claim	Original source	Assessment
Context gCaptain reports 14 October in Singapore time. Source passage [1] “was struck on October 14, Singapore time” Passage checked word for word against the source on 15 Oct 2026.	Singapore maritime authority via gCaptain	context only Attribution and original-source dependencies remain explicit; this quote does not establish drone involvement.
Impact The authority reported all 22 crew safe. Source passage [2] “all 22 crewmembers were safe” Passage checked word for word against the source on 15 Oct 2026.	Singapore maritime authority via The Maritime Executive	supports Attribution and original-source dependencies remain explicit; this quote does not establish drone involvement.

Original statements

Singapore maritime authority · repeated by sources [1][2]

Drones involved

The cited sources do not name the type of drone.

What we know

Hull damage was reported; the ship reached safety under its own power. Singapore’s authority reported all 22 crew safe.

Two newsrooms relay the same Singapore authority account. Their agreement does not independently establish the weapon.

What remains unknown

The event date follows 14 October Singapore time. IMO lists 13 October; the local event day remains unresolved without an exact time. No anonymous warning is assigned to this ship.

Operator attribution: Not established. Neither the attacker nor the weapon is established.

How the story changed

14 Oct 2026
Attack date as reported in Singapore time; not a demonstrated Oman-local date. [1]

Original sources (2)

2 source families · a count of sources is not a verification score

1gCaptain14 Oct 2026 · source family: gcaptain 2The Maritime Executive14 Oct 2026 · source family: maritime-executive

Editorial changes

Revision 1 · 15 Oct 2026Curated dossier created after checking the cited sources line by line.

Cite this dossier

DroneLedger. “GFS Giselle damaged in attack; drone involvement unclear.” Dossier gfs-giselle-hormuz-2026-10-14, revision 1, updated 15 Oct 2026. https://droneincidents.com/incident/gfs-giselle-hormuz-2026-10-14/

Cite the revision you used: later revisions may change evidence states.

Curated dossier · sources checked line by line on 15 Oct 2026
Dossier updated 15 Oct 2026

Editorial pack (print / PDF)Follow this dossier (feed)Earlier versions

Global drone incident observatory

What happened.What we actually know.

Drone incidents worldwide, each traced to its original sources. We keep what was reported apart from what is confirmed, and show how the story changed.

86dossiers

24countries

12with drone presence confirmed

Curated dossiers and automatic reports · no live detectionLatest source check 15 Oct 2026

Latest incidents

Full archive ↓

UA15 Oct 2026Drone report in Poltava region, UkraineDrone ReportedImpact Not establishedSingle source · unverified RU15 Oct 2026Drone report in Ryazan Oblast, RussiaDrone ReportedImpact ReportedSingle source · unverified RO15 Oct 2026Drone report in Tulcea County, RomaniaDrone ReportedImpact Not establishedSingle source · unverified RU15 Oct 2026Drone report in Rostov region, RussiaDrone ReportedImpact Not establishedSingle source · unverified

How to read a dossier

Every incident is judged on three separate questions. An airport can be confirmed closed while it is still unclear whether a drone was involved at all.

Was there a drone?

Drone presence: reported by a source, confirmed by explicit evidence, inconclusive after investigation, or debunked.

ConfirmedReportedInconclusiveDebunked

What was the impact?

Closures, diversions, damage or injuries, with their own evidence state. “Not established” means no source reports an impact.

ConfirmedReportedNot established

Who is responsible?

Attribution is never inferred. A party’s claim, a charge and a court finding are shown as different things.

Not establishedClaimedChargedConvicted

Incident archive

No matching dossiers

GFS Giselle damaged in attack; drone involvement unclear

GFS Pride lost after attack; drone involvement unclear

Drone strikes tanker Petro Dolphin off Sohar, Oman; two seafarers missing

Cape Dao lost after September strike; drone involvement unclear

Drone report in Poltava region, Ukraine

Drone report in Ryazan Oblast, Russia

Drone report in Tulcea County, Romania

Drone report in Rostov region, Russia

Authorities report drone strike on fishing boat off Sirik

Drone report in Lutsk, Ukraine

Regional authorities report three dead and six injured after drone attack in Kropyvnytskyi

Drone report in the Black Sea, off Romania

Drone report in Ryazan Oblast, Russia

Drone report in Moscow, Russia

Drone wave reported in Ukraine

Drone report in Balakovo, Russia

Police report five civilians injured in El Queremal drone attack

Drone report in Lutsk, Ukraine

Drone wave reported in Tula Oblast, Russia

Possible drone reports disrupt flights in Nuremberg

Drone wave reported in Kaluga Oblast, Russia

Drone report in Zhukovka, Russia

Drone report in Riyadh, Saudi Arabia

Drone report in Kharkiv region, Ukraine

Drone report in Pavlohrad, Ukraine

Drone report in Rivne, Ukraine

Drone wave reported in Russia

Drone report in Kyiv, Ukraine

Cargo ship Azov Concord sinks off Krapets, Bulgaria, after drone attack

Drones strike cargo ship Chelsea 3 off Byala, Bulgaria; crew of 15 rescued