Emirates 777 incident at Moscow
 

Emirates 777 continued flight after loud bang, messages

NTSB: Emirates 777 continued flight after loud bang, messages

The US National Transportation Safety Board revealed in a preliminary report issued 30 August that an Emirates Boeing 777-200ER crew continued a 5h flight from Moscow's Domodedovo airport to Dubai on 5 March after hearing a "loud bang" and receiving several error messages on departure.
Pilots of Flight 132 (A6-EMH) reported the incident after landing at Dubai, according to the General Civil Aviation Authority (GCAA) of the United Arab Emirates, the authority handling the investigation.
"Following the bang a number of status messages were annunciated, these messages occurred over a 16 minute time as per the Boeing AHM (airplane health management) data," the report stated.
Messages indicated a problem with the right Rolls-Royce Trent 800 engine, and included a thrust asymmetry compensation message that is issued when the flight control computer automatically uses rudder input counter the yaw effects of a failed engine.
Four additional messages were received on departure, followed by two AHM messages after landing.
Flightglobal's ACAS database shows that the 14-year-old aircraft is owned by Veling and has Trent 884-17 engines, members of the Trent 800 family. As of 31 June, the aircraft had accumulated 61,581 cycles and 12,945h, according to ACAS.
Inspection of the aircraft in Dubai revealed "a large section" of the right engine's inboard fan duct and thrust reverser were missing, starting at the trailing edge and ripping forward.
Overall, officials estimated that 2.8-3.7m2 (30-40m2) section of engine covering to be missing, along with the primary exhaust nozzle outer skin. The primary nozzle inner skin had been "holed in several locations at the 12 to 1 o'clock position," the report stated.
External to the engine, the one tyre on the main landing gear "was observed to have a large cut to the sideway" of approximately 36cm (14in), officials said. Examination of the aircraft and engine was to continue but the results have not yet been posted.
The report does not discuss what procedures the Emirates crew followed after hearing the bang and receiving the AHM annunciations or whether the aircraft should have been returned to Domodedovo.

Just off the top of my head, I would guess the crew disregarded the status messages because they know how to operate the airplane, unlike whoever wrote or is commenting on this report.

Status messages have no bearing or relevance in flight and in fact are to be ignored as soon as engine start has occurred. They are for the information of ground engineers post-flight only.

Exceedingly weak wind-up attempt, founded in ignorance as usual.

Oh yeah... you hear a loud bang, your eicas fills up with messages and you just continue to destination..pretty smart.
Another couple of unemployed pilots.

Without being there how do you know if they didn't communicate with the company regarding whatever messages were displayed on EICAS - STS or not?
Maintenance is often able to see things on the ground that we cannot yet see on the aircraft. And yes I speak from experience!
It is always an assumption that guys messed up? Nice support for our colleagues guys......

So....

Sheikmyarse, seer of seers, knower of all, doesn't know the difference between EICAS messages and STATUS messages......

No wonder he was "volunteered" to leave EK......

Hey drivers,
What about the "flight control sys" status message ...?
You know nothing ... and your problem is that you are all thinking , pilots in the UAE that you are great because you are working for this so called airlines ... but you have to open your eyes , you are just pilots ... and you are so afraid to loose your "so nice life with slaves" that you will go on while having a major problem , idiots who are risking lifes of others !!!

and for your info , an ER does not have Trent engines !!! impossible !!!

Drooppy the pilot , what is the name of the post flight report ?

777-200ER - Two 374kN (84,000lb) PW4084s, or 378kN (85,000lb) GE90-85Bs, or 373kN (84,000lb) Trent 884s; or 400kN (90,000lb) class PW4090s, GE90-90B1s, or Trent 890s; or 409kN (92,000lb) GE90-92Bs.

Our 200ERs have the Trent 890s.

The rest of your posts are no better informed.......

:uhoh:Read the last two paragraphs. External damage to the engine and can be seen from the cabin (have talked with witnesses). Tire damage from engine debris. Seems a bit more than a status msg. NTSB investigation, hmm. Don't believe they usually get involved over status msgs or even general EICAS warnings unless maybe just a little something else "amiss". Did the company say no problem bring her on in? Was Boeing involved in perhaps a "conference call" over satcom and they said, no problem bring her on in? Just askin'.

