A319 flight crew reported a possible bird strike during takeoff required a return to the departure airport.
Synopsis
A319 flight crew reported a possible bird strike during takeoff required a return to the departure airport.
Narrative
We performed a routine takeoff from Runway XXR at ZZZ with flaps set to 2 and a reduced flex temperature of 63°C in VFR conditions. Shortly after liftoff; just after retracting the landing gear and with the autopilot still disengaged at around 200 feet AGL; we heard a loud banging noise. This was followed by a noticeable yaw to the left and a drop in the EPR of engine 1; from approximately 1.4 to 1.2. Within a few seconds; the EPR on engine 1 returned to normal on its own; matching engine 2. All other engine parameters remained stable; and no ECAM alerts were displayed. However; we detected a strong odor in the cockpit; similar to burning hair; and suspected a bird strike. We immediately [requested priority handling] with the Tower and requested to return to ZZZ as a precaution. After a quick handoff to departure control; we requested Runway XXC and extended our downwind leg to review the overweight landing checklist and notify dispatch. Shortly after; we were vectored for a visual approach to Runway XXC; where we landed without further issues and taxied to the gate.
Second reporter narrative
The event was during flight ZZZ to ZZZ1. I was performing the duties of pilot monitoring. Pushback and taxi out proceeded uneventfully. On takeoff; everything was initially normal. After the CA rotated he asked for gear up; which I did. Shortly after; we heard a loud bang and felt a yawing motion toward the #1 engine. This occurred approximately at 200 ft AGL. Additionally; the CA and I both noticed a strong odor. It resembled a burning type smell; and we concluded we had most likely hit a large bird. We noticed at this time that we had partially lost power on the #1 engine; but that it had fully recovered after a few seconds and was showing normal indications. We continued the climb; and agreed that due to the strong nature of the yaw; the noise we heard; as well as the odor; that it made sense to return to ZZZ. We suspected there may have been further damage and did not think it was safe to continue to ZZZ1. At this time; I took controls and handled the ATC communication while the CA coordinated with dispatch and the FAs. He also made a PA to the PAX and helped set the plane up for a return at ZZZ. We [requested priority handling] and the CA landed back at ZZZ. We were escorted back to the gate where we wrote the plane up for overweight landing as well as a bird strike. Maintenance confirmed that the #1 engine was full of large feathers and it had been a strike shortly after takeoff.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.