B777-200 flight crew reported an EICAS engine overheat message that maintenance deferred resulted in engine shutdown and return to departure airport.
Synopsis
B777-200 flight crew reported an EICAS engine overheat message that maintenance deferred resulted in engine shutdown and return to departure airport.
Narrative
Aircraft had L Eng. Fire Detector Loop1 and L. Eng. Overheat Detector Loop 1 MELs applied at the gate by Maintenance. Upon climb out through 9;000 feet out of ZZZ; we received an OVERHEAT ENG L EICAS message. We leveled at 10;00 feet and followed the Electronic checklist. It led us to shut down the left engine. We [requested priority handling]; requested ARFF (Airport Rescue and Firefighting); and began a return to ZZZ. After the engine was secure; I had the F/O fly and handle the radios. I had my relief pilot backing me up on checklists and calling the company to tell them we were returning. I advised dispatch; the flight attendants; and passengers. We went through the Overweight landing checklist and Non-routine landing checklists. We did the landing performance assessment and agreed we had plenty of runway in ZZZ for the return. We all discussed threats and go-around procedures. I reviewed the ILS XXC approach. We did the descent checklist. We all agreed we had done everything we could think of to prepare for a single engine landing. We got clearance for the ILS; and I flew as normal an approach as possible with the autopilot on until 250 feet. Touchdown was at 500;000 lbs. around 100 ft. Per minute descent rate. We stopped on the runway. I made an announcement to have everyone remain seated while safety vehicles checked out the aircraft. We had ARFF check the left engine for smoke or signs of fire. Also; had them look at the brakes; which they reported were at 300 degrees. We felt that was sufficiently cool enough to taxi normally to a gate. We taxied to the gate and shut down. Perhaps Maintenance could have taken the time to look at why there were L Eng. Fire Detector Loop 1 and L. Eng. Overheat Detector Loop 1 status messages.
Second reporter narrative
We had an uneventful preflight from my perspective. MX (Maintenance) had to accomplish an MEL associated with one of the left engine overheat warning loops. The required procedure was accomplished (put inop stickers in the cockpit) and we pushed on time. Taxi / takeoff was normal. At around 9000 feet on climb out approximately 8 minutes after takeoff; we got an EICAS Msg - Engine Overheat Left. We leveled off; accomplished the abnormal checklist and shut the left engine down. Textbook; just like we walk through in the sim. FO started flying while CA coordinated and communicated our intentions to the company; dispatch; the FAs and the passengers. We accomplished all the appropriate checklists; landed overweight and stopped straight ahead. The fire trucks checked out our engine for any anomalies and brakes for excessive heat and we determined with their input that we should single engine taxi to our gate.What caused the problem is the EICAS alerted us to a possible engine overheat.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.