Pilot reported engine vibration during final climb to cruise altitude. Flight crew reduced power until vibration stopped and continued to destination airport.
Synopsis
Pilot reported engine vibration during final climb to cruise altitude. Flight crew reduced power until vibration stopped and continued to destination airport.
Narrative
I was pilot flying. We climbed to FL330 and leveled off for 10 minutes. We were then given a clearance to climb to FL350. Shortly after leveling off; we noticed airframe buffeting. We then noticed that the Number 2 Engine was at around 65% N1 and the white trend line was at the climb limit. The the auto-throttles disconnected. The no. 1 engine was at 95%. I moved the Number 2 throttle forward and aft; but could not get the motor to accelerate past 65% N1. The buffeting continued; all other engine indications were normal. We decided to run the Engine Limit/Surge/Stall checklist and ask for lower. When the power setting was reduced to 57% N1; the vibration stopped and the engine ran normally. We completed the checklist. At this point we were around 300 miles from ZZZ; or about 50 minutes from touchdown. We decided to continue on and [request priority handling]. We anticipated a normal landing but decided to treat it as a single engine landing and request Airport Rescue and Fire Fighting meet us upon landing. We ran the One Engine Inoperative Landing Checklist and the Non-Routine Landing Checklist. We landed normally and taxied to the gate after being examined by the Fire Chief.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.