RDT&E Project · President's Budget PB2027

Adversary Mission Systems

Project 1982·PE 0204571N — Consolidated Trng Sys Dev·U.S. Navy·BA7
FY2027 Request
$10.4M
▼ 32% vs FY2026
HitchAI read

Project 1982 — Adversary Mission Systems requests $10.4M in FY2027, 9.0% of the $115.8M requested for program element 0204571N, down 32% on FY2026. 1 R-2A activity decomposes the request. ATR is the largest named R-3 performer at $1.0M, 9.7% of the project's FY2027 R-3 total.

FY2027 Request
$10.4M
▼ 32% vs FY2026
FY2026 Enacted
$15.3M
▲ 194% vs FY2025
FY2025 Actual
$5.2M
Prior year
Project detail

What project 1982 buys

Airborne Adversary Mission Systems builds upon existing RedNet architecture to enable classified software development and classified hardware integration such as electronic attack, infrared search, Radio Frequency (RF) emulation with encrypted range training data links, such as Tactical Combat Training System (TCTS) and Link 16. This project will enable the aircrew to accurately emulate peer threat capabilities and provide a standalone Adversary Operational Flight Program (OFP)', that can be deployed on any aircraft with RedNet Multi-Layered Obstructed Brokered Bus-Controller & Routing for Advanced Integrated Networks (MOBBrain) avionics architecture and an encrypted range training pod. Primary platforms for development include the F-5, F-16 and F-18 within existing Naval Adversary Squadrons. These systems combined with a classified electronic kneeboard, allows for the development, integration and deployment of adversary mission hardware and software systems without modification of aircraft's existing OFP software. This program will provide for the future ability to participate fully in the Live Virtual Constructive (LVC) environment as well as provide physics and effects-based threat replications for the mission essential training of deploying Fleet aircrews.

R-3 lines of work
  • Product Development
  • Support
  • Test and Evaluation
  • Management Services
Funding trajectory

Project 1982 funding, FY2025–FY2031

Prior years are actuals, the budget year is the request, and the outyears are the FYDP plan. Estimate types are colored and never summed into one figure. Projects carry the full five-year plan; the activities inside them stop at the budget year.

05.2FY25ACTUAL15.3FY26ENACTED10.4FY27REQUEST17.2FY2816.4FY2916.1FY3016.4FY31
Actual Enacted Request Outyear (FYDP)
Fiscal YearEstimate TypeAmount ($M)
FY2025Actual5.2
FY2026Enacted15.3
FY2027Request10.4
FY2028Outyear17.2
FY2029Outyear16.4
FY2030Outyear16.1
FY2031Outyear16.4
Inside the project

1 accomplishment / planned program

The R-2A exhibit — the only level of the budget that describes work that has not happened yet. Activities carry the prior, current and budget year only, no five-year plan. Each describes FY2027 work in enough detail to have its own page; the rest are shown here in full. Coverage is partial across the corpus, so count activities, never total them.

FY2025 actual$5.2M
FY2026 enacted$15.3M
FY2027 request$10.4M

Continue hardware and software research and development activities for peer threat representative models, hardware development activities for Infrared Search and Track (IRST), as well as integration of existing onboard combat systems into the RedNet architecture. Development and integration testing of continuous software solutions and…

Read the FY2027 plan →
Who's building it

Named performers on project 1982

Performers named in the R-3 exhibit under this project. Share is of the project's whole FY2027 R-3 total — the same denominator the program-element split uses, so the two read on one scale and will not sum to 100% when unnamed or government work is in the mix. Budget-justification contract funding, not obligations.

ATR
$1.0M · 9.7%
NAWCAD
$1.0M · 9.6%