A B737-300 flight crew has erratic engine indications during climb to altitude.

Attributes
ACN	703263
Time
Date	200607
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : bos.airport
State Reference	MA
Altitude	msl single value : 17000
Environment
Flight Conditions	VMC
Aircraft 1
Controlling Facilities	artcc : zbw.artcc
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	climbout : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Experience	flight time last 90 days : 110 flight time total : 3100 flight time type : 510
ASRS Report	703263
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 240 flight time total : 15500 flight time type : 4000
ASRS Report	703261
Events
Anomaly	aircraft equipment problem : critical
Independent Detector	aircraft equipment other aircraft equipment : eng instruments other flight crewa other flight crewb
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	Aircraft Flight Crew Human Performance
Primary Problem	Ambiguous

Narrative:

I was flying on climb out with autoplt engaged. Climbing through 17000 ft aircraft began a roll/yaw. I began a scan to see if we had flown through wake turbulence. Captain noted that engine #1 was showing erratic indications. Captain took controls and disengaged the autothrottles. He slowly retarded the #1 throttle. Engine #1 was still showing erratic indications but no warnings or cautions had displayed. As the engine slowed to idle the indications were normal. We discussed the situation and elected to run the in-flight engine shutdown checklist but leave the engine running as long as there were normal indications. As the engine appeared to be operating normally at this point we felt we would be prepared for a shutdown if necessary but did not want to do so unless it was required. We briefed a single engine approach and landing as a precaution but utilized the engine for the approach. Captain conducted the uneventful approach and landing with both engines operating. Supplemental information from acn 703261: called for qrc; called dispatch; maintenance; I elected to proceed to bos since we could drift towards it and needed to lose altitude. Advised ATC also; planned a cabin advisory with flight attendants; planned for single engine approach but never shut down engine as it was now acting normal.

Original NASA ASRS Text

Title: A B737-300 FLT CREW HAS ERRATIC ENG INDICATIONS DURING CLB TO ALT.

Narrative: I WAS FLYING ON CLBOUT WITH AUTOPLT ENGAGED. CLBING THROUGH 17000 FT ACFT BEGAN A ROLL/YAW. I BEGAN A SCAN TO SEE IF WE HAD FLOWN THROUGH WAKE TURB. CAPT NOTED THAT ENG #1 WAS SHOWING ERRATIC INDICATIONS. CAPT TOOK CTLS AND DISENGAGED THE AUTOTHROTTLES. HE SLOWLY RETARDED THE #1 THROTTLE. ENG #1 WAS STILL SHOWING ERRATIC INDICATIONS BUT NO WARNINGS OR CAUTIONS HAD DISPLAYED. AS THE ENG SLOWED TO IDLE THE INDICATIONS WERE NORMAL. WE DISCUSSED THE SITUATION AND ELECTED TO RUN THE INFLT ENG SHUTDOWN CHKLIST BUT LEAVE THE ENG RUNNING AS LONG AS THERE WERE NORMAL INDICATIONS. AS THE ENG APPEARED TO BE OPERATING NORMALLY AT THIS POINT WE FELT WE WOULD BE PREPARED FOR A SHUTDOWN IF NECESSARY BUT DID NOT WANT TO DO SO UNLESS IT WAS REQUIRED. WE BRIEFED A SINGLE ENG APCH AND LNDG AS A PRECAUTION BUT UTILIZED THE ENG FOR THE APCH. CAPT CONDUCTED THE UNEVENTFUL APCH AND LNDG WITH BOTH ENGS OPERATING. SUPPLEMENTAL INFO FROM ACN 703261: CALLED FOR QRC; CALLED DISPATCH; MAINT; I ELECTED TO PROCEED TO BOS SINCE WE COULD DRIFT TOWARDS IT AND NEEDED TO LOSE ALT. ADVISED ATC ALSO; PLANNED A CABIN ADVISORY WITH FLT ATTENDANTS; PLANNED FOR SINGLE ENG APCH BUT NEVER SHUT DOWN ENG AS IT WAS NOW ACTING NORMAL.

Data retrieved from NASA's ASRS site as of January 2009 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.