How can a decade of brilliant engineering and 370 million dollars of scientific equipment be completely vaporized in exactly 37 seconds due to a single line of faulty computer code? The explosive maiden voyage of the European Space Agency's Ariane 5 rocket in 1996 remains the most infamous and costly software bug in the history of aerospace engineering. The rocket's catastrophic failure was entirely self-inflicted. Engineers had lazily reused the inertial reference software from the older, slower Ariane 4 rocket without adequately testing it for the new flight profile. As the vastly more powerful Ariane 5 accelerated, the horizontal velocity value exceeded the maximum limit of a 16-bit integer. The software attempted to cram a 64-bit number into a 16-bit space, triggering a massive "e;integer overflow."e; The navigation computer instantly crashed, violently flipped the rocket's nozzles to their extreme limits, and triggered the automatic self-destruct mechanism. This rigorous computer science autopsy explores the brutal unforgiving nature of code. It documents the cascading failure of the redundancy systems, the absolute necessity of rigorous stress-testing, and the dangerous illusion that "e;working"e; legacy code is always safe to reuse. Respect the variables. The Ariane 5 disaster is the ultimate engineering lesson: in the realm of high-velocity physics, a tiny mathematical rounding error is just as lethal as a bomb.
