 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B767-300 flight crew felt aircraft vibration with corresponding engine vibration gauge indications. Inspection after landing revealed previous bird ingestion.
| Attributes | |
| ACN | 740458 |
| Time | |
| Date | 200706 |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : sfo.airport |
| State Reference | CA |
| Altitude | agl single value : 0 |
| Environment | |
| Flight Conditions | IMC |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | B767-300 and 300 ER |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground : takeoff roll ground : taxi |
| Route In Use | departure sid : n/s |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Experience | flight time last 90 days : 200 flight time total : 15000 flight time type : 2500 |
| ASRS Report | 740458 |
| Events | |
| Anomaly | aircraft equipment problem : critical ground encounters : animal |
| Independent Detector | aircraft equipment other aircraft equipment : engine vibration display other flight crewa |
| Resolutory Action | none taken : detected after the fact none taken : anomaly accepted |
| Supplementary | |
| Problem Areas | Environmental Factor Aircraft |
| Primary Problem | Aircraft |
Narrative:
Had a high vibration indication on taxi out with no other indications. It was showing 3.0 on the left engine. We started the takeoff and got a reading of 4.0 and felt the vibration through the rudder pedals and floor with all other engine indications normal. I felt that we should continue and contact maintenance once in cruise. We did that and reached cruise at FL350 with a maximum reading of 5.0 on the vibration gauge. We no longer felt any vibration through the floor or pedals and after consulting maintenance we elected to continue to destination. Everything was normal until the power reduction on descent where the vibration reappeared on the pedals and floor. We kept power changes to a minimum and landed. We wrote up the problem and had maintenance greet us at the gate. There they found 3 fan blades bent due to a bird strike with evidence of the bird in various parts of the engine. We do not know where we encountered the bird. We never felt the bird strike or else we would have mentioned it.
Original NASA ASRS Text
Title: B767-300 FLT CREW FELT ACFT VIBRATION WITH CORRESPONDING ENG VIBRATION GAUGE INDICATIONS. INSPECTION AFTER LNDG REVEALED PREVIOUS BIRD INGESTION.
Narrative: HAD A HIGH VIBRATION INDICATION ON TAXI OUT WITH NO OTHER INDICATIONS. IT WAS SHOWING 3.0 ON THE L ENG. WE STARTED THE TKOF AND GOT A READING OF 4.0 AND FELT THE VIBRATION THROUGH THE RUDDER PEDALS AND FLOOR WITH ALL OTHER ENG INDICATIONS NORMAL. I FELT THAT WE SHOULD CONTINUE AND CONTACT MAINT ONCE IN CRUISE. WE DID THAT AND REACHED CRUISE AT FL350 WITH A MAX READING OF 5.0 ON THE VIBRATION GAUGE. WE NO LONGER FELT ANY VIBRATION THROUGH THE FLOOR OR PEDALS AND AFTER CONSULTING MAINT WE ELECTED TO CONTINUE TO DEST. EVERYTHING WAS NORMAL UNTIL THE PWR REDUCTION ON DSCNT WHERE THE VIBRATION REAPPEARED ON THE PEDALS AND FLOOR. WE KEPT PWR CHANGES TO A MINIMUM AND LANDED. WE WROTE UP THE PROB AND HAD MAINT GREET US AT THE GATE. THERE THEY FOUND 3 FAN BLADES BENT DUE TO A BIRD STRIKE WITH EVIDENCE OF THE BIRD IN VARIOUS PARTS OF THE ENG. WE DO NOT KNOW WHERE WE ENCOUNTERED THE BIRD. WE NEVER FELT THE BIRD STRIKE OR ELSE WE WOULD HAVE MENTIONED IT.
Data retrieved from NASA's ASRS site as of January 2009 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.