On the morning of July 22, 1962, an Atlas-Agena rocket lifted off from Cape Canaveral carrying a spacecraft built to perform humanity’s first close flyby of another planet. Two hundred and ninety-three seconds later, a range safety officer pressed the destruct button and Mariner 1 was scattered across the Atlantic in a cloud of liquid oxygen and kerosene fire — brought down, in the end, by a single character missing from a line of guidance code, an omission Arthur C. Clarke would later call the most expensive hyphen in history.
The probe was supposed to fly past Venus. Instead, it flew for less than five minutes.
The spacecraft and its launch had cost about $18.5 million in 1962 dollars — the loss landed hard on a young planetary program still scrambling to keep pace with the Soviet Union.
What Mariner 1 was built to do
Mariner 1 was NASA’s first planetary mission. The Soviets had already shocked the United States with Sputnik in 1957 and Yuri Gagarin in 1961, and the race to reach another world was on. Venus, the closest planet to Earth and at the time still a near-total mystery beneath its clouds, was the obvious first target. Mariner 1 was supposed to sweep close to the Venusian cloud tops, scanning microwave and infrared radiation to settle a long-running argument about whether the surface was a swamp, a desert, or something stranger.
The strangeness, of course, turned out to be greater than anyone guessed. The surface is hot enough to melt lead, pressurized like the deep ocean, and wrapped in sulfuric acid clouds that move faster than the planet itself rotates. None of that was known in 1962. Mariner 1 was going to start the answering.
The 293 seconds

The Atlas-Agena cleared the pad cleanly on the morning of July 22. For the first minute the climb looked nominal. Then the rocket’s airborne beacon — the antenna that fed velocity data back to the ground-based guidance computer — began losing lock. According to a reconstruction by Silicon Republic, the hardware fault meant the rocket’s guidance had to fall back on its software equations to stay on course.
That backup was where the typo lived.
The guidance equations had been transcribed by hand from a mathematician’s notebook onto punch cards. One symbol — an overbar, the small horizontal line drawn above a variable to indicate a smoothed, time-averaged value — had been left off. Without the bar, the software stopped averaging the rocket’s velocity over time and instead reacted to every tiny fluctuation as if it were a real course deviation. A later academic analysis of the failure traced exactly this chain: faithfully transcribed code, faithfully executing a specification that was already wrong.
The rocket began correcting for noise. The corrections were wild. The vehicle pitched down and yawed northeast, heading toward the North Atlantic shipping lanes.
At T+293 seconds, six seconds before the booster was due to separate, the button was pressed. The vehicle broke apart over the Atlantic.
The missing bar, the missing hyphen, and the line that stuck
What exactly was missing has been argued about for sixty years. The contemporary press, including an account later republished by WIRED, reported that a hyphen was missing. NASA’s own internal review referred to a missing bar. Later technical histories described it as an overbar transcription error. Some sources, as Mental Floss summarized in its rundown of major computer bugs, even pointed to a misplaced decimal point.
The truth is closer to the overbar story — a symbol that told the computer to treat a stream of velocity readings as a smoothed average rather than a series of jagged instantaneous values. Calling it a “hyphen” was simply easier to explain to a public that did not know what an overbar was.
Either way, the result was the same. A symbol the width of a pencil line had cost a planetary mission.
Clarke described Mariner 1 as having been wrecked by the most expensive hyphen in history, a phrase that has been widely repeated in nearly every retrospective since, including Business Insider’s list of small typos that caused big disasters and Mental Floss’s ranking of the most costly typographical errors on record.
The line stuck because it compressed something true about Mariner 1 specifically. A single missing character on a punch card had destroyed a machine worth tens of millions of dollars and erased years of work by hundreds of people. The error and the consequence were separated by an enormous multiplier called the rocket.

How the code reached the rocket
To understand how a single overbar could be left off Mariner 1’s guidance code, you have to picture how software actually got onto a rocket in the early 1960s. A mathematician at the Jet Propulsion Laboratory would write the guidance equations longhand on engineering paper. A second person would translate those equations into FORTRAN or assembly. A third person would punch the translated instructions, character by character, into stiff paper cards using an IBM keypunch machine. The cards were then fed through a reader, compiled, and the resulting binary loaded onto the ground-based computer that talked to the rocket in flight.
An overbar, written above a letter for a radius term, was particularly vulnerable at every step. It was small. It sat outside the main line of text. A transcriber working quickly, or a keypunch operator unfamiliar with the convention, could easily skip it — and once skipped, there was no way for the compiler to know the symbol had ever been intended.
The bug was latent. It only mattered when the primary antenna failed and the backup software was forced to drive the rocket alone. Under nominal conditions, the missing bar was invisible.
The twin that worked, and the failures that followed
NASA had built two probes. Mariner 2 was waiting on the pad.
The engineers corrected the guidance code, ran it through another round of verification, and launched the twin on August 27, 1962 — just thirty-six days after the first vehicle’s destruction. On December 14, Mariner 2 passed Venus and became the first spacecraft ever to successfully encounter another planet. Its microwave radiometer confirmed that the surface temperature was extreme, ending the swamp theory and establishing Venus as the furnace that later missions would keep confirming in increasingly grim detail.
The success was complete enough that Mariner 1’s failure became a footnote almost immediately. The agency had won the planetary first. The hyphen was forgotten by everyone except the people who had lived through those 293 seconds.
The decade that followed treated software with steadily more suspicion. At MIT’s Instrumentation Laboratory, Margaret Hamilton led the team that wrote the on-board flight software for the Apollo command and lunar modules, and she is credited with coining the term “software engineering” to argue that code deserved the same discipline and respect as the hardware it controlled. That shift was gradual and driven by many programs, not a single accident. But Mariner 1 sits early in the same lineage — a demonstration that a machine could do exactly what it was told and still be lost to something a person forgot to write down.
The pattern of catastrophic small errors did not stop. In 1996, the European Space Agency’s Ariane 5 disintegrated about forty seconds after launch when a 64-bit floating-point value was converted into a 16-bit signed integer that could not hold it. In 1999, NASA’s Mars Climate Orbiter, a mission costing roughly $125 million, burned up in the Martian atmosphere because one engineering team had used pound-force seconds and another had used newton-seconds. Each was, in its own way, the same story as Mariner 1. A unit, a symbol, a hyphen.
The hyphen that stayed
Sixty-four years on, the wreckage of Mariner 1 lies somewhere on the floor of the Atlantic, in pieces too small and too corroded to ever recover. The punch card with the missing bar was almost certainly destroyed in the routine clearing of JPL files long ago. The mathematician’s notebook, the keypunch operator’s hands, the computer that read the bad instruction and dutifully sent it to the rocket — all of it is gone.
What survives is the line. Six words from a science fiction writer about a probe that flew for 293 seconds and then did not fly anymore. Clarke’s phrase has outlasted every piece of hardware involved in the failure it describes, and it has outlasted most of the people who built that hardware. The hyphen, in the end, was the only part of Mariner 1 that ever reached anywhere.