One of the most expensive software failures ever recorded took place during the Ariane 5 Flight 501, when a European rocket was lost less than a minute after launch.
About 37 seconds into its first flight, the Ariane 5 veered off course and was automatically destroyed. The root cause was a small but critical software flaw in its navigation system. A number representing horizontal velocity was converted from a 64-bit format into a 16-bit integer. The value exceeded what the smaller format could handle, triggering an overflow error that shut down the system.
To make matters worse, the backup system used the same software and failed in exactly the same way. With both guidance systems offline, the rocket lost control, leading to its destruction.
The explosion resulted in a loss of roughly $370 million USD, including the rocket and its onboard payload. Beyond the financial hit, the failure forced engineers to rethink how software is tested and reused—especially in high-risk environments.
The bug traced back to code reused from the earlier Ariane 4 rocket, where the same variable never reached dangerous levels. Under Ariane 5’s different flight conditions, however, that assumption proved fatal.
Today, the incident stands as a powerful reminder that even minor coding oversights can have massive real-world consequences when systems are pushed beyond their original design limits.
