Skip to content
Fiscal Receipts

Mobile User Objective System

Air ForceProcurementReconciledBLIMUOS00
What it is
Mobile User Objective System (MUOS00) is an Air Force procurement line funded in the Procurement, Space Force account.
What changed
-$15.7M FY25→26 P-1 TOA · PB2026
Who gets it
No company is linked to this line. Award records do not carry the program element, so the crosswalk is silent here — why.

Budget figures

FY24 Actuals
$111.0MP-1 TOA · PB2026
FY25 Enacted
$64.7MP-1 TOA · PB2026
FY26 Request
$49.0MP-1 TOA · PB2026
FY25→26 Change
-$15.7MP-1 TOA · PB2026
Data coverage

FY2026 award data is a partial year — USAspending reports awards on a rolling basis, and this corpus runs through 2026-09-04. why partial FY2026 data? →

Budget trajectory

The program's 3 summary figures for FY24 to FY26, plotted in fiscal-year order: this line ends lower than it starts. The points are the summary cards above, not a separate derivation; the table beside the chart carries each figure with its own citation.
The program's 3 summary figures for FY24 to FY26, plotted in fiscal-year order: this line ends lower than it starts. The points are the summary cards above, not a separate derivation; the table beside the chart carries each figure with its own citation.FY24: $111.0MFY25: $64.7MFY26: $49.0MFY24FY25FY26
Budget trajectory: one row per fiscal year, carrying the summary figure the sparkline plots. Every figure opens its own citation.
Fiscal yearAmount
FY24$111.0M
FY25$64.7M
FY26$49.0M

All series figures: P-1 TOA · PB2026

Decade view

P-1/R-1 workbook TOA basis, shown compact in $B/$M (the workbook records USD thousands); each figure cites its own President's Budget edition

5 fiscal years of this program as published (FY2022–FY2026): a line through the actuals (filled dots), with the enacted (hollow circles) and request (diamonds) markers each edition reported. Read it for direction, not for precision — this program's actuals line rises across the span. The grid below is the same data as text, one cited figure per cell.
5 fiscal years of this program as published (FY2022–FY2026): a line through the actuals (filled dots), with the enacted (hollow circles) and request (diamonds) markers each edition reported. Read it for direction, not for precision — this program's actuals line rises across the span. The grid below is the same data as text, one cited figure per cell.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 editionFY22FY23FY24FY25FY26

The vertical scale does not start at zero: the baseline sits just below this program’s smallest year, so a low point on this line is not a small amount. Read the shape for direction and the grid below for the figures.

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

Decade series values by fiscal year and President's Budget edition: one row per series (actuals, enacted, request), one column per fiscal year. Every figure opens its own citation.
SeriesFY22FY23FY24FY25FY26
Actuals$45.4M$46.8M$111.0M
Enacted–$46.8M$101.1M$64.7M
Request––$101.1M$51.6M$49.0M

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

Asked vs spent: the PB2024 book requested $101.1M for FY2024; the PB2026 book reported $111.0M as actual total obligation authority — $9.90M above the request. 111.0 − 101.1 = 9.9 USD millions — the compact figures above are rounded for reading.

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 — Mobile User Objective System

