B777 flight crew reported receiving an engine fire warning during cruise; then received intermittent warnings. The flight returned to the departure airport and landed overweight.
Synopsis
B777 flight crew reported receiving an engine fire warning during cruise; then received intermittent warnings. The flight returned to the departure airport and landed overweight.
Narrative
On Day 0; I was operating from ZZZ to ZZZ1 with a crew of three pilots and nine flight attendants. The aircraft was dispatched in accordance with the MEL with the right engine fire loop 1 and right engine overheat system 1 inoperative.Approximately one hour after departure; a right engine fire warning was received. While referencing the QRC and accessing the associated checklist; the fire warning and associated EICAS messages cleared. All other engine indications were normal. Intermittent EICAS messages were displayed indicating the right engine fire detection and overheat detection systems were inoperative. The STATUS page indicated the right engine fire loop 2 and overheat system 2 were affected. Dispatch and Maintenance Control were contacted via SATCOM. Maintenance advised the issue was likely related to a faulty card common to both detection devices systems. Intermittent; erratic short-duration fire warnings continued to occur between fire detection and overheat detection system inoperative EICAS messages.Given the intermittent nature of the warnings and the loss of fire and overheat detection capability on the right engine; the decision was made to initiate an air return to ZZZ. Priority handling was requested with ATC and Non-routine landing procedures were referenced. The flight attendants and passengers were advised of a precautionary return to ZZZ. A descent to a lower altitude was initiated to reduce landing weight.Approximately 30 minutes prior to landing; the fire detection system returned online and operated normally for the remainder of the flight. The Overweight Landing Checklist was completed. The arrival briefing included use of the entire runway length to mitigate high-energy brake usage.The First officer made the landing and Fire and Rescue equipment was present. After stopping the aircraft clear of the runway; an inspection of the wheels and brakes was accomplished. Landing weight was less than 20;000 pounds above maximum landing weight and brake temperatures were within normal limits. After completion of the inspection; we taxied the aircraft to the gate without further incident.Cause: Don't MEL a fire loop 1 because as obviously demonstrated fire loop 2 can also fail in flight resulting in an engine fire indication in the cockpit.Failure to fix a fire loop prior to departure to save time and money did not pay off in this case. An inflight diversion; and literal days of an aircraft being offline in an outstation is not cheap; it led to the disruption of XXX people. The continual procedures of delaying known maintenance items and kicking the can down the road has consequences. Fixing a single loop failure may not have resulted in a dual fire loop failure.
Second reporter narrative
On Day 0; I was operating from ZZZ to ZZZ1 with a crew of three pilots and nine flight attendants. The aircraft was dispatched in accordance with the MEL with the right engine fire loop 1 and right engine overheat system 1 inoperative.Approximately one hour after departure; a right engine fire warning was received. While referencing the QRC and accessing the associated checklist; the fire warning and associated EICAS messages cleared. All other engine indications were normal. Intermittent EICAS messages were displayed indicating the right engine fire detection and overheat detection systems were inoperative. The STATUS page indicated the right engine fire loop 2 and overheat system 2 were affected. Dispatch and Maintenance Control were contacted via SATCOM. Maintenance advised the issue was likely related to a faulty card common to both detection devices systems. Intermittent; erratic short-duration fire warnings continued to occur between fire detection and overheat detection system inoperative EICAS messagesGiven the intermittent nature of the warnings and the loss of fire and overheat detection capability on the right engine; the decision was made to initiate an air return to ZZZ. Priority handling was requested with ATC and Non-routine landing procedures were referenced. The flight attendants and passengers were advised of a precautionary return to ZZZ. A descent to a lower altitude was initiated to reduce landing weight.Approximately 30 minutes prior to landing; the fire detection system returned online and operated normally for the remainder of the flight. The Overweight Landing Checklist was completed. The arrival briefing included use of the entire runway length to mitigate high-energy brake usage.The First officer made the landing and Fire and Rescue equipment was present. After stopping the aircraft clear of the runway; an inspection of the wheels and brakes was accomplished. Landing weight was less than 20;000 pounds above maximum landing weight and brake temperatures were within normal limits. After completion of the inspection; we taxied the aircraft to the gate without further incident.Cause: The crew utilized many aspect of CRM including the fix strategy; experience; communication and system knowledge to work thru a challenging issue to a successful completion.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.