B737-800 flight crew reported the #1 Engine failed during the climb and proceeded to shut down the affected engine. The flight crew then performed an air turnback.
Synopsis
B737-800 flight crew reported the #1 Engine failed during the climb and proceeded to shut down the affected engine. The flight crew then performed an air turnback.
Narrative
While climbing out from ZZZ on the ZZZZZ Departure; the aircraft experienced an engine failure of the #1 Left Engine. The flight was part of a [flight with a Check Airman] sequence. All appropriate checklists were completed and the aircraft returned to ZZZ for a successful; but overweight; landing. The biggest additive condition that occurred during this event was due to the multitude of requests for information from Dispatch during high workload times. Before we even had the chance to assess the engine condition; balance our response and communicate with ATC; there were 2 ACARS messages from Dispatch; followed by further requests; while we were executing the QRH Checklist; including the question; 'Did you [request priority handling]?' Once on the ground; ZZZ Operations and Dispatch were asking for information; while we were coordinating with the Airport Fire Response teams; ATC for a place to wait while the brakes cooled; and dealing with the passengers to set their expectations. All of these requests should have waited until the aircraft was at the gate.In a [situation] like this; requests for information; unless directly associated with ensuring a successful outcome; should be kept until the more immediate necessity of safely getting the aircraft on the ground has been accomplished. The numerous requests for information are an additive and task loading condition that the crew does not need while executing the QRH procedure. While I understand the need for information in the Company Operations Center; none of the requests were helpful to the crew. Dispatch pushing the weather and gate info to us via ACARS; plus a request to call when able would have helped. A checklist of who to contact would be helpful AFTER the aircraft is shut down; the passengers and crew are taken care of; and the crew has a chance to recover.
Second reporter narrative
The event occurred on the ZZZZZ Departure at FL230. We had just been given climb to FL270. The autopilot and engine anti-ice were on. We experienced a yaw to the left and had indications of an engine failure. There was an engine failure cue for the #1 Engine and a rapid rise in EGT. Within 30 seconds the EGT was over 900 degrees and kept increasing. As the pilot flying; I kept flying and called for the engine failure QRH. The engine was shut down in accordance with the QRH. The EGT peaked just over 1;000 degrees; and did not go down until the checklist was run. We coordinated a return to ZZZ. [Priority handling was requested] and the landing with One Engine Inoperative Checklist was run. Since the Captain was in the right seat we elected to have them make the single engine landing. We landed in a flaps 15 configuration and met the fire equipment just off of Runway XX. No indications of fire inflight or on the ground were noted. Brake cooling calculations called for a 30-minute cooldown. The plane was returned to the gate with no injuries or further complications.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.