The Mobile User Objective System (MUOS) provides a worldwide, multi-service population of mobile and fixed-site terminal users with ultra-high frequency (UHF), narrowband, and beyond line-of-sight satellite communications (SATCOM). MUOS significantly increases performance and capacity in support of critical Combatant Command SATCOM priorities. MUOS is the replacement system for the UHF Follow-on (UFO) system, which is currently beyond its design life. MUOS consists of Space, Ground, and User Entry Segments. MUOS reached full operational capability October 2019. The Space Segment consists of five geosynchronous satellites to support a four satellite constellation over the intended service life, and provides both a legacy UHF payload, which is backward compatible with UFO, and a Wideband Code Division Multiple Access (WCDMA) payload, which provides cellular-like capability. The User Entry Segment consists of the MUOS waveform that is ultimately integrated into MUOS- capable terminals. The cost for MUOS Ground Segment upgrades varies depending on the complexity of software defects being addressed and unique configuration of hardware and software requirements being fielded at each of the six MUOS ground sites within each given year. The MUOS Ground Segment upgrades address cybersecurity and lifecycle management issues at each of the six MUOS ground sites. The Ground Segment or System consists of four world-wide Radio Access Facilities (RAFs) (Wahiawa, Hawaii; Northwest Chesapeake, Virginia; Niscemi, Italy; and Geraldton, Australia) and two Satellite Control Facilities (Port Hueneme, California, and Schriever Space Force Base (SFB), Colorado). Each RAF includes three 60 ft. antennas and over 50 equipment racks which house a total of 5,000 major hardware components and 250 software applications across the MUOS Program. The RAF in Hawaii includes a Network Management Facility (NMF). The RAFs in Hawaii and Virginia each include a Switching Facility (SF). All four RAFs and two Satellite Control Facilities are considered Ground Sites. Beginning in FY 2017, the program's focus has been upgrading ground sites to address ongoing cybersecurity threats, hardware and software obsolescence, and operational deficiencies. The program awarded the follow-on ground sustainment and modernization contract in FY 2025. Funding for this exhibit is contained in PE 1203109SF. FY 2025 Full-Year Continuing Appropriations and Extensions Act included additional funding for Mawar Typhoon Disaster Relief.

Justification

Justification — Mobile User Objective System

The FY 2026 funding will address obsolescence and cybersecurity vulnerabilities within the MUOS Ground Segment. Emerging cybersecurity threats, increasing cybersecurity requirements, and the evolution of denial-of-service threats against DoD systems have made it imperative for the MUOS ground system to keep pace. Funding will be used to procure Ground System updates for each of the six ground sites in each fiscal year through the Future Year Defense Program (FYDP) to correct hardware and software deficiencies. The ground system updates address hardware/software defect resolution and hardware degradation. The hardware/software updates are installed at each ground site as part of the MUOS operational end item requirements; ground system defect resolution includes associated engineering, integration, test, and delivery efforts to address cybersecurity vulnerabilities, and corrects issues to ensure readiness levels support the warfighter's narrowband SATCOM requirements. These Ground System updates will address hardware degradation; obsolete items to be replaced include Redhat/Linux Operating System (OS)-based components and GPS-based Timing and Frequency Distribution System. FY 2026 funding will allow the program to rapidly respond to implement system resiliency and situational awareness necessary to operate through the contested space domain. Activities may include, but are not limited to, program office support, studies, technical analysis, and activities that may leverage commercial, U.S. Government partnership, and international opportunities to respond to existing and emerging adversarial threats with speed and agility, etc

Budget line items(workbook-cited)

P-1/R-1 workbook Total Obligation Authority basis (USD thousands) · PB2026.

Exhibit P-1

AccountOrgTypeAmount
Procurement, Space ForceFFY24 Actuals$111.0M
Procurement, Space ForceFFY25 Enacted$64.7M
Procurement, Space ForceFFY26 Disc. Request$49.0M
Procurement, Space ForceFFY26 Total$49.0M

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

J-book detail basis (R-2/P-40, USD millions) · PB2026 — a different accounting basis from the P-1/R-1 workbook TOA above; where the two disagree, the reconciliation strip under Budget figures shows both.

Wider than this screen — swipe the table sideways for the remaining fiscal-year columns.

ProjectAll Prior YearsFY24 ActualsFY25 TotalFY26 BaseFY26 Request
Program Element$101.6M$111.0M$64.7M$49.0M$49.0M

Follow the dollar

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

Awards

No awards are linked to this program element at high or medium 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.

Oversight

Department-level designation (not specific to this program)

GAO lists 5 high-risk areas for DOD as a whole. That designation covers the department, not Mobile User Objective System. No program-specific GAO finding for this line is in the ingested data. See the DOD oversight record.

Program dossier

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

Primary sources

Open any budget figure for its exact receipt. Verified line items lead with the highlighted government PDF; original spreadsheets download with their budget edition and exhibit in the filename.

Budget totals · TOA sources

Detailed budget justification

The related TOA spreadsheets above use a different accounting basis from R-2/P-40 detail. Their amounts are not assumed to match these detailed sources.