GDELT CloudGDELT Cloud
Connected Situation / Through 2026-10-14

Houthi–Saudi Attacks and Airport Disruption

stories
40
events
47
entities
143
connections
40
Retained edition
Evidence so far on 2026-10-14 UTC · updated 2026-10-14 00:22 UTC · analysis as of 2026-10-13 15:29 UTCSign in for the live Situation ↗
Narrative

As-of analysis

Carried forward
Situation at a glance

On October 11, the Houthis targeted King Fahd International Airport in Dammam, while Saudi Arabia and its partners demanded that the Houthis halt attacks. [The Dammam Event lists zero fatalities and says none were reported.] The October 12 headline “Yemen's Houthis strike Riyadh airport again amid deadly Saudi attacks” and “Missile attack hits Riyadh airport, killing 13 as Trump weighs U.S. strikes” report attacks on Riyadh; “Projectile strikes Riyadh airport terminal again after fatal attack” describes a terminal strike and flight suspensions. On October 12, Saudi Arabia’s General Authority of Civil Aviation extended the Riyadh airport closure, and Saudi authorities’ Event described an extension cancelling 32 flights. Yemen’s Presidential Leadership Council demanded international action on October 11, while the Federal Aviation Administration warned U.S. airlines about Saudi flights. The October 12 Story “Yemen's Houthis and Saudi-led coalition trade strikes targeting Saudi airports” reports an exchange of strikes, and a coded Event that day says Saudi air defenses intercepted a ballistic missile aimed at Khamis Mushait.

Footnotes[15][11][1][2][3][10][14][13][17][5][16]
Assessment

The strongest directly specified attack Event here is the October 11 Dammam airport incident, not a coded Riyadh attack. Riyadh coverage instead gives conflicting casualty accounts: “Missile attack hits Riyadh airport, killing 13 as Trump weighs U.S. strikes” gives 13 killed, while a headline carried within “Yemen's Houthis strike Riyadh airport again amid deadly Saudi attacks” attributes one death and 11 injuries to Saudi authorities; the terminal-strike Story is linked to the latter as duplicate coverage. These accounts do not establish a settled toll. The airport closure and flight cancellations, official demands, warnings, and reported interception are distinct developments, but their sequence alone does not establish that one caused another. “Yemen's Houthis and Saudi-led coalition trade strikes targeting Saudi airports” reports an exchange of strikes directed at Saudi airports. Separate October 12 Stories report Saudi airstrikes in Sanaa/Yemen; the Events cited here do not independently code those reported strikes.

Footnotes[15][2][1][3][22][10][14][11][13][17][16][5]

Explanation originally captured 2026-10-13 · Evidence through 2026-10-14 UTC · Source edition sed_cda431356db0f3047fa3fa5106e68c83

What informs this explanation
  • Complete retained Story and Event membership
  • Daily reporting and coded-occurrence time steps
  • Event taxonomies, metrics, units, and denominators
  • Canonical Entities and recorded actor/target bindings
  • Typed reporting, membership, and incident edges
  • Changes against the preceding retained edition
  • Permitted macro, public-record, and asset facts only when they were retained with an explicit source and observation date
Quantitative

Evidence in numbers

This retained edition
  • Scope

    A 3-day Situation represented by 47 coded Events carried across 40 member Stories.

  • Coded activity

    The coded activity is led by IN02 · Transport Disruption (8) and 111 · Criticize or Denounce (7).

  • Prominent subjects

    Houthis, General Authority of Civil Aviation, and Donald Trump are prominent in the retained actor and relationship evidence.

  • Entity coverage

    143 canonical Entities are linked to this edition.

Metric coverage. 47 coded Events · 41 CAMEO+ · 6 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.

Magnitude3.5
min 1max 7
41 measured
Systemic importance0.14
min 0.05max 0.47
41 measured
Propagation potential0.32
min 0.23max 0.65
41 measured
Market sensitivity0.14
min 0.05max 0.6
41 measured

Dot = mean · shaded span = observed range · position uses each metric’s defined scale.

All 8 scores, distributions & definitions

How the coder scored the full retained Event set

