Skip to main content
GCSE & A-Level Computer Science

Bug Hunting: Famous Coding Errors That Cost Millions

Sudershan SoniBy Sudershan Soni 28 July 2026 7 min read

A single missing punctuation mark destroyed a rocket worth millions of dollars, seconds after launch. A rounding error nearly crashed a stock exchange's opening. The most expensive bugs in software history are almost never dramatic, complicated mistakes — they're tiny, easily-overlooked ones that happened to sit in exactly the wrong place.

Mariner 1: the punctuation mark that cost a rocket

In 1962, NASA's Mariner 1 probe was destroyed by ground control less than five minutes after launch, after its guidance software began issuing wildly incorrect steering commands. The root cause traced back to a single missing character in a hand-transcribed guidance equation — a smoothing formula that was supposed to average out small sensor variations instead treated every tiny fluctuation as a real, urgent course correction, sending the rocket off its intended path.

DO 5 I = 1.10intended: DO 5 I = 1,10 (a loop) — one typo (. instead of ,)DO5I = 1.10read as: create a variable and assign it 1.10 — no loop at all

One missing character changed a smoothing formula into something that read every small sensor fluctuation as a real steering command — a tiny difference with a catastrophic result.

Why small bugs cause the biggest disasters

A large, obvious bug tends to get caught quickly — the program crashes immediately, or produces an obviously wrong answer that someone notices in testing. The bugs that cause real damage are almost always the ones subtle enough to survive testing and reach production: an off-by-one error in a loop, a rounding assumption that only breaks at an unusual value, a condition that's correct 99.9% of the time and catastrophically wrong the rest. The smaller and quieter the mistake, the more places it can hide.

What these failures actually changed

Mariner 1's failure became a standard case study in software engineering education, and it directly influenced how mission-critical code gets reviewed — the idea that a single transcription error could ever reach a live guidance system without a second check is precisely what modern code review, automated testing and formal verification exist to prevent. Every famous historical bug is, in a real sense, the reason a specific engineering safeguard exists today. If debugging, testing or software engineering practice needs explaining as real professional skill rather than exam-only material, that's exactly what our GCSE computer science tutoring is for — see the full learning pathway here.

Frequently asked questions

Was the Mariner 1 hyphen bug really just one character?

The most repeated version of the story is a missing hyphen (or overbar, in the original FORTRAN notation) in a guidance equation, which caused the rocket's software to misinterpret a formula and issue incorrect steering commands — the rocket was deliberately destroyed less than 5 minutes after launch to prevent it crashing into a populated area. Some historians debate the exact technical detail, but the core lesson — a tiny, easily-missed error causing a catastrophic failure — is well documented.

Why do 'off-by-one' errors happen so often?

Because counting in code often starts from 0, not 1 — the first item in a list is usually at position 0, not position 1 — and it's extremely easy to write a loop or condition that's out by exactly one position in either direction. It's one of the most common bug categories in all of programming, precisely because the mistake is so small and easy to make without noticing.

What actually stops bugs like these reaching production today?

Automated testing (running code against known expected results before it ships), code review (a second person checking the logic before it's merged), and stricter typed languages that catch some classes of error before the program even runs. None of these guarantee zero bugs, but they catch the overwhelming majority of the kind of small, easily-missed mistakes that caused the most famous historical failures.

Was this article helpful?

Tell us what you think — a correction, a question it left unanswered, or a topic you'd like covered next.

Sudershan Soni

About the author

Sudershan Soni

Founder & Lead Tutor at Mostak Services — an MSc-qualified Mathematics, Science, Computer Science & STEM tutor with 20+ years of professional experience, teaching students from 11+ and GCSE to A-Level and beyond, online worldwide.

Read full profile

Want computer science that builds real understanding?

One-to-one lessons build real debugging skill, not just syntax memorisation. Book a free discussion and we'll show you how.