Fire/Overheat Det Fault on 777 engine
Thread Starter
Join Date: May 2010
Location: Dubai
Posts: 9
Likes: 0
Received 0 Likes
on
0 Posts
Fire/Overheat Det Fault on 777 engine
Hi everyone.
I would like to have your thought about the following:
On an 11h flight on 777, after 6h you got an EICAS "DET FIRE ENG R or L": Engine fire and overheat detection is failed.
Would you consider continuing to destination? Return? Divert?
Thanks.
I would like to have your thought about the following:
On an 11h flight on 777, after 6h you got an EICAS "DET FIRE ENG R or L": Engine fire and overheat detection is failed.
Would you consider continuing to destination? Return? Divert?
Thanks.
FWIW Our 777 ECL/QRH for this has no action items, simply the condition statement the OP quotes:
“Engine fire and overheat detection is failed.”
I suspect the OP might have started a thread where having a supply of popcorn might be useful.
“Engine fire and overheat detection is failed.”
I suspect the OP might have started a thread where having a supply of popcorn might be useful.
It's a statistical thing, which we might not like but that's how failure analyses works in aviation...
What is the chance of failure after a failure? Very remote that it will happen for the remainder of the flight. So Boeing will not tell you to "land asap" as it is not required. As a pilot you prefer to stay safe so nobody should oppose the decision to divert and land. Although there is no reason to rush, plenty of time to choose a suitable alternate for your company.
If you would end up getting an engine fire, the fire will eventually destroy the engine which will be visible in other ways. In that case you would consider it a land asap situation as you cannot confirm a possible fire to be extinguished.
It gets even trickier with cargo hold fire detection system failures in flight...
But as mentioned, get out the popcorn and shoot my opinion :-)
What is the chance of failure after a failure? Very remote that it will happen for the remainder of the flight. So Boeing will not tell you to "land asap" as it is not required. As a pilot you prefer to stay safe so nobody should oppose the decision to divert and land. Although there is no reason to rush, plenty of time to choose a suitable alternate for your company.
If you would end up getting an engine fire, the fire will eventually destroy the engine which will be visible in other ways. In that case you would consider it a land asap situation as you cannot confirm a possible fire to be extinguished.
It gets even trickier with cargo hold fire detection system failures in flight...
But as mentioned, get out the popcorn and shoot my opinion :-)
Well that was boring...........no need for the popcorn so far..
FWIW agree with the likes of BraceBrace and flyboyike.
Not sure I’d be thinking of returning to base 6hrs into an 11 hour sector, even if that was possible. I’d be inclined to tell Company about the message (if I could) but TBH I’d be looking at carrying on to destination.
FWIW agree with the likes of BraceBrace and flyboyike.
Not sure I’d be thinking of returning to base 6hrs into an 11 hour sector, even if that was possible. I’d be inclined to tell Company about the message (if I could) but TBH I’d be looking at carrying on to destination.
Thread Starter
Join Date: May 2010
Location: Dubai
Posts: 9
Likes: 0
Received 0 Likes
on
0 Posts
Right. The situation doesn’t require a land asap. As mentioned above there are no crew actions required, the system brings to your attention you have lost fire/overheat detection on the engine.
Having discussed the scenario with some colleagues it came up continuing would be reasonable, also if Ops agrees and can fix the plane at destination.
We still have engine primary and secondary parameters to monitor a possible malfunction, and possibly liaise with engineering for further info.
It’s a bit of grey area though .
Having discussed the scenario with some colleagues it came up continuing would be reasonable, also if Ops agrees and can fix the plane at destination.
We still have engine primary and secondary parameters to monitor a possible malfunction, and possibly liaise with engineering for further info.
It’s a bit of grey area though .