DroneLedger

Maritime attack

Chios Lion: Chios Lion was damaged in a reported drone-boat assault on 15 July 2024; the Houthis claimed responsibility.

Red Sea, off Hodeidah · 15 Jul 2024 · event date · exact location not established

Chios Lion was damaged in a reported drone-boat assault on 15 July 2024; the Houthis claimed responsibility. A subsequent satellite-based report described an oil slick in the region, but did not establish which vessel caused it or whether the attack caused it. [1]

Drone presence is reported. Consequences are reported. A party has claimed responsibility.

Drone presenceReported[1]
ImpactReported[1]
AttributionClaimed[2]

DroneLedger editorial team, publisher and editor responsible for this project.

AI-assisted editorial source review. This label records the editorial workflow, not a personal check of every source or sentence. Method and corrections

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

AI-assisted editorial source review · 02 Nov 2026 · Dossier updated 02 Nov 2026

You are viewing revision 2 as published on 02 Nov 2026. The dossier text, evidence states, claims and sources of this revision are fixed; catalogue context such as cost estimates is not shown here. View the current version

What do we know now?

Chios Lion was damaged in a reported drone-boat assault on 15 July 2024; the Houthis claimed responsibility. A subsequent satellite-based report described an oil slick in the region, but did not establish which vessel caused it or whether the attack caused it. The vessel manager separately described small damage and an unharmed crew.

Facts at a glance
Drone type
  • No named drone type is recorded in this dossier.
Hit / damaged
  • According to The Maritime Executive, citing Chios Lion master, The master reported light damage
  • According to gcaptain.com, citing Stealth Maritime via Bloomberg, The manager described small damage and an unharmed crew
  • According to The Maritime Executive, citing Vessel master via maritime authorities, The earlier master account reported light damage
Human consequences
  • According to The Maritime Executive, citing Chios Lion master via authorities, The master’s account reports a safe crew
Who reported what
Source families
  • 3 source families are recorded; republication is not independent confirmation

Further details are not known from the cited sources.

Timeline

Three clocks, one reading line

Shared calendar-day axis, from left to right. Bars mark days or reporting windows, not durations. Publication and revision clocks are not event clocks. Missing clocks remain unknown; the table gives all available precision and source links. The plot follows recorded calendar dates; time zones may differ. It establishes neither within-day order nor causality.

Three clocks, one reading line
TrackRecorded date / time
1 · Event
  • · Calendar day; time unknown
2 · Source publication
3 · Dossier revisions

What remains uncertain?

  • Was a drone established? A published investigation or identification could resolve this.
Check the evidence
Source passage
  • CENTCOM, relayed by The Maritime Executive · “confirmed the attack by a drone boat” The Maritime Executive
  • Chios Lion master · “the ship was “lightly damaged,”” The Maritime Executive
  • Houthi military spokesperson, relayed by Reuters · “with ballistic missiles, drones and booby-trapped boats” gcaptain.com
  • Reuters / JMIC · “Liberia-flagged oil tanker Chios Lion” gcaptain.com
  • Chios Lion master via authorities · “crew was safe” The Maritime Executive
  • Stealth Maritime, relayed by Bloomberg · “a small amount of damage was caused to the vessel and the crew is unharmed” gcaptain.com
  • Bloomberg reporting · “It wasn’t clear which vessel caused the spill” gcaptain.com
  • Vessel master, via maritime authorities · “lightly damaged” The Maritime Executive

Claims and evidence

3 sources · 7 original statements

Sources that repeat the same original statement count once: a number of articles is not a number of independent confirmations.

ClaimOriginal sourceAssessment
Drone

CENTCOM identified a drone boat in the relayed report.

[1]
Source passage
“confirmed the attack by a drone boat”

Passage checked word for word against the source on 28 Oct 2026.

CENTCOM, relayed by The Maritime Executive via The Maritime ExecutiveSupports the report

Source read in full; this claim retains its original source family. No independent technical verification implied.

Impact

The master reported light damage.

[1]
Source passage
“the ship was “lightly damaged,””

Passage checked word for word against the source on 28 Oct 2026.

Chios Lion master via The Maritime ExecutiveSupports the report

Source read in full; this claim retains its original source family. No independent technical verification implied.

