Tactical Screen · Current Operations Analysis · EP.01
What Operation Epic Fury Proved — and What It Didn’t
On February 28, 2026, the joint U.S.-Israel Operation Epic Fury demonstrated five principles of modern combined-arms warfare: intelligence-driven targeting, command-and-control decapitation, platform convergence on Lattice-type C2 architecture, precision strike doctrine, and information superiority. It was, by every conventional metric, a tactical success. Fifty thousand personnel. Two hundred-plus aircraft. Coordinated strikes across multiple Iranian defense nodes. The operation confirmed that Western air power — when integrated through autonomous C2 — remains qualitatively superior to any adversary air defense network in the region.
What it also proved, though less discussed in operational after-action reviews, was the following: 50,000 personnel operating in close proximity to Iranian CBRN facilities, with zero autonomous decontamination capability deployed.
The CBRN Scenario No One Planned For
Iran has publicly acknowledged chemical precursor stockpiles at facilities near Parchin and Fordow. The post-strike stabilization phase — airfield seizure, personnel recovery, equipment decontamination following proximity operations — required a CBRN decon capability that no platform in the joint force inventory could provide autonomously. The legacy answer: call forward a 30-person decontamination team, deploy 500 gallons of water per asset, and wait 5–6 hours per site. In a dynamic joint operation with 200+ aircraft returning to forward-based airstrips, that pipeline is not a limitation — it is a complete operational stoppage.
Based on the U.S. Army ADS RFI modeling framework and academic CBRN casualty projections from the Korean Defense Research Institute’s Ilsan simulation, the estimated casualty impact of a chemical release scenario involving 50,000 personnel without autonomous decon capability: approximately 1,800 casualties. With CBRN-CADS deployed: 260.
Five Tactical Principles — and the Sixth They Missed
Operation Epic Fury executed on five of the six principles of modern joint operations. The sixth — autonomous CBRN decontamination as a standard platform capability — was missing. This is not a criticism of operational planning. It is a procurement gap. The Autonomous Decontamination System (ADS) RFI was issued in 2024. CBRN-CADS responded with the only fully autonomous, zero-water, Lattice-integrated dry decon system in existence. The gap identified in Operation Epic Fury is the same gap the ADS RFI was designed to close. The question is timeline.
Anduril’s Lattice platform — used for real-time platform convergence and task assignment in Epic Fury-type operations — already hosts the world’s first CBRNDecontaminate Task Definition, developed in partnership with UAM KoreaTech. The architecture for integration exists. The gap is political will and procurement speed, not technology.
The Platform That Should Have Been There
CBRN-CADS (Close Air Decontamination Support) is designed specifically for the theater-scale decontamination scenario that Operation Epic Fury exposed. The three-tier MUM-T architecture — SwissDrones SDO 50 mothership carrying BLIS-D chamber, supported by micro-drone recon swarm — operates as a single-operator asset, deployable within the Lattice task framework. Detection in under 5 minutes. Decontamination in 20–30 minutes. Zero water. Zero external power. Blockchain DDC certification in 2–5 minutes.
Palantir Foundry’s real-time CBRN ontology — deployed alongside the operation’s data stack — would have provided contamination zone mapping, plume prediction, and decon asset tracking across all 200+ aircraft recovery sites simultaneously. The capability package was ready. The procurement decision was not.
From After-Action to Procurement Action
Every major operation in the last decade has confirmed the same finding in its CBRN after-action review: detection was too slow, decontamination required too many personnel, and certification was too paper-dependent for the operational tempo of modern joint warfare. Operation Epic Fury added a new data point to that record — at 50,000-personnel scale. The doctrine answer is not complicated. It is a deployment decision: field one CBRN-CADS platform per forward operating base, integrate it with the Lattice task framework already in use, and stop planning joint operations that treat CBRN response as an afterthought.
“Epic Fury was a precision operation in every dimension except one. The CBRN gap is the gap that turns a successful strike into a catastrophic aftermath. CBRN-CADS closes it.” — Jason Park, CEO & Founder, UAM KoreaTech
Leave a Reply