Narrative:

On aug/xa/00 at about XA00, I made a maintenance entry for someone in our computer. We had aircraft xyz on the ground and during the engine run, fluid was noticed coming out of the #2 engine drain. I generated a write-up in the computer and xo xyo and I opened up the #2 engine to see what was leaking. No visible external leaks were found and the drain line was idented as coming from the strut. The leak was 24 drops per min and hydraulic fluid. Xo xyo got in contact with maintenance controller and was given the ok to defer this item, ok to defer per maintenance manual. Xo xyo was a mechanic who flew in to help ZZZ with the flts. As I stood there listening to the conversation xo xyo was having with maintenance controller, I was also on another computer working on another flight. After xo xyo got off the phone, he looked up the reference maintenance controller gave on the computer. He then proceeded to sign on to the computer terminal next to me. He couldn't get signed on to the computer, so I said we could use the one I was signed onto. I entered the information in the computer and used word for word the maintenance controller's name and the reference that was given to xo xyo. Later that day, I was contacted by another maintenance controller and he told me that the defer item was not a good defer and shouldn't have been deferred out. I told him maintenance controller's name. He said he couldn't find anything in his log. We are allowed to make entries into the computers for another mechanic, but should only enter 1 min for time. This is to show that you are only entering the information in the computer and the other person who is charged an hour is the person who did the actual work. I am sending this report because I believe the dispatch of aircraft xyz was not correct. I also may have done the entry into the computer without reflecting my 1 min time and xo xyo 1 hour time. This is to avoid being held responsible for this deferred item.

Related reports:

Google
 

Original NASA ASRS Text

Title: A B767-200 WAS DISPATCHED IN NON COMPLIANCE WITH A 24 DROP PER MIN HYD LEAK DEFERRED IN CONFLICT WITH THE MAINT MANUAL LIMITS.

Narrative: ON AUG/XA/00 AT ABOUT XA00, I MADE A MAINT ENTRY FOR SOMEONE IN OUR COMPUTER. WE HAD ACFT XYZ ON THE GND AND DURING THE ENG RUN, FLUID WAS NOTICED COMING OUT OF THE #2 ENG DRAIN. I GENERATED A WRITE-UP IN THE COMPUTER AND XO XYO AND I OPENED UP THE #2 ENG TO SEE WHAT WAS LEAKING. NO VISIBLE EXTERNAL LEAKS WERE FOUND AND THE DRAIN LINE WAS IDENTED AS COMING FROM THE STRUT. THE LEAK WAS 24 DROPS PER MIN AND HYD FLUID. XO XYO GOT IN CONTACT WITH MAINT CTLR AND WAS GIVEN THE OK TO DEFER THIS ITEM, OK TO DEFER PER MAINT MANUAL. XO XYO WAS A MECH WHO FLEW IN TO HELP ZZZ WITH THE FLTS. AS I STOOD THERE LISTENING TO THE CONVERSATION XO XYO WAS HAVING WITH MAINT CTLR, I WAS ALSO ON ANOTHER COMPUTER WORKING ON ANOTHER FLT. AFTER XO XYO GOT OFF THE PHONE, HE LOOKED UP THE REF MAINT CTLR GAVE ON THE COMPUTER. HE THEN PROCEEDED TO SIGN ON TO THE COMPUTER TERMINAL NEXT TO ME. HE COULDN'T GET SIGNED ON TO THE COMPUTER, SO I SAID WE COULD USE THE ONE I WAS SIGNED ONTO. I ENTERED THE INFO IN THE COMPUTER AND USED WORD FOR WORD THE MAINT CTLR'S NAME AND THE REF THAT WAS GIVEN TO XO XYO. LATER THAT DAY, I WAS CONTACTED BY ANOTHER MAINT CTLR AND HE TOLD ME THAT THE DEFER ITEM WAS NOT A GOOD DEFER AND SHOULDN'T HAVE BEEN DEFERRED OUT. I TOLD HIM MAINT CTLR'S NAME. HE SAID HE COULDN'T FIND ANYTHING IN HIS LOG. WE ARE ALLOWED TO MAKE ENTRIES INTO THE COMPUTERS FOR ANOTHER MECH, BUT SHOULD ONLY ENTER 1 MIN FOR TIME. THIS IS TO SHOW THAT YOU ARE ONLY ENTERING THE INFO IN THE COMPUTER AND THE OTHER PERSON WHO IS CHARGED AN HR IS THE PERSON WHO DID THE ACTUAL WORK. I AM SENDING THIS RPT BECAUSE I BELIEVE THE DISPATCH OF ACFT XYZ WAS NOT CORRECT. I ALSO MAY HAVE DONE THE ENTRY INTO THE COMPUTER WITHOUT REFLECTING MY 1 MIN TIME AND XO XYO 1 HR TIME. THIS IS TO AVOID BEING HELD RESPONSIBLE FOR THIS DEFERRED ITEM.

Data retrieved from NASA's ASRS site as of July 2007 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.