2025-09 · NASA ASRS report 2287709
B737 MAX 8 flight crew reported they shut an engine down during cruise climb due to excessive vibrations and loss of power and returned to departure airport.
We were operating flight XXXX to ZZZ1. I was PM and CA was PF. Preflight procedures; walk around; taxi; and takeoff were all normal. During climbout; we encountered icing conditions approximately 16-20;0000 feet where engine anti-ice was utilized on then off exiting conditions. We briefly were VMC; then re entered icing conditions turned the engine anti-ice back on and exited approximately FL260 where it was turned off again. Neither time in IMC was any moisture painting on the radar; and we observed a very light trace of icing. Normal anti ice indications were observed during operation. Approximately at FL270 an audible pop was heard followed by some vibrations; I immediately shifted my scan to the engines and #2 was flashing with all annunciations on the ND (Navigation Display). The N1 was showing decreasing and to about 60%. The CA called engine failure; I confirmed and stated that #2 was rolling back. The vibrations were well above limits; so we agreed it was an engine limit situation and then proceeded with the engine limit surge or stall immediate action items; which the CA executed. We discussed briefly and elected to return to ZZZ. I requested priority handling with Center; told them we lost an engine and wanted vectors for ZZZ and were requesting crash and fire rescue to be ready. The FA's had called us almost immediately; but the CA waited to answer and take their input then inform them briefly. He called them back a few minutes later and gave them the Brief info. I then followed up the immediate action items with the QRC; then drove me into the continued checklist in the FM. Engine indications were still abnormal with high vibrations; after step 3; which drove us to step 7 to shut down the engine. We followed the proceeding checklist to step 17 which states do not attempt an air start and then to the one engine- inoperative landing checklist. I ran the one engine inoperative landing checklist for the MAX8 flaps 15 data for current weight and conditions. We notified Dispatch that we had shut down and engine and were diverting to ZZZ. We finished the deferred items checklist and landed approximately 12;000lbs over weight. The CA made an excellent landing without issue. We verified with crash fire and rescue that no visible damages; smoke or abnormalities were observed on the airplane after we exited the runway and before we decided to taxi to the gate. The CA made the write up for engine limits and shut down and overweight landing. We debriefed the flight in detail; as well with the flight attendants.
During climbout of ZZZ on the Departure Procedure I was PF; we entered icing conditions around 16;000msl and turned on the TAI (Thermal Anti-Ice). We exited icing around FL200 and turned the TAI off. Then we re-entered Icing conditions again around FL230; turned on TAI; and exited icing conditions around FL260 and again turned off the TAI. Climbing through about FL280 we heard an audible bang from what we believe was an engine surge; and observed the ENG2 parameters on the ND (Navigation Display) were all warning; ENG vibration indicating 4.5; and N1 rolling back to about 60%. I continued hand flying to maintain control of the aircraft; we quickly diagnosed that we had engine parameters in exceedance of limits and ran the immediate action items for (MAX) Engine Limit or Surge or Stall QRC. The FAs immediately called us up front asking if we heard or felt the problem; I answered and told them we had an engine issue and I will call them back. We then requested priority handling and told ATC we wanted to return to ZZZ. They cleared us Direct to ZZZZZ for the ZZZZZ1 6 arrival Runway XX. We programmed that into the FMC. Turned the Autopilot on. We then ran the checklist continued in the QRH. At step 3 we still observed high ENG vibrations at 4.4-4.5 and continued to step 7 per the checklist because we had abnormal engine indication existing; which drives us to shutdown and secure the engine. At step 16 we still had high vibrations that were felt and observed so we elected to not attempt a restart. Once we had gotten a lot of the workload under control I called the FAs and gave them their briefing items. We notified Dispatch we had an engine shutdown and were returning to ZZZ. Then at the conclusion of the previous checklist; we ran the One ENG Inoperative Landing Checklist and completed all performance data required for landing. I then gave a brief PA to the passengers about the return. We executed a safe single engine overweight landing back into ZZZ. We landed about 12;000lbs overweight. We asked for the ARFF (Airport Rescue and Firefighting) team to be prepared for us upon landing and they observed no abnormal signs of the aircraft on the ground so we continued in and parked at Gate XX. I wrote up the ENG Vibrations exceedance and all ENG parameters were indicating a warning as well as the overweight landing. We thoroughly debriefed between Captain and I and also debriefed with the FAs.
More incidents for this aircraft family
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.