NASA Viking 1 lander loss of contact
NASA's Viking 1 Mars lander, which had already vastly outlived its planned 90-day mission, was permanently lost after ground controllers tried to fix an unrelated battery issue.
The damage was public. The root cause was preventable.
NASA's Viking 1 Mars lander, which had already vastly outlived its planned 90-day mission, was permanently lost after ground controllers tried to fix an unrelated battery issue.
What the software actually got wrong
While uplinking a software command intended to work around a battery-charging problem, engineers accidentally overwrote the memory location storing the antenna-pointing software needed to aim the lander's high-gain antenna at Earth, and without it NASA was never able to re-establish a strong enough signal to fix the problem or recover the spacecraft.
While uplinking a software command intended to work around...
While uplinking a software command intended to work around a battery-charging problem, engineers accidentally overwrote the memory location storing the antenna-pointing software needed to aim the lander's high-gain antenna at Earth
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.
Without it NASA was never able to re-establish a...
without it NASA was never able to re-establish a strong enough signal to fix the problem or recover the spacecraft
Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.
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.