Skip to content
You can now search across every topic, entity and event.What's new
European Tech Sovereignty
4AUG

Saudi jets hit Iraq, citing Article 51

3 min read
10:16UTC

Riyadh sent aircraft over a neighbouring state for the first time in this war, invoking self-defence against drones that were all intercepted before they landed.

← Back to AI Act fines arrive, three states list no regulatorJump to analysis ↓
TechnologyAssessed
Key takeaway

Riyadh bombed a neighbour over drones that were all shot down, and has published no attribution.

The Saudi Armed Forces struck militia targets inside Iraq at 05:00 GMT on Wednesday 29 July "in coordination with United States Central Command", the Defence Ministry spokesman Maj. Gen. Turki al-Malki said in a statement carried by the Saudi Press Agency, The Kingdom's official state news agency 1. Riyadh invoked Article 51 of the UN Charter, the provision reserving a state's right of self-defence against an armed attack, and added that The Kingdom "does not seek escalation but will respond decisively to any aggression". CENTCOM said separately that it had struck "multiple terrorist logistics and weapons sites across eastern Iraq" 2.

The stated cause sits two days back. Saudi and Jordanian air defences intercepted drones aimed at Eastern Province oil facilities and at Riyadh on 27 July, launched from Iraqi territory according to Al-Malki . Nothing landed. Iraqi ground took drones of its own the same day, when strikes hit camps housing Iranian-Kurdish opposition fighters in the north . The Popular Mobilisation Forces (PMF), the Iraqi paramilitary umbrella formally folded into the state's security apparatus, put its own losses across the struck sites at 20 killed and 32 wounded 3. That figure is the PMF's own, and neither Baghdad nor Riyadh has confirmed it.

Article 51 turns on an armed attack, and the drones of 27 July were intercepted before any of them landed. Iraq's armed forces spokesman has demanded evidence that anything was launched from Iraqi ground, and none has been published 4. Iran-aligned Iraqi factions say they launched nothing and call the Saudi account a fabrication 5.

Both propositions can hold at once. Riyadh plausibly faces a northern launch axis it cannot police from its own airspace, and a strike on a neighbouring state, resting on unpublished attribution and answering attacks that did no damage, is a legal argument The Kingdom has not yet had to make in public. Until it does, every state on the Gulf littoral now has a live precedent for treating an intercepted drone as grounds to bomb the territory it came from.

Deep Analysis

In plain English

Saudi Arabia's air force bombed militia targets inside neighbouring Iraq, saying it was defending itself under a UN rule called Article 51. The group that lost people, the Popular Mobilisation Forces or PMF, is an Iraqi paramilitary group with strong ties to Iran. The PMF says 20 of its fighters died and 32 were wounded, though nobody outside the PMF has confirmed that count. Iraq's government was not the one under attack, so this raises the question of whether one country can bomb targets inside another without that country's permission.

Deep Analysis
Root Causes

Iraq's territory functions as a permissive launch zone because the Popular Mobilisation Forces (PMF) operate as a state-recognised paramilitary structure answerable to Baghdad in name but often directed by factions aligned with Tehran; this dual loyalty means strikes on PMF positions inside Iraq are simultaneously attacks on a nominal Iraqi government asset and a proxy of a foreign power.

Saudi Arabia's decision to act without an Iraqi request stems from the absence of any functioning air-defence coordination agreement between Riyadh and Baghdad, unlike the CENTCOM-Gulf state deconfliction lines that already existed before 29 July.

What could happen next?
  • Risk

    An unconfirmed casualty figure sourced only to the PMF itself may harden into an accepted death toll if no independent count from Baghdad or Riyadh follows.

  • Consequence

    A unilateral Saudi strike inside Iraq without a bilateral coordination framework increases the risk of a future strike hitting a target neither government intended.

Sources:Al Jazeera·Al Jazeera·Tasnim News
Mentions:Turkey →Saudi Arabia →Eastern Province →Iraq →Saudi Press Agency →Popular Mobilisation Forces (PMF) →CENTCOM (US Central Command) →UN Charter →Baghdad →Riyadh →Ankara →Article 51 →United States →Iran →Turki al-Maliki →
First Reported In

Update #164 · The pause ends, and the map moves west

Al Jazeera· 31 Jul 2026
Read original →
Causes and effects
Caused by
Riyadh's drones now come from Iraq
The Saudi and Jordanian interception of drones launched from Iraq (ID:5406) is the stated cause of the Saudi strike inside Iraq.
Occurred 26 Jul 2026
Read story →
Drones hit Kurdish camps in Iraq
Drones striking Iranian-Kurdish opposition camps in Iraq the same day (ID:5407) accompanied the Saudi strike into Iraq.
Occurred 26 Jul 2026
Read story →
This Event
Saudi jets hit Iraq, citing Article 51
A US ally has widened the war on its own initiative, on attribution it has not published, against attacks that caused no damage.
Led to
Baghdad cancels Riyadh visit over strike
Baghdad's cancellation of Zaidi's Saudi visit and NSC directives were a direct response to the Saudi strike inside Iraq.
Occurred 29 Jul 2026
Read story →
Different Perspectives
Germany (Bundeskartellamt)
Germany (Bundeskartellamt)
Germany's Bundeskartellamt declined to open antitrust proceedings against SAP, the company disclosed on 30 July, in the same fortnight the Commission's EUR 890m DMA fine against Google approached its 21 September compliance deadline. A German software champion cleared domestic scrutiny while an American platform faces enforcement, in the same regulatory season.
United States (USTR)
United States (USTR)
Washington's Section 301 investigation into EU digital enforcement, opened 24 July, had produced no Federal Register docket as of 4 August, even as Dell and 1,008 Nvidia GB200 NVL4 accelerators sit inside the EU's own sovereignty-branded MeluXina-AI build. The absent docket and the American hardware inside a European sovereignty project pull the same relationship in opposite directions.
UK government
UK government
The UK's Sovereign AI vehicle took a nine-figure equity stake in chip startup OLIX on 30 July, its fifth deal since April, while the Cabinet Office's 27 July fact sheet named no accounting officer for the GBP 1.1bn AI Hardware Plan. Whitehall is buying equity rather than capacity, inside a department mid-rename to Business, Innovation, Science and Trade.
Luxembourg government
Luxembourg government
Luxembourg is covering half of the newly disclosed EUR 80m contract value for MeluXina-AI, EuroHPC's Grand Duchy build, with Dell Technologies confirmed as supplying 1,008 Nvidia GB200 NVL4 accelerators, a hardware detail absent from the earlier project description. The disclosure means Luxembourg's national co-funding buys a facility built on American silicon under a European ownership badge.
European Commission
European Commission
The Commission activated its Article 101 fining power on 2 August while the Article 70 register it must keep current still showed a 26 September 2025 footer and blank rows for Denmark, Finland and Hungary. It issued no comment, though Article 70 puts the publication duty on Brussels, not member states.
China's Ministry of Commerce
China's Ministry of Commerce
Spokesperson He Yadong said on 16 July that Beijing and the Netherlands should let firms settle the Nexperia dispute through consultation, after a Dutch ministerial visit to Beijing. The conciliatory tone contrasts with the confrontational US trade response to the same fortnight's DMA enforcement.