B737-700 flight crew reported a bird strike event during takeoff resulting in left wing leading edge and fan blade damage. The flight crew returned to the departure airport and landed.
Synopsis
B737-700 flight crew reported a bird strike event during takeoff resulting in left wing leading edge and fan blade damage. The flight crew returned to the departure airport and landed.
Narrative
Normal takeoff on Runway XXL at ZZZ. On takeoff rotation felt/heard a bang/bump. Takeoff continued. Landing Gear/Flaps retracted per normal takeoff profile. Followed LNAV PATH to clear terrain and leveled off at 17;000 ft. Initial idea between FO and Captain was a blown main gear tire. The was a slight increase in engine noise and vibration on climbout; but no abnormal engine indications. When power retarded at level off engine noise/vibration returned to normal. Immediately following rotation there was an abnormal smell in the cockpit/cabin for two to three minutes that cleared after that time. We immediately notified Tower of our expected blown tire and requested a runway inspection to confirm our suspicion. Flight Attendants called the flight deck and described the smell/noise/vibration described above. While waiting for runway inspection findings we held over the ZZZ VOR at 15;000 ft. I requested the Flight Attendants to attempt to view the flap area to do a damage assessment. They reported back that multiple Passengers witnessed multiple bird strikes.We talked to Dispatch through Company communications to coordinate a diversion to our departure point of ZZZ. Departure Control got back to us and reported 10 dead birds were discovered on/near the runway near our estimated rotation point. No aircraft tire remnants were discovered; and we determined the event was indeed a bird strike. We [requested priority handling] and requested Crash/Fire Rescue to meet the aircraft at our intended runway turn-off (High Speed Taxiway 1). We received vectors for the ILS to Runway XX at ZZZ and landed without incident. Crash/Fire Rescue met the aircraft and on Ground Control frequency we requested an inspection of the aircraft with emphasis on smoke/fire/leakage of flammable liquids etc. They discovered no such issues and we taxied under our own power to Gate XX at ZZZ. Post flight exterior inspection revealed multiple bird strikes on the left wing leading edge and #1 Engine. Multiple bent fan blades on the #1 Engine were observed. Logbook writeup was completed by the Captain. Passengers and Flight Attendants were kept aware of our progress throughout the event.Suggestions: No birds were observed prior to the bird strike. Lighting conditions were dark dusk/almost night. During the event we discussed what non-normal checklists we should/could reference. No abnormal engine indications were observed throughout the event. While debriefing the event with the First Officer we reference the Engine Limit or Surge or Stall QRH Checklist and discovered the bullet point: Abnormal engine noises are heard; possibly with airframe vibration. In retrospect; this QRH checklist should have been referenced. Further; out of an abundance of caution we could have run the One Engine Inoperative Landing QRH Checklist. This could have been appropriate even though both engines continued to operate to prepare us in the event of an engine shutdown/malfunction prior to landing.
Second reporter narrative
During rotation on Runway XXL at ZZZ the aircraft experienced a slight thud and slight settling on what I perceived at the time to be on the left side of the aircraft. Since I was flying the aircraft; I verbalized this to the Captain; and he verified the sound. The aircraft was flying normally; and both engine instruments appeared to be normal. We both initially thought it was a tire issue. The aircraft flew normally; and normal checklists were flown through 10;000 ft. To me; it seemed that one or both of the engines were very slightly louder than normal. But no air frame vibration was noted; and the engine instruments were normal. I brought this up to the Captain and he said he could not hear it at the time. Most likely because the sound was extremely slight. At this time the Flight Attendants called us; and they said they could smell something and some of the passengers may have seen some birds on takeoff. The smell dissipated quickly. We discussed this complex issue and the Captain decided to enter holding and coordinate with the Tower to have a runway sweep conducted and he then coordinate with Dispatch. We were told that approximately eight quail were found on the runway. The Captain elected to return to ZZZ. The Captain flew the landing and following landing rollout; the Fire Chief inspected the aircraft and did not notate any damage. We taxied back to the gate.Suggestions: Upon post flight debrief; we discussed the incident and determined we possibly should have run the Engine Limit; or Surge or Stall QRH Checklist. Based on one of the condition notes for abnormal engine noises
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.