An MD-11 Flight Crew experienced an 'Confirm Engine Out' FMC message after takeoff. The engine had some abnormal indications; so they elected to return to their departure airport.
Synopsis
An MD-11 Flight Crew experienced an 'Confirm Engine Out' FMC message after takeoff. The engine had some abnormal indications; so they elected to return to their departure airport.
Narrative
Second takeoff of the night following a rejected takeoff for a engine fail light and maintenance correction. Normal reduced thrust takeoff and initial climb. After takeoff power reduction and flap/slat reduction the F/O noticed the 'confirm engine out' page on the FMC. Upon inspection of the engine instruments we noticed that the #2 engine N1 was indicating aprox. 15% and its fuel flow 4000 lbs.less than #1 and #3. Considering our previous problem we requested a level off and turn back. Since the #2 engine was still running we also elected not to declare an emergency but did advise local Operations that we had an engine problem. We then made several attempts to contact Central Operations and Maintenance via SATCOM but could not get through. We then contacted local Operations and advised them that we had a problem and were returning. We then sent a divert message via ACARS to advise local Operations followed by a request to approach control for an approach and landing. On short final we received a SATCOM call but elected to not answer.
Second reporter narrative
Upon further reflection; due to the fact we did not declare an emergency with ATC; the 'Diversion' message we sent via ACARS did not acquire the Dispatch permission that was needed. In the future; considering the situation; I would declare an emergency to give a higher level of protection to crew and aircraft. Also; I would request Dispatch permission assuming time and safety permitted.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.