A B767 relief officer reported a CRM issue when a reluctant first officer accepted an engine indicat...

Narrative:

During climb out first officer noted right engine was tagging behind approximately 1.0% N1 of the commanding N1 setting. The captain made a note of it and I was sent back on my crew rest break. Upon returning from my break approximately 2 hour 20 minutes later the captain stepped back to use the lavatory and the first officer gave me the turn over brief. Just then we received a clearance to climb to our crossing altitude. During the climb first officer stated captain was concerned about he right engine not being able to achieve mct power and he called dispatch to give them a heads up. First officer demonstrated during the climb to our crossing altitude by pushing the right engine throttle full forward noting the N1 was lagging behind but by less than 1.0% of the commanded N1. That maneuver caused the plane to yaw in the climb. He informed me that now the captain had made dispatch aware of the problem and we were taking this aircraft across the pond that he was doing a report on it. First officer went to break captain said he had already put it in the book. I was out of the loop but did question the captain and he said a report wasn't necessary. I did discuss the possibility of loss of the engine and a go-around on the right engine at our destination but nothing more was discussed. I felt out of the loop since most of this went on during my break.

Original NASA ASRS Text

Title: A B767 Relief Officer reported a CRM issue when a reluctant First Officer accepted an engine indication and the issue was not discussed by all three pilots as a crew.

Narrative: During climb out First Officer noted right engine was tagging behind approximately 1.0% N1 of the commanding N1 setting. The Captain made a note of it and I was sent back on my crew rest break. Upon returning from my break approximately 2 hour 20 minutes later the Captain stepped back to use the lavatory and the First officer gave me the turn over brief. Just then we received a clearance to climb to our crossing altitude. During the climb First officer stated Captain was concerned about he right engine not being able to achieve MCT power and he called Dispatch to give them a heads up. First Officer demonstrated during the climb to our crossing altitude by pushing the right engine throttle full forward noting the N1 was lagging behind but by less than 1.0% of the commanded N1. That maneuver caused the plane to yaw in the climb. He informed me that now the Captain had made Dispatch aware of the problem and we were taking this aircraft across the pond that he was doing a report on it. First Officer went to break Captain said he had already put it in the book. I was out of the loop but did question the Captain and he said a report wasn't necessary. I did discuss the possibility of loss of the engine and a go-around on the right engine at our destination but nothing more was discussed. I felt out of the loop since most of this went on during my break.

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	840655
Time
Date	200906
Local Time Of Day	1801-2400
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Light	Dusk
Aircraft 1
Make Model Name	B767-300 and 300 ER
Operating Under FAR Part	Part 121
Flight Phase	Climb
Flight Plan	IFR
Component
Aircraft Component	Turbine Engine
Person 1
Function	Pilot Not Flying Relief Pilot
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy

A B767 relief officer reported a CRM issue when a reluctant first officer accepted an engine indication and the issue was not discussed by all three pilots as a crew.