Air carrier pilot reported possible bird strike after takeoff and a compressor stall during cruise. Flight diverted to a nearby airport.
Synopsis
Air carrier pilot reported possible bird strike after takeoff and a compressor stall during cruise. Flight diverted to a nearby airport.
Narrative
We were cleared for takeoff on runway XXR with an RVR of 2000 feet. ATC did not report any known bird activity and I do not recall any reference to birds on the ATIS. Shortly after takeoff at approximately 2-300 feet in IMC conditions; we impacted what we believed to be birds. After a quick assessment of the aircraft systems; we reported the bird strike to ATC and informed them that we had no apparent aircraft damage. We continued our climb out while closely monitoring for any signs of malfunction due to the bird strike. We communicated the incident to our dispatcher via ACARS and asked them to coordinate with maintenance to ensure that they did not see any real time maintenance data that would indicate damage occurred. After collaborating with dispatch and the maintenance department we elected to continue the flight to ZZZ because there were no indications of any damage. About 50 minutes into the flight while level at FL350 we felt a violent shutter; loud bang; followed by an ENG 2 STALL ECAM message. The event was very brief and the engine returned to normal parameters after a few seconds. At this point we requested a lower altitude and began discussing a precautionary diversion to have the aircraft assessed by maintenance personnel. I contacted dispatch and coordinated a diversion to ZZZ1. I advised the flight attendants of the situation and addressed the passengers while the first officer began the diversion to ZZZ1. All engine indications remained normal but I elected to [requested assistance] as a precaution. At this point we did not know if the engine malfunction was attributed to the bird strike or not; but we wanted all parties to be prepared in the event of a reoccurrence of the engine hiccup or the emergence of another undiscovered issue linked to the bird strike. We landed normally at ZZZ1 and cancelled the [request] because all systems were functioning properly. After maintenance personnel inspected the aircraft they determined there was no apparent damage associated with the bird strikes on the aircraft or engines. They located signs of several impacts of small birds on the nose of the aircraft; just below the windscreen. There was no indication of any bird strikes on the wings; engines; or any critical areas. It appears that the engine malfunction may have been unrelated to the bird strike strike incident; but with the compounding of bird strikes and an engine irregularity; I felt it was the safest course of action to discontinue the flight to ZZZ and land at the nearest suitable airport for evaluation. Unfortunately bird activity is a persistent threat to aircraft. Due to the low visibility it was impossible for anyone to see the birds involved in this event. The only mitigation I can imagine would involve a detection or mitigation strategy that is beyond see and avoid.
Second reporter narrative
Struck birds at about 250ft in IMC conditions. Reported to ATC and dispatch and mix all indications were normal. Later in flight [requested assistance] due to compressor stall not sure if related to original incident Birds in area
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.