Narrative:

While pre-flighting the airplane I heard a distinct sound; somewhat similar to a socket wrench ratchet returning. This sound start immediately as soon as I started turning the rudder trim knob and it continued until I reached 7 units of right rudder trim. After passing 7 units of right trim; the noise subsided and did not return when I was checking the trim; although it did return later in the day with several different mechanics checking the trim. The trim operated smoothly; full travel from stop-to-stop with no stiffness or binding noted. My major concern was over what caused the initial noise we heard and would the cause of the noise eventually cause trouble in the normal operation of the rudder trim. Maintenance was summoned and an entry with the maintenance discrepancy was entered into the maintenance logbook. Initially the local mechanic didn't act as if he wanted to work the problem and then he got maintenance control involved. Maintenance control decided to sign off the logbook discrepancy since there was no prior history within the past 30 days and since they were not able to duplicate the noise we heard. I was not happy with this course of action as we still had not answered the question of what caused the noise and why was the noise present in the first place. After I expressed my concerns; maintenance must have decided the prudent thing to do would be to troubleshoot in hopes of learning what was causing the noise we had once heard. The plane was OTS for nearly 12 hours before maintenance discovered the source of the noise. Turns out there was a bundle of capped and disconnected wires (from the auxiliary fuel tanks I'm assuming) that had come untied and they were rubbing against parts of the rudder trim as it turned. My major concern is that when a write-up is entered on a flight control problem such as the rudder trim; maintenance should always do a thorough troubleshoot until the source of the problem is positively idented and corrected. We can't afford to take chances with flight control problems. Maintenance needs to properly troubleshoot when a maintenance discrepancy is entered into the maintenance log rather than just signing it off with no troubleshoot.

Google
 

Original NASA ASRS Text

Title: FOLLOWING UNUSUAL PREFLT CHECK OR RUDDER TRIM; CAPT OF MD80 PREVAILS UPON MAINT FOR COMPREHENSIVE TROUBLESHOOTING.

Narrative: WHILE PRE-FLIGHTING THE AIRPLANE I HEARD A DISTINCT SOUND; SOMEWHAT SIMILAR TO A SOCKET WRENCH RATCHET RETURNING. THIS SOUND START IMMEDIATELY AS SOON AS I STARTED TURNING THE RUDDER TRIM KNOB AND IT CONTINUED UNTIL I REACHED 7 UNITS OF R RUDDER TRIM. AFTER PASSING 7 UNITS OF R TRIM; THE NOISE SUBSIDED AND DID NOT RETURN WHEN I WAS CHKING THE TRIM; ALTHOUGH IT DID RETURN LATER IN THE DAY WITH SEVERAL DIFFERENT MECHS CHKING THE TRIM. THE TRIM OPERATED SMOOTHLY; FULL TRAVEL FROM STOP-TO-STOP WITH NO STIFFNESS OR BINDING NOTED. MY MAJOR CONCERN WAS OVER WHAT CAUSED THE INITIAL NOISE WE HEARD AND WOULD THE CAUSE OF THE NOISE EVENTUALLY CAUSE TROUBLE IN THE NORMAL OP OF THE RUDDER TRIM. MAINT WAS SUMMONED AND AN ENTRY WITH THE MAINT DISCREPANCY WAS ENTERED INTO THE MAINT LOGBOOK. INITIALLY THE LCL MECH DIDN'T ACT AS IF HE WANTED TO WORK THE PROB AND THEN HE GOT MAINT CTL INVOLVED. MAINT CTL DECIDED TO SIGN OFF THE LOGBOOK DISCREPANCY SINCE THERE WAS NO PRIOR HISTORY WITHIN THE PAST 30 DAYS AND SINCE THEY WERE NOT ABLE TO DUPLICATE THE NOISE WE HEARD. I WAS NOT HAPPY WITH THIS COURSE OF ACTION AS WE STILL HAD NOT ANSWERED THE QUESTION OF WHAT CAUSED THE NOISE AND WHY WAS THE NOISE PRESENT IN THE FIRST PLACE. AFTER I EXPRESSED MY CONCERNS; MAINT MUST HAVE DECIDED THE PRUDENT THING TO DO WOULD BE TO TROUBLESHOOT IN HOPES OF LEARNING WHAT WAS CAUSING THE NOISE WE HAD ONCE HEARD. THE PLANE WAS OTS FOR NEARLY 12 HRS BEFORE MAINT DISCOVERED THE SOURCE OF THE NOISE. TURNS OUT THERE WAS A BUNDLE OF CAPPED AND DISCONNECTED WIRES (FROM THE AUX FUEL TANKS I'M ASSUMING) THAT HAD COME UNTIED AND THEY WERE RUBBING AGAINST PARTS OF THE RUDDER TRIM AS IT TURNED. MY MAJOR CONCERN IS THAT WHEN A WRITE-UP IS ENTERED ON A FLT CTL PROB SUCH AS THE RUDDER TRIM; MAINT SHOULD ALWAYS DO A THOROUGH TROUBLESHOOT UNTIL THE SOURCE OF THE PROB IS POSITIVELY IDENTED AND CORRECTED. WE CAN'T AFFORD TO TAKE CHANCES WITH FLT CTL PROBS. MAINT NEEDS TO PROPERLY TROUBLESHOOT WHEN A MAINT DISCREPANCY IS ENTERED INTO THE MAINT LOG RATHER THAN JUST SIGNING IT OFF WITH NO TROUBLESHOOT.

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.