Air carrier Captain reported an engine failure during climb. The pilots turned back to the departure airport.
Synopsis
Air carrier Captain reported an engine failure during climb. The pilots turned back to the departure airport.
Narrative
Climbing through about 22;000ft; we heard a load thud accompanied by a sudden yaw. I was PF (Pilot Flying). The autopilot was on. The autopilot remained engaged. I shallowed the climb. We analyzed the situation and determined that the # 2 Engine had seized. I instructed the FO (First Officer) to [request priority handling] with ATC and ask for a turn back to ZZZ. We completed the Engine Failure Severe Damage QRC and then I transferred control to the FO; while I completed the checklists. I advised the Flight Attendants and asked if they saw or smelled anything unusual. They were aware that the engine had failed and described a large fireball that erupted briefly from the engine. I sent a diversion ACARS message to Dispatch with the note; Engine failure" in the comments section. I also called ZZZ Ops and ensured they knew we were returning; and that Dispatch was aware. I updated the performance data and sent for landing data for Runway XX. I only sent for flaps 30 numbers as I was getting task loaded at this point and ATC had just turned us onto a final approach. I knew the runway was one of the longest; so I wasn't really concerned with having the exact stopping margin. Had I sent for the Flaps 15 Engine Failure numbers; I would have also received the prompt for brake cooling numbers. With the distraction of coordinating with ATC and ARFF (Airport Rescue and Firefighting); we did not check those after landing. I took control at about 1;000ft agl. We were a little fast and I used the speedbrake at flaps 15 to slow us down. We were also slightly low on the PAPI; but I was able to easily correct; and we landed uneventfully in the Touchdown Zone. I stopped the aircraft in the runway and instructed the ARFF Crew to inspect the entire aircraft. After receiving the "All Clear;" we taxied to the gate."
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.