47 coded events — 41 CAMEO+ (31 political) · 6 conflict

  • Significance · 470.31
    min 0.16max 0.56
  • Magnitude · 413.5
    min 1max 7
  • Systemic · 410.14
    min 0.05max 0.47
  • Propagation · 410.32
    min 0.23max 0.65
  • Market · 410.14
    min 0.05max 0.6
  • Goldstein · 37-2.4
    min -10max 7
  • Fatalities · 60
    min 0max 0
  • Confidence · 470.7
    min 0.28max 0.96

Quad class over those 37 events · Verbal Conflict 16 · Verbal Cooperation 13 · Material Conflict 7 · Material Cooperation 1. 10 sit outside POLITICAL, where Goldstein and quad class are undefined. The four CAMEO+ scores are over the 41 CAMEO+ events only; the 6 conflict events have no such column.

Significance

47 measured / 47 eligible · 0 missing · 0 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across all 47 events

Magnitude

41 measured / 41 eligible · 0 missing · 6 not applicable

score (0 to 10) · Event-level distribution, not a Situation risk score.

across the 41 of 47 events coded in the CAMEO+ family; the conflict family has no such column

Systemic

41 measured / 41 eligible · 0 missing · 6 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across the 41 of 47 events coded in the CAMEO+ family; the conflict family has no such column

Propagation

41 measured / 41 eligible · 0 missing · 6 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across the 41 of 47 events coded in the CAMEO+ family; the conflict family has no such column

Market

41 measured / 41 eligible · 0 missing · 6 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across the 41 of 47 events coded in the CAMEO+ family; the conflict family has no such column

Goldstein

37 measured / 37 eligible · 0 missing · 10 not applicable

score (-10 to 10) · Event-level distribution, not a Situation risk score.

across the 37 of 47 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics

Fatalities

6 measured / 6 eligible · 0 missing · 41 not applicable

reported people · Reports may overlap; these are Event-level reports, not an additive unique human toll.

across the 6 of 47 events that report a toll — the conflict family only, and never 0 on a CAMEO+ event

Confidence

47 measured / 47 eligible · 0 missing · 0 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across all 47 events

Metric definitions and limitations

This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.

Day by day3 reporting days · click a day to open or close it

2026-10-13from the recordslatest

Yemen’s Houthis threaten renewed strike on Riyadh airport

19 Stories and 23 coded Events (-2 / +9 against the day before). Widest coverage: Saudi-led coalition warns Houthi-held Sanaa oil site as Houthis threaten Aramco (122 articles). Recorded acting: Donald Trump, Houthis, IndiGo, Royal Jordanian.

19-2
Stories · vs day before
23+9
Events · vs day before
543
articles
The lay of the land

Situation timeline

Threads
All 3 daysarticlesstoriesevents
10-1110-1210-13
Loading Situation timeline…

What kind of event · 20 coded types

over 47 coded events on this edition

  • Political31
    • 111 · Criticize or Denounce7
    • 01 · Make Public Statement6
    • 02 · Appeal5
    • 1056 · Demand De-escalation of Military Engagement2
    • 13 · Threaten2
    • 041 · Discuss By Telephone1
    • 051 · Praise or Endorse1
Salient structure

What holds this Situation together

Selected from the complete retained edition

Key threads

  1. core
    AnalystHouthi attacks, Saudi responses, and airport disruption

    These Stories report attacks on Saudi airports and oil facilities, the Riyadh airport incident and disruption, and an exchange of strikes involving Yemen. The Dammam attack and Riyadh casualty accounts should remain distinct.

    These Stories report attacks on Saudi airports and oil facilities, the Riyadh airport incident and disruption, and an exchange of strikes involving Yemen. The Dammam attack and Riyadh casualty accounts should remain distinct.

    Footnotes[2][1][3][4][5][15]
  2. development
    AnalystDiplomatic, travel, and aviation responses

    These Stories describe official condemnation, travel advice, and aviation cautions alongside calls for renewed Gulf cooperation.

    These Stories describe official condemnation, travel advice, and aviation cautions alongside calls for renewed Gulf cooperation.

    Footnotes[6][7][9][8]

Key actors

  1. H
    AnalystHouthis

    The Houthis are the actor in the Dammam airport attack Event and the target of Saudi Arabia and partners’ demand to halt attacks.

    The Houthis are the actor in the Dammam airport attack Event and the target of Saudi Arabia and partners’ demand to halt attacks.

    Footnotes[18][15][11]
  2. GA
    AnalystGeneral Authority of Civil Aviation

    The General Authority of Civil Aviation is the source actor in the Event extending the Riyadh airport closure.

    The General Authority of Civil Aviation is the source actor in the Event extending the Riyadh airport closure.

    Footnotes[19][10]

