PPRuNe Forums

PPRuNe Forums (https://www.pprune.org/)
-   Spectators Balcony (Spotters Corner) (https://www.pprune.org/spectators-balcony-spotters-corner-52/)
-   -   AF66 CDG-LAX diverts - uncontained engine failure over Atlantic (https://www.pprune.org/spectators-balcony-spotters-corner/600170-af66-cdg-lax-diverts-uncontained-engine-failure-over-atlantic.html)

Olympia 463 14th Oct 2017 16:17

NWA,
You are right to say that changes in load can have an effect on the progress of a fatigue crack. And you rightly note that the maximum axial load on the engine is at the front where the fan is since it is the part which is producing most of the thrust. I had a feeling these big fans which are really ducted propellors would have a big influence on the stresses at the front of the engine. That fan is literally dragging the whole aeroplane behind it. We had it easier on the low bypass engines like the Conway (0.6 bypass ratio). But what do I know - it is a long time since I designed the turbines and thrust reversers on the Conway and I left RR before the RB211 debacle. Stewart Miller the man who rescued RR from that catastrophe worked on the next board to me in those long gone days.

Olympia 463 14th Oct 2017 16:42

scfi
Unless you have one of these bolts in your hand you cannot know if it failed in tension or from fatigue. The fan assembly will have been tested rigorously on a development rig over many hundreds of cycles before the design was signed off for production. Now we know this engine is a 'bitser' (bits of one design combined with bits from another design) but I have no doubt that the combination was also tested through many cycles before being signed off. What I am getting at here is that this failure seems to me to be a unique event, and may never occur again. So all the AD's in the world are not going to make much difference. But as I have already said we have no information at all right now on this forum about which bits are actually available for inspection. Till we have....

Onceapilot 14th Oct 2017 17:02


Originally Posted by NWA SLF (Post 9924986)
Fatigue is induced by stress cycles. I haven't even touched on thermal cycles. How do you manage to design for this? Is it by overdesign or by realization there will be a failure at some point, predict the safe limit, and replace the critical component at that point?

NWA,
Components can be designed to operate at below fatigue inducing stress levels and, therefore, not fatigue fail. However, where circumstances require, components that have to operate inside their fatigue vulnerability are given a "safe life" that requires replacement before likely failure. Unfortunately, the combination of defects or unplanned loads can corrupt both strategies of component integrity. Consequently, the fact that the Fan hub has obviously failed on the remains of this engine does not confirm the type of failure or, even that the Fan hub is the cause of the incident.:8

wiedehopf 14th Oct 2017 17:17

@scifi and @olympia463 :

the attachment ring you see is actually the front of the low pressure compressor which hangs onto the fan as far as i understand it.
the part in the middle that is sheared off is the connection of the shaft connecting to the fan.

so the shaft connection there needs to carry the torque and pull from the low pressure compressor as well as the fan.

see various depictions / diagrams in the thread.

lomapaseo 14th Oct 2017 17:39

The thrust loads across a fan disk are insignificant to the loads caused by spinning.

Vibratory stresses are typically way below any measurable contribution to the tangential stresses in a fan disk.

The materials used in the fan disk and the design stresses are very resistant to crack growth in a few cycles.

Whatever happened is likely way outside simple assumptions.

When you design a bolt flange attachment in a high stress area you have to avoid concentrating stress fields around only a few bolt holes. You do this by adding extra holes (typically not used) to smooth out the stress field thus avoiding fatigue fatigue cracking from these holes.

Olympia 463 14th Oct 2017 18:59

lomapaseo,

You are confusing 'steady' stress such as that due to centrifugal forces on fan blades and disc from rotation, with 'varying' stress (ie stress which alternates) such as might arise in non rotating parts like casings etc. A steady stress which is below the safe stress for the material is quite different to an alternating stress which will cause failure if the cycles reach the fatigue limit for the material. I think we may need to ask people to state their engineering qualifications before entering this discussion. pm me and I'll tell you mine if you are interested.

number0009 14th Oct 2017 19:38

AD = 2 hour inspection when hub assembly failed at less than 25% of life limit cycles per previously linked article?
http://www.iba.aero/wp-content/uploa...e-May-2017.pdf


Similar fan disc failure some of us may remember.
Lessons Learned

The NTSB determined that the probable cause of this accident was the inadequate consideration of the human factors limitations in the inspection and quality control procedures used by the UAL engine overhaul facility. These limitations resulted in the failure to detect a fatigue crack originating from a previously undetected metallurgical defect located in a critical area of the stage 1 fan disk of the engine.

lomapaseo 14th Oct 2017 22:20

Olympia 463


lomapaseo,

You are confusing 'steady' stress such as that due to centrifugal forces on fan blades and disc from rotation, with 'varying' stress (ie stress which alternates) such as might arise in non rotating parts like casings etc. A steady stress which is below the safe stress for the material is quite different to an alternating stress which will cause failure if the cycles reach the fatigue limit for the material. I think we may need to ask people to state their engineering qualifications before entering this discussion
Nope, not confused.

There is such a thing as a "Goodman diagram" (combined steady stress and alternating stress) which applies equally to rotating parts as well as stationary parts. I simply put them in perspective as to how rare it was to combine them in a fan disk failure unless something was seriously amiss.

Vendee 15th Oct 2017 12:13

As a propulsion technician of over 40 years maintaining and overhauling gas turbine engines, I am used to boroscoping various parts of the engine. In my experience, some defects/cracks propagate quite slowly and can be monitored safely... i.e. combustion chamber liners and HPNGV vanes. Other defects, particularly on rotating components fail within a very short time (a few hours) of the defect becoming visible to the naked eye.

I would have thought that a crack on an LP fan disk would go from "visible" to "failure" very quickly. Perhaps someone better qualified in that field could comment on that? I'm guessing that the mandated inspection of the engines must be NDT rather than boroscope or visual to be of any value?

Chu Chu 15th Oct 2017 12:34

It looks like the AD is available here: http://rgl.faa.gov/Regulatory_and_Gu..._Emergency.pdf

The "AD Requirements" section says: "This AD requires a one-time visual inspection of the GP7200 series engine fan hub, with the compliance time based on the number of accumulated flight cycles, and removal of the fan hub if damage or defects are found that are outside of serviceable limits."

Onceapilot 15th Oct 2017 13:24

The "AD Requirements" section says: "This AD requires a one-time visual inspection of the GP7200 series engine fan hub, with the compliance time based on the number of accumulated flight cycles, and removal of the fan hub if damage or defects are found that are outside of serviceable limits."[/quote]

Yes. However, the visual inspection is to be performed iaw a proceedure that will detail the exact method used.
Also worth noting:
"Interim Action
We consider this AD interim action. An investigation to determine the cause of the failure is
on-going and we may consider additional rulemaking if final action is identified". And:
"FAA’s Determination
We are issuing this AD because we evaluated all the relevant information and determined the
unsafe condition described previously is likely to exist or develop in other products of the same type
design".

My interpretation of this is that, the FAA think there may be further failures.:uhoh:

nicolai 15th Oct 2017 14:08

Is the GP7200 engine (as fitted to the AF A380, if there are variations) typically transported with fan attached, or with the fan detached from the propulsion core and re-attached at the destination?

What size of aircraft is required to transport the fan and the fairing pieces, as well as the core? Are AF going to have to wait a while for an oversize cargo aircraft to be available to take the replacement (ballast :) ) engine to Canada?

(A quick look at some sales documents implies that the engine with fan will not fit through the doors of a 747-8F but will fit into an An-124.)

Longtimer 15th Oct 2017 17:06

Perhaps AirBus will use their Beluga, can not find anything published re the range of that aircraft though.
The Airbus A300-600ST (Super Transporter) or Beluga, is a version of the standard A300-600 wide-body airliner modified to carry aircraft parts and oversized cargo. It received the official name of Super Transporter early on; however, the name Beluga, a whale it resembles,[2][3] gained popularity and has since been officially adopted

atakacs 15th Oct 2017 18:04


Originally Posted by nicolai (Post 9925851)
(A quick look at some sales documents implies that the engine with fan will not fit through the doors of a 747-8F but will fit into an An-124.)

Does the a380 have any provision for 5 engine ferry flights (as the 747 does)?

DaveReidUK 15th Oct 2017 18:26

No. Nor do the majority of 747s, come to that.

bvcu 15th Oct 2017 19:02

Normal transportation without Fan case , same as GE 90-115

NWA SLF 15th Oct 2017 20:08

My fracture mechanics training came primarily from Dr. DW Hoeppner who had recently moved from Lockheed where he had been involved in fan disk failures on L1011s equipped with RB211 engines. He started off our first class by showing several airplane and helicopter components that had failed in crashes involving multiple loss of lives. Gets your attention and builds a focus on material selection. At that time, 1974, I remember it being a given that materials were going to fail. The focus was to determine life expectancy to that failure point, material selection matching the requirements, and inspections with the ability to find a crack prior to failure. In the ensuing 40+ years materials may have been developed that will have infinite life. Age and retirement have me out of the loop - note my name reference to an airline of the past. However this failure takes me back to Dr. Hoeppner's lectures and avoiding rush to judgement. One of our lectures was a few days after the DC-10 crash near Senlis, France. He came to class carrying a DC-10 cargo door latch, jumped on the desk and yelled at us how some engineer's mistaken material selection resulted in the death of 346 people. Illustration of rush to judgement. The latch was the failure mode but it was due to poor system design, not material failure.

My rush to judgement on this failure is there is a material inclusion not properly detected initiating a premature fatigue crack that precipitated the front falling off. Having learned from Dr. Hoeppner that this strategic part will have a fault tolerant material, the crack could grow quite large prior to failure. This would result in an AD requiring inspections at intervals where it is felt any crack will be discovered prior to becoming critical size that will result in the front falling off.

ConnieLover 15th Oct 2017 20:41

SLF coming out of lurk mode to share some info about the ranges of a Beluga and an An-124.

Purely FWIW:

NOT from the Airbus website, which left the range blank:
According to airliners.net:
Beluiga -- A300-600ST -- range with a 30 tonne (66,150lb) payload 4000km (2160nm)

According to Wikipedia:
An-124-100 range:
10 tons of cargo= 14,100 km (7,613 nmi)
20 tons of cargo= 13,250 km (7,154 nmi)

Аn-124-100М-150 range:
40 tons of cargo= 11,900 km (6,425 nmi)

55 An-124 have been made.

According to a PDF on the "mtu.de" website, a GP7000 series engine weighs 13,400 lbs without the housing.

Looks as though they would need to use an AN-124 to ferry the ballast engine to Goose Bay.

Has the luggage been retrieved and sent to the pax?

lomapaseo 15th Oct 2017 21:17


My rush to judgement on this failure is there is a material inclusion not properly detected initiating a premature fatigue crack that precipitated the front falling off. Having learned from Dr. Hoeppner that this strategic part will have a fault tolerant material, the crack could grow quite large prior to failure. This would result in an AD requiring inspections at intervals where it is felt any crack will be discovered prior to becoming critical size that will result in the front falling off.
I'm not saying that your judgement is wrong, but considering the fracture toughness of a titanium fan disk you need a "huge" detectable defect to have progressed to start-stop cyclic failure this early in life.

Other possibilities are still open and we as readers have no new facts to go on.

I'm waiting for a hint on the RPM in the last sec trace and better pics of the attachments.

Tetsuo 15th Oct 2017 22:14

How will AF rescue the aircraft from Wired

https://www.wired.com/story/how-air-...red-engine/amp

andrasz 16th Oct 2017 08:05


Looks as though they would need to use an AN-124 to ferry the ballast engine to Goose Bay.

The Beluga can easily do it with a tech stop in Shannon or Keflavik, but even a non-stop from Hamburg or Paris might be feasible with a less than full payload. It will depend on cost/availability, both types are capable. I would assume AB would rather use their own assets if possible.

EDLB 16th Oct 2017 08:13

So after 2 weeks the A380 is still there and nothing happened?

Onceapilot 16th Oct 2017 08:24


Originally Posted by Tetsuo (Post 9926196)
How will AF rescue the aircraft from Wired

https://www.wired.com/story/how-air-...red-engine/amp

Thanks for posting. :rolleyes: That article is good reading for quite a few of the posters on this forum.

DaveReidUK 16th Oct 2017 11:02


Originally Posted by Tetsuo (Post 9926196)
How will AF rescue the aircraft from Wired

https://www.wired.com/story/how-air-...red-engine/amp

Basically just a rehash of the Reuters article quoting an unnamed source from the BEA, which will have little or no say in how the aircraft is recovered.

To be taken with a pinch of salt.

rouelan 16th Oct 2017 11:07

If I may, there is something incorrect in the article: we did not wait 2 hours in Goose Bay before being rescued but ... 15 hours. It is probably the worst case for an OCC to deal with: how to reaccomodate 500 pax stranded in a remote military base ?

WHBM 16th Oct 2017 11:37

It's not a difficult issue, and some carriers are better at it than others, it seems. But in any event, it should be all worked out in advance and on the shelf in a manual in ops control ready to be taken down.

The fact it happened on a Saturday afternoon rather than a weekday is illustrative of modern trends, despite it being a 24x7 industry, where nobody low enough in the hierarchy to be working the 24x7 shifts, rather than office hours, is allowed to decide anything.

A realistic plan would have AF cancel the first (or first two) evening departures from Eastern US/Canada, and send the aircraft to Goose, which would allow the crews enough hours remaining to transfer the passengers and take them on to somewhere more hospitable, if not LAX then at least a major city with hotels and onward flights.

rouelan 16th Oct 2017 12:08

This is what AF did : cancel a YUL-CDG flight and use the a/c to fly YUL-Goose-ATL.
The problem again is the number of pax. Even the biggest a/c in AF fleet (apart from 380) the 77W in leisure configuration - by chance operating the late flight from YUL - was not big enough for 500 pax. So, an additional 737 had to be chartered.

WHBM 16th Oct 2017 13:07

My understanding was that the relief 777, which was diverted from the late evening YUL departure, had not even left Paris on its westbound schedule when the incident happened; it flew to Montreal first (quite likely overflying Goose on the way) before being redirected. It then seems to have spent the remainder of the night at Goose, only departing well into the following day.

rouelan 16th Oct 2017 15:02

I think you have a point ! No idea why AF decided not to cancel the westbound flight. The 777 spent something like 5 hours in Goose Bay. There were various issues. The 777 was initially due to fly to LAX but could not because of flight plan issues (???). Pax had to be bused between the 380 and the 777 with only 2 small shuttles. And there were IT problems to issue the load sheet.

Havingwings4ever 16th Oct 2017 16:51

Glad we have Canada to divert to after crossing bunch of water and ice in case of (presumed) issues.
Think about that sometimes flying over the continent Africa in the dark, i know there are some ok places to divert to but for the rest...
Years ago diverted to Yellowknife with an engine fire indication, great welcome and support, pax(272) were put up with the locals since hotels are not abundant and the local hamburger joint provided first nite dinner for all of us.
Pax had a great time and continued to Frisco the next day on a spare plane flown in.
Canadian warm welcome even made the news in Frisco.
Thank you

WHBM 16th Oct 2017 17:44

Just to pick up, the A380 landed at Goose at 1240 L (1540 Z). A 777 departing Paris at 1850 L (1650 Z) flew AF348 to Montreal, did a 4 hour turnround there, double the normal for the return to Paris, departing after midnight (over 12 hours after the A380 landed), flew empty to Goose, was on the ground there from 0250 to 0650 L, then flew to Atlanta, arriving there mid-morning. The crew who would have reported at Montreal at normal time were possibly out of hours, with all the delays, for then getting to LA. I presume the pax finally got to LAX on Delta flights about the same time as the following day's A380 from Paris. With no hotac.

cappt 16th Oct 2017 18:52

How Air France will rescue its A380 from Canada | Daily Mail Online

Looks like a three engine ferry is in the works.

BluSdUp 16th Oct 2017 19:16

I have followed this event as I did the Swizz B777 diversion.
Remind me why an engine has not been flown in, installed tested and departed.

In the B777 there was no N-1 ferry option, and no wing damage.

With regards to the slats that have to be changed and the wing inspected, that has to be 100% , regardless , me thinks?

Hanging on a new engine and not using it makes no sense to me.!
Might it be that MOT thinks the same?

By the way, a new engine on a ship would have been there by now.!

DaveReidUK 16th Oct 2017 20:07

Yet again, just another rehash of the Reuters article, plus the usual dash of DM hyperbole.


Looks like a three engine ferry is in the works.
That's far from certain, a four-engined ferry is at least as likely.

msbbarratt 16th Oct 2017 20:08


Originally Posted by BluSdUp (Post 9927123)
By the way, a new engine on a ship would have been there by now.!

Probably yes! But one suspects that there's a ton of work to ensure that everything else (flaps, wing, you name it) is fine and that no more damaged bits will fall off anywhere else. Only then will it be fit to fly with either 3 or 4 engines.

The shipping of the engine is, I suspect, the least of their problems to solve at the moment.

A bit of topic creep, apologies, but my interest is piqued. Whilst not relevant to this particular incident, it is interesting that the Trent 900 fits in a 747 freighter. I don't know if RR have managed to keep their other large Trent derivatives under that size limit, but doing so is a big economic enabler for fancy deals on engine purchasing, ownership, maintenance, etc. Anyone out there know? The XWB has a slightly larger fan, but I don't know if that is reflected in overall diameter. The 7000 fan is slightly narrower, as is the 1000. And if RR has exploited this fit-in-a-jumbo characteristic to enable fancy deals with airlines buying the engine, what happens when (a long time in the future) the 747 freighter stop flying?

DaveReidUK 16th Oct 2017 20:43


Originally Posted by msbbarratt (Post 9927188)
And if RR has exploited this fit-in-a-jumbo characteristic to enable fancy deals with airlines buying the engine, what happens when (a long time in the future) the 747 freighter stop flying?

I'm not sure that's an issue. The Swiss B77W that diverted to Iqualit in February had a replacement GE90-115B flown in on an An-124.

tdracer 16th Oct 2017 23:38


Originally Posted by msbbarratt http://www.pprune.org/images/buttons/viewpost.gif And if RR has exploited this fit-in-a-jumbo characteristic to enable fancy deals with airlines buying the engine, what happens when (a long time in the future) the 747 freighter stop flying?
The big GE engines have a readily removable fan module that can be removed or installed in less than a shift, no special tooling required. Sure, they can go into the AN-124 intact, but it's not that big a deal if a -124 isn't available and it needs to fit in a 747F.
BTW, you do know that Boeing is still building new 747-8F, and remain convinced that there will remain sufficient demand to make it worth while to keep building them for many years. Many of the 747F currently flying are getting pretty long in the tooth - well over 100k hours (especially the freighter conversions - most were pretty high time before they were converted to freighters) and Boeing sees them getting replaced with new 747-8F before too much longer...

galaxy flyer 17th Oct 2017 00:07

The AF did the same thing on C-5 TF-39s. I had a fan changed in EDF once, 141 brought in the fan module, couple of shifts later, outside, we were off.

megan 17th Oct 2017 00:48


a four-engined ferry is at least as likely
Apparently not due pylon and wing damage.

https://www.avweb.com/eletter/archiv...t=email#229785

A 380 Captains take.

https://twitter.com/DaveWallsworth/s...87041278566400

mickjoebill 17th Oct 2017 03:09

Is the tail camera from an A380 have loop record?


All times are GMT. The time now is 20:15.


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