The U.S. Army has successfully destroyed small unmanned aerial systems from a moving vehicle platform, demonstrating a fire-control capability that removes one of the most persistent tactical liabilities in counter-drone defense: the requirement to stop before shooting.

Picatinny Arsenal announced June 23, 2026, that SWAT-FC — Simultaneous Weapon Autonomy Technology for Fire Control — completed live-fire testing in April at Aberdeen Proving Ground, Maryland. The software, integrated with the Army's Common Remotely Operated Weapon Station (CROWS), tracked and destroyed multiple small drone targets while the host vehicle was itself in motion. The U.S. Army Combat Capabilities Development Command Armaments Center, headquartered at Picatinny, led the development.

"Once we started destroying drones, it showed the hard work was paying off." — Nick Cascia, project armaments officer, Picatinny Arsenal (Army Times)

The April tests at Aberdeen constitute a live-fire validation of the concept. DEVCOM Armaments Center, which led the SWAT-FC development effort, brings the fire-control algorithm to a platform already woven into the Army's vehicle fleet.

What SWAT-FC Actually Solves

The fire-control problem at the heart of SWAT-FC is a compounded one: a moving gunner platform attempting to intercept a moving aerial target requires continuous, real-time recalculation of aim points in three dimensions simultaneously. Current vehicle-mounted counter-UAS systems generally require the vehicle to halt before engaging aerial threats. In a convoy or patrol context, that halt creates a predictable exposure window — the vehicle stops, the crew engages, and everyone in the vicinity is stationary and vulnerable for however long the engagement takes. Against an adversary employing coordinated drone swarms designed to saturate a small area, that halt may be precisely what the attack is engineered to force.

SWAT-FC addresses this by feeding real-time sensor data into a fire-control algorithm that continuously updates the aim solution as both platform and target move. The integration point is CROWS, the remotely operated weapon station already mounted on CROWS-equipped Army vehicles across the force. Rather than requiring new hardware procurement, SWAT-FC could theoretically be pushed as a software upgrade across an existing fleet — a much faster and cheaper path to widespread capability than fielding a purpose-built system. The upgrade-versus-new-buy distinction has real programmatic weight in an acquisition environment where counter-UAS programs compete for funding against a long list of higher-profile platforms.

The algorithm's lineage is also worth noting. SWAT-FC was adapted from software originally developed for the Future Attack Reconnaissance Aircraft program — a rotary-wing development effort — meaning the underlying math for tracking and engaging aerial targets in a dynamic environment was not built from scratch for the counter-UAS role. That pedigree gives the fire-control logic a meaningful head start on the hardest part of the problem: maintaining a valid firing solution when neither the shooter nor the target is cooperating by holding still. Repurposing algorithms across programs is a standard acceleration tactic at DEVCOM, but it still requires significant validation work under real-world conditions — the April test at Aberdeen was that validation moment for the vehicle-mounted application.

Tactical Context: Convoys, Patrols, and the Halt Problem

The operational logic behind SWAT-FC is inseparable from lessons accumulated in Ukraine and the Red Sea, where small commercial and purpose-built UAS have proven devastatingly effective against vehicle formations, logistics convoys, and static installation perimeters. Those theaters have accelerated C-UAS priority across the U.S. defense establishment, driving demand for organic defeat capability that does not require a vehicle to telegraph its position by stopping mid-mission.

SWAT-FC directly addresses that requirement. A convoy that can engage drone threats without stopping retains momentum and denies an adversary the predictable halt behavior that enables coordinated multi-drone attacks. A mobile security patrol that can engage without halting removes the crew exposure that makes CROWS engagements tactically costly even when they succeed. The capability also has relevance for installation perimeter defense, where mobile security elements can engage airspace incursions without giving up their patrol tempo.

None of these scenarios requires exotic new hardware. CROWS is already on the vehicles. The upgrade path, if the Army moves SWAT-FC toward a program of record, runs through software integration and qualification testing rather than new procurement — a significant difference in both timeline and cost.

Why It Matters

The ability to shoot down a drone from a moving vehicle sounds straightforward, but the fire-control problem it requires solving is a condensed version of what has historically required dedicated tracking radars and fire-control computers found only on large, expensive platforms. Bringing that solution down to the CROWS level — a system that a dismounted soldier can operate remotely — represents a meaningful compression of capability into a widely fielded, low-cost form factor.

The April test at Aberdeen validates the concept under controlled but physically real conditions: actual drones, actual vehicle movement, actual rounds. That is a different threshold than simulation or static testing, and it positions SWAT-FC for the next step in Army acquisition — whether that is a formal program-of-record proposal, an Operational Needs Statement from a unit commander, or inclusion in an existing C-UAS integration program. The CROWS installed base gives the Army a compelling upgrade argument: the hardware is already there, the gap is the fire-control software, and SWAT-FC now has a live-fire demonstration behind it.

Counter-UAS at the vehicle level has historically been a reactive, piecemeal capability — bolt-on jammers, retrofitted sensors, hastily integrated defeat systems fielded in response to an immediate threat rather than designed from the ground up. SWAT-FC represents a more deliberate approach: purpose-developed fire-control logic, tested against real targets, integrated with a platform already woven into the Army's vehicle fleet. Whether it moves quickly toward fielding or stalls in the acquisition process remains to be seen, but the live-fire validation at Aberdeen removes the most fundamental uncertainty about whether the core concept works at all.

Sources