The Pentagon’s counter-drone problem has not been a shortage of hardware. Since the first Shahed-136 strikes in Ukraine in the fall of 2022 forced Western planners to rethink low-altitude air defense, the Department of War has funded a parade of purpose-built counter-unmanned aerial systems: directed-energy turrets, microwave arrays, kinetic interceptors, and net-firing drones. The Defense Innovation Unit is still running an open solicitation for more. What the services have been short on is a way to make the guns they already own shoot down the drones they already see.<\/p>\n
A live-fire exercise at Fort Hood, Texas in late March, conducted under the name Operation Condor Rebirth, took a run at that gap. According to a US Army account of the exercise<\/a> and a joint statement<\/a> from the three contractors involved \u2014 radar maker Echodyne, turret builder Moog, and software firm Picogrid \u2014 the team bolted their respective products onto a secure US Army network and engaged Group 1 through Group 3 drone targets in under three seconds from detection. No new weapon was built. No new mount was fabricated. The turret was one the Army already fields.<\/p>\n That is the part worth sitting with. The fix, if it holds up under scrutiny, is mostly code.<\/p>\n The configuration paired Moog’s Reconfigurable Integrated-weapon Platform \u2014 RIwP, in the contractor shorthand \u2014 with Echodyne’s EchoShield radar and Picogrid’s Legion software. RIwP is a modular turret<\/a> that the Army has already integrated onto Stryker variants, the Armored Multi-Purpose Vehicle, and other ground platforms; it carries an onboard edge computer that can host third-party fire-control logic without a trip back to the depot. EchoShield is a commercially available medium-range radar built around an electronically scanned array, marketed by Echodyne for drone detection and tracking. Legion is the connective tissue: a software layer that ingests sensor data, runs classification, and pushes firing solutions to the turret.<\/p>\n According to the contractors’ joint statement, the system used radar-generated airspace data and AI-based fire control to calculate firing solutions, maintain track on moving targets, and handle multi-object engagements, including reacquiring targets after a track was briefly lost. The reported engagement window was under three seconds from initial detection across the Group 1 through Group 3 envelope \u2014 a span that, per the DoD’s own classification, covers handheld quadcopters at the low end up to fixed-wing systems weighing several hundred pounds at the upper bound.<\/p>\n “By combining high quality radar sensors and rapid integration of data it is possible to deliver impressive C-UAS capabilities from existing battlefield systems, affordably and more quickly than using purpose-built systems,” Echodyne CEO Eben Frankenberg said in the companies’ statement on the exercise.<\/p>\n Almost every counter-drone briefing in the past two years has led with artificial intelligence. The Fort Hood demonstration used AI, but the more consequential claim is structural: a turret already in the Army’s inventory, fed by a commercial radar and a software fire-control stack, can hit small drones inside three seconds without anyone designing a new platform around the threat.<\/p>\n That matters because the alternative \u2014 fielding a dedicated C-UAS system for every forward unit \u2014 has been slow and expensive. The Army’s own counter-small-UAS office has spent the last several years sorting through dozens of candidate systems, with mixed deployment results. A retrofit path that runs through software updates and sensor packages, rather than new vehicle programs, sidesteps the procurement timelines that have frustrated commanders watching Ukraine and the Red Sea in real time. It is the same affordable-mass logic now driving the offensive side of the drone war, where the Pentagon is racing to secure cheap, scalable hardware<\/a> rather than small numbers of exquisite platforms.<\/p>\n Moog Defense Senior Vice President Mike Gruver framed the exercise as part of an effort to accelerate counter-UAS capabilities for US and allied forces, calling it “a critical moment to rapidly strengthen C-UAS defenses and protect warfighters against evolving threats.” The contractors said the test also helped identify capability gaps in a simulated battlefield environment and validated the integration on a military network \u2014 language that suggests this was a developmental milestone, not a fielded capability.<\/p>\n A few things are worth holding at arm’s length before this gets oversold.<\/p>\n First, “engagement” in a live-fire C-UAS context can mean a tracked firing solution executed on a target, but it does not automatically mean a kill at the rates a battlefield would demand. The contractors reported sub-three-second engagement times across the Group 1\u20133 range; they did not publish hit probabilities, ammunition expenditure per target, or the specific drone airframes and flight profiles used as threats. Group 3 covers a wide envelope \u2014 a Shahed-class loitering munition flies very differently from a fixed-wing surveillance drone \u2014 and the public statements do not break out performance by class.<\/p>\n Second, the test was conducted on a “secure US Army network,” in the contractors’ phrasing, but neither the Army’s Program Executive Office Missiles and Space nor the Joint Counter-small UAS Office has issued a public assessment of the exercise as of this writing. The detailed performance data so far comes from the three companies that ran the demonstration and stand to benefit from its success.<\/p>\n Third, the autonomy question is unresolved. The systems calculated firing solutions and maintained tracks automatically, but US policy under DoD Directive 3000.09<\/a>, last updated in January 2023, still requires commanders and operators to exercise appropriate levels of human judgment over the use of force. The Fort Hood configuration shortens the kill chain dramatically; it does not, on the public record, remove the human from it.<\/p>\n The exercise lands alongside a broader push to plug commercial sensors and software into legacy Army platforms. The US Army Combat Capabilities Development Command’s C5ISR Center has been developing government-owned counter-UAS architectures<\/a> \u2014 work that has already moved from the lab to real-world border-protection operations with the 10th Mountain Division \u2014 built around the same idea of integrating sensors and effectors onto a single vehicle. The Defense Innovation Unit’s live C-UAS solicitation, posted earlier this year, is explicitly looking for dual-use systems that integrate with existing architectures rather than replace them.<\/p>\n The common thread is that the Pentagon has stopped asking who can build the best new counter-drone system and started asking who can make the turrets, radars, and networks already in the field talk to each other fast enough to matter. Operation Condor Rebirth is one data point in that shift. It is a useful one, in part because the integration was done by three companies that do not, individually, build a complete weapon system \u2014 Echodyne does not make turrets, Moog does not make radars, and Picogrid does not make either. The same multi-domain, networked logic is showing up across the unmanned field, from hydrogen-powered ISR drones<\/a> to seabed robotics.<\/p>\n The press materials did not put a unit cost on the integrated configuration, did not name a follow-on Army program of record, and did not specify which RIwP-equipped platforms would be candidates for the upgrade. Those are the questions that determine whether a Fort Hood demonstration becomes a fielded capability or another line item in next year’s counter-UAS retrospective.<\/p>\n What the exercise did establish, on the public record, is that the engineering problem of getting an existing Army turret to engage a small drone in under three seconds is no longer the bottleneck. The bottleneck is whether the Army buys the integration, on what schedule, and at what scale. Echodyne, Moog, and Picogrid have made their pitch. The next move belongs to the Pentagon’s acquisition side, and that is a much slower clock than three seconds.<\/p>\n","protected":false},"excerpt":{"rendered":" A live-fire Army exercise at Fort Hood paired Echodyne radar, Moog turrets and Picogrid software to engage Group 1\u20133 drones in under three seconds. (149 chars)<\/p>\n","protected":false},"author":8,"featured_media":9035,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[121,3],"tags":[],"class_list":["post-9040","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-industry","category-news","resize-featured-image"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.autonocion.com\/us\/wp-json\/wp\/v2\/posts\/9040","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.autonocion.com\/us\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.autonocion.com\/us\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.autonocion.com\/us\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/www.autonocion.com\/us\/wp-json\/wp\/v2\/comments?post=9040"}],"version-history":[{"count":2,"href":"https:\/\/www.autonocion.com\/us\/wp-json\/wp\/v2\/posts\/9040\/revisions"}],"predecessor-version":[{"id":9069,"href":"https:\/\/www.autonocion.com\/us\/wp-json\/wp\/v2\/posts\/9040\/revisions\/9069"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.autonocion.com\/us\/wp-json\/wp\/v2\/media\/9035"}],"wp:attachment":[{"href":"https:\/\/www.autonocion.com\/us\/wp-json\/wp\/v2\/media?parent=9040"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.autonocion.com\/us\/wp-json\/wp\/v2\/categories?post=9040"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.autonocion.com\/us\/wp-json\/wp\/v2\/tags?post=9040"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}What actually got tested at Fort Hood<\/h2>\n
Why “existing turret” is the headline, not “AI”<\/h2>\n
What the demonstration did not prove<\/h2>\n
Where this fits in a crowded field<\/h2>\n
The procurement question nobody answered<\/h2>\n