On July 22, 1962, an Atlas-Agena rocket lifted off from Cape Canaveral carrying Mariner 1, the first American spacecraft ever built to reach another planet. It flew for just under five minutes before the range safety officer at the Cape pressed a button, and the rocket — along with the small probe bolted to its nose, bound for Venus — was torn apart above the Atlantic. The cause, once investigators dug through the guidance code, came down to a single mark of mathematical notation that had never been typed in.
Arthur C. Clarke, writing about it later in his 1968 book The Promise of Space, called it the most expensive hyphen in history.

The rocket that flew for minutes
Mariner 1 was supposed to be the opening move of American planetary exploration. Its instruments were designed to sweep past Venus, sample the temperature and magnetic environment of a planet nobody had ever visited, and radio the numbers home. According to the NASA NSSDCA record for the mission, Mariner 1 was identical to the Mariner 2 backup already waiting on the pad, and the two spacecraft together were meant to guarantee that at least one American probe reached Venus in 1962. The United States wanted the first successful flyby on the board.
The planet Mariner 1 was aimed at was still, in 1962, essentially unknown. The clouds hid everything. Ground-based telescopes could not tell whether the surface was a swamp, a desert, or something stranger. Mariner 1’s small suite of instruments was going to start the answering.
The Atlas-Agena that lifted Mariner 1 off the pad relied on two guidance systems working in tandem. The airborne beacon on the rocket was known to drop out briefly during flight. That was expected. To cover for the gaps, engineers had written backup software that would smooth the signal — average out the jitter — until the beacon came back cleanly. The smoothing kept the rocket flying straight when the data was noisy.
Both systems had to work. On July 22, neither did.
The mark that wasn’t there
Roughly a minute into the climb, the airborne beacon started feeding the guidance computer noisy, unreliable numbers. The backup software should have taken over and quietly ridden out the interference. Instead, it read every twitch in the raw data as a real deviation from the flight path and started firing steering commands to correct for problems that did not exist. The rocket began to yaw.
When investigators reconstructed the failure, they found the flaw in the transcription of the guidance equations. In the original handwritten formula, one variable carried a small horizontal line drawn above it — an overbar. That mark told the computer to use a time-averaged, smoothed value of the variable rather than the raw instantaneous reading. It was the mathematical instruction that made the smoothing work.
The overbar had been left out of the typed code. One character.
Without it, the equation used the raw radar reading directly. Every burst of noise became, to the guidance computer, a real steering emergency. As the technical reconstruction of the failure describes it, the rocket began swerving violently in response to fluctuations that were never really there.
With the vehicle veering off its planned trajectory and threatening to come down in a populated area or in the North Atlantic shipping lanes, the range safety officer at Cape Canaveral sent the destruct command 293 seconds after liftoff — six seconds before Mariner 1 was scheduled to separate from the Agena upper stage, after which the vehicle could no longer have been destroyed. The Atlas-Agena exploded over the Atlantic. Mariner 1, still bolted to the top, went with it. The probe’s radio transponder continued transmitting for another 64 seconds as the wreckage fell.
The cost of the mission has been reported at roughly $18.5 million in 1962 dollars. Accounting for inflation puts the loss at hundreds of millions in today’s currency.

