A B737-200 WAS DISPATCHED WITHOUT A RECONFIGURATION LISTED IN THE LOGBOOK.
Synopsis
A B737-200 WAS DISPATCHED WITHOUT A RECONFIGURATION LISTED IN THE LOGBOOK.
Narrative
ON NOV/TUE/05; ONE OF THE JOB ASSIGNMENTS I WAS GIVEN WAS A DAY CHK; MIDFLAP SPINDLE CARRIAGE GAP CHK AND A RECONFIGURE ON ACFT X. WHEN ACFT X ARRIVED; I MET IT AT THE GATE SO I COULD TALK TO THE PLT AND GET THE LOGBOOK. THEN I TOOK THE LOGBOOK INTO THE LINE OFFICE AND WENT TO HELP ANOTHER MECH ON ANOTHER ACFT. ABOUT 1/2 HR LATER; I CAME BACK TO MY ACFT WITH A HEATER AND NOTICED THE RAMP WAS THERE EARLY FOR THE RECONFIGURATION. SO I WENT AHEAD AND DID THE RECONFIGURATION; HOOKED UP THE HEATER AND THEN WENT IN TO GET WARM. IT WAS 0 DEGS WITH A LIGHT WIND. LATER I CAME OUT WITH MY WORK CARDS FOR THE DAY CHK AND GAP CHK. I FINISHED THOSE CARDS AND WENT BACK INSIDE. THERE I COMPLETED MY PAPERWORK; GAVE IT TO THE LEAD AND TOLD HIM THAT ACFT X NEEDED AN INSPECTION OF THE RECONFIGURATION. LATER THAT NIGHT AFTER SHIFT CHANGE (MY FIRST LEAD HAD GONE HOME); THE SECOND LEAD GAVE ME ANOTHER JOB -- A CSD OIL CHANGE -- WHICH I WORKED ON UNTIL I WENT HOME. THAT NIGHT THE ACFT FLEW TO ZZZ1 WHERE IT (THE RECONFIGURATION) WAS DISCOVERED WHEN THEY WENT TO RECONFIGURE IT BACK TO A PAX CONFIGN. THE MOST IMPORTANT IDEA I CAN THINK OF IS TO NOT LET MYSELF GET OUT OF MY NORMAL MODE OF WRITING A LOGBOOK ENTRY BEFORE STARTING A JOB. EVEN ON THE ROUTINE JOBS OR WHEN OTHER PEOPLE HAVE TO WAIT.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.