The US Military’s GPS Software Is an $8 Billion Mess | WIRED
Sixteen Years, $8 Billion, and a Ground System That Still Doesn't Work
Bottom Line Up Front
On July 1, 2025, the U.S. Space Force accepted formal delivery of the GPS Next-Generation Operational Control System from RTX Corporation. Senior leaders issued cautious statements expressing guarded optimism. Nine months later, the system still cannot operate GPS satellites in any full operational capacity, the Pentagon is weighing termination of the RTX contract, and the program — already the most-cited cautionary tale in U.S. space acquisition — has deepened its extraordinary record of failure.
The timing is painfully ironic: RTX's primary contract option expired on March 31, 2026 — the same week that Thomas Ainsworth, performing the duties of the Space Force acquisition executive, delivered prepared congressional testimony acknowledging that government-led testing had exposed "extensive system issues across all sub-systems," and that the program's persistent troubles stem from a systemic breakdown on both sides of the government-contractor relationship that has persisted for over a decade.
Origins and Architecture
The OCX program traces its origins to a recognition in the early 2000s that the GPS constellation was being modernized — new satellites, new signals, new cybersecurity requirements — and the legacy ground control system, the Architecture Evolution Plan (AEP) managed by Lockheed Martin, would eventually be unable to support it. In 2010, the Air Force awarded RTX (then Raytheon) a contract to design and build the replacement. Prototyping had actually begun as early as 2007.
From the outset, OCX faced a requirements profile of unusual ambition: it was required not just to command and control the GPS constellation, but to do so with an unprecedented level of cyber-hardening — a ground system designed to be effectively impenetrable to adversary intrusion — while simultaneously managing a full suite of modernized signals including the L2C civilian signal, the L5 aviation safety signal, and critically, the M-code military signal. The system was also required to support two master control stations and a network of 17 global monitoring stations.
A Government Accountability Office report from 2015 identified the foundational problem early: "The Air Force began OCX development in 2010 prior to completing preliminary development reviews in contrast with best acquisition practices." That premature start, combined with accelerating the schedule in 2012 to align with optimistic GPS III satellite launch timelines, set a trajectory toward failure that compounding decisions over the next decade could not reverse.
"Poor acquisition decisions and a slow recognition of development problems."— U.S. Government Accountability Office, characterizing OCX program management (GAO-15-657, 2015)
The Nunn-McCurdy Breach and First Reckoning
By mid-2016, the program had deteriorated to the point that the Air Force was compelled to notify Congress of a Nunn-McCurdy breach — the Pentagon's formal threshold for a "critical" cost overrun, triggered when per-unit program cost rises more than 25% above current baseline. OCX had blown past that threshold, and a mandatory review process was initiated to determine whether the program should be cancelled or restructured.
The factors behind the breach were damning. Root cause analysis identified inadequate systems engineering at program inception, Block 0 software carrying a high defect rate, and Block 1 designs requiring extensive rework. In October 2016, then-Pentagon acquisition chief Frank Kendall — applying significant pressure through quarterly reviews — certified the program to continue on the grounds that no viable alternative existed and that the program was vital to national security. Raytheon's program manager offered assurances that the company had "turned the corner."
It had not. The subsequent eight years produced a succession of schedule rebaselines, cost adjustments, and promised delivery dates that came and went without operational acceptance. The 2012 cost estimate of $3.7 billion grew to $4.3 billion by 2015 and $6.2 billion by 2018. By November 2023, the GAO reported costs for Blocks 0, 1, and 2 at $7.6 billion. Accounting for Block 3F — the follow-on version required to control GPS III Follow-On satellites — the total program cost approaches $8 billion, with some GAO analysis projecting the full lifecycle cost to exceed $10 billion.
| Milestone | Original Plan | Actual / Current | Status |
|---|---|---|---|
| Contract Award | 2010 | February 25, 2010 | On time |
| Original Contract Value | $1.5–$3.7B | $7.6B+ (Blocks 0–2) | +$4–6B overrun |
| Delivery Date | 2016 | July 2025 (acceptance) | 9 years late |
| Nunn-McCurdy Breach | N/A | June 2016 (>25% overrun) | Critical breach |
| Block 0 Delivery | 2016 | November 2017 | 1+ yr late; limited function |
| Block 1 & 2 Delivery | 2016 | July 2025 (accepted) | 9 years late; non-operational |
| Operational Acceptance | 2016 | Unknown / TBD | Not yet achieved |
| Open Deficiencies (Dec. 2024) | 0 at delivery | 270+ (102 site acceptance, 129 developmental, 39 simulator) | Unresolved |
| Block 3F (GPS IIIF support) | 2025 | 2027–2028 (projected) | 2–3 yr delayed |
| RTX Contract Option | Ongoing | Expires March 31, 2026 | Unlikely to be extended in full |
The M-Code Imperative: What Is Actually at Stake
Understanding why OCX's failure matters operationally requires understanding M-code — the Mil-Code encrypted GPS signal that is the core military modernization at issue. M-code is designed to be jam-resistant and spoof-resistant in contested environments, transmitted from separate high-power antennas on GPS III satellites in a spot beam configuration delivering roughly 20 dB more power than the full-Earth signal. It was scheduled to enter operational service in October 2016. It has not done so.
M-code requires OCX Block 2 for full broadcast capability. While 24 of the 31 operational GPS satellites are M-code-capable in hardware, and while Space Systems Command implemented stopgap modifications to the legacy AEP in 2020 enabling a limited subset of M-code operations, full M-code capability has not been fielded. The Pentagon's independent test office, the Director of Operational Test and Evaluation, stated in its most recent annual report: "Continued delays to OCX put U.S. warfighters and allies at risk" — noting that full M-code capability has not been deployed for operational use.
The downstream implications extend across approximately 700 weapon system types — aircraft, ground vehicles, ships, and munitions — that will ultimately require M-code-capable user equipment. The Military GPS User Equipment (MGUE) program, which develops the receiver chips and cards necessary to exploit the M-code signal, faces its own parallel set of delays, but its utility remains fundamentally limited without a functioning OCX ground segment. Alison Brown, president and CEO of GPS systems supplier NAVSYS Corp., put it plainly: "You can't do anything, even with existing capability, until they get" the full M-code ecosystem operational.
The GPS III Follow-On (IIIF) satellite program, under Lockheed Martin at a cost approaching $9 billion for up to 22 satellites, adds another dimension of urgency. GPS IIIF will provide a steerable, high-power M-code signal known as Regional Military Protection — providing warfighters with dramatically increased jamming resistance in localized areas of contested operations. OCX Block 3F is required to operate these satellites. The first IIIF satellite has already slipped from a projected April 2026 launch to November 2026, partly due to technical issues with the satellite's mission data unit. OCX delays further compress the already marginal timeline for IIIF support.
Testing Revelations and the Path to Cancellation
The sequence of events that now threatens outright program termination began in mid-2025 when OCX transitioned from contractor-led to government-led testing. That transition — standard practice as a program moves toward operational acceptance — proved far more revealing than the Space Force anticipated.
As of December 2024, before the government-led phase began, the GAO had already documented 102 open deficiencies related to site acceptance testing requirements, 39 related to simulators and testing systems, and 129 directly related to developmental testing. An April 2024 assessment had identified a backlog of 292 critical deficiencies. Testing in 2024 achieved only an 88% pass rate against a reported Space Force requirement of 100%. GAO noted bluntly that "it is hard to be optimistic with estimated time frames, particularly with OCX given recent performance."
Government-led testing made things worse. In a March 27, 2026, email to Air & Space Forces Magazine, a Space Force spokesperson stated that testing had revealed software defects requiring "substantially more time than planned to resolve," and that the issues driving delays "are in part a continuation of challenges the program has repeatedly been experiencing." The Space Force has now conducted what it describes as a "lengthy analysis" of options, including full cancellation.
People familiar with Pentagon deliberations told SpaceNews that the RTX contract option is "unlikely to be extended in full." Instead, officials are evaluating a hybrid approach: retaining RTX in a limited role for near-term needs such as launch support for an upcoming GPS III mission, while harvesting usable components from the delivered OCX software and integrating them into an upgraded AEP system. The legacy AEP, originally intended as a temporary bridge pending OCX completion, has through Lockheed Martin's incremental upgrades evolved into a potential long-term alternative. Lockheed completed the AEP 7.5 upgrade in 2018, described as the largest architectural change in the system's history. A Space Force spokesperson confirmed that if OCX is cancelled, "AEP will require further upgrades to enable GPS III's L5 civilian signal and to support GPS IIIF satellites," but that GPS constellation operations would not be interrupted since AEP is currently providing full command and control.
"There's been problems in program management, problems with contractor performance, problems in system engineering, both on the government and on the contractor side, over a number of years."— Thomas Ainsworth, performing duties of Space Force Acquisition Executive, testimony to House Armed Services Committee, March 25, 2026
Congressional Reckoning
The March 25, 2026, hearing before the House Armed Services Committee's Strategic Forces Subcommittee brought rare bipartisan exasperation to the surface. Rep. Don Bacon (R-Neb.) asked Ainsworth directly: "We're still struggling with it. Can you tell us what went wrong, or what are we learning from this?" Ainsworth's response, while diplomatically balanced, amounted to an acknowledgment of systemic institutional failure at every level of the program.
GAO Director Jon Ludwigson, whose office has tracked OCX since 2009 and issued more than a dozen major reports on the program, offered an unusually candid assessment to reporters: "This has clearly been a beleaguered program. I think folks would have very much liked it to have been completed and called a win." An updated GAO assessment is expected. Ludwigson's office had previously found that the Air Force "consistently overstated progress to the Office of the Secretary of Defense compared to advisory independent assessments it received" — a finding that underscores the degree to which institutional optimism bias compounded technical failures for years without triggering decisive corrective action.
RTX's response has remained corporate and defensive. An RTX spokesperson stated: "The GPS OCX program is a large-scale, highly complex ground system modernization effort. The U.S. Space Force accepted delivery of a mission-capable system in 2025 and assumed operational control at that time. RTX is working alongside the government to address any post-delivery concerns." The company declined to address specific deficiency counts or timeline commitments.
The Contractor Accountability Question
The OCX program has shadowed RTX's standing with Space Force acquirers for years. Space Systems Command maintained a Contractor Responsibility Watch List — informally described by former Space Force acquisition chief Frank Calvelli as "Santa's naughty list" — under which designated contractors face restrictions on receiving new contracts, engineering change proposals, or option exercises. In late 2024, SSC commander Lt. Gen. Philip Garrant confirmed that a contractor was currently on the watch list, contributing to a high-priority space program, while declining to name the company. Circumstantial evidence — the timing, Calvelli's repeated public criticisms of OCX as an "albatross" and "problem child," and Lockheed Martin's explicit exclusion from speculation — pointed strongly toward RTX.
The 2025 National Defense Authorization Act transferred watch list authority from SSC to the service acquisition executive, and Calvelli indicated before his departure that he intended to use it more aggressively. The implications for RTX's broader Space Force work could be significant if the OCX program is formally terminated for default or convenience.
Acquisition Lessons — Applied Too Late
Analysts and officials across the defense acquisition community have cited OCX as a case study in the pathologies of large-scale, single-contractor, fixed-scope software development. The program attempted to build an extraordinarily complex, cyber-hardened system in a single monolithic architecture — an approach now widely recognized as fundamentally incompatible with complex software-intensive programs. Calvelli and other officials have said the program "attempted to create an entirely new, very large software system all in one go, a practice now largely abandoned in favor of rapid, iterative updates."
NAVSYS Corp.'s Brown attributed much of the cascading failure to requirements instability: "They keep changing requirements and keep adding stuff on. It's like everything in the kitchen sink." The cybersecurity mandate was particularly cited as a compounding driver of complexity — the Air Force wanted a ground system with unprecedented cyber resilience, which, while operationally essential given adversary satellite-jamming and intrusion capabilities, substantially elevated the engineering difficulty of an already-ambitious program.
The GAO's 2019 assessment identified a further institutional failure: the absence of an independent schedule assessment. Best practices for complex programs of this magnitude require periodic independent schedule reviews. For most of OCX's development history, such assessments either did not occur or were not acted upon. GAO made the recommendation; DoD concurred but treated existing actions as sufficient. They were not.
Outlook: Where the GPS Enterprise Goes from Here
The Space Force faces a branching decision tree with no clean options. Full cancellation of OCX would preserve AEP operations but require additional investment to bring legacy infrastructure to the point of fully supporting GPS III signals and GPS IIIF satellites — a process that could itself introduce scheduling risk into the IIIF constellation rollout. The "harvest" approach — extracting reusable OCX components and integrating them into AEP — offers a middle path but requires careful systems engineering to avoid introducing defects from a known-problematic codebase into an otherwise-stable operational system.
Any path forward will also require a resolution of the MGUE user equipment challenge. Without sufficient numbers of M-code-capable receiver cards deployed across the force — a separate but interdependent program involving BAE Systems, L3Harris, and RTX in parallel roles — even a fully functional OCX ground segment would not translate into warfighter capability. The Air Force has been most delayed in integrating M-code with its aviation and maritime platforms. The Army has made more progress, with platforms scheduled for fiscal years 2024–2025; the Navy is completing maritime receiver testing.
Compounding the picture is the parallel cancellation by the Space Force of the Resilient GPS (R-GPS) small satellite program — a proposed proliferated layer of GPS satellites intended to increase constellation resilience against jamming and kinetic attack — which did not survive the FY2026 budget process due to "higher priorities within the Department of the Air Force." The simultaneous collapse of the ground segment modernization and the resilience-layering initiative leaves the GPS enterprise more vulnerable than planners envisioned even five years ago.
For the warfighter, the bottom line has not changed materially since 2016: the M-code signal that was supposed to provide assured PNT in contested environments a decade ago remains out of reach. In an era when GPS jamming and spoofing are increasingly routine in multiple active theaters of operation — as documented in multiple open-source analyses of electronic warfare activity in Ukraine, the Middle East, and the Indo-Pacific — the absence of operational M-code capability is not an abstract bureaucratic failure. It is a gap in the force.
Verified Sources & Formal Citations
https://arstechnica.com/space/2026/03/after-16-years-and-8-billion-the-militarys-new-gps-software-still-doesnt-work/
https://spacenews.com/pentagon-weighing-termination-of-raytheon-gps-ground-control-contract-after-years-of-delays/
https://www.airandspaceforces.com/pentagon-eyes-canceling-troubled-gps-ground-system/
https://breakingdefense.com/2025/07/space-force-begins-testing-of-first-ocx-software-blocks-for-gps-sats/
https://www.airandspaceforces.com/space-force-new-operating-system-gps-accepts/
https://www.airandspaceforces.com/space-force-long-delayed-gps-ground-control-ocx/
https://www.defensedaily.com/upgrading-current-gps-ground-system-now-a-viable-option-as-gps-ocx-problems-continue-space-official-says/space/
https://www.c4isrnet.com/battlefield-tech/space/2023/06/09/space-force-sees-further-delays-to-troubled-gps-ground-segment/
https://breakingdefense.com/2024/02/ground-system-for-jam-resistant-gps-delayed-again-to-july-2025-at-earliest-pentagon-tester-says/
https://www.nationaldefensemagazine.org/articles/2024/11/12/timeline-for-troubled-gps-programs-continues-to-grow
https://www.theregister.com/2024/09/10/gps_modernization_us_gao/
https://breakingdefense.com/2023/04/space-force-to-implement-santas-naughty-list-of-contractors-for-under-performance/
https://federalnewsnetwork.com/defense-main/2024/11/space-force-puts-a-defense-contractor-on-watch-list/
https://www.gpsworld.com/raytheon-receives-space-force-gps-ocx-contract-extension/
https://insidegnss.com/space-force-cancels-resilient-gps-smallsat-layer-citing-budget-priorities/
https://www.gao.gov/products/gao-15-657
https://www.gao.gov/products/gao-18-74
https://www.gao.gov/products/gao-19-250
https://www.gao.gov/assets/gao-24-106841.pdf
https://spacenews.com/air-force-declares-nunn-mccurdy-breach-on-gps-ground-system/
https://www.defensenews.com/air/2016/10/17/raytheon-s-ocx-offering-survives-nunn-mccurdy-breach/
https://breakingdefense.com/2024/02/ground-system-for-jam-resistant-gps-delayed-again-to-july-2025-at-earliest-pentagon-tester-says/
https://www.gps.gov/next-generation-operational-control-system-ocx
https://investors.lockheedmartin.com/news-releases/news-release-details/lockheed-martin-delivers-gps-iii-contingency-operations-cops
