A320 flight crew reported an engine failure and a return to the departure airport
Synopsis
A320 flight crew reported an engine failure and a return to the departure airport
Narrative
Captain was pilot flying; and as we were climbing above approximately 5100 ft. indicated altitude and in a left turn to the North; a loud noise was heard in combination with a jolt and yaw to the left. An ENG 1 stall ECAM warning subsequently appeared but quickly disappeared. The next ECAM to appear was the ENG 1 FAIL warning. During this period I observed a vapor briefly enter the cockpit via the vents above the windows - it quickly dissipated and was not observed again. Captain called for ECAM actions after establishing positive control; and I ran through the ECAM procedure. There were no applicable OEBs (Operational Engineering Bulletins). We determined that damage had occurred; and that fuel was not leaking. We reviewed the affected systems pages; and after ECAM actions were complete we verified that all checklists were completed and that there were no resets or relights possible prior to reviewing the status page. We also determined that we would be overweight for landing. We considered reviewing the comm procedures but determined that that activity was not a priority. I resumed comms at this point briefly before taking control while the Captain set up for; and briefed; the approach. They then took back control and comms so that I could run the landing distance assessment. After I completed that; I resumed pilot monitoring duties for the remainder of the flight. Captain executed the RNAV XXL approach to land smoothly and uneventfully; the landing was very soft. We stopped on the runway and waited for Airport Rescue and Firefighting (ARFF) to approach the airplane and conduct a visual inspection. ARFF communicated with us directly on Tower frequency and told us there were no indications of fire or leaking fluids. We taxied to the ramp and gate with ARFF on the trail as a precaution.
Second reporter narrative
The flight originated in ZZZ with destination to ZZZ1 and additionally was a training event OE new student. We experienced a ground delay due to smoke in ZZZ1 and ATC informed us of an ETD of XA:41. Maintenance was in the process of removing MELs 22-XX-XX-X and 24-XX-XX-XX. We waited for the log book to arrive. Once the log book arrived we started our push and taxi single engine to Runway XXR. Once we confirmed with ATC there were no more delays to ZZZ1 we started the number 2 engine. I was the pilot flying. We take off right at wheel up time and in our climb to our assigned altitude 7000 ft. While climbing through 5100 ft. we heard a very loud boom on the left side of the aircraft and a yaw to the left. ECAM warning was ENG 1 stall followed by ENG fail. I ask for ECAM actions. We communicated the issue to ATC. We established positive control. The First Officer ran the associated ECAM procedures. We confirmed the engine was damaged; reviewed status pages; OEBs (Operational Engineering Bulletins); mention the overweight landing and comm procedures.Set up for the approach Runway XYR but ATC offered us Runway RNAV XYL. I set up for that approach transfer controls to the First Officer and briefed the approach. I talked to our Flight Attendants and made an announcement to the passengers. I took control of the aircraft; got vectors and cleared the approach. We verified the Airport Rescue and Firefighting (ARFF) and equipment was standing by on the runway. Once we landed I stopped the aircraft and called Flight Attendants to stations and verify with ARFF that the aircraft didn't have any indication of smoke or fluids of any type. I made the PA remain seated announcement three times and we were clear to taxi off the runway. We taxied to gate and no injuries or damages were experienced besides the engine failure. I added two log book entries; one for engine fail and one for overweight landing. Considering the First Officer was only their fourth trip on OE their performance was outstanding. The cabin crew was also outstanding at communicating and maintaining passengers safe and calm.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.