Go Back  PPRuNe Forums > Flight Deck Forums > Tech Log
Reload this Page >

QANTAS A380 Uncontained failure.

Wikiposts
Search

Notices
Tech Log The very best in practical technical discussion on the web

QANTAS A380 Uncontained failure.

Thread Tools
 
Search this Thread
 
Old 27th June 2013 | 15:23
  #741 (permalink)  
 
Joined: Mar 2002
Posts: 4,569
Likes: 1
From: Florida
One of the most thorough reports I have seen.

I wonder if the other manufacturers will learn from it. It highlighted problem areas that certainly are not unique to RR or Airbus.

Very few investigating agencies in the world would have the staff or level of expertise to produce such a report. I only hope that such agencies will assist their brothers when the need arises.
lomapaseo is offline  
Reply
Old 27th June 2013 | 22:52
  #742 (permalink)  
15 Anniversary
 
Joined: Jan 2008
Posts: 1,269
Likes: 79
From: Denver
Whoof! Took me three times longer to read the report than it did for the crew to handle all those ECAM items.

All that from a ~1mm machining error.
pattern_is_full is offline  
Reply
Old 28th June 2013 | 22:24
  #743 (permalink)  
20 Anniversary
 
Joined: Feb 2005
Posts: 4,581
Likes: 0
From: flyover country USA
All that from a ~1mm machining error.
That was only the first domino to fall.

In the basic architecture of the turbine section, the IPT system could not tolerate a shaft separation; It was virtually guaranteed to overspeed until the disc burst. That is a basic design issue; the manufacturing fault in the oil tube was merely the straw that broke the camel's back.
barit1 is offline  
Reply
Old 29th June 2013 | 00:33
  #744 (permalink)  
 
Joined: Mar 2002
Posts: 4,569
Likes: 1
From: Florida
That was only the first domino to fall.

In the basic architecture of the turbine section, the IPT system could not tolerate a shaft separation; It was virtually guaranteed to overspeed until the disc burst. That is a basic design issue; the manufacturing fault in the oil tube was merely the straw that broke the camel's back.
Of course they have addressed that little detail by changing the architect of the FADEC

I hope their FMEA analysis shows that good engines will not be shutdown erroneously with this doomsday code
lomapaseo is offline  
Reply
Old 21st October 2015 | 12:57
  #745 (permalink)  
 
Joined: Oct 2015
Posts: 1
Likes: 0
From: Sydney Australia
Qantas, Rolls Royce, Airbus who knew prior to 4 Nov 2010

Re Qantas, Rolls Royce, Airbus
Who knew prior to 4 Nov 2010
that there was a high risk in the occurance of a QF32 failure and where there was no informed consent in advance of departure?

Cybercy
cybercy is offline  
Reply
Old 21st October 2015 | 21:33
  #746 (permalink)  
20 Anniversary
 
Joined: Feb 2005
Posts: 4,581
Likes: 0
From: flyover country USA
In fact there were two warning signals earlier in 2010:

I give you QF74, 744, RB211 on 30 Aug 2010 (SFO local date): Qantas QF74 Uncontained Engine Failure - Video & Pics
IPT came disconnected from its shaft and drifted aft due to pneumatic forces in the engine. In this case, the IPT blades DID clash (i.e. first made contact) with LPT stator vanes, thus very rapidly destroying the driving torque to the loose IPT disc. Blade shrapnel penetrated the case and cowl, but the pieces were relatively small so the damage to the airframe was limited.
The above happened within a few weeks of a RR test bench failure of another Trent (787 version). Little detail is publicly available, but I believe I heard someone mention IPT.

Contrast this with the QF32, A380, 04 Nov 2010 SIN: T972 suffers IPT disc rupture after shaft disconnect. No rotor/stator airfoil clash, instead the disc became axially restrained against relatively hard/smooth/low friction internal surfaces. Disc continued to accelerate, driven by relatively intact airfoils, until burst speed was reached.
barit1 is offline  
Reply
Old 21st October 2015 | 23:31
  #747 (permalink)  
 
Joined: Mar 2002
Posts: 4,569
Likes: 1
From: Florida
In fact there were two warning signals earlier in 2010:
Warning signals consist of two parts...... cause and effect.

I doubt that anyone foresaw that the combinations that occurred in QF32 were likely.

Afterwards it's easy to look at all combinations ever having occurred in the total data base of the industry and then say, not surprised given etc. etc.
lomapaseo is offline  
Reply
Old 22nd October 2015 | 13:01
  #748 (permalink)  
20 Anniversary
 
Joined: Feb 2005
Posts: 4,581
Likes: 0
From: flyover country USA
I'm not saying they were in any way identical - only that IP shaft separations occurred and these should have sparked a "what if..." in some engineer's mind. QF32 should not have been a complete surprise.
barit1 is offline  
Reply

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off



Contact Us - Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service

Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.