Army FY2026 C-UAS budget: realignment, not a new award

What the source establishes

US Army budget exhibits dated June 2025 describe FY2026 Counter Unmanned Aerial Systems Agile Development under PE 0609135A, project A33. The documents explicitly realign existing work from PE 0604741A, project FG5, rather than identify a new programme start. Planned activity includes KuRFS design updates, producibility and integration across FY2026–FY2030. These are budget-request plans, not evidence that all listed work occurred.[S1] [S2] [S3]

UXV Searcher insight: administrative transfers can create false growth

When work moves between budget lines, counting the receiving line as entirely new activity while retaining the old line can overstate programme expansion. A consistent time series must link the predecessor and successor scope before interpreting changes. The programme identifier alone is not proof of incremental market demand.

The funding stage also matters. A President’s Budget request is distinct from an enacted appropriation, a contract obligation and supplier revenue. Each stage can provide useful information, but they should not be added together or treated as interchangeable measures of spending.[S1] [S2] [S3]

Commercial implications

Suppliers can use the schedule to identify planned development areas and potential future requirements, while verifying which activities receive actual obligations. Buyers and analysts should follow the programme across its administrative transfer rather than assume discontinuity from the new code. RTX documentation connects Coyote and KuRFS with the Army’s LIDS system, but that product context does not allocate the full programme request to one company or component.[S1] [S2] [S3]

Scope and timing

Only the June 2025 document period is established; no publication day is invented. No monetary amount, supplier award or completed FY2026–FY2030 milestone is inferred. This article describes a programme-budget event, not a dated RTX contract.[S1] [S2] [S3]