Case file
- What happened: On 4 November 2010, Qantas flight QF32, an A380-800 powered by four Rolls-Royce Trent 900 engines, suffered an uncontained failure of the No. 2 engine shortly after departing Singapore for Sydney. The intermediate-pressure (IP) turbine disc burst, ejecting fragments through the engine casing and into the wing.
- Scale: 469 passengers and crew on board. The crew faced over 100 ECAM messages affecting fuel, hydraulics, landing gear, brakes, and flight controls. All returned safely to Singapore Changi. Qantas grounded its entire A380 fleet; Singapore Airlines and Lufthansa conducted urgent Trent 900 inspections.
- Root cause: An oil-feed stub pipe in the IP turbine area was manufactured with wall thickness thinner than the drawing specified. The pipe fatigued, cracked, and leaked oil into a hot zone. The fire weakened the IP turbine disc retaining feature until the disc broke free.
- The bill: Rolls-Royce took a charge reportedly in the tens of millions of pounds for inspection, modification, and compensation. Qantas grounded its six A380s for roughly three weeks.
The situation
The Trent 900 was a flagship engine for a flagship airframe. The A380 entered service in 2007, and the Trent 900 had accumulated a solid service record across multiple operators. The oil-feed stub pipe was a small internal component routing lubricating oil to the IP turbine bearing. Like every rotating-part oil line in a gas turbine, it carried the assumption that if it failed, the engine would be shut down before the failure propagated beyond the casing. That assumption depended on two things: the pipe meeting its dimensional specification, and the turbine casing containing any resulting fire or disc liberation. The pipe did not hold. The casing was never designed to stop a full IP disc burst.
How it unfolded
About four minutes after take-off from Singapore, climbing through roughly 7,000 feet, the No. 2 engine's IP turbine disc burst. Fragments exited the casing at high velocity, punctured the left wing's front spar, severed wiring bundles, and damaged fuel and hydraulic lines. Fuel leaked from a punctured tank. Two engine control channels failed. The crew received over 100 ECAM messages — more than any simulator scenario had ever presented — and began working through each one by severity.
Five pilots on the flight deck brought the aircraft back to Changi roughly two hours later. Gravity-drop gear extension. Partially compromised brakes. No injuries. The aircraft was repaired over 18 months at a reported cost in the tens of millions. The safety outcome was a credit to crew resource management and the A380's system redundancy — not to the quality chain that built the pipe.
Root-cause anatomy
The ATSB investigation documented the mechanism precisely. The stub pipe was manufactured with a counter-bore that left one wall section significantly thinner than the drawing required. The thin wall concentrated fatigue stress. A crack initiated, propagated, and the pipe fractured. Oil escaped into the turbine chamber and ignited. The fire degraded the IP turbine disc's locking mechanism until the disc broke free under centrifugal load.
The organisational root is less comfortable. Not a design flaw — the geometry, tolerances, and inspection requirements were all defined. This was an escape. A non-conforming part left the supplier and entered service inside a certified engine. Somewhere in the manufacturing chain, a dimensional check on a small bore did not catch what it was designed to catch. Either the PFMEA under-rated the wall-thickness deviation, or the detection control on paper was not the detection control performed on the floor.
Where the quality system failed
Run this through a VDA 6.3 lens and the questions land hard on the production section — measurement system capability and reaction to non-conformances. The PFMEA should chain wall-thickness deviation to oil leak to disc liberation to uncontained failure. Severity 10. At that severity, detection has to be nearly certain. A manual wall-thickness check dependent on operator positioning and gauge access is not nearly certain.
The change-control angle matters too. If the counter-bore process was modified — tooling change, feed-rate adjustment, supplier transfer — the change should have triggered capability re-validation. If it drifted without a formal change, that is a process-control failure: no control chart, no Cpk monitoring, no drift detection. Either way, the gate was not present, not capable, or not followed.
A drawing tolerance is a contract. The moment your process treats it as a suggestion, the escape has already happened — you simply haven't met its consequences yet.
What would have caught it
Three controls, any one of which changes the outcome. Automated dimensional verification at the counter-bore station — a gauging system with documented MSA, not a manual check. If you cannot demonstrate gage R&R below 10% on the critical wall dimension, you have an opinion, not a measurement. Process capability monitoring with control charts and a documented reaction plan: a drift toward the lower tolerance limit should trigger containment long before the wall reaches minimum. Standard SPC in any IATF or AS9100 environment, but only when someone actually reads the charts. And a targeted VDA 6.3 P6 sub-question on critical-to-safety dimensions — not "are measurements performed?" but "show me the gage study for this bore, the last 30 data points, and the reaction plan that fired when point 27 drifted." If the supplier cannot produce all three in under five minutes, the control lives in the manual, not on the floor.
My take
I have spent two decades chasing this category of escape — the small sub-tier component that was never supposed to matter until it anchored an 8D. Building a QA/QC department for a 900-person greenfield plant, running process audits at Airbus, the pattern repeats: a dimension on a non-glamorous internal component, a control plan that lists a check nobody can physically perform reliably, and a PFMEA severity downgraded because "the casing will contain it." The casing will not contain a turbine disc. It was never asked to.
What is instructive about QF32 is not that the defect existed. Defects exist in every process. The instructive part is that a single sub-tier dimensional escape propagated through the entire quality chain and reached flight hours on a passenger aircraft. Every gate between the machining centre and the wing had an opportunity to stop it. None did. When I run QRQC sessions or VDA 6.3 audits now, I use cases like this for one point: the dimension you are tempted to waive through today is the one that will be on the front page of the ATSB report tomorrow.
What this means on your floor
- Treat every critical-to-safety dimension as an escape point. Walk the process backward from part to raw stock: what is the last control that would catch a wall-thickness deviation? If you cannot name it and show data, you have no control.
- Challenge PFMEA severity ratings. "The next assembly will catch it" is an assumption, not a control. If the failure mode is uncontained liberation of rotating hardware, severity is 10 — and your detection rating earns its number with evidence.
- Validate that your inspection method measures what the drawing demands. A gauge that cannot access the critical bore radius is not a gauge. Run the MSA before you trust the data.
- Audit your sub-tier against the same questions you would fear being asked yourself. The stub pipe was not manufactured by the engine OEM — it came from deeper in the chain, and that is where the process audit has to reach.
The QF32 crew brought 469 people home because the A380 was built with enough redundancy and because the pilots were trained to a standard no quality system can replicate. They should never have been in that position. A fraction of a millimetre bypassed every theoretical safeguard in the quality chain — and the lesson is not that the system almost worked. "Almost" is not a standard we tolerate in aerospace manufacturing.