Wiz , you are a muppet , who is using wikipedia and you do not even know which kind of engines your so called airline operates ...

Tango Uniform , the only good MCC Engineers are gone from ek ... the last ones are under pressure of their management ... and i am not telling you how much they are useless as they are unexperienced !

GCAA is investigating ... thats the joke of the day ! they are not even able to go out from their offices and do not even know where the airport is !

MATMAX,

Just so I can enjoy you continuing to make a fool of yourself, can you confirm that you are sticking to the line that Emirates does not have RR Trent powered B777 200ERs, and that I, a serving EK 777 Captain, am too stupid to realize this, even though I regularly fly them?

PLEASE supply one more post to that effect!!

THEN go and research the difference between a 300ER (only available with GE-90 115 Engines), a 200LR (only available with GE 90 110s), and the 200ER which was available with the above mentioned engine options.

Then put the bottle down.....

Wiz , i was one of the guy who was signing the releases of the A/C you were flying with , and not your A/C , even before you heard about engines problems !
FYI , before ek , i was with the launch company of the 300ER and as an Engineer , do not tell me about engines as you do not even know about which sense , clockwise or counterclockwise an engine is turning ...
I am not telling you how much i am happy nowadays to deal with Etihad Pilots , Captain or F/Os , as they are listening to Engineers and not thinking that they are the ones who are knowing everything...
Mate , as i guess that you are an Aussie , a serving Captain , use your brain and follow common sense ... an advice.
Get some respects to Engineers too.
Now tell us , what is the difference between an EICAS and a STATUS message ?
If Sheiky was volunteer to leave ek , he was clever enough not to follow really stupid stuff ... thats what i did too !

MAT,

Just to be clear, are there or are there not RR Trent powered B777 200ERs?

Your last post appeared to be a lot of bluster because you won't admit you are wrong.

I'll talk to you about engines because YOU made the erroneous statement that there are no RR powered 777ERs when there are.

EICAS messages are Warnings, Cautions and Alerts. They are displayed on the upper DU and appear automatically outside inhibited flight segments.

Status messages appear on this Status page, and have no associated condition statements or non-normal checklists.

That's the difference.

This is an interesting scenario!

Let assume you MATMAX were on that EK flight as an in-flight Engineer ... what kind of suggestion or even action (only if allowed to take actions in-flight) you would have recommend to that Capt...

(...and for the purpose of the exercise let assume the Capt was NOT Wiz, because we all probably know the answer already!)

Well, in this case, it would be "Land immediately! Some fools put the wrong engines on this aircraft!!"

Wiz , as i said already , you are a monkey who is following what he has been learnt ...
EICAS means engine indicating and crew advertisement systems ...hope that your colleagues know about collision avoidance with you ...
This guy is so stupid that he will go on just to show to others that he is a TRI or TRE , and that his bo..ocks are replacing his brain...
Non Zero , i am more interested in what you say:
Even if Flight Engineers had been replaced by "computers" , you still have Cabin Crews ... call them and ask them about what they saw or heard... that could helps ! thats my own experience and thats valid on the Bus too as about engines , it could be seen from the cabin...
Hope that you follow me.

OBOGS , some words of wisdom ...?
I am not saying that these guys did not do everything...
I have lived some same situations and just get nervous by this Wiz who thinks that everything is written in the books and that he is the best pilot on earth ...
Just wonder mate , why the A/C sent a lot of messages after a loud bang ...

MAT,

Where did I do that?

No, all the answers are not in the books and in this case the crew assessed all the information and made what was ultimately a safe decision.

I note that you demand respect and accuse me of egotism, while you will not acknowledge making an error regarding the engines on the 200ER.

An engineer who won't admit when he's wrong makes ME nervous.

Oh, and BTW

Nope. Engine indication and crew ALERTING system.

Yes, Status is part of it, but in common parlance there is a distinction between EICAS alerts and EICAS Status messages.


OBS,

