The Army's Balloon Swarms Got Their First Combat Test
The US Army pivoted high-altitude balloon experiments to live CENTCOM operations—and came back with a checklist of hard lessons.
By The Defense Desk
The balloon didn't make it to the Pacific. Instead, it went to war. [1]
Andrew Evans, the director for the Strategy & Transformation Office inside the Army's Deputy Chief of Staff for Intelligence shop (G-2), spoke on the sidelines of the Annual Association of the US Army conference. "We were asked to pivot and do some experimentation in combination with operations, and we pivoted and supported operations in CENTCOM," Evans told Breaking Defense. "They were effective for the mission that they were assigned." [1]
The scale shift alone was significant. What actually flew over the Middle East was smaller—but still a meaningful jump. "From a scale perspective, we went from one to two to dozens simultaneously," Evans said. [1]
That gap between ambition and execution is where doctrine gets written. Every technology that moves from test range to active theater compresses years of planning into weeks of improvisation, and the lessons that emerge tend to be less about the hardware than about the system surrounding it.
The Army has tested high-altitude balloons multiple times over the last few decades, reviving the push in recent years as a cost-effective complement to satellites and drones for battlefield sensing and communications.
The CENTCOM deployment surfaced three specific friction points the Army will carry into future planning. The first was logistical. There were logistical challenges tied to transporting the balloons into the Middle East and then storing them. "Balloons can be a little finicky in terms of temperature, and you have to contend with environmental characteristics," Evans said. [1]
The second challenge was operational: who actually runs the balloon? "As you think about employing your systems and going from something like a Pacific [theater] to something like a CENTCOM [theater], you learn where those friction points might exist between what the military might need to inherently own, and … what a vendor could help provide in terms of the service," Evans said. [1]
Given the ongoing regional options, industry had to put the military in "driver's seat" to ensure everything was in accordance with the proper authorities the US military had. [1] That arrangement worked—but it also revealed that there are not a lot of folks trained on how to operate the systems at scale. "There's just not a lot of folks that are trained on how to operate it, so we've learned some things along the way and we're going to take those back," Evans said. [1]
This is the familiar tension in any emerging military capability: the technology outpaces the institution. The hardware floats. The workforce, the doctrine, and the training pipelines take longer to rise.
The third challenge was airspace. "There were some challenges," Evans acknowledged. "That was not a new finding, [but] a consistent observation." [1] Consistent, meaning it has appeared in every balloon and drone program review for years, and consistent, meaning no one has solved it yet.
The force structure question Evans raised—who owns and operates these systems at scale—connects directly to a broader debate inside the service about how to institutionalize emerging capabilities before they become operationally critical. The Army and joint force will need to do "a little bit of additional thinking" about what that force structure looks like, Evans said. [1] That phrasing, diplomatic in a Washington way, translates roughly to: no one has written the manual yet.
The gap between capability and doctrine is not unique to balloons. Every autonomous system the military has fielded at speed has left a similar trail—hardware that works, bureaucracy still catching up, and somewhere in between, the soldiers who have to make it function on a deployment timeline.
What happens next is less certain than the Army's rhetoric might suggest. Evans confirmed that service leaders are confident they need stratospheric sensing capabilities—persistent eyes at altitude, above commercial air corridors and below satellites. But the platform question remains entirely open. "Would it be a balloon? Would it be a solar glider? Would it be some sort of pseudo satellite?" Evans said. "It's unclear. No decision has been made." [1]
That openness is itself informative. The Army was looking to experiment with over a hundred high-altitude balloons in the skies over waters in the Indo-Pacific in 2026 before pivoting to CENTCOM, and that demonstration never came to fruition. [1] The fact that senior leaders are still weighing balloons against solar gliders and pseudo-satellites suggests the CENTCOM deployment, effective as it was declared to be, raised as many questions about the future form factor as it answered.
This is how military technology matures in real theaters rather than on test ranges: not through clean validation but through accumulated friction. The useful lessons are rarely the ones planners anticipated. They are the ones that show up in the storage tent, in the vendor contract, in the airspace deconfliction call at two in the morning.
The CENTCOM deployment won't be the last iteration. The Army's trajectory—one balloon, two balloons, dozens simultaneously—points toward a future where swarms are a standard operational tool, not a demonstration asset. [1] But before the fleet scales, the service has to resolve the workforce gap, define the vendor-military boundary, and find a workable answer to the airspace problem that has shadowed every autonomous platform it has tried to field.
The balloon went to war before the doctrine did. The Army's job now is to close that distance—and decide whether the next vehicle to fill that stratospheric role will even be a balloon at all. [1]