Narrative:

On the morning of dec/xa/01 I was called to the aircraft by ramp personnel. They found a cargo door side lock that wouldn't lock. I looked at it and decided the lock needed to be replaced. The lock would lock into place with some effort. I then called maintenance to defer the lock as the plane was loaded and ready to go. After 1 min or so, my supervisor came over the radio and said just to let it go without deferring. I reluctantly said ok. So, I signed the logbook off as 'entered in error,' to keep the aircraft from further delay. I feel this lock needed to be deferred so that is why I'm bringing this to your attention. Also, the way I signed the logbook off didn't really set well with me either. So, to keep from possible enforcement action from the FAA, I am reporting this incident.

Google
 

Original NASA ASRS Text

Title: B727-200 MECH WAS INSTRUCTED TO CLR A LOGBOOK WRITE-UP REGARDING A MALFUNCTIONING CARGO DOOR SLIDE LOCK BY THE COMPANY MAINT SUPVR.

Narrative: ON THE MORNING OF DEC/XA/01 I WAS CALLED TO THE ACFT BY RAMP PERSONNEL. THEY FOUND A CARGO DOOR SIDE LOCK THAT WOULDN'T LOCK. I LOOKED AT IT AND DECIDED THE LOCK NEEDED TO BE REPLACED. THE LOCK WOULD LOCK INTO PLACE WITH SOME EFFORT. I THEN CALLED MAINT TO DEFER THE LOCK AS THE PLANE WAS LOADED AND READY TO GO. AFTER 1 MIN OR SO, MY SUPVR CAME OVER THE RADIO AND SAID JUST TO LET IT GO WITHOUT DEFERRING. I RELUCTANTLY SAID OK. SO, I SIGNED THE LOGBOOK OFF AS 'ENTERED IN ERROR,' TO KEEP THE ACFT FROM FURTHER DELAY. I FEEL THIS LOCK NEEDED TO BE DEFERRED SO THAT IS WHY I'M BRINGING THIS TO YOUR ATTN. ALSO, THE WAY I SIGNED THE LOGBOOK OFF DIDN'T REALLY SET WELL WITH ME EITHER. SO, TO KEEP FROM POSSIBLE ENFORCEMENT ACTION FROM THE FAA, I AM RPTING THIS INCIDENT.

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.