AN MD90 WAS DISPATCHED IN NON-COMPLIANCE WITH AN INCOMPLETE LOGBOOK SIGN OFF BY A CONTRACT MECH.
Synopsis
AN MD90 WAS DISPATCHED IN NON-COMPLIANCE WITH AN INCOMPLETE LOGBOOK SIGN OFF BY A CONTRACT MECH.
Narrative
WE HAD A L PNEUMATIC SYS FAULT ON TKOF OUT OF SLC ENRTE TO ZZZ. CONTINUED ON TO ZZZ WHERE WE LEFT THE PLANE FOR OUR LAYOVER. WE WERE TAKING THE SAME PLANE OUT THE NEXT MORNING. THE CAPT CALLED IN THE MORNING TO MAKE SURE THE ACFT HAD BEEN FIXED AND WAS READY TO GO. WHEN WE ARRIVED AT THE ACFT WE WERE GIVEN A MESSAGE FROM MAINT TO RUN ACFT ENGS BEFORE DEP. UNDER OUR LOGBOOK ENTRY THAT WE MADE THE CONTRACT MECH HAD SIGNED 'CLRED FAULT; RE-RACKED CTLR; NEEDS ENG RUN. HE HAD SIGNED UNDERNEATH WITH HIS A/P NUMBER AND SIGNATURE. WE RAN ENGS BEFORE DISPATCH AND EVERYTHING WAS GOOD. ONCE AIRBORNE WE REALIZED WE PROBABLY NEEDED TO ENTER OUR ENG RUN INTO THE LOGBOOK. WE CONSULTED OUR FOM (FLT OPS MANUAL) AND FOUND THE CONTRACT MECH HAD NOT PROPERLY SIGNED OFF THE LOGBOOK; BY NOT SIGNING IN THE 'MECH SIGNATURE' BLOCK OR 'CORRECTIVE ACTION BLOCK.' UPON ARRIVING IN DFW WE CALLED OUT MAINT OUT TO MAKE SURE OUR LOGBOOK ENTRY WAS CORRECT. THEY THEN INFORMED US MAINT SHOULD HAVE OBSERVED THE ENG RUN BEFORE SIGNING LOGBOOK.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.