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

2011 Southwest US blackout (San Diego)

A cascading power failure blacked out San Diego and parts of Arizona and Mexico for hours, affecting roughly 5 million people.

2011-09-08
When it happened
Energy / Utilities
Sector
#280 of 300
Ranked by documented impact
01 — What Happened

The damage was public. The root cause was preventable.

A cascading power failure blacked out San Diego and parts of Arizona and Mexico for hours, affecting roughly 5 million people.

Energy
Sector affected
2011-09-08
Date of the event
#280
Rank in the 300 Software Failure Case Studies
1
Distinct root-cause clause identified below
02 — The Root Cause

What the software actually got wrong

A joint FERC/NERC report found grid operators' real-time monitoring tools did not give them a clear enough picture of how close the system was to a cascading failure after a single piece of equipment was taken out of service for maintenance, so the contingency wasn't recognized and addressed before the outage cascaded across the interconnected grid.

01Root Cause

A joint FERC/NERC report found grid operators' real-time monitoring...

What Happened

A joint FERC/NERC report found grid operators' real-time monitoring tools did not give them a clear enough picture of how close the system was to a cascading failure after a single piece of equipment was taken out of service for maintenance, so the contingency wasn't recognized and addressed before the outage cascaded across the interconnected grid.

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.

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.