Attribution

The Houthis claimed a mixed-weapon assault.

[2]
Source passage
“with ballistic missiles, drones and booby-trapped boats”

Passage checked word for word against the source on 28 Oct 2026.

Houthi military spokesperson, relayed by Reuters via Reuters via gCaptainSupports the report

Source read in full; this claim retains its original source family. No independent technical verification implied.

Context

The cited source records the vessel identity, type or flag.

[2]
Source passage
“Liberia-flagged oil tanker Chios Lion”

Passage checked word for word against the source on 28 Oct 2026.

Reuters / JMIC via Reuters via gCaptainSupports the report

Historical vessel detail; no position or current vessel information.

Impact

The master’s account reports a safe crew.

[1]
Source passage
“crew was safe”

Passage checked word for word against the source on 28 Oct 2026.

Chios Lion master via authorities via The Maritime ExecutiveSupports the report

Literal historical source detail; uncertainties elsewhere in the dossier remain.

Impact

The manager described small damage and an unharmed crew.

[3]
Source passage
“a small amount of damage was caused to the vessel and the crew is unharmed”

Passage checked word for word against the source on 02 Nov 2026.

Stealth Maritime, relayed by Bloomberg via Bloomberg via gCaptainSupports the report

Original contribution is attributed; shared official or party origins are not independent corroboration of every claim.

Context

The satellite report does not establish which vessel caused the slick.

[3]
Source passage
“It wasn’t clear which vessel caused the spill”

Passage checked word for word against the source on 02 Nov 2026.

Bloomberg reportingSupports the report

Original contribution is attributed; shared official or party origins are not independent corroboration of every claim.

Impact

The earlier master account reported light damage.

[1]
Source passage
“lightly damaged”

Passage checked word for word against the source on 02 Nov 2026.

Vessel master, via maritime authorities via The Maritime ExecutiveSupports the report

Original contribution is attributed; shared official or party origins are not independent corroboration of every claim.

Source genealogy

Grouped by recorded original statement, not by publisher. Unmapped sources have unknown dependency; linked statements may also share an earlier origin. This is not an independence score.

  1. CENTCOM, relayed by The Maritime Executive
    • The Maritime Executive: Chios Lion master and authorities [1] · Relayed statement
  2. Chios Lion master / Chios Lion master via authorities
    • The Maritime Executive: Chios Lion master and authorities [1] · Relayed statement
  3. Houthi military spokesperson, relayed by Reuters
    • Reuters via gCaptain: Houthi claim on Chios Lion and Bentley I [2] · Relayed statement
  4. Reuters / JMIC
    • Reuters via gCaptain: Houthi claim on Chios Lion and Bentley I [2] · Relayed statement
  5. Stealth Maritime, relayed by Bloomberg
    • Bloomberg via gCaptain: regional oil-slick analysis and manager response [3] · Relayed statement
  6. Bloomberg reporting
    • Bloomberg via gCaptain: regional oil-slick analysis and manager response [3] · Direct account
  7. Vessel master, via maritime authorities
    • The Maritime Executive: Chios Lion master and authorities [1] · Relayed statement
Show source graph

Left: publishers; right: recorded original statement. Converging lines show shared origin, not publication order. Dashed nodes have unknown dependency.

Read with a source omitted

Reading aid: switch off a source or family to inspect the remaining visible support below. Evidence status is not recalculated.

How to read this table

Reading aid only. Switch off a source or its recorded family to inspect the remaining visible support for exact claim texts. Evidence status is not recalculated. Shared wording or a shared family does not prove independence. Only recorded links labelled “supports” count here; context and contradiction links are not support. The dossier itself is unchanged.

Claim → supporting sources · recorded links
ClaimSupporting sourcesVisible support
CENTCOM identified a drone boat in the relayed report.[1]Support remains visible
The master reported light damage.[1]Support remains visible
The Houthis claimed a mixed-weapon assault.[2]Support remains visible
The cited source records the vessel identity, type or flag.[2]Support remains visible
The master’s account reports a safe crew.[1]Support remains visible
The manager described small damage and an unharmed crew.[3]Support remains visible
The satellite report does not establish which vessel caused the slick.[3]Support remains visible
The earlier master account reported light damage.[1]Support remains visible

