Airbus A380 wiring harness design-software crisis
Production of the A380 superjumbo was delayed by roughly two years, costing Airbus's parent company an estimated EUR4.8 billion, as dozens of aircraft sat unable to be wired correctly.
The damage was public. The root cause was preventable.
Production of the A380 superjumbo was delayed by roughly two years, costing Airbus's parent company an estimated EUR4.8 billion, as dozens of aircraft sat unable to be wired correctly.
What the software actually got wrong
Airbus's German and French design offices used incompatible versions of the CATIA electrical design software (an older version in Hamburg versus a newer one in Toulouse), so wiring harnesses designed on one system did not fit the airframes built to specifications from the other, forcing many harnesses to be re-engineered from scratch.
Airbus's German and French design offices used incompatible versions...
Airbus's German and French design offices used incompatible versions of the CATIA electrical design software (an older version in Hamburg versus a newer one in Toulouse), so wiring harnesses designed on one system did not fit the airframes built to specifications from the other, forcing many harnesses to be re-engineered from scratch.
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.