Hyphen or overbar? What Clarke actually got wrong
The line about the most expensive hyphen in history stuck because Clarke was Clarke, and because the sentence is nearly perfect. It is also, strictly speaking, wrong about the punctuation.
The missing character was not a hyphen — a short horizontal line placed between two letters. It was an overbar, a horizontal line drawn above a letter to indicate a smoothed average in the mathematical notation. The NASA mission record refers to a software error in the launch vehicle’s guidance software; the more detailed NSSDCA account specifies the omission of a superscript overbar. The two marks look almost identical when handwritten or roughly typed. As the story of Mariner 1 moved from NASA technical reports into newspapers and, eventually, into computer science textbooks, the more familiar word won. The overbar became a hyphen. Clarke’s phrase locked it in.
Some early accounts confused matters further by pointing at a misplaced decimal point. Even popular histories of costly software errors have carried competing versions of the story. The engineering substance survives all the retellings: one small piece of mathematical notation, missing from a line of code, was enough to destroy a mission to Venus.
The failure was not really about one character
The tidy version of the Mariner 1 story — a hyphen killed a spacecraft — is what makes it famous. The fuller version is more uncomfortable.
Two independent things had to go wrong. The airborne beacon hardware had to glitch, feeding bad data to the rocket. And the backup software, which existed precisely to catch that kind of glitch, had to be broken. If either system had worked, Mariner 1 would probably have reached Venus. The missing overbar was not the cause of the failure in isolation. It was the reason the backup could not save the vehicle when the primary system faltered.
This is the pattern that shows up again and again in modern spaceflight and aviation accidents. A single fault rarely destroys anything by itself. Redundancy is what makes complex systems survivable. When redundancy fails silently — when a backup is broken and nobody knows — the next hardware glitch becomes catastrophic.
Mariner 2, five weeks later
NASA did not stop. The agency had built Mariner 2 as a backup, and it was almost ready. On August 27, 1962 — thirty-six days after Mariner 1 exploded — Mariner 2 lifted off from the same launch complex on a corrected Atlas-Agena. On December 14, 1962, it flew within about 34,800 kilometres of Venus and became the first spacecraft in history to return close-range measurements from another planet. Its microwave radiometer confirmed that the surface was hot enough to melt lead, ending decades of speculation that Venus might be a temperate world.
Mariner 2 is the mission that opened planetary science. Mariner 1 is the one that is remembered. The Soviet Union eventually landed on the surface — Venera 7 survived 23 minutes on the Venusian ground in 1970 — but the first data from Venus at all came from Mariner 2, launched five weeks after its twin had been blown up over the Atlantic.
What one missing mark bought
Sixty-plus years on, the missing overbar is still cited in software engineering courses, in aerospace ethics seminars, and in code review policies at companies that have nothing to do with rockets. George Mueller, who ran NASA’s crewed spaceflight programme through the Apollo era, had been an executive at Space Technology Laboratories — the contractor responsible for writing the Mariner 1 guidance equations — before joining the agency. Throughout his years running Apollo, he kept a framed image of a hyphen on the wall behind his desk. The engineer who transcribed the equations was doing careful work under real deadlines. What Mariner 1 showed was that the smallest transcription error, in the wrong context, can cascade into the largest possible consequence.
The pattern shows up in other domains. A spreadsheet error in a 2010 Harvard economics paper by Carmen Reinhart and Kenneth Rogoff, discovered in 2013 by graduate student Thomas Herndon at the University of Massachusetts Amherst, undermined one of the most influential findings behind post-crisis austerity economics. The missing rows in a formula were, in policy terms, arguably even more consequential than the missing overbar in Mariner 1. Both share the same DNA: a small, unnoticed defect in a system that everybody assumed had been checked.
The numbers, in the end, are worth sitting with. About $18.5 million in 1962 dollars. Roughly the price, that year, of five or six B-52 bombers. Enough to fund a small research university for a year. Gone in less than five minutes because of a mark of ink about a millimetre long, drawn above a letter in a handwritten equation, that never made the jump from the notebook to the code.
Clarke’s phrase has outlived the mission it described. In a sense, the hyphen he named has outlived him too — Clarke died in 2008, and the line still gets quoted in every serious discussion of software failure. He was wrong about the punctuation. He was right about the price.
Somewhere in the Atlantic, off the coast of Florida, the pieces of Mariner 1 have been on the sea floor for sixty-three years. The instruments it carried never saw Venus. The mark that would have saved it was small enough that a careful reader could have missed it in a single pass through the code, and expensive enough that its absence is still being taught to engineers who were not born when it happened.