A GMJoe™ Consulting observation on counter-UAS, autonomous interception, and the emerging architecture of low-altitude defense
By Joe Cozart
I have increasingly come to believe that the next consequential phase of the unmanned systems market will not be defined by the proliferation of drones. That phase is already underway. The next phase will be defined by the architecture required to defeat them.
The distinction matters because much of the defense conversation continues to concentrate on the unmanned aircraft itself: range, payload, endurance, autonomy, manufacturing scale, cost, communications resilience, and increasingly the ability to operate in contested or denied environments. Those remain important characteristics, but they describe only one side of a rapidly changing operating environment. Every successful offensive technology eventually creates demand for its defensive counterpart.
The extraordinary proliferation of relatively inexpensive unmanned aerial systems has accelerated that cycle. What was once a specialized military capability has become an increasingly accessible instrument capable of reconnaissance, targeting, electronic effects, kinetic attack, and coordinated operations. The economic threshold for placing an aircraft into the battlespace has fallen dramatically. The economic threshold for destroying one must eventually fall with it. That may become one of the defining defense-industrial problems of the next decade.
I was therefore interested in T3 Defense’s acquisition of a majority interest in Project35 not simply because another defense company had acquired another unmanned-systems company, but because of what the transaction represents. Project35 brings capabilities involving drones, aerial interceptors, and counter-UAV systems. Viewed narrowly, those are product categories. Viewed architecturally, they represent something more consequential: the gradual convergence of unmanned aviation and unmanned air defense.
That convergence deserves attention because the traditional air-defense model was developed around comparatively valuable threats. Aircraft, cruise missiles, and ballistic missiles justified sophisticated detection networks and expensive interceptors because the attacking systems themselves represented substantial military investments and substantial destructive potential. Small unmanned aircraft have complicated that equation. A defensive system can successfully destroy an incoming threat and still lose economically if the interceptor repeatedly costs orders of magnitude more than the object being intercepted. Tactical success does not automatically produce sustainable defense.
This creates what I consider an emerging requirement for cost symmetry. The defender must increasingly be capable of meeting inexpensive mass with inexpensive mass, and that requirement leads naturally toward autonomous interception. The concept is straightforward even if its implementation is not. Sensors identify an object, software classifies it, networks distribute information, command architecture determines the appropriate response, an autonomous or semi-autonomous interceptor is assigned, and the engagement occurs. The important development is not any individual component. It is the compression of detection, identification, decision, assignment, interception, and assessment into an increasingly coordinated machine-speed process.
That is why I view counter-UAS not primarily as another defense product category but as an emerging systems architecture. The distinction is important for defense planners and defense companies alike. A drone can be purchased, but an architecture must be integrated.
That architecture may include radar, passive RF detection, electro-optical and infrared sensing, acoustic detection, electronic warfare, command-and-control software, artificial intelligence, edge computing, kinetic interceptors, directed-energy systems, autonomous aircraft, and conventional air-defense assets. No single technology solves the problem because no single threat defines it. The operating environment may contain commercial quadcopters, reconnaissance platforms, one-way attack systems, autonomous aircraft, coordinated swarms, decoys, electronic-warfare platforms, and increasingly systems designed specifically to survive or circumvent existing countermeasures. Defense therefore becomes layered.
This is where the significance of companies combining unmanned aircraft with counter-unmanned capability begins to emerge. The competitive advantage may eventually reside less in producing the individual platform than in understanding how the platform participates within the defensive stack. That stack is becoming increasingly important because the requirement extends beyond conventional battlefield air defense.
Military installations must protect low-altitude approaches. Forward operating locations must protect personnel and equipment. Ports must protect logistics infrastructure. Airfields must protect runways and aircraft. Energy facilities must protect generation and distribution assets. Communications infrastructure must protect critical nodes. Data centers and edge-computing installations must protect increasingly consequential physical infrastructure. The problem is therefore moving from battlefield defense toward infrastructure defense, and that transition substantially enlarges the strategic significance of counter-UAS.
It also changes how I think about sovereignty. Modern sovereignty increasingly depends upon control over systems rather than territory alone. Data sovereignty matters. Communications sovereignty matters. Energy sovereignty matters. Computational sovereignty matters. Low-altitude airspace is becoming another layer. The question is no longer simply who possesses the ability to fly through that space. The more important question is who possesses the ability to observe it, classify activity within it, determine what belongs there, and act when something does not.
That is an operating architecture, and once viewed through that lens, the T3 Defense–Project35 transaction becomes less interesting as an isolated acquisition and more interesting as evidence of a larger defense-industrial convergence. Drone companies are moving toward counter-drone capability. Sensor companies are moving toward integrated command systems. Software companies are moving toward autonomous decision support. Defense primes are integrating layered counter-UAS solutions. Edge computing is moving closer to the battlespace. Artificial intelligence is moving closer to the engagement decision. The pieces are beginning to converge.
I do not assume that every company participating in this convergence will succeed. Acquisitions must be integrated. Technologies must perform outside controlled demonstrations. Manufacturing must scale. Supply chains must survive. Systems must operate under electronic attack. Customers must procure them. Capital structures must support rather than undermine growth. Those are execution questions. The architectural direction is the more important observation.
The first era of unmanned aviation was about access. The second was about capability. The third is becoming about control. Control requires something larger than a drone. It requires sensing, computation, communications, decision-making, interception, and command to operate as a coherent defensive environment.
That is why I believe the most important question surrounding the future of drones is gradually changing. It is no longer simply what the drone can do. It is becoming a question of who controls the sky in which the drone operates. The answer will not be found in a single aircraft. It will be found in the architecture surrounding it.
Joe Cozart, GMJoe™, GMJoe™ Consulting
——— GMJoe™ ———
Clarity. Strategy. Sovereignty.
Books by Joe Cozart are available at: amazon.com/author/joecozart
GMJoe.org