Skip to content
Fiscal Receipts

UMCS-Unman Carrier Aviation(UCA)Mission Cntrl

NProcurementPartial Reconciliation4269
What it is
UMCS-Unman Carrier Aviation(UCA)Mission Cntrl — a procurement program run by Navy.
What changed
No FY25→26 comparison — trajectory data incomplete for this line.
Who gets it
No award linkage at high confidence.

Budget Figures

FY24 Actuals
$143.6M
FY25 Total
FY26 Request
$189.6M
FY25→26 Change

FY2026 award data is a partial year — USASpending awards are reported on a rolling basis and the fiscal year does not close until September 30. why partial FY2026 data? →

Budget Trajectory
FY24: $143.6MFY26: $189.6MFY24FY26
FY24
$143.6M
FY26
$189.6M
Decade view — each figure cites its own President's Budget edition
FY2022 actuals — PB2024 editionFY2023 actuals — PB2025 editionFY2024 actuals — PB2026 editionFY2023 enacted — PB2024 editionFY2024 enacted — PB2025 editionFY2025 enacted — PB2026 editionFY2024 request — PB2024 editionFY2025 request — PB2025 editionFY2026 request — PB2026 editionFY22FY26

● actuals (line)  ·  ○ enacted  ·  ◇ request — gaps are editions the program is absent from, never interpolated.

SeriesFY22FY23FY24FY25FY26
Actuals$67.2M$134.7M$143.6M
Enacted$134.7M$152.7M$119.6M
Request$152.7M$130.1M$189.6M

blank = series not published for this year; – = absent from that edition.

Asked vs spent: the PB2024 book requested $152.7M for FY2024; the PB2026 book reports $143.6M actually spent — $9.07M below the request.

Program Lineage

No predecessor/successor lineage was recorded for this program element — no FY-to-FY transfer into or out of this line was stated in the ingested J-books, and none was inferred from the program structure.

Description

Description UMCS-Unman Carrier Aviation(UCA)Mission Cntrl Stn

