Mariner 1 was meant to be the first United States spacecraft to fly past another planet, headed for Venus. It launched on July 22, 1962, atop an Atlas-Agena B rocket from Cape Canaveral. Shortly into the flight the vehicle began to fishtail and veer off its planned trajectory, and the Range Safety Officer sent the destruct command about 293 seconds after liftoff, sending Mariner 1 into the Atlantic. A backup, Mariner 2, launched about five weeks later and went on to become the first spacecraft to successfully fly past another planet.
The Mariner 1 failure is one of the most retold software anecdotes in computing history, usually summarized as “the missing hyphen” and quoted as the most expensive punctuation mark ever. The NASA History account corrects that popular shorthand. It states that the loss was caused by “the omission of an overbar for the symbol R for radius (R instead of R-bar) in an equation,” and explicitly notes that “the omission was not a hyphen, as sometimes erroneously reported.” The overbar denoted a smoothed or averaged value; without it, the guidance program used a raw, unsmoothed quantity.
The nuance that matters most is that the coding error alone would not have doomed the flight. The missing overbar had been present in the equation on previous Atlas launches without causing a loss, because the affected branch of the computation only mattered when the airborne guidance beacon failed. On Mariner 1 that branch was actually exercised: a hardware problem caused the rocket’s airborne beacon to lose lock with the ground guidance system, so the ground computer fell back on the flawed smoothing equation. With the overbar missing, the program responded to ordinary tracking noise as if it were real steering error and issued erratic course corrections, sending the vehicle off course.
So the honest version of the story is a two-fault failure: a hardware fault (loss of the guidance beacon lock) and a software-specification fault (the missing overbar) had to occur together. The software defect was the latent flaw that removed the system’s ability to ride out the hardware glitch safely. This is a recurring pattern in the history of computing disasters, where a single named “bug” gets all the blame while the real story is the unlucky combination of an underlying hardware or operational problem with a software path that was never properly hardened against it.
Mariner 1 endures as a teaching example partly because of the colorful “expensive hyphen” legend and partly because the corrected account is more instructive than the myth. It shows how transcription and specification errors in guidance software can hide for multiple flights, surfacing only when an independent failure forces the flawed code path to run, and it foreshadows later spaceflight software losses such as Ariane 5 Flight 501 where reused or under-tested code met conditions its authors never anticipated.