Key Events

  1. contextAnalystHouthis target King Fahd International Airport in Dammam

    On October 11, the Houthis targeted King Fahd International Airport in Dammam; the Event lists zero fatalities, with none reported.

    On October 11, the Houthis targeted King Fahd International Airport in Dammam; the Event lists zero fatalities, with none reported.

    Footnotes[15]
  2. contextAnalystSaudi Arabia and partners demand Houthis halt attacks

    On October 11, Saudi Arabia and partners demanded that the Houthis halt attacks.

    On October 11, Saudi Arabia and partners demanded that the Houthis halt attacks.

    Footnotes[11]
  3. contextAnalystYemen's Presidential Leadership Council demands international action

    On October 11, Yemen's Presidential Leadership Council demanded international action.

    On October 11, Yemen's Presidential Leadership Council demanded international action.

    Footnotes[13]
  4. contextAnalystFederal Aviation Administration warns U.S. airlines about Saudi flights

    On October 11, the Federal Aviation Administration warned U.S. airlines about Saudi flights.

    On October 11, the Federal Aviation Administration warned U.S. airlines about Saudi flights.

    Footnotes[17]
  5. contextAnalystSaudi civil aviation authority extends Riyadh airport closure

    On October 12, the General Authority of Civil Aviation extended the Riyadh airport closure.

    On October 12, the General Authority of Civil Aviation extended the Riyadh airport closure.

    Footnotes[10]

Notable connections

Evidenced relationships involving significant participants beyond the central cast.

  1. The Houthis are the source actor in the Dammam airport attack. · recorded participationAnalystHouthis → Houthis target King Fahd International Airport in Dammam

    The Event binds the Houthis as its source actor.

    The Event binds the Houthis as its source actor.

    Footnotes[18][15]
  2. The Houthis are the target of Saudi Arabia and partners’ demand to halt attacks. · recorded participationAnalystHouthis → Saudi Arabia and partners demand Houthis halt attacks

    The Event binds the Houthis as the target of the demand.

    The Event binds the Houthis as the target of the demand.

    Footnotes[18][11]
  3. The General Authority of Civil Aviation is the source actor for the Riyadh airport closure extension. · recorded participationAnalystGeneral Authority of Civil Aviation → Saudi civil aviation authority extends Riyadh airport closure

    The Event binds the Authority as its source actor.

    The Event binds the Authority as its source actor.

    Footnotes[19][10]
  4. The closure Event is linked to “Houthis attack airports and oil facilities in Saudi Arabia.” · reporting linkAnalystSaudi civil aviation authority extends Riyadh airport closure → Houthis attack airports and oil facilities in Saudi Arabia

    The Event lists this Story as supporting coverage.

    The Event lists this Story as supporting coverage.

    Footnotes[10][4]
  5. The Dammam attack Event is linked to “Missile attack hits Riyadh airport, killing 13 as Trump weighs U.S. strikes.” · reporting linkAnalystHouthis target King Fahd International Airport in Dammam → Missile attack hits Riyadh airport, killing 13 as Trump weighs U.S. strikes

    The Event lists this Story as supporting coverage; its title names Dammam, while the Story headline names Riyadh.

    The Event lists this Story as supporting coverage; its title names Dammam, while the Story headline names Riyadh.

    Footnotes[15][2]
How a Situation is put together40 Stories · 47 Events · 40 membership connections · 720 graph edges

A retained time step

This edition freezes the complete served membership and analysis available through its UTC cutoff. Later repairs or identity changes do not rewrite what this edition showed.

Stories, Events, and cast

Stories are reporting clusters. Events are coded occurrences within that reporting. The cast contains 143 canonical people and organizations linked to the retained evidence.

Typed connections

Story-to-Event edges identify supporting reporting. Entity-to-Event edges identify recorded actor or target participation. Mentions and analytical roles stay visibly distinct from recorded participation.

Core, precursor, and continuation labels organize the reading. They do not by themselves establish causation. Collapsed graph groups and paginated evidence change presentation only; counts use the complete retained edition.