This Budget Line Item funds The Unmanned Carrier Aviation (UCA) Mission Control System (UMCS) program. This program builds, integrates, installs, and sustains the systems (control station, communications, and networks) required to operate the MQ-25, Collaborative Combat Aircraft (CCA) and future unmanned systems, which comprises the Air Wing of the Future (AWOTF), afloat and ashore. The UMCS program is the system-of-systems required for MQ-25 vehicle and payload control, both shipboard and shore based. The UMCS consists of all ground and ship-based hardware, software, and networks associated with the planning and execution of flight operations and tactical missions, including the control stations (displays, computers, and servers), line-of-sight communications, and beyond line-of-sight satellite communications. The ground control station (GCS), designated as the MD-5, allows pilots to command and control the MQ-25 Air Vehicle using external Command, Control, Communication, Computers, and Intelligence (C4I) systems. The main component of the GCS is the Multi Domain Combat System (MDCX), which will support multiple classification levels, control of multiple unmanned aircraft, and improve MQ-25 interoperability with other DoD systems. UMCS modifies approximately 12 -15 spaces on the aircraft carrier (CVN), using the Ship Change Document (SCD) process, to install the GCS and ancillary systems needed for communications, video management, and integration with existing CVN networks. The NAVWAR C4I systems provide the CVN network paths for air vehicle and mission payload data using a variety of wideband and narrowband communication paths. UMCS modifies and integrates with Launch and Recovery systems on both NIMITZ and FORD class CVNs: Aircraft Launch and Recovery Equipment (ALRE) and Joint Precision Approach Landing Systems (JPALS). Through the Software Support Activity (SSA), UMCS maintains software for the GCS and ancillary systems and verifies integration with MQ-25 Air Vehicle unique software. The GCS has three variants: fixed shore (MD-5D), CVN (MD-5C), and mobile (MD-5E, Embarkable - RDT&E funded). The fixed shore and CVN variants will be permanent installations to support MQ-25 operations. The GCS consists of the following components: Air Vehicle Pilot (AVP) workstations, server racks, network interface racks, integrated communication system (ICS), and software. The CVN variant leverages shore system components but differs slightly to account for the rugged CVN environment. The UMCS ancillary systems provide the necessary communication, data, and network integration paths that allow MQ-25 pilots to control the MQ-25 and exchange data with CVN systems. MQ-25 pilots receive situational awareness data from two sources: the Video Management System (VidMS) and Air Traffic Control (ATC) picture. The Unmanned Carrier Aviation Transport System (UTS), used both afloat and ashore, integrates operational networks to provide narrowband and wideband communications and it contains the Data Transfer System (DTS) which allows the mission plan to be loaded on the MQ-25. Narrowband communications are provided by the ARC-210 Radio Communication System (RCS) and the Digital Modular Radio (DMR), which is used to access the Mobile User Objective System (MUOS). Each of these systems have afloat and ashore variants. The ARC-210 Radio Communication System ship system has an additional equipment rack to integrate with antennas located on the mast. The Integrated communication system half-rack, only installed on CVNs, is the interface between the GCS and Shipboard Air Traffic Control Communications (SATCC) systems allowing MQ-25 pilots access to existing ship radios. There are several ancillary systems that only have shore variants. The Shore Common Data Link (CDL) provides wideband line of sight command and control and data communications between the GCS and the MQ-25. The Ashore Routing Communication System (ARCS) is the interface between the Unmanned Carrier Aviation Transport System and the C4I wideband communication data networks. The URC-300 Voice Communication System is a set of radios for communication between the GCS and flight line personnel. UMCS leads the modification, engineering, and integration activities with NAVWAR C4I baseline systems. NAVWAR C4I is integrating the following baseline Program of Record systems to support MQ-25 operations: Consolidated Afloat Networks and Enterprise Services (CANES), Automated Digital Network System (ADNS), Shore Tactical Assured Command and Control (STACC), Network Tactical Common Data Link (NTCDL), CVN MUOS DMR (AN/SRC-61A(V)18 & AN/SRC-61A(V)19), Shore MUOS DMR (AN/FRC-147A(V)5), Classic Reach, Distributed Common Ground System-Navy (DCGS-N), Global Command and Control System-Maritime (GCCS-M), Automatic Identification System (AIS) & Naval Integrated Tactical Environment System-Next (NITES-Next). UMCS performs CVN infrastructure modifications and hardware installations on twelve (12) NIMITZ and FORD Class carriers and three (3) operational shore locations. Currently there are seven (7) workstations planned for each NIMITZ class carrier and nine (9) workstations per GCS planned for each FORD class carrier. The CONUS shore sites have two (2) GCSs each while the OCONUS site has one (1) GCS. There are nine (9) workstations planned for both the CONUS and OCONUS sites. All CVN Modification Planning and Integration activities follow the NAVSEA Navy Modernization Process (NMP) which identifies specific schedules for documentation, drawing, and hardware deliveries. CVN installations are conducted serially across multiple ship maintenance availability periods. The Navy Modernization Process can be divided into four phases. Phase 1 (three years prior to an availability period) is the CVN system planning and design phase that includes generation of technical data and top-level drawings as well as some long-lead procurement. Phase 2 (two years prior to an availability period) focuses on specific CVN hulls that includes ship checks, generation of drawings, and GCS/ancillary system procurement. Phase 3 (one-year prior to the availability period) is the final approval for design, drawings, schedule, and documentation. Phase 4 is the actual CVN Installation and Shipyard Services process that occurs during an availability period. A minimum of two six-month availability periods are required to complete modifications and installations. Phases 1, 2, and 3 repeat for each availability period. Therefore, it is possible that UMCS can be installing hardware and planning for future installation work on the same CVN or multiple CVNs in any given fiscal year. Modifications and installations are subject to change based on ship availability schedule updates. CVN Modification Planning and Integration requires extensive stakeholder coordination by a program to perform carrier modifications following NAVSEA processes and requirements for integration into a CVN Maintenance Availability (Avail) work package. Programs are responsible to prepare the technical documentation and detailed guidance information for each ship that will be modified per the Ship Change Documents so that Ship Installation Drawings (SIDs) can be produced. This process typically takes over a year, due to the complexity of modifications. The Unmanned Air Warfare Center (UAWC) Ship Change Documents are characterized by NAVSEA as complex since these impact several compartments, cooling, power and network/circuits on the ship. UMCS uses government and contractor resources to prepare the Ship Change Documents and supporting guidance packages across all hulls for both NIMITZ and FORD Class carriers. These resources also manage the communications and administrative paperwork levied on a Program by the Navy Modernization Process leading up to, during and after the ship installation. Guidance packages contain detailed design and interface specifications for the equipment, UAWC arrangement drawings for placement of hardware in the control room, schematics for cabling details, supporting details and analyses to address physical security, cyber design details, RF spectrum studies for topside antennas, and suitability provisions for the shipboard environment. CVN Installation and Shipyard Services involve the physical modifications to the ship. These services are the implementation of the CVN Modification Planning and Integration processes and are significant in scope and cost. The Planning Yard produces Ship Installation Drawings and a Shipyard approved work package with a detailed installation schedule. These installations are aligned with the Avail schedule to minimize impact to key events & milestones so that the ship exits the Avail on time. Contractor Alteration Installation Teams (AITs) perform the industrial work and hardware installation. AITs and their subcontractors must be approved by the Shipyard. Scheduling AITs are done well in advance of the Maintenance Avail, mostly due to the lengthy contracting process and for them to receive approved Ship Installation Drawings to plan the installation work, procure raw materials and align subcontractors. Following the approval of the Ship Change Documents and Ship Installation Drawings, industrial work can proceed during the aligned Avail. Industrial work includes setting up shipyard services (e.g. scaffolding, ventilation, air/electric for tools, storage containers on the pier, material handling/cranes), removal of old paint and hazardous coatings/materials, cutting/grinding of metal, welding structural members, foundations and fixtures, installation of electrical and network cabling, priming and painting, installation of thermal & acoustic insulation, fabrication and installation of ventilation ducting, modification/ increasing the size of cooling fans and coils, and the application of flooring. Once the industrial work has been completed, any hardware to be installed is brought aboard. If the hardware is of small enough size, it will be brought onboard the ship through the existing hatches. However, larger equipment, such as the fan room modifications, will need to have special holes cut in the deck to allow installation. The fully populated racks of the GCS require careful rigging to get the hardware through passageways and hatches into the space. Once these difficulties are overcome, hardware installation ensues, with cabling and other electrical/mechanical tasks going through various quality checks ultimately leading to a final System Operational Verification Test (SOVT).

