An md-11 flight crew experienced an 'confirm engine out' FMC message after takeoff. The engine had s...

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 first officer 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.

Original NASA ASRS Text

Title: 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.

Data retrieved from NASA's ASRS site as of April 2012 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.

Attributes
ACN	873868
Time
Date	201002
Local Time Of Day	1801-2400
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	MD-11
Operating Under FAR Part	Part 121
Flight Phase	Takeoff
Route In Use	SID ZZZ
Flight Plan	IFR
Component
Aircraft Component	Turbine Engine
Person 1
Function	Captain Pilot Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Person 2
Function	First Officer Pilot Not Flying
Experience	Flight Crew Last 90 Days 100 Flight Crew Type 1000
Events
Anomaly	Aircraft Equipment Problem Critical

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.