F-22 Raptor navigation failure crossing International Date Line
A flight of F-22s deploying to Guam lost navigation, communication, and some fuel subsystems simultaneously; jets had to follow their tanker aircraft back to Hawaii.
The damage was public. The root cause was preventable.
A flight of F-22s deploying to Guam lost navigation, communication, and some fuel subsystems simultaneously; jets had to follow their tanker aircraft back to Hawaii.
What the software actually got wrong
The onboard navigation software had never been tested against crossing the 180th meridian (International Date Line) and faulted when it did.
The onboard navigation software had never been tested against...
The onboard navigation software had never been tested against crossing the 180th meridian (International Date Line) and faulted when it did.
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.