Re EICAS, I've talked BS? Not unusual, but can you highlight where?

It's simple chaps... matmax is a girl's bush:{:{:{:{



A pilot wannabe:D:D:D

haha this thread is hilarious,

Those advertising agencies have just gone overboard IMHO. You've got an engine problem and you have to wait 30 seconds before you can check the systems, seriously.

haha I think we've got enough material to film Airplane 3: Disaster in the Desert. Too bad Peter Sellers isn't around to play Max.

complete with the 'french' accent.......!!!!!!

...And doesn't dear Maxy show one common trait of a certain kind of poster...NEVER EVER admit you are wrong.

I suspect he had a little "liquid propulsion" when posting, and got confused between the 300ER (which can only have GEs) and the 200ERs (the EK versions of which have Rollers).

But admit it? Nope. Insult, bluster, mis-direct and simply ignore, but simply say "yes, that was my mistake"? No way.

Odd.....

I suspect you are exactly right. But once it was pointed out to him that the aircraft in question WAS a RR powered 200 ER (in current parlance) there was simply no way he would admit it.

Straight from the FCOM, just to avoid any further arguing about engines

200ER Registry Number Airplane Number Serial Number Model Cabin Config Engine Type

A6-EMH 005 27251 777-200.1 3 Class RR - Trent 892

Fack5 , i guess that you are right.
Anyway , continuing a flight with an un-contained engine failure is totally unsafe ... whatever the engine is ...

Thrust Assym and EEC could be either status or alert messages, depending on whether they were single or dual channel failures. Even if they were alerts,neither is a land ASAP condition.

The others are all STATUS messages.

The "Bang" is obviously the biggest indication there is a big problem, and I'm not saying it was a slam-dunk decision either way, but in light of the good result, I think the guys did a good job.

Matmax, the engine DID NOT FAIL!!!

Oh yeah , and the "loud bang" was coming from where ?
What about the "TURB OVHT SNSR ENG R" and "FIRE LOOP 1 ENG R" ???
Just a small hot air leak ...?

Matmax,
A loud bang can come from anywhere.... a bird strike on the windscreen etc etc etc. An unconfined engine failure implies the engine destroyed itself and ceased to work. In this case it continued to work as advertised all the way to destination. It was NOT an uncontained engine failure. There are many flights around the world where parts fall off the airplane and they continue to fly perfectly safely.
So get off your high horse. You were not there on the flight deck with the guys. They made an assessment based on information at the time, in communication with various departments at the company and elected to continue based on that information.
It's very easy making armchair decisions after the fact with all the information available. They didn't. They did the best they could at the time.
Let's all be grateful for a safe outcome and that nobody got hurt.
How about we wait for the actual findings of an investigation before pulling anyone apart.
And by the way, according to you, all the good engineers have left EK have they? I disagree. we have some damn fine, hard working, dedicated engineers who do the best they can under difficult, short-staffed circumstances. I find I work quite nicely with them all. I have a great respect for them and appreciate that they keep me safe. I'm sure a lot of my colleagues feel the same way.
Enjoy Etihad, from your attitude I don't think your departure was much of a loss. Maybe I'm wrong?????
Safe flying everyone
J

This thread is embarrassing now, just like the one on the R&N forum.

Armchair pilots (some not even pilots) with an obvious lack of systems knowledge on the 777 looking for a chance to have a dig at some ex-colleagues... and end up making a fool of themselves.

Sheikhmyarse, if you're an ex-777 pilot you should have known your aeroplane better than that.

MATMAX, if you were working for the launch customer of the -300ER would that not be Air France...? Why would you leave a good cushy position with heavily unionised AF Industries to come to EK...? Did you get the chop for for putting the wrong big round things on the wrong flappy wingy things?

Oh dear!
 

MATMAX

It's bad enough having to read your posts on 'Engineers & Techs' but when you come on here insulting all and sundry with your ill-informed, bitter comments it's embarrassing to ALL the professionals out there.

Wind your neck in and save it for JB.

Oh, and just for good measure.....

Emirates B777-21H-ER

Turin, you just got that guy in the photo sacked... did he not learn anything from the CMB incident? ;)

Note that this is as near as Mat will come to admitting he was wrong about the engines on the 200ER, in spite of insulting people for who tried to point out the error.

Judge not lest ye be judged
 

The judgment of a company’s or crew’s actions during an in-flight non-normal event is probably foolish and definitely inappropriate without full knowledge of the facts. However this event does raise some issues to be considered and perhaps learnt from.

But first some facts:

Status messages are in fact part of the EICAS system. Status messages are available full time when powered. The “Status Cue” which alerts the crew that there are in fact status messages on the status page is inhibited for 30 minutes after engine start. This is because status messages are essentially related to dispatch. Once engines are started the idea is that the flight is essentially dispatched with regard to status messages only and the crew does not need to and should not be concerned with the message. This falls away however if an EICAS Alert (Warning, Caution or Advisory) message occurs before takeoff. Some of these messages are actually there to prevent a takeoff and only appear on the ground. These messages in themselves are often accompanied by a status message and these combinations may therefore prevent takeoff. The MEL will decide. If EICAS displays an Alert (warning, caution or advisory), between engine start and takeoff then crews would then take notice of the status message having done whatever checklists are required. In some instances an EICAS caution can even resolve itself but the underlying and remaining status message should be considered prior to takeoff. E.g. Flap problems that are temporarily resolved when in commanded postion despite FSEU status messages - Probably not a great idea to commence the takeoff.

Multiple status messages affecting the same system are beyond the scope of the MEL. Its intention is to cover each fault in isolation. Multiple status messages on the same system generally indicate a larger problem that cannot always be dealt with by simply looking at each message as a single issue and applying the MEL.

In flight a status message on its own should not dictate a course of action. In some events the status message can simply be cleared without further action as the fault was transient. It would be a pity to jettison fuel and return on the assumption that the fault may prevent dispatch at the next station according to MEL. This has been done before and the engineer simply walked in, cleared the fault and said “off you go”. A few red faces I imagine. Multiple Status messages (possibly with EICAS Alert messages) in flight occurring simultaneously and related to the same general system should be some cause for concern. Clearly an event has occurred. Maintenance looking at downlinked data may be able to shed more light on the subject. When this event is accompanied by visual, tactile or aural feedback, it leaves little to doubt; the only question remains is “how bad?” In this particular instance the messages are all related to the engine and/or sensors deriving information off it. A bang and a number of sensors being lost or related systems being affected is almost conclusive of damage of a more serious nature.

To look at each status then in isolation and assume this is simply a redundant feature being lost and therefore inconsequential, somewhat defeats the purpose and design of the system. It was never intended to be used like that, either on the ground or in the air. Clearly this event was not enough reason for an engine shutdown if it continued to run without loss of power or parameters exceeded but the event should be considered as a possible reason to land the aircraft and investigate.

Who knows what actually happened on the day. I’m fairly confident any EK crew would have contacted maintenance before taking hasty unilateral decisions but here is where it gets a little sticky.

The commercial dictate would argue that the engine was running normally and the status messages each in isolation did not warrant a return. After all, the engine is turning and burning quite happily for now. On the other hand one would hope the engineering side would have been heavily prompted to come to the conclusion that a fairly significant engine event had taken place. So would have the crew who then had to face a route without an abundance of friendly airports and some significant terrain.

My guess is that the crew and some engineers were concerned that if they jettisoned fuel and landed, and it transpired that there was not much wrong with the engine itself that they then would have the book thrown at them. The one that says you don’t need to land for status messages or shutdown engines that are running without parameters exceeded and if both engines are running normally you carry on. I suspect this was going through a few minds. Had they landed and the damage been proved they would have been let off the hook. Who knows, perhaps even commended but even still possibly queried if they ignored engineering advice and took the decision upon themselves.

Now the engineering advice in itself is a minefield. It comes with a disclaimer that they are not ultimately responsible despite them probably often being better informed on a system than the crew. An easy way out indeed. I wish I could use the same umbrella sometimes!

I don’t envy the crew. They could have been damned either way. And I don’t know what transpired after they became aware of the problem. It’s interesting to muse what the decisions might have been taken if some senior post holder had been aware of the problem and his family was on board.

What I do know from a number of discussions and incidents is this:

In many cases the crew is more concerned with what the company may do to them if they get something wrong rather than the actual consequences to the flight of getting it wrong. They are not the same thing. If one errs on the side of safety but it subsequently appears as overcautious then this can be a cause for a nasty letter or worse. Look at what happens if a bit extra fuel is carried despite the reasons.

We make mistakes. The CRM department tells us that all the time. But if a mistake puts the crew in a jam which they recognize as of their own making then they become panicked, not by the situation but by the recriminations. It’s somewhat akin to having an in flight problem and then compounding it by telling the crew they may lose their whole livelihood. This is exacerbated by the expat existence. It’s not just the job at stake but the home they live in, the friends they see, the schools the kids attend etc. A panicked crew is unlikely to perform well. Show them threats from an in-flight situation and they often perform wonderfully as trained; throw in the threat to livelihood and family and they can come to pieces.

Unfortunately the price for costing a company a bit of cash or negative publicity can be a hugely punitive reaction despite the mistake being unintentional or even well meaning. An interview panel, time and thousands of pages of manuals can and will often be used to demonstrate the failures. Its also not difficult to make an argument that safety has been compromised. But face it this happens to some small degree on every flight. There will always be some degree of error. I dont know how many times I've seen a crew make a bigger error in a simulator because they are worried about the instructor noticing a small one. This is exacerbated in flight with recorders that miss nothing and are now used to hang crews rather than the original intention of anonymously monitoring trends.

Pilots are acutely aware of all this. We have moved to a new era in aviation. The corporately motivated pilot is superseding the safety motivated pilot. The two should go hand in hand but sometimes do not. And by this I don’t mean corporately motivated in a positive manner – huge bonuses for obvious good performance. No - they have been left with the final responsibility thereby providing a useful scapegoat for others if anything goes wrong and this feature is being used more and more frequently. And when did you last see a crew get an SVP type bonus when they made decisions that ultimately saved a lot of lives, money, or the company itself. No that’s their job – they are trained to do it. But doesn’t the same apply to any SVP?

Not a lot when a crew gets it right - maybe a pat and a star. Personal calamity if they get it wrong, even if no one is hurt. On the other hand there are huge bonuses for not so obvious performance for other senior post holders and no accountability for some obviously appalling decisions. This is the corporate way and is not only confined to airlines. The crux is aviation plays for high stakes, not just the profits of the shareholders; hence responsibility from all should be of the highest order and leaning towards the conservative.

The crew are the last defense against silly decisions motivated by economic gain but worldwide they are being manipulated into a situation where making a stand may be career suicide. Did this phenomenon influence this particular case? Who knows? But it is happening and the pressure is mounting. The tools and options for pilots to stand against commercial pressure are being slowly dismantled. This should be of great concern to the flying public.

Today’s pilots are often so afraid of being in front of a wooden desk that they make choices that could result in a lot of wooden boxes.

If you look closely at the pic you can see that he is in fact at the apogee of a star jump. Just a lucky shot I suppose. :ok:

Ah, yes.

Then he should be commended for attempting to keep his BMI below limits...:E

Doh!!

Warning, Caution, and Advisory!

Excellent post, Pixy.

I would say this, though. EK have certainly been punitive in situations where they feel crews have made errors that have affected safety, and more than once stupidly and counter-productively so.

This has no doubt built a climate of fear among the Pilots and the thought of "will I get a bollocking/demoted/fired" DOES weigh heavily in any non-normal situation.

This is a bad state of affairs for reasons you point out so eloquently.

I am not aware, however, of anyone actualy having any punitive action taken against them for managing a non-normal to a safe outcome, even if it has not been the optimal commercial decision.

Sure there are debriefs- that's what any airline does to learn lessons- and no doubt at least one of our DCPs demeanor would make that unpleasant.

But in cases like this, I honestly don't think the guys would have faced any form of discipline had they returned-It's one option they are trained to consider.

They assesed it was safe to continue and the outcome was good.