B737-300
Flight Crew Last 90 Days 157; Flight Crew Type 5000
Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Inflight Event / Encounter Bird / Animal; Inflight Event / Encounter Weather / Turbulence
Air Traffic Control Provided Assistance; Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; General Declared Emergency
Aircraft; Environment - Non Weather Related
On departure; just as we were bringing up the flaps; I saw a bird go by my window followed by a very loud bang. Then the Number 2 Engine began a heavy vibration. It seemed to still be turning; but was shaking badly. The EGT began to rapidly rise. At the same time; the smell of burnt feathers and smoke began to come into the cabin. I pulled the engine back to idle. After a quick conversation with the Captain; we decided we had hit a bird and were quickly losing the engine. We decided to shut down Number 2 in accordance with the Engine Fire/Seizure/Separation/Severe Damage Checklist in the QRH. We followed Company procedures confirming each move as we proceeded through the immediate action items. We were able to remain VMC and keep the airport in sight. We ran landing data and [determined we] were able to land on either XXR or XXL. Since the Number 1 Engine had an MEL on the thrust reverser; we elected to land on the longer runway (XXL). We configured for a Flaps 15 landing. The aircraft began to rumble again; but the landing was fairly uneventful. Fire crews met the aircraft and reported that the engine appeared to have shut down fine and no evidence of fire was visible. We elected to leave the flaps down since we were unsure how much damage had been done to the surface of the aircraft. After getting to the gate and deplaning passengers; we went outside to view the damage. It had; indeed; suffered a catastrophic hit and lost multiple fan blades. The blades that remained were severely damaged. Also; inboard of the Number 2 Engine was a hole the size of a softball which probably explained the rumbling on final.I imagine it was geese that we hit. After landing; we saw a 'V' formation of them flying overhead. Bird mitigation is probably the best way to prevent this.
Upon placing the start level to cutoff; the EGT began to drop. At no time did it overtemp or did we get a fire indication. The N1 and N2 went to zero. The flight attendants rang up and said it was getting smoky in the cabin. We notified Departure that we were an emergency and would be returning to ZZZ landing on Runway XXR. They asked for fuel onboard and souls. I responded with two hours and standby on the count. Due to overcast and icing conditions; we stayed at 2;500 MSL to keep sight of the field. Upon inspection of the aircraft; it appeared to be multiple birds with damage to the leading edge and all the fan blades of the number two engine of which some were missing. The leading edge of the right wing had a 12 to 14 inch hole in it. There was an eight inch plus gap on the outside of the engine cowling where it appears a blade had gone through. A write-up was placed in the logbook and the aircraft was impounded until the NTSB could assess the damage.
When birds; most likely geese; struck and disabled the right engine of a B737-300 shortly after takeoff the flight crew declared an emergency; shut down the engine; and returned safely to their departure airport. An after flight inspection divulged extensive damage to the engine fan blades and cowl; plus a large hole in the leading edge of the wing leading to the supposition of; likely; multiple bird strikes.