Skip to content
Briefings are running a touch slower this week while we rebuild the foundations.See roadmap
European Tech Sovereignty
17MAY

Pentagon Sent Congress Stale Casualty Data

2 min read
14:28UTC

The Intercept reported 520 or more US service members wounded, citing Pentagon sources, against CENTCOM's official figure of 303. CENTCOM sent Congress a three-day-old statement that excluded the Prince Sultan Air Base attack entirely.

TechnologyDeveloping
Key takeaway

CENTCOM's 72 per cent casualty undercount to Congress shapes war-funding votes with deliberately incomplete information.

The Intercept reported on 3 April that 520 or more US service members have been wounded in Operation Epic Fury, citing multiple Pentagon sources. CENTCOM's official figure sent to Congress was 303. The gap is 72 per cent. The statement sent to Congress was three days old and excluded the Prince Sultan Air Base attack of 27 March entirely.

The Prince Sultan attack wounded 12 US troops and destroyed a KC-135 tanker and an E-3 Sentry AWACS . Excluding it from the congressional submission is not an administrative oversight: Prince Sultan was the largest single US base attack of the campaign and the proximate cause of the EA-37B Compass Call's emergency pre-IOC deployment. Congress should be informed of precisely this kind of event when asked to support a war.

Official US KIA stood at 15 as of Day 34, up from 13 on Day 29 . The wounded count matters separately: wounded service members represent a sustained operational cost, covering medical evacuation, personnel pipeline replacement, and long-term veterans care. A 72 per cent undercount understates that cost substantially.

The Pentagon's $200 billion war supplemental faced Republican resistance without formal submission as of 31 March . Congressional members voting on that request are working from casualty data that the Pentagon's own sources describe as incomplete. The accountability gap is not merely statistical; it shapes the legislative arithmetic of the war.

Deep Analysis

In plain English

An independent human rights organisation says 7,300 people have been killed in Iran over 34 days. Iran's government says 1,937. The gap is not unusual in wars — governments routinely undercount casualties. The 7,300 figure also includes people who died because hospitals were destroyed or because they could not get medicine, not just people killed directly by bombs.

Deep Analysis
Root Causes

The reporting gap reflects two structural causes.

On the Iranian side, the official count is a political instrument: acknowledging 7,300 deaths would create domestic pressure to negotiate that the regime cannot afford. On the independent monitor side, Hengaw's overdue publication schedule (the 9th report was described as overdue) suggests either access restrictions or internal capacity constraints that may have delayed capturing deaths that occurred over a broader window than a single reporting period.

Escalation

The IRGC's documented use of civilian structures (schools, dormitories, mosques) as military positions has direct legal consequences. It simultaneously provides CENTCOM with a potential IHL defence for strikes on those structures and opens Iran to violations of Additional Protocol I obligations. The accountability track is now active on both sides.

What could happen next?
  • Consequence

    IRGC forces in civilian buildings gives CENTCOM a proportionality argument for strikes on those buildings, but documentation of that use must precede any strike to be legally defensible.

    Immediate · High
  • Risk

    If the Hengaw methodology is validated by a UN body, the casualty gap becomes a basis for a Security Council resolution demanding accountability — vetoed by Russia and China but diplomatically damaging.

    Short term · Medium
  • Meaning

    The 400-death increment in a single reporting period, despite 35 days of campaign, contradicts CENTCOM's claims of increasing precision and reduced collateral harm.

    Immediate · High
First Reported In

Update #57 · Bridge strike kills eight; Army chief fired

US Central Command· 3 Apr 2026
Read original
Causes and effects
This Event
Pentagon Sent Congress Stale Casualty Data
A 72 per cent gap between official and independently sourced casualty figures, sourced from inside the Pentagon itself, is not a rounding error. It is deliberate perception management directed at Congress at a moment of active war funding debate.
Different Perspectives
OpenForum Europe / open-source community
OpenForum Europe / open-source community
The EUR 350m Sovereign Tech Fund has no Commission host, no budget line, and no commissioner's name attached six weeks after the April conference, while Germany is already paying maintainers to staff international standards bodies. The CRA open-source guidance resolves contributor liability but leaves the financial-donations grey area open with the 11 September reporting clock running.
ASML / Christophe Fouquet
ASML / Christophe Fouquet
ASML's Q2 guidance miss of roughly EUR 300m below consensus reflects DUV revenue compression set by US export controls, not European policy. Fouquet said 2026 guidance accommodates potential outcomes of ongoing US-China trade discussions; a bipartisan US bill to tighten DUV sales further would accelerate the cross-subsidy thinning Chips Act II's equity authority is designed to address.
Anne Le Henanff / French G7 Presidency
Anne Le Henanff / French G7 Presidency
Le Henanff chairs the 29 May Bercy ministerial two days after Brussels adopts the Tech Sovereignty Package, making the G7 communique the first international read of the Omnibus enforcement split and CAIDA's scope. France's Cloud au Centre doctrine is already operational via the Scaleway Health Data Hub contract.
German federal government
German federal government
Berlin operationalises sovereignty through procurement mandates (the ODF requirement and the Sovereign Tech Standards programme) rather than waiting for Commission legislation. The Bundeskartellamt has still not received the Cohere-Aleph Alpha merger filing, leaving Germany's flagship AI champion in structural limbo six weeks after the deal resolved.
US Trade Representative
US Trade Representative
The USTR Section 301 investigation into EU digital rules closes with a 24 July 2026 final determination. CAIDA's public-sector cloud restriction sits within the criteria that triggered the 2020 Section 301 action against France's digital services tax, and the US has not signalled whether the Thales-Google S3NS arrangement resolves CLOUD Act jurisdiction concerns.
CISPE / Valentina Mingorance
CISPE / Valentina Mingorance
CISPE shipped its own pass-fail sovereignty badge in April to establish an industry-auditable floor the Commission could adopt. Whether CAIDA inherits the CISPE binary or the multi-tier SEAL approach will determine whether certification is enforceable by public contracting authorities or requires Commission discretion.