Air carrier flight crew reported bird strike on takeoff climb. Returned to departure airport and landed uneventfully.

Date: 2023-09 · Aircraft: B737-700 · Phase: climb

Anomalies: aircraft-equipment-problem-critical|inflight-event-encounter-bird-animal

Synopsis

Air carrier flight crew reported bird strike on takeoff climb. Returned to departure airport and landed uneventfully.

Narrative

While operating Flight ZZZ-ZZZ1 we encountered a bird strike on the Number 1 Engine during initial climb. We push off the gate on time and proceeded to taxi to Runway XXR. Upon reaching the runway; we completed before takeoff checklist and took off at (XA00). On climb out approximately 500 ft. MSL we hit a large bird on the Number #1 Engine. I noticed the roll back on the N1 with about 5 to 6 compressor stalls. Captain immediately reduced power to about 60% N1 and engine continue to operate normally. ATC was busy talking so we squawked and were able to advise ATC and requested vectors back for landing. We discussed our options including running the engine failure and/or severe damage checklist but since the engine was operating; we decided not to. We did run performance numbers for a Flaps 15 landing as a precaution. We requested about a 10-15 mile final to allow us to string the approach and do the necessary briefings including the overweight landing and brake cooling info once on the ground. Approach and landing were uneventful. We exited the runway and had the Fire Department Crew inspect the engine before proceeding to the gate.

Second reporter narrative

We took off on Runway XXR at ZZZ. At about 500' AGL as we were making a turn to our assigned heading of 210; we took a bird in the #1 Engine. We heard a loud thud; then the #1 Engine rolled back momentarily; then had 4 to 5 compressor stalls; I thought we were going to lose it; so I reduced power to about 60% N1 and the compressor stalls ceased. We continued a turn; Tower was busy; so we squawked on the transponder. When he asked; we told Tower what happened; was [requested priority handling]; and would be returning. He gave us an initial heading and altitude. The #1 Engine continued to run smooth at the reduced power. There was a burnt burn smell in cockpit and cabin. The First Officer and I discussed our options and decided not to shut it down. We continued our vectors for about a 15-mile final. We ran landing data for a Flaps 15 in case the engine decided later to quit.We made a normal touchdown and stopped momentarily for CFR (Crash Fire Rescue) to do a quick visual inspection. They confirmed debris or stains on engine cowl. After two minutes or so we shut down #1 Engine; then continued to the gate. We ran brake cooling data while taxing to gate and it said MQTW not exceeded. At the gate we notified Dispatch; Maintenance Control; Dispatch Manager; and ZZZ Tower had requested a call. Logbook entries were made for engine; and overweight landing.Suggestion: Paint aircraft like an owl.

More incidents for this aircraft family →

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