The Pentagon Burned $8 Billion on GPS Software That Still Doesn’t Work After 16 Years
The Pentagon Burned $8 Billion on GPS Software That Still Doesn’t Work After 16 YearsRaytheon got the contract in 2010. It was supposed to cost $3.7B and be done by 2016. It’s now 2026 and the damn thing still can’t go live.
$7.6 billion spent → 7 years behind schedule → still broken after delivery → Pentagon now considering just killing it entirely
The GPS Next-Generation Operational Control System — “OCX” — is the software that’s supposed to command 30+ military GPS satellites and handle their new jam-resistant signals. RTX Corporation (that’s Raytheon with a new coat of paint) has been building it since 2010. They finally “delivered” it last July. Nine months of testing later? More bugs. More delays. The Space Force says the defects will take “substantially more time than planned to resolve.” The Pentagon is now seriously looking at pulling the plug and just upgrading the old system instead.
🧩 Dumb Mode Dictionary
| Term | What It Actually Means |
|---|---|
| OCX | The new GPS ground control software — the thing that tells 30+ satellites what to do |
| RTX / Raytheon | The defense contractor who built this. Changed their name but not their delivery speed |
| GPS III | The newest generation of military GPS satellites — they started launching in 2018 |
| M-Code | Military-only encrypted GPS signal that’s supposed to be jam-proof |
| AEP | The OLD GPS ground system (made by Lockheed Martin) that still works and keeps getting patched |
| GAO | Government Accountability Office — the auditors who keep writing “this is bad” reports |
| Space Force | Yes, it’s real. They run the GPS satellites now |
📅 The Timeline of Pain
- 2010 — RTX wins the OCX contract. Budget: $3.7 billion. Deadline: 2016.
- 2012-2015 — Early warning signs. Software architecture problems. Cybersecurity gaps. The GAO starts flagging concerns.
- 2016 — Original deadline passes. System nowhere close to ready. Cost already ballooning.
- 2018 — First GPS III satellite launches. The ground system to control it? Still cooking.
- 2021 — Pentagon restructures the program. Again. Budget now over $6B.
- July 2025 — RTX finally “delivers” OCX to the Space Force for government testing.
- March 2026 — Nine months of testing reveals even more bugs. Pentagon openly discusses cancellation.
- Now — Total cost: ~$8 billion. Status: nonoperational.
📊 The Receipts
| Stat | Number |
|---|---|
| Original budget | $3.7 billion |
| Current cost | $7.6 billion |
| Extra augmentation cost | $400+ million |
| Years behind schedule | 7 |
| GPS satellites it should control | 30+ |
| Months since “delivery” | 9 |
| Operational status |  Still broken |
| Pentagon’s next move | Considering full cancellation |
🔍 What Actually Went Wrong
Between you and me, this is a textbook case of what defense procurement nerds call “concurrency” — building the plane while you’re flying it.
RTX was developing OCX at the same time the GPS III satellites were still being designed. Every time the satellite specs changed, the ground software had to change too. Layer on top of that:
- Cybersecurity was an afterthought — they had to retrofit security into code that was never built for it
- The government didn’t have enough technical staff to actually oversee what RTX was doing (the GAO flagged this specifically)
- “Poor acquisition decisions” — that’s a direct GAO quote, not my words
- Defect rates stayed high even after restructuring the program multiple times
The kicker? The OLD system (AEP), which Lockheed Martin has been quietly upgrading all these years as a backup, actually works fine. It keeps getting patched. It handles the satellites. It’s not sexy, but it’s functional. So now the Pentagon is probably going to take the useful bits from OCX, fold them into AEP, and pretend the last 16 years of OCX development was “lessons learned.”
🗣️ What People Are Saying
Thomas Ainsworth, Assistant Secretary of the Air Force for Space Acquisition: Called OCX “a very stressing program” — Pentagon-speak for “this is a disaster.”
Space Force spokesperson: Software tests revealed defects requiring “substantially more time than planned to resolve.”
GAO auditors: Identified “poor acquisition decisions” and “slow recognition of development problems” across the entire program history.
Defense community: Multiple analysts pointing out this is the most expensive GPS failure in history — and taxpayers funded every dollar of it.
💰 Where the $8 Billion Actually Went
Here’s the play that defense contractors run, and it works every single time:
- Bid low → RTX bid $3.7B knowing full well the real cost would be higher
- Get locked in → Once the contract is signed and work begins, switching contractors costs even more
- Scope creep → Every requirement change = more billing hours
- Delay = revenue → Every month the project drags on, RTX bills the government for staffing, facilities, overhead
- “Deliver” something → Hand over software that technically exists but doesn’t work → now it’s the government’s problem to find the bugs
- Offer to fix it → For another $400 million, naturally
RTX’s stock price, by the way? Up 40% over the last five years. The system doesn’t work, but the business model absolutely does.
Cool. The Pentagon Just Proved You Can Burn $500 Million a Year and Ship Nothing… Now What the Hell Do We Do? (╯°□°)╯︵ ┻━┻
🕳️ The FOIA Miner
Here’s what you do: Every failed government software project generates MOUNTAINS of public records — inspection reports, audit findings, contract amendments, emails between officials admitting things are broken. These documents are gold for journalists, think tanks, and defense reform groups — and they’ll pay for someone who knows how to find them.
File targeted FOIA requests specifically around OCX subcontractors, testing failures, and internal memos. Package the findings into organized, searchable databases. Sell access to defense journalists and policy researchers.
Example: A 26-year-old policy researcher in Berlin files FOIA requests about failed U.S. defense programs, packages the documents into organized briefs, and sells them at $200/pop to European defense publications. She covers 3 programs per month.
Timeline: First sellable package in 14 days. Steady income by month 2. Plateau when you run out of programs to investigate (you won’t — there are hundreds).
📡 The Legacy System Lifeline
Between you and me, every time a shiny new government IT system fails, the OLD system gets a second life — and a second budget. That means the companies and freelancers who know the legacy tech become instantly more valuable.
The play: learn the old systems that governments keep being forced to fall back on. COBOL is the famous example, but there are dozens of legacy military/government systems running on ancient stacks. OCX failing means AEP (the old GPS ground system) gets more funding → Lockheed needs contractors who understand it → those contractors charge premium rates because nobody under 45 knows this stuff.
Example: A 34-year-old contractor in Hyderabad specializes in maintaining legacy Ada (a programming language the U.S. military loves) codebases. He charges $180/hour for remote consulting because there are maybe 200 people on Earth qualified to do what he does. He found his clients on SAM.gov subcontractor postings.
🪟 The Procurement Tracker
Government contracts are public. Failed ones especially. And there’s a pattern: when a big contract fails, the replacement contract goes out within 6-12 months — often to smaller firms because the big contractor just embarrassed everyone.
Here’s the angle: build a tracker that monitors SAM.gov, USASpending.gov, and FPDS for contracts that are overdue, over budget, or recently cancelled. Cross-reference with GAO audit reports. The result = a heat map of where the NEXT contract opportunity is about to open up. Sell subscriptions to small defense firms who can’t afford their own business development teams.
Example: A 29-year-old data analyst in Bucharest built a scraper that pulls SAM.gov contract modifications daily and flags anything with cost overruns above 200%. He sells a weekly email digest to 40 small U.S. defense contractors at $150/month. That’s $6,000/month from a Python script and a $5 VPS.
🎯 The Audit Report Translator
GAO reports are public, free, and incredibly detailed — but they’re written in bureaucratic English that makes normal humans’ eyes glaze over. The OCX report alone is dozens of pages of dense acquisition jargon.
The trick: translate these reports into plain-language summaries with charts, timelines, and “so what” sections. Post them on Substack or a niche newsletter. The audience? Congressional staffers, defense journalists, policy students, and — here’s the real money — the PR teams at defense contractors who need to know what the government is saying about THEIR competitors.
Example: A 31-year-old former government intern in Nairobi runs a Substack that breaks down one GAO report per week into 800-word plain-English summaries with data visualizations. He has 2,400 subscribers, 300 of them paid at $12/month. That’s $3,600/month from reading documents nobody else wants to touch.
🎰 The Defense Stock Fade
This one’s for the traders. Here’s the pattern: when a major defense program fails publicly → the CONTRACTOR’S stock barely moves (priced in, golden parachute contracts) → but the COMPETITOR’S stock spikes quietly because the street knows the replacement contract is coming their way.
OCX dies → AEP gets the expansion → Lockheed Martin wins. This pattern repeats across every major program failure. The play: track GAO “high risk” program lists, bet on the backup contractor BEFORE the cancellation announcement, and ride the quiet appreciation.
Example: A 27-year-old quantitative analyst in São Paulo built an alert system that scrapes GAO High Risk List updates and cross-references them with defense subcontractor relationships on USASpending.gov. When he sees a program flagged “critical,” he buys options on the backup contractor. His last 4 trades averaged 23% returns.
🛠️ Follow-Up Actions
| Want To | Do This |
|---|---|
| Read the full GAO roast of OCX | GAO-25-106815 report |
| Browse failed defense contracts yourself | USASpending.gov → filter by agency + cost overrun |
| Find subcontractor opportunities | SAM.gov → search “GPS” or “OCX” |
| Track which programs are in trouble | GAO High Risk List (updated regularly) |
| Understand how military GPS works | GPS.gov official explainer |
| Read the original Ars Technica deep dive | Full article |
Quick Hits
| Want | Do |
|---|---|
 Understand the scale |
$8B = enough to fund NASA’s entire Artemis I mission twice |
 Read the audit |
Grab the GAO report — it’s free and devastating |
 Find defense contract opps |
Set alerts on SAM.gov for cancelled program rebids |
| Track GPS status |
GPS.gov constellation status — real-time satellite health |
 Follow the money |
USASpending.gov → search “RTX” or “Raytheon” |
Between you and me, the scariest part isn’t that they burned $8 billion — it’s that the GPS in your phone right now is being controlled by the “backup system” that was never supposed to be permanent. Sleep tight.
!