B767 flight crew reported an engine surge during descent. Flight continued to safe landing at destination.
Synopsis
B767 flight crew reported an engine surge during descent. Flight continued to safe landing at destination.
Narrative
On initial descent from 380 as the power began to reduce we had an engine surge. I was pilot flying and called for the eng surge QRC. We ran the QRC and Checklist and determined that a continuation to ZZZ was a safe course of action. Dispatch was involved in the decision making. We discussed a separation of duties where I flew the aircraft and worked with ATC while the captain and relief pilot worked the checklists and with Dispatch. The captain elected to request priority handling and have the emergency equipment inspect the aircraft upon landing. The rationale was due to a potentially weakened engine; priority handling would be helpful even though after the initial surge the engine indications and function seemed normal. In our planning/briefing for landing we emphasized smooth power inputs along with a stable approach with earlier than normal configuration. We also discussed a plan of action should the engine surge or fail before landing. A safe landing was performed. After landing the fire equipment inspected the engine and we then taxied to the gate. We met with maintenance; debriefed the Chief Pilot and dispatch. A crew debriefed was also completed.
Second reporter narrative
We initiated our decent from FL380 when we heard one loud bang. The EPR (Engine Pressure Ratio) carrots bounced around; N1 surged from 76 to 91; and the EGT rose. We performed the Engine Limit Surge or Stall QRC and were able to land uneventfully with the autothrottles off for the remainder of the flight. We talked with dispatch; requested priority handling; and proceeded to a landing on XXL at ZZZ. We taxied clear of the runway; shut the Left engine down; then had the fire trucks inspect the aircraft for any issues. They then followed us to our gate. The previous flight had had similar issues. It was worked on for 2 days before being signed off.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.