What we know

The master reported light damage and a safe crew. The manager later described small damage but did not answer whether the tanker was leaking. A regional satellite-observed slick is not a measured spill volume from this ship.

The earlier maritime report relays the master and naval authorities; the Houthi claim remains a party claim. Bloomberg adds its own manager contact and reporting on satellite interpretation by PAX and SkyTruth. These are separate original contributions, without independent physical inspection or established ship-to-slick causation. No images or vessel positions are republished.

Data
No structured detail recorded
Fell near · Intercepted (claimed)

What remains unknown

The complete damage, any leaked quantity, and whether the observed slick came from this vessel remain unresolved. A ship-specific environmental or liability finding is not established by the satellite report.

The Houthis claimed responsibility, as relayed in the cited reporting; this does not independently establish the operator. [2]

How the story changed

  1. Chios Lion was damaged in a reported drone-boat assault on 15 July 2024; the Houthis claimed responsibility. [1]

  2. Bloomberg reports a regional oil slick in satellite imagery and a manager response, while explicitly leaving its vessel of origin and connection to an attack uncertain. [3]

Original sources (3)

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

1The Maritime Executive: Chios Lion master and authorities16 Jul 2024 · source family: Ukmto2Reuters via gCaptain: Houthi claim on Chios Lion and Bentley I16 Jul 2024 · source family: Houthi military media3Bloomberg via gCaptain: regional oil-slick analysis and manager response18 Jul 2024 · source family: Bloomberg

Editorial changes

  1. Revision 2 · 02 Nov 2026Added the later satellite-slick and vessel-manager account while retaining the uncertainty of causation and spill quantity.
  2. Revision 1 · 28 Oct 2026Curated dossier created after checking the cited sources line by line.

Cite this dossier

Permanent page · Revision 2

Chicago

DroneLedger editorial team. “Chios Lion: Chios Lion was damaged in a reported drone-boat assault on 15 July 2024; the Houthis claimed responsibility..” Dossier chios-lion-drone-boat-red-sea-2024-07-15, revision 2, updated 02 Nov 2026. https://droneincidents.com/incident/chios-lion-drone-boat-red-sea-2024-07-15/v2/

APA

DroneLedger editorial team. (02 Nov 2026). Chios Lion: Chios Lion was damaged in a reported drone-boat assault on 15 July 2024; the Houthis claimed responsibility. (Dossier chios-lion-drone-boat-red-sea-2024-07-15, revision 2). https://droneincidents.com/incident/chios-lion-drone-boat-red-sea-2024-07-15/v2/

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

Cite this version

Maker
DroneLedger editorial team
ID
chios-lion-drone-boat-red-sea-2024-07-15
Revision or edition
2
Release
20261109T002636372024-fb099f
Publication date
02 Nov 2026
Accessed
09 Nov 2026
Permanent URL
https://droneincidents.com/incident/chios-lion-drone-boat-red-sea-2024-07-15/v2/
Hashed file
JSON · SHA-256 06fd575dd5b57e13b5f772fd6bc812ca8c7fee66a90aea2ac8507e6d9721355e

Dataset DOI for this exact version: Not yet in a DOI snapshot · DOI binding manifest

Dataset DOI (series, not this revision): 10.5281/zenodo.23345422

DroneLedger editorial team. Chios Lion: Chios Lion was damaged in a reported drone-boat assault on 15 July 2024; the Houthis claimed responsibility.. ID chios-lion-drone-boat-red-sea-2024-07-15; revision or edition 2; release 20261109T002636372024-fb099f; published 02 Nov 2026. https://droneincidents.com/incident/chios-lion-drone-boat-red-sea-2024-07-15/v2/ Accessed 09 Nov 2026. SHA-256 06fd575dd5b57e13b5f772fd6bc812ca8c7fee66a90aea2ac8507e6d9721355e (https://droneincidents.com/data/citations/incident/chios-lion-drone-boat-red-sea-2024-07-15/r2/06fd575dd5b57e13b5f772fd6bc812ca8c7fee66a90aea2ac8507e6d9721355e/data.json). Not yet in a DOI snapshot.

Citation uses the English reference edition. Access date is the UTC date when this page was built; change it to your consultation date when reusing the citation.

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