Drone Dominance Phase III: How the RFS Reframes Deep Strike and CQB for Low-Cost Lethality

Strike and CQB as separate tactical problems with different constraints and performance targets. That lets designers optimise airframes, sensors, autonomy, and lethality for each envelope rather than forcing compromises across a single platform.

Deep Strike focuses on one-way attack missions against deep-tier targets such as command and control nodes, logistics hubs, and air-defence radars. Key technical and operational requirements in the RFS include:

• Range and endurance: extended operational ranges and loitering to wait for transient targets behind the forward line of own troops (FLOT).
• Navigation resilience: operation under total GNSS denial. The RFS requires alternative navigation techniques such as optical flow, terrain contour matching (TERCOM), and visual inertial odometry (VIO).
• Terminal guidance: onboard, edge-processed Automatic Target Recognition (ATR) that can identify, track, and strike moving or camouflaged military hardware without relying on continuous human-in-the-loop communications.

CQB: micro-UAS for urban and subterranean fights

CQB covers micro and hyper-agile platforms meant for urban interiors, tunnels, bunkers, and confined spaces. Requirements include:

• Spatial awareness: robust SLAM using micro-LiDAR or stereo vision to locate and map in three dimensions with zero GPS.
• Physical agility and survivability: ruggedised airframes, propeller guards, and multi-directional collision avoidance to survive high-velocity impacts with walls, door frames, and debris.

Open Systems Architecture and modular design

Phase III insists on an Open Systems Architecture (MOSA) to prevent vendor lock-in. The RFS requires vendors to decouple hardware and software so commercial-off-the-shelf (COTS) components, government-furnished equipment (GFE), and third-party payloads can interoperate. The architecture blueprint includes:

• Modular airframes and standard kinetic payload interfaces.
• Edge-AI compute blocks for local sensor processing.
• Government-compatible autonomy stacks that can be flashed with new software, EW countermeasures, or target libraries right before deployment.

Software, autonomy, and edge processing

The RFS specifies modular autonomy stacks compatible with unified government control software. Onboard edge-AI must process multi-spectral sensor data locally to avoid transmitting raw feeds that create RF signatures. This local processing is central to both GNSS-denied navigation and autonomous terminal engagements.

Lethality is the defining performance metric for Phase III. The program mandates modular kinetic payloads and integrated terminal guidance to enable autonomous strike capability. The RFS emphasises rapid fielding of low-cost, lethal systems rather than high-cost, multipurpose designs.

What this means for developers and users

Vendors should prioritise mission-specific designs, modular hardware and software interfaces, and robust local autonomy for GNSS- and RF-denied environments. For operators, Phase III promises systems tailored to either deep penetration strikes or immediate tactical support in confined spaces, with government control over autonomy stacks and payload libraries.