B737 Flight Crew experiences an engine failure passing FL240 in the climb. The departure airport has short runways and the first choice for diversion has low ceilings. The second choice is VFR and the crew diverts but is unable to inform Dispatch in advance due to time constraints.
Synopsis
B737 Flight Crew experiences an engine failure passing FL240 in the climb. The departure airport has short runways and the first choice for diversion has low ceilings. The second choice is VFR and the crew diverts but is unable to inform Dispatch in advance due to time constraints.
Narrative
During our climb; through FL240; we experienced an engine failure. We leveled off; took care of the problem; and declared an emergency. We requested a turn back toward ZZZ1 in the process (thinking long runways; good emergency support; and close field). The Center began giving us a descent and vectors. Once we had the initial parts of the Emergency Checklists and coordination with the Cabin Crew completed; we asked about the weather in ZZZ1. Hearing the weather was poor (low visibility in fog); we decided ZZZ would be a more suitable divert field and requested a turn toward ZZZ. We were still somewhat high for a stable approach into ZZZ1 at that point; so ZZZ worked out well for getting down. The weather was better in ZZZ allowing for a visual approach; rather than the high probability of a single-engine ILS approach in ZZZ1. We didn't know the forecast trend in ZZZ1 either. As I approached ZZZ; I was finally able to speak to the passengers directly about our intentions. The Flight Attendants had briefed them prior to that. Unfortunately; our workload was high; completing all the necessary checklists; so answering Dispatchs' ACARS message wasn't accomplished.I usually check the weather in ZZZ and ZZZ1 prior to departure; but for some reason today I didn't. That would've made me more prepared for a last-minute divert. I wish I had made a quick PA right after the initial engine failure was under control; letting the Passengers know that the plane will fly fine on one engine and that the good engine was working fine. I later heard that the Passengers were pretty nervous given the loud; explosive nature of the event; combined with vibration and noise. We were task saturated and did our best; but that's an area where I personally feel I could have done better. I could've had the First Officer make a quick call to ZZZ Operations just to let them know we're coming and to notify Dispatch of our intentions.
Second reporter narrative
On climbout; at approximately FL240; we heard a loud bang and a loud buzzing sound with left yaw. The Captain leveled the aircraft and announced accomplishing the checklist items. The Captain told me her initial plan was to turn around and land in ZZZ1. I declared an emergency and was directive with ATC about our plans. Once it was determined that ZZZ1 had weather near minimums the Captain got the weather for ZZZ (we could see it and tell it was VMC). We completed the checklist items and landed uneventfully in ZZZ. My issues were with time compression and prioritization of cockpit duties. It was not as pure as a simulator event (they never are). It became a balance of accomplishing checklist items and talking with Cabin Crew about what they were seeing out the window; as well as changing the box for navigation and landing location; getting weather; continued analysis of the event with the Captain; and talking with ATC. The Captain kept us on the right pace and we had the checklists complete with a complete plan through post landing items while on downwind. There just wasn't time to bring Dispatch or Operations into the loop.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.