R-2A Activity · President's Budget PB2027

Autonomous Systems Control Integration and Demonstration

FY2027 Request
$12.1M
◆ New start in FY2027
HitchAI read

This activity requests $12.1M in FY2027, 4.7% of project 634920 — a new start with no prior-year and no current-year money. The R-2A exhibit describes it across FY2026–FY2027, including what the FY2027 money is planned to buy.

New start

This activity requests $12.1M in FY2027 with no prior-year and no current-year funding. There is no incumbent line to compare it with — it did not exist before this President's Budget.

FY2027 Request
$12.1M
No FY2026 funding
FY2026 Enacted
$0.0M
No FY2025 funding
FY2025 Actual
$0.0M
Prior year
Planned work

What the FY2027 request buys

Verbatim from the R-2A exhibit for project 634920 of PE 0603211F. 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

Complete development of advanced contingency management capabilities required for credible affordable mass. - Deliver contingency management strategies and capabilities to enable affordable mass in high-speed systems. Commence development of autonomy architecture and communication changes for contingency management. - Activities include initial studies of architecture changes for flight- and mission-critical contingencies, passing representative contingency information between modeled vehicle, flight and mission layers.

FY2026 to FY2027 change

FY 2027 funding increased by $12.114 million due to the transfer of the Autonomous Systems Control Integration and Demonstration effort and associated funding within this Program Element from Project 634927 / Flight Systems Control to Project 634920 / Aerospace Systems Integration & Demonstration. This includes an increase from FY2026 to FY2027 of $9.317 million due to increased need for autonomous contingency management to deliver affordable credible mass and due to the complexity of developing and integrating contingency solutions across the autonomy hardware and software stack due to their potential impact on flight safety and mission success.

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

In FY 2025 and FY 2026, the Autonomous Systems Control Integration and Demonstration effort and funding were reported in Program Element 0603211F/ Aerospace Technology Dev/Demo/Project 634927/Flight Systems Control. FY 2025 funding was $0.636 million and FY 2026 funding is $2.797 million.

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.

00.0FY25ACTUAL0.0FY26ENACTED12.1FY27REQUEST
Actual Enacted Request
Fiscal YearEstimate TypeAmount ($M)
FY2025Actual0.0
FY2026Enacted0.0
FY2027Request12.1

This activity is 4.7% of project 634920's FY2027 request and 4.7% of PE 0603211F'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

7 activities in project 634920

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 project page.

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