R-2A Activity · President's Budget PB2027

Fixed/Mobile System Capabilities

Activity a0·Project A34 — Counter Unmanned Aerial Systems (UAS)·PE 0605347A·U.S. Army
FY2027 Request
$23.6M
▲ 78% vs FY2026
HitchAI read

This activity requests $23.6M in FY2027, 6.6% of project A34, up 78% on FY2026. The R-2A exhibit describes it across FY2026–FY2027, including what the FY2027 money is planned to buy.

FY2027 Request
$23.6M
▲ 78% vs FY2026
FY2026 Enacted
$13.3M
In law
Planned work

What the FY2027 request buys

Verbatim from the R-2A exhibit for project A34 of PE 0605347A. This is the budget justification's own description of work that has not happened yet — the one thing no other level of the budget carries.

FY2027 planned work

FY 2027 funding will continue efforts to increase commonality and improve producibility, resulting in cost efficiencies and system improvements among the C-sUAS sensor variants, such as procuring prototype hardware and conducting prototype integration and testing in support of redesign of line replaceable units, due to obsolescence and multiple components approaching end-of-life. Funding will support development and testing of updated technical manuals and safety documentation required to conduct a Logistics Demonstration for the C-sUAS mobile solution, to initiate transition to field level sustainment. Funding will address hardware obsolescence and replacement for interceptor system components, resulting in higher operational availability and a lower cost. Funding will also support biannual C-sUAS system-of-systems integration/record tests for new and enhanced components, systems, and subsystems.

FY2026 to FY2027 change

FY 2026 to FY 2027 funding increase is due to the ramp up of efforts in support of transitioning M-LIDS to field level sustainment.

Before the request year

FY2026: the year under way

Prior-year accomplishments and current-year plans from the same exhibit. Context for the FY2027 plan, not a series — an activity partitions its project exactly in the request year, but can under-cover it in earlier years.

FY2026 plans — current year

FY 2026 funding will continue efforts to increase commonality and improve producibility among the CsUAS sensor variants, such as procuring prototype hardware in support of redesign of line replaceable units (e.g., System Control Unit and Advanced Back-End Unit), due to obsolescence and multiple components approaching end-of-life. Funding will also support biannual C-sUAS system-of-systems integration/record tests for new and enhanced components, systems, and subsystems.

Money

Three years, and no five-year plan

An R-2A activity publishes the prior year, the current year and the budget year. The FYDP outyears exist at project and program-element level and are deliberately absent here rather than inferred. Estimate types are colored and never summed into one figure.

013.3FY26ENACTED23.6FY27REQUEST
Enacted Request
Fiscal YearEstimate TypeAmount ($M)
FY2026Enacted13.3
FY2027Request23.6

This activity is 6.6% of project A34's FY2027 request and 6.6% of PE 0605347A's. In the request year the activities under a project sum to it exactly; in the current year they under-cover it in about 9% of cases, so an activity's delta can legitimately exceed its parent's and the two must not be compared row to row.

Where this sits

5 activities in project A34

Every R-2A line of this project, largest FY2027 request first. Linked where the activity has enough of its own narrative to carry a page; the rest are shown in full on the program-element page.

Source
FY2027 Department of the Army RDT&E Budget Justification · Exhibit R-2A · PE 0605347A, project A34 (President's Budget PB2027). Congressional marks are recorded on the program element, never on an activity.
Machine access
Markdown twin /programs/0605347A/A34/a0.md · MCP mcp.hitchintel.combudget_get_activity