 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
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.
| Attributes | |
| ACN | 1137650 |
| Time | |
| Date | 201312 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | Mixed |
| Aircraft 1 | |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Takeoff |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Turbine Engine |
| Person 1 | |
| Function | Pilot Flying First Officer |
| Experience | Flight Crew Last 90 Days 157 Flight Crew Type 5000 |
| Person 2 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Aircraft Equipment Problem Critical Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor Inflight Event / Encounter Weather / Turbulence Inflight Event / Encounter Bird / Animal |
Narrative:
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.
Original NASA ASRS Text
Title: 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.
Narrative: 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.
Data retrieved from NASA's ASRS site as of July 2013 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.