Justification

Justification UMCS-Unman Carrier Aviation(UCA)Mission Cntrl Stn

The FY 2026 request was reduced by $7.037 million for Advisory and Assistance Services to promote efficiencies and advance the policies of the Administration in alignment with Executive Order 14222, "Implementing the President's Department of Government Efficiency Cost Efficiency Initiative." The FY 2026 request was reduced by $2.333 million for civilian personnel to optimize the workforce in compliance with Executive Order 14210, "Implementing the President's Department of Government Efficiency Workforce Optimization Initiative." The FY26 budget increases by $69.992M from FY25 to FY26 to fund modifications on four (4) aircraft carriers and the installation of the MD-5 Ground Control Station (GCS) on three of those aircraft carriers. One of the installations is to fully fund a complete modification and installation to CVN J, which is accelerated by four years. Additionally, more MD-5 subsystems (also called ancillary systems), are being procured and built in FY26 than in FY25. The MD-5E for the CONUS West site, is being built, tested, and installed. Software Support Activity (SSA) build-up and MD-5 Field Service Representative (FSR) support begin in FY26. In FY2026 UMCS will fund the following: CVN B - Complete Initial Deployment Configuration (IDC) installation. This configuration capitalizes on work performed in prior years when MD-5A was planned and is an evolutionary step to enable Deployment of MQ-25. Only the necessary/limited set of hardware will be installed for Deployment. The Unmanned Air Warfare Center will be configured to the Final Deployment Configuration during a future Maintenance Avail that has sufficient duration to accommodate all necessary major industrial work. - CVN installation and shipyard services began hardware installations in 3rd quarter FY25 during the six-month, FY25 Planned Incremental Availability (PIA) to support deployment: MDCX-C control station (6 pilot consoles,4 processing/storage racks), Unmanned Carrier Aviation Transport System integrated communication system half-rack, Video Management System upgrade, and Work Centers/Ready Room modification to support the MQ-25 detachment. - Procure hardware in support of the tech refresh planned for the Planned Incremental Availability (PIA) to include retrofits to the MD-5C, UTS, VidMS, ARC-210 RCS, and AIT support. - Original Equipment Manufacturer (OEM) field tech support services for the installation of the MDCX-C control station. CVN C - Preparation of ADMACS installation documentation of Engineering Change Proposal 579. CVN D - A large portion of the increase from FY2025 to FY2026 funds the acceleration of CVN D from 2 future avails into 1 avail period. - Execute installation of Final Deployment Configuration (FDC)-Increment 1. This configuration of the Unmanned Air Warfare Center is planned to accommodate all hardware necessary to enable Deployment of MQ-25 with additional multi-level security capabilities. Completion of all work on the CVN includes alteration of the ship with major industrial work to incorporate structural, power, cooling, data/signal cabling, and topside/antennas, MQ-25 work centers, ready room and installation of all UMCS hardware. - Original Equipment Manufacturer (OEM) field tech support services for the installation of the MDCX-C control station. - Installation of ADMACS Engineering Change Proposal 447. - Procure 1 Air Traffic Control (ATC) Picture system, UYY-1, for installation during the Maintenace availability that starts in FY26. CVN E - Commence Initial Deployment Configuration-Increment 1. This configuration capitalizes on work performed in prior years when MD-5A was planned and is an evolutionary step to enable Deployment of MQ-25. - Preparation for the Initial Deployment Configuration-Increment 2. Only the necessary/limited set of hardware will be installed for Deployment. The Unmanned Air Warfare Center will be configured to the Final Deployment Configuration during a future Maintenance Avail that has sufficient duration to accommodate all necessary major industrial work. - CVN installation and shipyard services for the Alteration Installation Teams to perform hardware installations during the four-month, FY26 Selected Restricted Availability (SRA) in support of FY19 NDAA conference language. - MD-5C GCS (6 pilot consoles, 4 processing/storage racks), Unmanned Carrier Aviation Transport System, integrated communication system 1/2 rack. Commence first increment of MQ-25 work centers/Ready Room modifications and ARC-210 Radio Communication System including topside antennas. CVN G - Procure 1 ARC-210 Radio Communication System (RCS) - Ship variant for installation in FY30; this system consists of long lead components (~48 months) CVN J - Complete installation of Final Deployment Configuration (FDC) - Increment 1 of the Unmanned Air Warfare Center (UAWC) to accommodate all hardware necessary to enable MQ-25 deployment with additional multi-level security capabilities and maximum number of operator consoles. Alteration of the ship with major industrial work to incorporate structural, power, cooling, and data/signal cabling, and to incorporate MQ-25 work centers, ready room and installation of all UMCS hardware accelerated to occur during FY25 availability vice FY30 to meet deployment requirements in the current Master Aviation Plan (MAP). - Original Equipment Manufacturer (OEM) field tech support services for the installation of the MDCX-C control station.- Installation of ADMACS workstation into Unmanned Air Warfare Center (UAWC). - Continue CVN installation and shipyard services for the Alteration Installation Team installing all required hardware during the 16-month, FY25 Docking Planned Incremental Availability (DPIA), to include upgrading the fan coil to provide adequate cooling and modifying work centers and pilot ready room for the MQ-25 detachment. CONUS West Operational Shore Location - Procure 1 MD-5D GCS in support of the installation of Core 2, facilities expected to be completed in FY28 timeframe. - Procure 1 Video Management System in support of the installation of Core 2, facility expected to be completed in FY28 timeframe. - Tasking to support Embarkable at West Operational Shore Location to include integration of system and operation support. Tasking includes: fabrication completion, test, shipping, and installation. - Prepare and submit artifacts for Fleet Readiness Certification board (FRCB) approval to support installation and connection to operational networks in Q1 FY26. - Tasking to prepare and submit artifacts for Fleet Readiness Certification board (FRCB) approval to support installation and connection to operational networks in FY26. Tasking includes: (1) System Testing (Test Reports) (2) Cybersecurity & Accreditation Authority to Operate/Interim Authority to Operate (ATO/IATO) - Hardware installation System Operational Verification Test (SOVT) Plans (3) Drawings: floor plans, rack elevations, schematics, block diagrams, network architectural diagrams (4) Logistic and Lifecycle Support Documentation to include Users Logistic Support Summary (ULSS) or Logistics Support Statement (LSS) and Configuration Data Managers Database-Open Architecture (CDMD-OA) CONUS East Shore Location - Procure 1 MUOS Digital Modular Radio (DMR) Communication System Shore for installation in FY29. - Procure 2 Shore Common Data Link (CDL) systems for installation in FY29 - Procure 1 Ashore Routing Communication System (ARCS) for installation in FY29 - Procure 1 ARC-210 Radio Communication System (RCS) for installation in FY29 - Procure 1 UCA Transport System (UTS) for installation in FY29 - Procure 1 ARC-210 Shore Voice Communication System for installation in FY29 - Procure 1 set of ancillary gear for installation in FY29 In FY2026 UMCS will fund the following support tasking: - Revise GCS and ancillary system guidance documentation (top-level drawings and installation instructions) as needed for the CONUS West Shore location. - Continue maturing GCS and ancillary system guidance documentation for the CONUS East and Forward Deployed Naval Forces (FDNF) locations. - Continue preparing GCS installation guidance documents for all FORD Class carriers: all CVNs. These documents allow NAVSEA to generate the Ship Installation Drawings (SIDs). Modification work will be funded with OPN (CVN K) in FY29 - FY32 and planned installation work on in-service CVNs G and K (OPN funded) and during new Ship construction of CVNs H and I (SCN funded). - Continue preparing and updating guidance documents for NIMITZ Class installations; CVNs B, C, D, E, I, and J. Work is required to generate Ship Installation Drawings for the growth configuration planned for the Unmanned Air Warfare Center (UAWC). On CVNs where installation work had been performed to the MD-5A layout, additional guidance is needed to remove and reconfigure the UAWC. - Continue modifying ALRE systems for future installation on FORD Class carriers. This work is necessary for MQ-25 to operate from FORD Class CVNs. - Complete Video Management System redesign due to component End of Life (EOL). - Continue GCS hardening modifications, complete final testing Electromagnetic Interference (EMI), shock, and vibration testing, and implement modifications. - Address obsolescence issues across the MD-5C and MD-5D systems - Continue implementing the UMCS Software Support Activity. - Continue creating technical manuals and Operator/Maintenance Training documentation for the GCS. - Complete integration efforts between the GCS and communication/ancillary systems. - Update technical data, software, and logistics documentation to support GCS operations and maintenance. - Continue C4I support to facility and GCS design to support integration with operational communication systems and networks at the three (3) shore locations. - Update Automated Digital Network System (ADNS) and other C4I systems to support integration with the new GCS and MQ-25 operations. - Continue maturing the shore based network architecture to support wideband beyond line of sight (BLOS) communications using Starlink - Continue modification, integration, and test with externally managed C4I systems to support MQ-25 operations.- Provide continued sustainment for the ARC-210 Radio Communication System. While individual hardware items are fully funded, procurement is based on lead-times and when that system is installed in the CVN or Shore location.

Budget Line Items(workbook-cited)

Exhibit P-1

AccountOrgTypeAmount
Other Procurement, NavyNFY24 Actuals$143.6M
Other Procurement, NavyNFY25 Enacted$119.6M
Other Procurement, NavyNFY26 Disc. Request$189.6M
Other Procurement, NavyNFY26 Total$189.6M

Budget Details(R-2/P-40 facts)

ProjectAll Prior YearsFY24 ActualsFY25 TotalFY26 BaseFY26 Request
Program Element$277.6M$143.6M$119.6M$189.6M$189.6M

No follow-the-dollar view — this program's awards haven't been crosswalked at high confidence (flows cover 17 of 1741 programs). why coverage is partial? →

Awards

No awards are linked to this program element at high confidence — the budget→award crosswalk only asserts links it can defend, and this line has none yet.

Lobbying Mentions

No Senate LDA lobbying filing in the tracked data mentions this program element by code or alias.

No research dossier for this program — dossiers cover 50 of 1741 programs, the largest fully J-book-detailed lines by FY2026 requested dollars. why no dossier here? →