 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B737-300 possible bird strike was reported by the crew. Technician accomplished bird strike inspection and found no evidence of bird strike. Technician failed to note logbook with findings. No bird strike found.
| Attributes | |
| ACN | 672557 |
| Time | |
| Date | 200509 |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : zzz.airport |
| State Reference | US |
| Altitude | agl single value : 0 |
| Aircraft 1 | |
| Controlling Facilities | artcc : zhn.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground : maintenance ground : pushback |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | maintenance : technician |
| Qualification | technician : airframe technician : powerplant |
| ASRS Report | 672557 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | maintenance : technician |
| Events | |
| Anomaly | aircraft equipment problem : less severe maintenance problem : improper documentation non adherence : far non adherence : published procedure |
| Independent Detector | other other : 3 |
| Resolutory Action | none taken : detected after the fact |
| Consequence | other other |
| Factors | |
| Maintenance | performance deficiency : logbook entry performance deficiency : non compliance with legal requirements |
| Supplementary | |
| Problem Areas | Maintenance Human Performance Chart Or Publication Aircraft |
| Primary Problem | Maintenance Human Performance |
Narrative:
I was called to aircraft for possible bird strike. The captain indicated they had an odor of burnt bird for a very brief moment after takeoff. They did not hear; feel; or see any indication of a bird strike. I complied with a bird strike inspection and found no evidence of a bird strike anywhere on the aircraft fuselage; engines; or wings. No evidence anywhere on the aircraft was found; so I signed the logbook as complied with bird strike inspection per maintenance manual 05-51-37. The mistake I made was in my signoff -- I did not indicate there was no evidence of the bird going through the engine core and no damage was noted.
Original NASA ASRS Text
Title: A B737-300 POSSIBLE BIRD STRIKE WAS RPTED BY THE CREW. TECHNICIAN ACCOMPLISHED BIRD STRIKE INSPECTION AND FOUND NO EVIDENCE OF BIRD STRIKE. TECHNICIAN FAILED TO NOTE LOGBOOK WITH FINDINGS. NO BIRD STRIKE FOUND.
Narrative: I WAS CALLED TO ACFT FOR POSSIBLE BIRD STRIKE. THE CAPT INDICATED THEY HAD AN ODOR OF BURNT BIRD FOR A VERY BRIEF MOMENT AFTER TKOF. THEY DID NOT HEAR; FEEL; OR SEE ANY INDICATION OF A BIRD STRIKE. I COMPLIED WITH A BIRD STRIKE INSPECTION AND FOUND NO EVIDENCE OF A BIRD STRIKE ANYWHERE ON THE ACFT FUSELAGE; ENGS; OR WINGS. NO EVIDENCE ANYWHERE ON THE ACFT WAS FOUND; SO I SIGNED THE LOGBOOK AS COMPLIED WITH BIRD STRIKE INSPECTION PER MAINT MANUAL 05-51-37. THE MISTAKE I MADE WAS IN MY SIGNOFF -- I DID NOT INDICATE THERE WAS NO EVIDENCE OF THE BIRD GOING THROUGH THE ENG CORE AND NO DAMAGE WAS NOTED.
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.