Air Carrier flight crew reported engine number 2 failure during cruise. The flight crew diverted to a suitable airport where a safe landing was executed.

2022-10 · NASA ASRS report 1944142

Date: 2022-10 · Aircraft: EMB ERJ 145 ER/LR · Phase: cruise

Anomalies: aircraft-equipment-problem-critical|deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-published-material-policy

Synopsis

Air Carrier flight crew reported engine number 2 failure during cruise. The flight crew diverted to a suitable airport where a safe landing was executed.

Narrative

Flight began normally in ZZZ1 and operated normally in cruise. We had just initiated a direct turn direct ZZZZZ for the ZZZZZ1 1 arrival in ZZZ2. As we made the turn we heard a loud bang. It was immediately identified that the #2 engine had failed. No N2; oil pressure; engine 2 out EICAS message; etc. I was the pilot flying. The airplane began to yaw when the engine failed. I disconnected the Autopilot and maintained positive aircraft control. The Captain; pilot monitoring; transmitted a [request for priority handling] call to ATC and began using the QRH to find drift down altitude via the chart. The pressurization continued to function normally. We agreed to fly to ZZZ for the landing. It was the nearest suitable. Once we established with ATC that we needed to go to ZZZ we received vectors and altitudes and what runway to expect. ATC arranged for [airport rescue and firefighting] vehicles to be ready in ZZZ. Once we got to an appropriate point in the QRH the captain gave the flight attendant a landing briefing. Then briefed the passengers what was happening and the plan. As we descended we armed the Autopilot again. Captain completed the QRH action items and prepared us for the RNAV XXL approach. The descent to landing was successful. No passengers or crew were injured during the event. We agreed it was safe to taxi the airplane to the gate. [Airport] vehicles followed and were in contact with us; as well as Tower.

Second reporter narrative

Flight was a normally operated flight between ZZZ1 and ZZZ2. At a cruising altitude of 28;000 ft. in cruise at approximately 280 kts. and Autopilot engaged after initiating a turn to ZZZZZ to begin the ZZZZZ1 Arrival into ZZZ2 the First Officer (FO) (pilot flying (PF)) and I (pilot monitoring (PM)) heard a loud bang and promptly witnessed the failure and roll back of engine #2. The aircraft began to bank right and I immediately called power loss lost and asked the FO to turn off the Autopilot and fly the aircraft to regain positive control. The aircraft never banked more than 15 degrees and the FO promptly took control and brought us to straight and level. I then went on the radio and [requested priority handling to suitable airport] and would be asking for a decent and heading shortly but to please stand by. With the aircraft under control and the FO hand flying I told him I would get a speed and altitude from the drift down table. At this point the EICAS message Eng Out (2) and associated messages were displayed. QRH drift down at 45;000 lbs called for a speed of 166 and alt of 17000. At this point I set 17;000 and told the FO we would defend when reaching 166 kts. He agreed with that and I told ATC we needed a descent to 17000 and I asked for an initial heading towards ZZZ3 due to our current location. At this point I went to QRH 6.12 engine out. We ran the checklist to electing to secure the engine and land at nearest suitable airport. As a crew we agreed not to attempt to restart because of a lack of N2 and no oil pressure. After completing QRH section; I messaged dispatch telling them we were going to ZZZ3 or ZZZ. I then made sure the FO was okay beginning our drift down descent and he was very good and handling the aircraft well.I called the FA to ascertain the status of the passengers; her and to give her a landing briefing. She copied and repeated back. I made a PA telling the passengers the situation and that we would be landing at ZZZ out of an abundance to caution and safety and asked they remain seated until we were safely on the ground. The FA performed her duties and called me back telling the cabin was secured. We as a crew decided to go to ZZZ due to familiarity with the field as opposed to ZZZ3 which neither of us operated into before. Informing ATC they gave us vectors and made sure [airport services] were waiting upon arrival. We [completed appropriate landing data]; using the data cards and performance section in the QRH for our numbers needed to land. We ran all applicable checklist and the FO executed a perfect landing. We elected to turn off the runway and stop there. We ran the after landing checklist and evaluated the status of the aircraft and decided it was safe to taxi into the gate which was nonevent. Passengers were all okay and deplaned normally. As a crew I feel we handled the situation professionally with due care; resulting in a safe landing.

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

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

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.

Which aircraft types can I filter by?

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.

Is FlightFinder free to use?

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.

Where does the route data come from?

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.