Why the Pentagon’s GPS backup push still has an alignment problem

Original AFA Connect reporting. Facts are attributed to the public records and reporting listed below. Report a factual error.

Sources and records

• Precision Navigation Systems: Challenges Remain with Fielding New Capabilities — U.S. Government Accountability Office
• Precision Navigation Systems: Challenges Remain with Fielding New Capabilities — Accessible Report — U.S. Government Accountability Office
• Watchdog Urges Alignment Across Pentagon’s GPS Backups — Air & Space Forces Magazine
• GPS III at Buckley Space Force Base — Defense Visual Information Distribution Service / U.S. Space Force

Image: Context image: U.S. Space Force photo by Staff Sgt. Amanda Flower via DVIDS; depicts GPS III Space Vehicle 10 transport on Jan. 6, 2026, before GAO’s Oct. 7 report.

The Pentagon’s effort to make positioning, navigation and timing more resilient is not one program. It is a chain of satellite control, secure receivers, service-specific integration and alternatives that can work when GPS is disrupted. A new Government Accountability Office review shows why that distinction matters: progress in one link cannot compensate for schedules and budgets that remain misaligned elsewhere.

The GAO report, released Oct. 7, found that Department of Defense GPS modernization still faces delays while the services pursue complementary PNT systems. GAO said fragmented efforts complicate the Pentagon’s ability to complete M-code and complementary-PNT work promptly. Its central concern is coordination: the PNT Oversight Council can make budget recommendations, but the military departments still control their own budgets.

Context image: Defense Contract Management Agency members prepare GPS III Space Vehicle 10 for loading aboard a C-17 at Buckley Space Force Base, Colorado, on Jan. 6, 2026. U.S. Space Force photo by Staff Sgt. Amanda Flower via DVIDS. The photo predates GAO’s Oct. 7 report.

The appearance of U.S. Department of War visual information does not imply or constitute DoW endorsement.

The control-system reset makes the dependencies visible

GAO reported that the Defense Department directed the Air Force in April 2026 to terminate the long-delayed Next Generation Operational Control System, known as OCX. The Space Force had accepted OCX in July 2025 with waivers and deviations, but later analysis concluded that completing it posed more risk than modifying the existing Operational Control Segment.

That decision did not remove the requirement; it moved the work. GAO said the Space Force awarded contracts in April and July to modify the existing control system for GPS IIIF satellites. Program officials said ground-control capability would be needed by early 2027 to support the planned 2028 launch of the first GPS IIIF satellite. The cancellation therefore creates schedule risk for launch, checkout and operations rather than a clean reset with no downstream effects.

The organizational handoff matters as much as the technology

The report also documents a shift in responsibility for secure M-code user equipment. The first increment moved from the Space Force to the Air Force under a 2024 mandate, and the services agreed in 2025 to move the second increment as well. Program officials began transferring both efforts to an Air Force-managed joint office in December 2025.

That consolidation could improve accountability, but it also exposes an integration test: aircraft, ships, munitions and other platforms must receive compatible equipment on schedules set by different services. A receiver program can meet its own milestone while the platform integration needed to use it remains late. For commanders, the meaningful measure is not the number of programs underway; it is whether satellites, control systems, receivers and fallback sources can be fielded as a usable chain.

What alignment should look like

GAO made three recommendations—one for each military department—to assess where consolidating GPS modernization and complementary-PNT efforts would improve strategic alignment and to develop consolidation plans. The Defense Department concurred.

The practical test is whether those plans produce common dependency schedules, named owners for cross-service interfaces and budget decisions tied to operational outcomes. For the Air Force and Space Force, that means treating control-system modernization, M-code receivers and alternative PNT as one resilience problem even when they remain separate acquisition lines.

The Pentagon does not need every service to buy the same solution. It does need a portfolio in which the timing of one program does not quietly make another unusable. GAO’s findings suggest that the remaining alignment gap is less about recognizing the threat to GPS than about governing the interdependent response.

Sources: U.S. Government Accountability Office, GAO-27-107676; Air & Space Forces Magazine; DVIDS image record.