37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 759669 |
Time | |
Date | 200710 |
Place | |
Locale Reference | airport : zzz.airport |
State Reference | US |
Altitude | agl single value : 0 |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B737-900 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : parked |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | maintenance : technician |
ASRS Report | 759669 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | aircraft equipment problem : critical maintenance problem : improper maintenance maintenance problem : non compliance with mel non adherence : far non adherence : published procedure |
Independent Detector | other flight crewa |
Resolutory Action | other |
Consequence | other |
Factors | |
Maintenance | contributing factor : briefing performance deficiency : non compliance with legal requirements performance deficiency : logbook entry performance deficiency : installation |
Supplementary | |
Problem Areas | Aircraft Maintenance Human Performance |
Primary Problem | Maintenance Human Performance |
Narrative:
I applied MEL to #2 FMC on aircraft X. I accomplished MEL special requirements; including collaring the circuit breaker; however I did not put in the logbook that the special requirements had been accomplished; and I do not believe I performed a 100% readback with the maintenance controller involved. 3 days later I was sent back out to the same aircraft on crew call-out. The crew had found the #2 FMC computer circuit breaker had been reset and no collar present. Upon entering cockpit; found overhead switch in proper position and correct placarding present; including the special requirements block on the maintenance log correctly completed. I re-accomplished the special requirements and noted this on a maintenance discrepancy write-up form.
Original NASA ASRS Text
Title: A B737-900 FLIGHT CREW FINDS THE #2 FLIGHT MANAGEMENT COMPUTER (FMC) CIRCUIT BREAKER HAD BEEN RESET AND NO COLLAR ON CIRCUIT BREAKER. CREW NOTED THE FMC HAD BEEN DEFERRED WITH A COLLAR ON THE CIRCUIT BREAKER; AN MEL REQUIREMENT.
Narrative: I APPLIED MEL TO #2 FMC ON ACFT X. I ACCOMPLISHED MEL SPECIAL REQUIREMENTS; INCLUDING COLLARING THE CIRCUIT BREAKER; HOWEVER I DID NOT PUT IN THE LOGBOOK THAT THE SPECIAL REQUIREMENTS HAD BEEN ACCOMPLISHED; AND I DO NOT BELIEVE I PERFORMED A 100% READBACK WITH THE MAINT CTLR INVOLVED. 3 DAYS LATER I WAS SENT BACK OUT TO THE SAME ACFT ON CREW CALL-OUT. THE CREW HAD FOUND THE #2 FMC COMPUTER CIRCUIT BREAKER HAD BEEN RESET AND NO COLLAR PRESENT. UPON ENTERING COCKPIT; FOUND OVERHEAD SWITCH IN PROPER POS AND CORRECT PLACARDING PRESENT; INCLUDING THE SPECIAL REQUIREMENTS BLOCK ON THE MAINT LOG CORRECTLY COMPLETED. I RE-ACCOMPLISHED THE SPECIAL REQUIREMENTS AND NOTED THIS ON A MAINT DISCREPANCY WRITE-UP FORM.
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.