{"id":13056,"date":"2025-02-26T15:19:22","date_gmt":"2025-02-26T15:19:22","guid":{"rendered":"https:\/\/pstqb.pt\/?p=13056"},"modified":"2025-02-26T15:36:55","modified_gmt":"2025-02-26T15:36:55","slug":"como-um-bug-custou-185-milhoes-de-dolares-a-nasa","status":"publish","type":"post","link":"https:\/\/pstqb.pt\/en\/como-um-bug-custou-185-milhoes-de-dolares-a-nasa\/","title":{"rendered":"How a Bug Cost NASA 18.5 Million Dollars"},"content":{"rendered":"
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
<\/i><\/span><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

In the high-risk world of space exploration, precision is everything. A single misplaced decimal place, an omitted character or a small syntax error can mean the difference between success and catastrophic failure. One of the most infamous coding errors in history - the absence of a hyphen - led to the destruction of NASA's Mariner 1 spacecraft just moments after launch, costing the agency a staggering 18.5 million dollars.\u00a0<\/p>

On July 22, 1962, NASA's Mariner 1 was ready to embark on a groundbreaking mission to the planet Venus. The spacecraft was designed to transmit valuable scientific data back to Earth, advancing humanity's understanding of the solar system, yet just 293 seconds after liftoff, the mission ended in disaster: The rocket veered off course, prompting ground control to initiate the self-destruct sequence. The culprit? A single missing hyphen in the code of the software<\/em> orientation. The missing hyphen led to incorrect speed calculations, causing erratic flight behavior that eventually made the spacecraft uncontrollable.\u00a0<\/p>

In short, the Mariner 1 spacecraft relied on a combination of ground-based and on-board guidance systems, and its software<\/em> was responsible for interpreting the signals from the tracking stations and adjusting the rocket's trajectory accordingly. The missing hyphen in the code disrupted the mathematical instructions that dictated the velocity corrections, resulting in erroneous calculations. The error translated into unintentional trajectory deviations that became increasingly serious, leaving NASA with no option but to abort the mission.<\/p>

This incident remains one of the most costly typographical errors in history, highlighting the critical importance of meticulous attention to detail in programming, particularly in mission-critical applications. In the world of software<\/em>Even the slightest oversight can have far-reaching consequences. This is especially true in aerospace engineering, where precision is paramount. For today's developers and engineers, the failure of Mariner 1 serves as a cautionary tale; it underlines the need for rigorous code reviews, extensive testing and redundancy in mission-critical systems. Currently, the verification processes for software<\/em>Automated error detection and simulation-based testing have evolved to reduce these risks, but the lesson remains relevant: every character in the code is important.<\/p>

Although the Mariner 1 incident is among the most famous coding errors, history is littered with other examples of small mistakes that led to catastrophic results:<\/p>