By Robbin Laird
The kill web concept, which Ed Timperlake and I have been developing and writing about for more than a decade, is fundamentally about replacing the linear kill chain with a distributed, interactive combat architecture. Rather than sequencing effects through a fixed hierarchy of platforms, the kill web operates through interlocking nodes, sensors, shooters, decision-makers, and enablers , that can reconstitute targeting solutions dynamically and faster than an adversary can adapt.
What has distinguished Admiral Brad Cooper’s career is that he has been building and operating kill webs before the term became fashionable. His trajectory from fifth-generation airpower operations to the creation of Task Force 59, and then to command of U.S. Central Command, is the story of a practitioner who has shaped the concept through operational use rather than theoretical advocacy.
The central shift that kill web thinking demands is deceptively simple to state but enormously difficult to execute: the value of any platform is not what it can do alone but what it contributes to the wider combat network. A fifth-generation aircraft is not primarily a strike asset. It is a sensing and decision node that happens to carry weapons. An unmanned surface vessel is not a replacement for a frigate. It is a persistent presence in the sensing grid that makes manned platforms more lethal by cueing them to where they need to go.
Admiral Cooper has operated inside this logic at every command level.
As Commander of Expeditionary Strike Group 7 in Japan, Cooper led a landmark moment in U.S. naval history overseeing the first operational deployment to integrate the F-35 into amphibious and maritime operations in the Western Pacific. This was not simply a technology introduction; it was a strategic inflection point, as fifth-generation capability was woven into the fabric of expeditionary strike operations for the first time. Cooper had to work through the operational, doctrinal, and interoperability challenges that come with fielding a genuinely new kind of combat aircraft in a live operational environment, translating the F-35’s sensing, networking, and strike potential into real mission execution across the strike group. That experience gave him a practitioner’s understanding of what fifth-generation integration actually demands, well before it became a settled concept across the joint force.
His engagement with F-35 operations in CENTCOM illustrates his kill web perspective. In describing recent high-end air operations over Iran, Cooper emphasized not individual platform performance but the orchestration of waves of advanced fighters, supported by tankers, legacy aircraft, ISR assets, and space-based enablers, cycling through contested airspace faster than the adversary could respond. The F-35’s contribution in this architecture is its ability to fuse multi-spectral data in a contested environment and pass that fused picture across the force in near-real time. That is kill web logic: the aircraft is a node, and the network is the weapon.
What is particularly notable in Cooper’s public articulations of these operations is his insistence on orchestration over heroics. His language is operational and architectural. He speaks of sequencing, repositioning, and re-targeting inside the adversary’s decision loop.
That is not the vocabulary of platform-centric warfare. It is the vocabulary of someone who has internalized the idea that speed of decision and continuity of effect matter more than the performance ceiling of any individual system.
If the F-35 operations illustrate Cooper’s comfort with kill web logic in the air domain, Task Force 59 shows him actively building one at sea. When Cooper established TF-59 in September 2021 under U.S. Naval Forces Central Command and U.S. Fifth Fleet, the stated mission was to rapidly integrate unmanned systems and artificial intelligence into fleet operations. What that meant in practice was constructing a persistent, AI-enabled sensing grid across some of the world’s most strategically demanding maritime terrain, the Strait of Hormuz, the Arabian Gulf, the Bab el-Mandeb, and doing it operationally, not in a laboratory.
The concept TF-59 pursued what Navy and industry participants described as a “digital ocean” is a direct maritime expression of kill web architecture. Large numbers of low-cost unmanned surface vessels, including Saildrone Explorers and MARTAC MANTAS T-12 craft, were deployed for extended periods carrying electro-optical, infrared, and other sensors. Their continuous data streams fed into AI-enabled command and control tools, creating an automated anomaly detection and cueing capability that extended maritime domain awareness across areas no manned force could cover at comparable cost. Manned ships and aircraft were then freed to do what manned platforms do best: intercept, board, deter, and strike cued by the unmanned grid rather than searching for targets themselves.
In fact, the MARTAC vessels MANTAS T-12 (12‑ft catamaran USV) integrated early with TF 59 as a “workhorse” ISR and test platform and the Devil Ray T-38 (38‑ft high‑speed USV) brought in later for higher‑end, longer‑range missions and as an armed platform. That is what a mesh fleet can do: mix different kinds of payloads to deliver various kill web effects.
Cooper drove a particular operational discipline inside TF-59 that is worth emphasizing because it reflects a core kill web design principle: the importance of a unified operational picture. He insisted on what he called a “single pane of glass” through which operators could see and task the entire distributed unmanned force through one interface, aided by AI flagging anomalies and potential threats in near-real time. That kind of interface is not just a convenience. It is what makes the web operable: the point where distributed sensing becomes actionable intelligence and actionable intelligence becomes directed force.
What also distinguished TF-59 under Cooper was the speed of its development cycle. During exercises like Digital Horizon, his team was iterating software in hours and hardware configurations in days. That compression of the traditional acquisition and experimentation timeline is itself a kill web principle: the force that learns and adapts faster inside its own network can sustain operational advantage over an adversary adapting more slowly. Cooper was not waiting for programmatic solutions: he was pulling capability forward through operational demand and feeding lessons back into the development cycle in real time.
The influence of Cooper’s work with TF-59 extended well beyond Fifth Fleet. The Chief of Naval Operations publicly credited what Cooper was doing with small unmanned systems in Fifth Fleet as having changed his own thinking about unmanned systems and their role in the future fleet. That is an unusual acknowledgment. Theater-level operational experimentation rarely drives that kind of strategic redesign from the top. What it tells us is that TF-59 was not simply a regional solution to a regional problem. It was a proof of concept for a different model of maritime warfare, and Cooper made it credible by making it operational.
The Navy’s evolving vision for distributed maritime operations, smaller, more numerous manned and unmanned platforms linked by resilient networks and AI-enabled C2, draws directly on TF-59’s lessons. In that sense, Cooper’s work in Bahrain is not just an operational success story. It is an input to force design. He has moved a kill web architecture from demonstration to enduring operational concept, and in doing so has helped the Navy understand what distributed maritime warfare actually requires at the tactical and operational levels.
Cooper’s elevation to Commander, U.S. Central Command moved a proven kill web practitioner from a maritime theater command to a joint warfighting command responsible for integrating air, land, maritime, cyber, and space operations across one of the world’s most consequential regions. The principles he applied in Fifth Fleet scale directly to this broader context. Distributed sensing, integrated C2, multi-axis strike, and the use of F-35s and other advanced platforms as connected nodes rather than isolated assets, all of these remain central to how CENTCOM has operated under his leadership.
Operation Epic Fury is the clearest current illustration. CENTCOM launched a large-scale, cross-domain operation combining advanced fighters, bombers, tankers, ISR aircraft, naval assets, and space support to neutralize Iranian capabilities and signal deterrent resolve. The operation relied on a tightly integrated air and missile defense network, cross-domain targeting, and rapid adaptation to adversary reactions. Fifth-generation aircraft operated within this architecture as both sensors and shooters, contributing to and drawing from a wider web that Cooper orchestrated at theater level. The operation was not a linear strike sequence. It was a kill web executing at operational depth.
The GCC-Israel kill web architecture that has emerged as a result of sustained CENTCOM engagement represents a further evolution of what Cooper has been building. The integration of Israeli F-35Is, Gulf partner air and missile defense systems, U.S. naval and air assets, and space-based enablers into a coherent regional network is precisely the kind of extended kill web that Timperlake and I have argued is the structural answer to the region’s security challenges. Cooper has been the operational architect at the joint and combined level making that integration real.
What has always distinguished the kill web from its critics’ caricatures is that it is not a technology argument. It is an operational logic.
The argument is not that unmanned systems or AI will replace judgment. It is that connecting sensors, shooters, and decision-makers through resilient networks, and then using that connectivity to out-cycle adversaries, produces military advantage that no single platform, however exquisite, can match. Cooper has lived that argument through two major commands and proven it operationally in both.
His contribution is not only to have commanded kill web operations but to have built the operational understanding within his own commands and across the Navy and joint force of what those operations require. The creation of TF-59, the drive for the “single pane of glass,” the insistence on compressing the learning cycle, and the integration of fifth-generation aircraft as network nodes rather than standalone strike assets all reflect a coherent and consistently applied operational philosophy. That philosophy is kill web thinking, applied by a practitioner who has shaped its development through practice rather than prescription.
As U.S. and allied forces move deeper into an era of major power competition and contested domains, the critical leadership question is not who understands the concept but who has proven they can execute it under operational conditions.
By that measure, Admiral Brad Cooper stands out as one of the most consequential kill web practitioners in the current U.S. military leadership.
The record is operational, not theoretical, and that is precisely what makes it significant.
The Admiral at the Helm: How Brad Cooper’s Years in Bahrain Are Shaping the Iran War