Significance
19 measured / 19 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 19 events
Connected Situation / Through 2026-10-01
Flydubai Diversion and Regional Aviation Response
- stories
- 26
- events
- 19
- entities
- 54
- connections
- 26
Evidence so far on 2026-10-01 UTC · updated 2026-10-01 15:27 UTC · analysis as of 2026-10-01 04:28 UTCSign in for the live Situation ↗
Narrative
As-of analysis
Situation at a glance
On September 30, a Flydubai flight from Dubai to Tel Aviv diverted toward Saudi Arabia after a distress signal, as described in “Dubai–Tel Aviv flight diverts toward Saudi Arabia after distress signal.” Accounts of the cockpit episode differ: “Israel-bound passenger plane lands after pilots fight mid-flight” describes a fight, while “Pilot stabbed in cockpit fight as FlyDubai flight makes emergency landing in Saudi Arabia” reports a stabbing. Other reports characterized the episode as an attempted hijacking, and a passenger said the pilot tried to crash the flight; these are reported claims, not established findings. On September 30, the Israeli Air Force scrambled fighters after a Flydubai alert. Miri Regev asked the Shin Bet to halt Flydubai flights to Israel, while an Israeli transport minister sought a review of the aviation deal and urged Flydubai to halt Israel flights. A separate report said Emirates suspended Flydubai codeshare flights to Tel Aviv; that is distinct from a confirmed halt to Flydubai’s own service. Saudi Arabia rejected Israel’s request to send military planes, and EASA advised airlines to avoid parts of Saudi airspace. Benjamin Netanyahu met a passenger described as having subdued the Flydubai pilot.
Footnotes[1][6][3][10][2][13][11][12][14][7][16][4]Assessment
The diversion and the Israeli fighter scramble are distinct from the unresolved question of what happened in the cockpit. Reports describe a pilots’ fight, a stabbing, an attempted hijacking, and a passenger’s allegation that the pilot tried to crash the plane; the coded attempted-assault event has confidence 0.43. These sources do not establish a settled sequence or intent. The Israeli requests and calls to halt flights or review the aviation deal establish demands, not that Flydubai halted its own Israel service or that the agreement changed. Separately, a report says Emirates suspended Flydubai codeshare flights to Tel Aviv. Saudi Arabia’s refusal is a separate development. EASA’s warning about parts of Saudi airspace was reported amid Houthi attacks; the cited evidence does not tie the warning to the Flydubai diversion.
Footnotes[1][6][3][15][11][12][13][14][16][4]Explanation originally captured 2026-10-01 · Evidence through 2026-10-01 UTC · Source edition sed_bf1790da3cdc3f59e4044a5ebc961a61
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
- Scope
A 2-day Situation represented by 19 coded Events carried across 26 member Stories.
- Coded activity
The coded activity is led by 01 · Make Public Statement (6) and 051 · Praise or Endorse (2).
- Prominent subjects
Israeli Air Force, Shin Bet, and Benjamin Netanyahu are prominent in the retained actor and relationship evidence.
- Entity coverage
54 canonical Entities are linked to this edition.
Metric coverage. 19 coded Events · 19 CAMEO+ · 0 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.
Magnitude3.5
min 2max 7
Systemic importance0.1
min 0.03max 0.18
Propagation potential0.24
min 0max 0.38
Market sensitivity0.11
min 0.05max 0.6
Dot = mean · shaded span = observed range · position uses each metric’s defined scale.
All 7 scores, distributions & definitions
How the coder scored the full retained Event set
19 coded events — 19 CAMEO+ (16 political)
- Significance · 190.28min 0.17max 0.51
- Magnitude · 193.5min 2max 7
- Systemic · 190.1min 0.03max 0.18
- Propagation · 190.24min 0max 0.38
- Market · 190.11min 0.05max 0.6
- Goldstein · 16-1.4min -7.2max 3.4
- Confidence · 190.7min 0.35max 0.88
Quad class over those 16 events · Verbal Cooperation 9 · Verbal Conflict 6 · Material Conflict 1. No conflict-family event here, so nothing carries a fatality count — a missing column, not a toll of zero. 3 sit outside POLITICAL, where Goldstein and quad class are undefined.
Magnitude
19 measured / 19 eligible · 0 missing · 0 not applicable
score (0 to 10) · Event-level distribution, not a Situation risk score.
across all 19 events — every one of them CAMEO+
Systemic
19 measured / 19 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 19 events — every one of them CAMEO+
Propagation
19 measured / 19 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 19 events — every one of them CAMEO+
Market
19 measured / 19 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 19 events — every one of them CAMEO+
Goldstein
16 measured / 16 eligible · 0 missing · 3 not applicable
score (-10 to 10) · Event-level distribution, not a Situation risk score.
across the 16 of 19 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics
Confidence
19 measured / 19 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 19 events
This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.
Day by day2 reporting days · click a day to open or close it
2026-10-01from the recordslatest
Flydubai suspends some flights as El Al works to evacuate Israelis
9 Stories and 9 coded Events (-8 / -1 against the day before). Widest coverage: Knife attack on Flydubai flight near Tabuk prompts Israeli terror claim (578 articles).
- 9-8
- Stories · vs day before
- 9-1
- Events · vs day before
- 779
- articles
The lay of the land
Situation timeline
Threads
All 2 daysarticlesstoriesevents
09-3010-01
Loading Situation timeline…
What kind of event · 13 coded types
over 19 coded events on this edition
- Political16
- 01 · Make Public Statement6
- 051 · Praise or Endorse2
- 04 · Consult1
- 091 · Investigate Crime/corruption1
- 10 · Demand1
- 1042 · Policy Change1
- 105 · Demand That Target Yield1
Countries · where it happened
Countries · who is acting
Salient structure
What holds this Situation together
Selected from the complete retained edition
Key threads
- core
AnalystEmergency diversion and cockpit accounts
The diversion Stories describe one Dubai–Tel Aviv flight and report different details about the cockpit episode, including a fight and a stabbing. A separate Story reports that a second Flydubai flight returned to Dubai.
- development
AnalystIsraeli and Saudi response
The Stories connect the flight incident with Israeli calls to suspend Flydubai service and Saudi Arabia’s rejection of Israel’s request to send planes; those calls and that rejection are distinct actions.
- development
AnalystSaudi airspace advisory
The Story and linked Event describe EASA advising airlines to avoid parts of Saudi airspace; they do not establish a causal connection to the Flydubai diversion.
Key actors
- IA
- SB
- BN
Key Events
contextAnalystPassengers overpower attacker after pilot stabbing attempt
The Event codes an attempted assault on a pilot, with confidence 0.43.
The Event codes an attempted assault on a pilot, with confidence 0.43.
Footnotes[15]contextAnalystMiri Regev asks Shin Bet to halt flydubai flights to Israel
On September 30, Miri Regev asked the Shin Bet to halt Flydubai flights to Israel.
On September 30, Miri Regev asked the Shin Bet to halt Flydubai flights to Israel.
Footnotes[13]
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
Benjamin Netanyahu was the actor in the meeting with the passenger. · recorded participationAnalystBenjamin Netanyahu meets passenger who subdued Flydubai pilot → Benjamin Netanyahu
The Event identifies Benjamin Netanyahu as its actor.
The fighter-scramble Event is linked to the diversion Story. · reporting linkAnalystIsraeli Air Force scrambles fighters after Flydubai alert → Dubai–Tel Aviv flight diverts toward Saudi Arabia after distress signal
The Event lists the diversion Story as supporting it.
The Saudi rejection Event is linked to the Story about Israel’s request to send planes. · reporting linkAnalystSaudi Arabia rejects Israel’s request to send military planes → Saudi Arabia rejects Israeli request to let planes collect passengers
The Event lists this Story as supporting it.
How a Situation is put together26 Stories · 19 Events · 26 membership connections · 207 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 54 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.