← Back to the 300 Software Failures Timeline
Case Study #103 — 300 Software Failure Case Studies

Hitomi (ASTRO-H) X-ray satellite breakup

JAXA's flagship X-ray astronomy satellite broke apart in orbit just over a month after launch, a total loss of the roughly $273 million mission.

2016-03-26
When it happened
Aerospace / Space
Sector
#103 of 300
Ranked by documented impact
01 — What Happened

The damage was public. The root cause was preventable.

JAXA's flagship X-ray astronomy satellite broke apart in orbit just over a month after launch, a total loss of the roughly $273 million mission.

Aerospace
Sector affected
2016-03-26
Date of the event
#103
Rank in the 300 Software Failure Case Studies
2
Distinct root-cause clauses identified below
02 — The Root Cause

What the software actually got wrong

A software error in the satellite's attitude control system miscalculated its rotation rate, and a subsequent software safeguard applied thruster firings based on that bad data, spinning the satellite up until structural components broke off.

01Root Cause

A software error in the satellite's attitude control system...

What Happened

A software error in the satellite's attitude control system miscalculated its rotation rate

How Requs AI Catches This

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.

02Root Cause

A subsequent software safeguard applied thruster firings based on...

What Happened

a subsequent software safeguard applied thruster firings based on that bad data, spinning the satellite up until structural components broke off

How Requs AI Catches This

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.

03 — How This Gets Caught Before It Happens

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.

Requs AI Edge Case

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.

Requs AI Software FMEA

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.