A B757-200 WAS DISPATCHED IN NON COMPLIANCE WITH 2 OPEN UNANSWERED LOGBOOK MAINT RPTS.

Date: 2004-02 · Aircraft: B757-200

Anomalies: aircraft-equipment-problem-less-severe|deviation-discrepancy-procedural-maintenance|deviation-discrepancy-procedural-published-material-policy|deviation-discrepancy-procedural-far

Synopsis

A B757-200 WAS DISPATCHED IN NON COMPLIANCE WITH 2 OPEN UNANSWERED LOGBOOK MAINT RPTS.

Narrative

ACFT X (A B757) CALLED IN ON THE MAINT FREQ TO THE MAINT SHOP AND SAID THEY HAD A WRITE-UP IN THE LOGBOOK AND WERE WAITING FOR A MECH TO COME SIGN THE ITEM OFF. AFTER GOING OUT TO THE ACFT AND READING THE ONE WRITE-UP ON THE AFT R LAVATORY 'M SPIGOT HOT WATER INOP;' I WENT AND RESET THE HOT WATER HEATER IN THE 'LAVATORY M.' THE LAVATORY WATER HEATER OP WAS NORMAL AFTER RESET. I THEN PROCEEDED TO SIGN OFF THE LOGBOOK ITEM. I SIGNED OFF THE 'LAVATORY M WATER HEATER' AND THE NEW AIRWORTHINESS RELEASE. I LEFT THE AFT AT THAT POINT; BECAUSE IT WAS DEP TIME FOR THE ACFT. WHEN I WENT TO ENTER THE LOG SHEET IN THE COMPUTER; I THEN NOTICED THE LOG SHEET THAT I PULLED DID NOT HAVE AN AIRWORTHINESS RELEASE SIGNOFF. AFTER EXAMINING THE LOG SHEET SOME MORE AND LOOKING UP THE ACFT OUTSTANDING MAINT ITEMS IN THE COMPUTER; I SAW IT WAS 2 OTHER ITEMS IN THE LOGBOOK ON LOG SHEET X FOR LAVATORY WATER HEATERS THAT WERE NOT SIGNED OFF. THE ACFT HAD ALREADY LEFT THE GATE AND WAS ON ITS WAY TO ZZZ1. THE MAINT COORDINATOR IN ZZZ2 WAS NOTIFIED BY TELEPHONE AND ZZZ3 MAINT WAS CALLED ALSO TO INFORM THEM OF THE 2 WRITE-UPS IN THE LOGBOOK. AS OF THE TIME I LEFT WORK TODAY; ACFT X MADE 1 REVENUE FLT FROM ZZZ4 TO ZZZ3 WITH 2 OPEN ACFT WRITE-UPS ON LAVATORY WATER HEATERS BEING INOP IN LAVATORY G AND K. THE LOG SHEET I DID NOT PULL WAS X. LAVATORY WATER HEATERS FALL UNDER THE SYS/SUB-SYS; BUT ARE CONSIDERED PAX CONVENIENCE ITEMS. WHAT I BELIEVE REALLY CAUSED THE PROB WAS MY RUSHING TO AVOID A DELAY. HAD I TAKEN MY TIME AND NOT WORRIED ABOUT WHEN THE ACFT WAS SCHEDULED TO LEAVE; I MIGHT NOT HAVE OVERLOOKED THE PREVIOUS LOG SHEET.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.