A B737-700's left engine flamed out but as a descent was begun and the thrust lever retarded it relit. The flight diverted to a nearby airport where the aircraft was removed from service.

Date: 2011-05 · Aircraft: B737-700 · Phase: cruise

Anomalies: aircraft-equipment-problem-less-severe

Synopsis

A B737-700's left engine flamed out but as a descent was begun and the thrust lever retarded it relit. The flight diverted to a nearby airport where the aircraft was removed from service.

Narrative

During cruise at FL410 IMC; the number one engine rolled back accompanied with a low muffled bang. The RPM went low enough to drop the autothrottles; but not low enough for the generator to drop off the line. We requested a descent as we may have lost an engine. The descent clearance was almost immediate. When the throttles were retarded for the descent; the engine returned to normal operation. We leveled at FL390 and ATC was told to standby while we contacted Dispatch. The First Officer ran the Engine Limit/Surge/Stall Checklist in the QRH. Dispatch was contacted and the decision was made to divert to a nearby airport. ATC was notified and a clearance to the divert airport was received. The flight attendants; who had been seated since the departure due to turbulence; were contacted and told that we had an engine malfunction; we would be diverting; and we were planning a normal approach and landing. They stated that they had heard the noise and that it had been loud in the forward cabin. A PA announcement was made saying that we had an engine malfunction and that the safest course of action was a diversion to a nearby airport. We reviewed the QRH and discussed the engine failure in the landing configuration section should the engine again malfunction. The decision was made to use a normal flap setting as at this time the engine was operating normally. We prepared to land to the southwest at the divert airport. The diversion checklist was reviewed and the landing altimeter was reset in the pressurization controller. Dispatch sent us a message verifying ZZZ as our destination which we agreed to via ACARS. After the descent checklist; the flight attendants were again contacted and told the time to landing and that again it would be a normal approach and landing. A PA announcement was made telling the time to landing as that this was a precautionary diversion and the approach and landing would be normal. We landed and taxied to gate. Passengers were deplaned and told that we would take the first terminator; due in an hour; and complete the trip to. Dispatch; Maintenance; and the Chief Pilot on duty were contacted via telephone. A logbook entry was made outlining the event. The pilots were removed from the remainder of the trip by Crew Scheduling and the flight attendants were to continue with the passengers. We talked to the flight attendants to be sure that they were comfortable to continue the trip. ATC was very helpful arranging the turn and let down into the airport. Dispatch was easily contacted and the decision was made to divert with minimal discussion. We also contacted the station to let them know we were coming (Pre-ACARS; this would have been harder to do). The First Officer was very helpful in having the QRH out and ready and being ahead of the developing situation. Coordination between ATC; Dispatch; the diversion station; and the flight attendants made our job easier.

Second reporter narrative

The aircraft appeared to have enough thrust with the number two engine to maintain altitude; however; the descent seemed prudent. I throttled back and began the descent. In the descent; we pulled out and reviewed the Engine Stall Checklist as that seemed to be most appropriate and reviewed the procedures. At that time; the engine re-lit and was working itself back to idle. No exceedances were noted throughout the event. The number one engine came back online and functioned normally throughout the descent and recovery to the nearby divert airport. After the engine stabilized; the Captain coordinated with Dispatch; Maintenance and the Chief on call. They concluded it would be prudent to recover at the nearest suitable field. The recovery was uneventful.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.