37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 522748 |
Time | |
Date | 200108 |
Day | Sat |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : tus.airport |
State Reference | AZ |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : fok.tower |
Operator | common carrier : air carrier |
Make Model Name | B737-700 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : preflight |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 240 flight time total : 8000 flight time type : 2000 |
ASRS Report | 522748 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | aircraft equipment problem : less severe maintenance problem : improper documentation non adherence : far non adherence : company policies |
Independent Detector | other flight crewa |
Resolutory Action | none taken : detected after the fact |
Consequence | other other |
Supplementary | |
Problem Areas | Flight Crew Human Performance Maintenance Human Performance Chart Or Publication Aircraft Company |
Primary Problem | Company |
Situations | |
Airport | procedure or policy : tus.airport |
Publication | LOG BOOK |
Narrative:
This incident involved the maintenance logbook on a B737-700. The aircraft arrived in tucson, az for a scheduled departure to seattle, wa. As the first officer on the flight, I was the first to arrive at the aircraft and conducted the preflight, which included a review of the maintenance logbook. During the review of the logbook, I noticed that on log page xxxxx there was a write-up that said 'east.a. Yyyyy due.' in the corrective action it said 'required before revenue flts' with a deferred maintenance code of 'mct' not a 'Y' which would have meant that the corrective action had been accomplished. I looked in the mig-2B's for the corrective action to ensure that it had been accomplished. I found no evidence in either the old or the new book in any of the mig-2B's that the corrective action was accomplished. The previous page of the mig-2A showed that east.a zzzzz was accomplished and it referred to the next page for ea yyyyy, the discrepancy in question. (The actual page number referred to was incorrect as it was misprinted) I brought this open discrepancy to the capts attention, left the cockpit to complete my preflight. Upon my arrival back to the cockpit, the captain was on the cell phone with maintenance control in ZZZ about the subject. After completing the phone conversation the captain informed me that maintenance control was faxing the corrected log page to us for inclusion in the book. When the facsimile arrived at the aircraft, it was a computer print out from the main computer, not the corrected logbook page. The captain looked at it and said that he was satisfied since it stated at the bottom of the computer printout that 'east.a. Yyyyy was complied with.' I looked at it and said that normally we received a copy of the mig-2A 'white sheet' that was then attached over the existing yellow copy of the mig-2A as the corrected version. The captain disagreed and said he always got the computer printout. I had never seen that particular computer printout before. The captain asked if I was happy with what we had and my response was no, that it was clear the east.a. (Engineering action) had been complied with but the paperwork was not correct as I understood it. He said that it was correct and we were taking it as it was. Since our flight operations manual is very clear that it is the captain who shall determine the status of the aircraft maintenance log I deferred to him but said I would file a report on the incident. Looking into the issue more in depth upon return from the trip, I verified from both the line maintenance supervisor and maintenance control (a different individual) that the procedures followed were not correct. Even the copy of the corrected mig-2A, that I wanted, had recently been revised to the discrepancy being transferred to a new log page and the problem being corrected on the new log page. The maintenance computer printout was correct in that the east.a. Had been complied with but the documentation was not correct. The company is trying to revise procedures that will eliminate misunderstanding of proper methods but there needs to be a more concerted effort to educate everyone and the documentation needs to be simplified so that it doesn't take a lawyer to endure that the paperwork is ready to go fly. Incidentally there had been two airworthiness releases signed off by maintenance after this error was made without their catching it so it is not just the pilots that have problems with the logbooks.
Original NASA ASRS Text
Title: A B737-700 FO REPORTS ON THE CONFUSION EXISTING WITHIN AN AIRLINE OVER THE DESIGN AND FUNCTIONALITY OF THE ACFT LOGBOOK SO FAR AS DEFERRALS AND PAGE UPDATING FOR AIRWORTHINESS PURPOSES AT ZZZ, US.
Narrative: THIS INCIDENT INVOLVED THE MAINT LOGBOOK ON A B737-700. THE ACFT ARRIVED IN TUCSON, AZ FOR A SCHEDULED DEP TO SEATTLE, WA. AS THE FO ON THE FLT, I WAS THE FIRST TO ARRIVE AT THE ACFT AND CONDUCTED THE PREFLIGHT, WHICH INCLUDED A REVIEW OF THE MAINT LOGBOOK. DURING THE REVIEW OF THE LOGBOOK, I NOTICED THAT ON LOG PAGE XXXXX THERE WAS A WRITE-UP THAT SAID 'E.A. YYYYY DUE.' IN THE CORRECTIVE ACTION IT SAID 'REQUIRED BEFORE REVENUE FLTS' WITH A DEFERRED MAINT CODE OF 'MCT' NOT A 'Y' WHICH WOULD HAVE MEANT THAT THE CORRECTIVE ACTION HAD BEEN ACCOMPLISHED. I LOOKED IN THE MIG-2B'S FOR THE CORRECTIVE ACTION TO ENSURE THAT IT HAD BEEN ACCOMPLISHED. I FOUND NO EVIDENCE IN EITHER THE OLD OR THE NEW BOOK IN ANY OF THE MIG-2B'S THAT THE CORRECTIVE ACTION WAS ACCOMPLISHED. THE PREVIOUS PAGE OF THE MIG-2A SHOWED THAT E.A ZZZZZ WAS ACCOMPLISHED AND IT REFERRED TO THE NEXT PAGE FOR EA YYYYY, THE DISCREPANCY IN QUESTION. (THE ACTUAL PAGE NUMBER REFERRED TO WAS INCORRECT AS IT WAS MISPRINTED) I BROUGHT THIS OPEN DISCREPANCY TO THE CAPTS ATTENTION, LEFT THE COCKPIT TO COMPLETE MY PREFLT. UPON MY ARRIVAL BACK TO THE COCKPIT, THE CAPT WAS ON THE CELL PHONE WITH MAINT CTL IN ZZZ ABOUT THE SUBJECT. AFTER COMPLETING THE PHONE CONVERSATION THE CAPT INFORMED ME THAT MAINT CTL WAS FAXING THE CORRECTED LOG PAGE TO US FOR INCLUSION IN THE BOOK. WHEN THE FAX ARRIVED AT THE ACFT, IT WAS A COMPUTER PRINT OUT FROM THE MAIN COMPUTER, NOT THE CORRECTED LOGBOOK PAGE. THE CAPT LOOKED AT IT AND SAID THAT HE WAS SATISFIED SINCE IT STATED AT THE BOTTOM OF THE COMPUTER PRINTOUT THAT 'E.A. YYYYY WAS COMPLIED WITH.' I LOOKED AT IT AND SAID THAT NORMALLY WE RECEIVED A COPY OF THE MIG-2A 'WHITE SHEET' THAT WAS THEN ATTACHED OVER THE EXISTING YELLOW COPY OF THE MIG-2A AS THE CORRECTED VERSION. THE CAPT DISAGREED AND SAID HE ALWAYS GOT THE COMPUTER PRINTOUT. I HAD NEVER SEEN THAT PARTICULAR COMPUTER PRINTOUT BEFORE. THE CAPT ASKED IF I WAS HAPPY WITH WHAT WE HAD AND MY RESPONSE WAS NO, THAT IT WAS CLEAR THE E.A. (ENGINEERING ACTION) HAD BEEN COMPLIED WITH BUT THE PAPERWORK WAS NOT CORRECT AS I UNDERSTOOD IT. HE SAID THAT IT WAS CORRECT AND WE WERE TAKING IT AS IT WAS. SINCE OUR FLT OPS MANUAL IS VERY CLEAR THAT IT IS THE CAPT WHO SHALL DETERMINE THE STATUS OF THE ACFT MAINT LOG I DEFERRED TO HIM BUT SAID I WOULD FILE A REPORT ON THE INCIDENT. LOOKING INTO THE ISSUE MORE IN DEPTH UPON RETURN FROM THE TRIP, I VERIFIED FROM BOTH THE LINE MAINT SUPVR AND MAINT CTL (A DIFFERENT INDIVIDUAL) THAT THE PROCEDURES FOLLOWED WERE NOT CORRECT. EVEN THE COPY OF THE CORRECTED MIG-2A, THAT I WANTED, HAD RECENTLY BEEN REVISED TO THE DISCREPANCY BEING TRANSFERRED TO A NEW LOG PAGE AND THE PROBLEM BEING CORRECTED ON THE NEW LOG PAGE. THE MAINT COMPUTER PRINTOUT WAS CORRECT IN THAT THE E.A. HAD BEEN COMPLIED WITH BUT THE DOCUMENTATION WAS NOT CORRECT. THE COMPANY IS TRYING TO REVISE PROCEDURES THAT WILL ELIMINATE MISUNDERSTANDING OF PROPER METHODS BUT THERE NEEDS TO BE A MORE CONCERTED EFFORT TO EDUCATE EVERYONE AND THE DOCUMENTATION NEEDS TO BE SIMPLIFIED SO THAT IT DOESN'T TAKE A LAWYER TO ENDURE THAT THE PAPERWORK IS READY TO GO FLY. INCIDENTALLY THERE HAD BEEN TWO AIRWORTHINESS RELEASES SIGNED OFF BY MAINT AFTER THIS ERROR WAS MADE WITHOUT THEIR CATCHING IT SO IT IS NOT JUST THE PLTS THAT HAVE PROBLEMS WITH THE LOGBOOKS.
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.