Raytheon Burned $8 Billion on GPS Software That Still Doesn’t Work After 16 Years
Raytheon Burned $8 Billion on GPS Software That Still Doesn’t Work After 16 YearsThe Pentagon hired one contractor in 2010 to upgrade GPS ground control. Sixteen years, three restructurings, and $8 billion later — it’s still broken.
$8 billion spent. 16 years elapsed. Zero operational capability. The Pentagon is now considering pulling the plug entirely.
Raytheon (now RTX Corporation) won the contract in 2010 to build new ground control software for GPS III satellites. It was supposed to cost $3.7 billion and ship by 2016. Instead, nine months after “delivery,” the system still can’t actually run the GPS constellation. The GAO blamed poor engineering, bad acquisition decisions, and a “persistently high software defect rate.” And now the military might just kill the whole thing.
🧩 Dumb Mode Dictionary
| Term | Translation |
|---|---|
| OCX | GPS Next-Generation Operational Control System — the software that’s supposed to tell 30+ GPS satellites what to do |
| RTX Corporation | Raytheon’s new corporate name after merging with United Technologies. Same company, fancier letterhead |
| GPS III | The newest generation of GPS satellites. Been launching since 2018. Still waiting for their brain to boot up |
| GAO | Government Accountability Office — the federal auditors who keep writing reports nobody acts on |
| Ground segment | All the stuff on Earth that controls the satellites: control stations, monitoring stations, and (theoretically) working software |
| GPS IIIF | Even NEWER GPS satellites arriving next year that need yet another $400M software add-on |
📖 The Backstory: How We Got Here
OKAY SO here’s the timeline of this absolute trainwreck:
- 2010: Raytheon wins the contract. Budget: $3.7B. Deadline: 2016. Easy, right?
- 2016: Costs blow past targets so badly that the Pentagon triggers a formal review for possible cancellation. They restructure instead.
- 2018: GPS III satellites start launching. The satellites are fine. The ground software to run them? Still broken.
- July 2025: Space Force officially “takes delivery” of OCX. Everyone celebrates.
- March 2026: Nine months later, it’s still not operational. Officials admit to Congress it’s “a very stressing program.”
The budget has more than doubled — from $3.7B to $7.6B. And there’s another $400M+ tacked on for GPS IIIF support. That’s $8 billion total for software that doesn’t work.
📊 The Numbers Are Bonkers
| Metric | Original Plan | Reality |
|---|---|---|
| Budget | $3.7 billion | $8 billion (and counting) |
| Deadline | 2016 | Still not operational in 2026 |
| Years over schedule | 0 | 10+ years |
| Cost overrun | 0% | ~116% over original budget |
| Satellites waiting | 0 | 30+ GPS III birds flying without new ground control |
| Restructurings | 0 | At least 3 |
| Status after “delivery” | Operational | Nonoperational |
🔍 What Actually Went Wrong
The GAO basically wrote a roast. Their findings:
- “Poor acquisition decisions” — the Pentagon signed off on a plan that was too ambitious from day one
- “Slow recognition of development problems” — everyone knew it was failing and nobody hit the brakes
- “Persistently high software development defect rate” — the code was riddled with bugs. Persistently. That word is doing heavy lifting.
- Cybersecurity software issues — in a system designed to run military GPS. (Let that sink in.)
- “Poor systems engineering” by Raytheon — the GAO’s polite way of saying the contractor couldn’t build what they promised
- Government’s lack of software expertise — the people overseeing the project didn’t understand software well enough to catch problems early
Even after restructuring the program, it kept running into delays and overruns. The assistant secretary of the Air Force told Congress: “It’s a very stressing program.” And added they’re “still considering how to ensure we move forward.”
That’s Pentagon for “we might kill this.”
🗣️ Why This Matters Beyond GPS
This isn’t just a GPS story. It’s the pattern:
- The F-35’s software has been plagued by similar issues for decades
- The VA’s health records modernization burned $5.5B before getting paused
- The IRS spent $1.7B on a tax processing system that still runs COBOL from the 1960s
The defense acquisition system was designed for buying tanks and jets — physical things you can inspect. Software is different. You can’t kick the tires on 25 million lines of code. And when the contractor’s incentive is to bill hours, not ship working products, you get exactly this.
The GPS constellation still works fine on the old system, by the way. But GPS III’s advanced jam-resistant signals and new capabilities are basically locked behind software that can’t run them. The satellites are up there. They’re ready. The ground just can’t talk to them properly.
😤 The Reactions
- Congress: Increasingly impatient. Multiple hearings. Still writing checks.
- Space Force: Admitted the program is “stressing” — but hasn’t pulled the trigger on cancellation
- GAO: Has written multiple reports basically saying “we told you so”
- Defense industry watchers: Pointing out that RTX keeps getting new contracts despite the OCX mess
- Taxpayers: Mostly don’t know this exists (which is kind of the problem)
Cool. The Pentagon can’t build software. Now What the Hell Do We Do? ( ͡ಠ ʖ̯ ͡ಠ)
🔍 Become a GovTech Auditor / Compliance Consultant
Government agencies are desperate for people who can actually evaluate whether contractors are delivering what they promised. The GAO can’t audit everything — there are independent firms that do this work, and they bill $200-400/hour. You don’t need a security clearance to start — many state and local contracts need the same oversight.
Example: A former QA engineer in Bucharest started doing remote compliance audits for a US-based GovTech consultancy after getting a CMMI certification online. She reviews contractor deliverables against SOW requirements. Pulls in $6,500/month working 25 hours a week.
Timeline: 2-3 months for relevant certifications (PMP, CMMI, or FedRAMP basics). First contracts within 6 months.
💰 Build Open-Source Alternatives to Bloated Gov Software
Here’s the thing — a lot of government software requirements aren’t actually that complicated. They just get buried under layers of compliance theater. Open-source projects like OpenMRS (medical records) and DHIS2 (health data) have proven that small teams can build what billion-dollar contracts fail to deliver. Governments are increasingly open to FOSS solutions if they meet security requirements.
Example: A three-person team in Estonia built an open-source document management system that got adopted by two Baltic state agencies. They now sell support contracts at €3,000/month per agency and have 11 clients.
📝 Start a GovCon Newsletter or Podcast
The government contracting space is a $700B+ annual market and most people in it get their info from boring PDFs. There’s a real gap for someone who can translate GAO reports, contract awards, and acquisition failures into plain English. Monetize through sponsorships from GovTech startups, consulting referrals, or a paid tier.
Example: A former DoD program analyst in Virginia started a weekly newsletter breaking down defense acquisition news. Hit 8,000 subscribers in 14 months. Now makes $4,200/month from two sponsors and a $12/month premium tier.
🛡️ Get Into FedRAMP / CMMC Security Consulting
Every company that wants to sell software to the US government needs FedRAMP authorization or CMMC compliance. The OCX program’s cybersecurity failures highlight exactly why this matters. Companies will pay $150-300/hour for consultants who can guide them through the process. And there aren’t enough qualified people.
Example: A cybersecurity analyst in São Paulo got his CMMC Registered Practitioner certification and now does remote assessments for US defense subcontractors. He charges $175/hour and books 15-20 hours per week through a GovCon matchmaking platform.
⚙️ Offer 'Software Rescue' Services for Stalled Projects
OCX isn’t unique. Tons of software projects — government and private — get stuck in development hell. Companies hire “rescue teams” to come in, audit the codebase, triage the bugs, and get the thing shipping. This is a real niche. You need strong debugging skills and the ability to read someone else’s terrible code without crying.
Example: A freelance dev team of two in Kraków specializes in rescuing failed Laravel and .NET projects. They charge €8,000 per rescue engagement (2-4 weeks), found clients through clutch.co, and did 14 rescues last year.
🛠️ Follow-Up Actions
| Step | Action |
|---|---|
| 1 | Read the GAO’s OCX report (free, public) — search “GAO GPS OCX” to see real audit methodology |
| 2 | Browse sam.gov for active government software contracts — study what agencies are buying |
| 3 | Check out GovWin IQ or GovTribe for contract intelligence and subcontracting opportunities |
| 4 | Look into CMMC or FedRAMP certifications if security consulting interests you |
| 5 | Join r/GovContracting and r/FedRAMP on Reddit for real talk from people in the space |
Quick Hits
| Want to… | Do this |
|---|---|
 Understand GovTech failures |
Read GAO reports on sam.gov — they’re free and shockingly readable |
 Break into gov consulting |
Get PMP or CMMI certified, then list on GovTribe as a subcontractor |
 Do security compliance work |
Start with CMMC Registered Practitioner — lowest barrier, highest demand |
 Build an audience in this space |
Cover contract awards and audit reports in plain English — the bar is on the floor |
 Rescue failed software projects |
Build a portfolio on platforms like clutch.co or toptal, specialize in specific stacks |
Eight billion dollars. Sixteen years. And the satellites are just up there, waiting for someone competent to answer the phone.
!