New Horizons pre-Pluto safe-mode glitch
NASA lost contact with the New Horizons spacecraft for about 90 minutes just 10 days before its historic Pluto flyby, threatening the mission's single, irreplaceable close encounter.
The damage was public. The root cause was preventable.
NASA lost contact with the New Horizons spacecraft for about 90 minutes just 10 days before its historic Pluto flyby, threatening the mission's single, irreplaceable close encounter.
What the software actually got wrong
The main computer became overloaded and rebooted into safe mode after simultaneously receiving a large command sequence to compress previously stored data while also preparing files for the approaching flyby, a timing conflict in the sequencing software that had not been anticipated in testing.
The main computer became overloaded and rebooted into safe...
The main computer became overloaded and rebooted into safe mode after simultaneously receiving a large command sequence to compress previously stored data while also preparing files for the approaching flyby, a timing conflict in the sequencing software that had not been anticipated in testing.
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.