NASA Mars rover Spirit flash-memory software fault
Just three weeks after landing, NASA's Spirit rover stopped sending usable data and began rebooting continuously, nearly ending the mission before its science campaign began.
The damage was public. The root cause was preventable.
Just three weeks after landing, NASA's Spirit rover stopped sending usable data and began rebooting continuously, nearly ending the mission before its science campaign began.
What the software actually got wrong
The rover's flash file system had accumulated more files than its software was designed to properly manage, and when it ran low on memory the flight software entered a repeated reset loop; JPL engineers diagnosed the fault remotely and reformatted the memory to recover the rover.
The rover's flash file system had accumulated more files...
The rover's flash file system had accumulated more files than its software was designed to properly manage
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.
When it ran low on memory the flight software...
when it ran low on memory the flight software entered a repeated reset loop
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.
JPL engineers diagnosed the fault remotely and reformatted the...
JPL engineers diagnosed the fault remotely and reformatted the memory to recover the rover
Requs AI Edge Case and Software FMEA together treat this as a known, catalogued defect pattern — not a novel surprise — so it gets tested for deliberately rather than discovered after deployment.
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.