 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 encountered birds after takeoff and experienced number 1 engine vibration. Flight crew elected to return where they found damaged blades.
| Attributes | |
| ACN | 1065365 |
| Time | |
| Date | 201301 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737-700 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Climb |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Fan Blade |
| Person 1 | |
| Function | First Officer |
| Experience | Flight Crew Last 90 Days 123 Flight Crew Type 6000 |
| Events | |
| Anomaly | Aircraft Equipment Problem Critical Inflight Event / Encounter Bird / Animal |
Narrative:
Flock of medium white birds flew in front of aircraft at liftoff; and I immediately heard loud groan/whine from engine number 1. All engine indications were normal except the number 1 engine vibration monitor indicated 1.5 vs .5 for engine number 2.we notified ATC of a likely bird strike; and first officer continued flying aircraft with vectors around field as a precaution.we accomplished the QRH 'immediate action' items for engine limit/surge/stall due to the abnormal engine noise. Upon reducing power on the number 1 engine; the noise was reduced. We completed the QRH procedure and elected to leave the affected engine running since no abnormal indications other than noise. Captain coordinated with dispatch and maintenance who noted that since vibrations not greater than 4.0; we could continue. We did not like the noise and elected to return as a precaution to prevent further damage. We computed landing data and flew an uneventful approach and landing to the longer runway. We shut down the affected engine after one minute and returned to the gate. Damage to the number 1 engine (3 blades) was noted on post-flight inspection as well as bird strikes on right landing gear and underside of right elevator. We coordinated with dispatch; scheduling; maintenance in ZZZ1 and the ZZZ tower for necessary repair and reporting.
Original NASA ASRS Text
Title: B737 encountered birds after takeoff and experienced Number 1 Engine vibration. Flight crew elected to return where they found damaged blades.
Narrative: Flock of medium white birds flew in front of aircraft at liftoff; and I immediately heard loud groan/whine from Engine Number 1. All engine indications were normal except the Number 1 Engine vibration monitor indicated 1.5 vs .5 for Engine Number 2.We notified ATC of a likely bird strike; and First Officer continued flying aircraft with vectors around field as a precaution.We accomplished the QRH 'Immediate Action' items for engine limit/surge/stall due to the abnormal engine noise. Upon reducing power on the Number 1 Engine; the noise was reduced. We completed the QRH procedure and elected to leave the affected engine running since no abnormal indications other than noise. Captain coordinated with Dispatch and Maintenance who noted that since vibrations not greater than 4.0; we could continue. We did not like the noise and elected to return as a precaution to prevent further damage. We computed landing data and flew an uneventful approach and landing to the longer runway. We shut down the affected engine after one minute and returned to the gate. Damage to the Number 1 Engine (3 blades) was noted on post-flight inspection as well as bird strikes on right landing gear and underside of right elevator. We coordinated with Dispatch; Scheduling; Maintenance in ZZZ1 and the ZZZ Tower for necessary repair and reporting.
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.