Ariane 5 Flight 501 software failure: cause and lessons
Ariane 5 Flight 501 failed on June 4, 1996 after an unhandled numeric conversion in its inertial reference software disabled both reference systems. Diagnostic information was then interpreted as flight data, leading to extreme steering commands, loss of control, and the destruction of the launcher and its four Cluster satellites.
Why did Ariane 5 Flight 501 fail?
The immediate software failure: A value in an alignment function exceeded the range of a 16-bit signed integer when converted from a 64-bit floating-point number. The conversion was not protected against that exception. The backup and active inertial reference systems, running the same software, both failed.
How the failure reached the flight controls: Diagnostic information from the failed reference system was interpreted by the onboard computer as flight data. The resulting nozzle commands drove the launcher off course; it broke up roughly 40 seconds after flight-sequence initiation.
Why it was not caught: The inquiry identified specification and design errors in the inertial reference software and inadequate analysis and testing of that system and the complete flight-control system. Software carried over from Ariane 4 contained assumptions that were not valid for Ariane 5’s flight conditions.
Reliability lesson: Reused software needs its operating assumptions revalidated, numeric limits need explicit handling, and identical backup software can share the same failure mode. These lessons are Mission Ready Software’s retrospective analysis; they are not a guarantee that a particular modern tool would have prevented the loss.
Compare the numerical-accuracy lesson with the Patriot missile failure at Dhahran, where rounding error accumulated during extended operation. The Mars Climate Orbiter loss offers a separate lesson in checking the units and assumptions at software interfaces. Neither incident had the same immediate cause as Ariane 5.
For a structured way to examine how a software failure can lead to a system hazard, explore software FMEA. Our software FMEA training develops the analysis skills needed to examine failure modes and their effects in your own systems.
Sources: ESA’s presentation of the Inquiry Board report and the Inquiry Board report text, hosted by Carnegie Mellon University.
What the software actually got wrong
Reused Ariane 4 guidance software suffered an unhandled 64-bit float to 16-bit integer conversion overflow, crashing both inertial reference units and causing the rocket to veer off course.
Reused Ariane 4 guidance software suffered an unhandled 64-bit...
Reused Ariane 4 guidance software suffered an unhandled 64-bit float to 16-bit integer conversion overflow, crashing both inertial reference units and causing the rocket to veer off course.
Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.
Beyond code coverage and "shall" testing
Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.
Surfaces this before code exists
Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.
Connects the failure mode to the hazard
Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.
Find the overlooked root causes before they ship.
Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.
See real failures this would have caught
Failures like this one can be found before release. See how Requs AI finds them early:
- Software FMEA tool — find failure modes and root causes before code ships
- Software reliability prediction — predict defects before code is written (IEEE 1633)
- Software risk assessment checklist — spot the risks behind failures like this