37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 674506 |
Time | |
Date | 200510 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : phx.airport |
State Reference | AZ |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B757-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : parked ground : maintenance |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Qualification | pilot : atp |
Experience | flight time last 90 days : 180 flight time total : 12500 flight time type : 1800 |
ASRS Report | 674506 |
Person 2 | |
Affiliation | other |
Function | maintenance : technician |
Events | |
Anomaly | maintenance problem : improper documentation non adherence : published procedure non adherence : company policies non adherence : far |
Independent Detector | other flight crewa |
Resolutory Action | none taken : unable other |
Supplementary | |
Problem Areas | Maintenance Human Performance Flight Crew Human Performance Company Aircraft |
Primary Problem | Maintenance Human Performance |
Narrative:
A contract mechanic performed an ETOPS check prior to departure. Aircraft logbook presented to crew 10 mins before departure time. The first officer and I inspected the aircraft log in presence of the mechanic. I discovered the required 'line service' check had not been completed. Review of previous logbook indicated the last properly entered line service check was completed on oct/sun/05. The aircraft had a log entry in the second discrepancy box indicating 'line service check work card due oct/tue/05.' the corrective action signed off; but the wording of 'line service completed' was not entered. Also; no 'line service maintenance check' or 'airworthiness release' with date and signature of mechanic in the appropriate boxes in the upper r-hand corner of log had been entered; which is required. The mechanic agreed the logbook was not legal for flight. We called mr Y in company maintenance control. After a discussion of the issue; they were unable to resolve the logbook problem; so I was handed the phone. The maintenance controller stated the line service check had been completed on oct/wed/05 even though the aircraft logbook did not reflect the work completed. I requested a facsimile hard copy of the log page in question and was informed the log page was in transit; but the entry was indicated in the maintenance computer -- a system that is not recognized by the FAA; that the line service had been complied and completed. I requested a computer hard copy be faxed so it could be placed in the aircraft log; even though I knew that wasn't legal and maintenance control failed to provide it and would not give a definitive answer to its legality. I requested to speak to the regional chief pilot. The regional chief pilot assured me the line service had been completed and the aircraft log was legal. I again questioned how it was possible for the logbook to be legal without the proper entries; and was told it was concluded the work was done; if there is any problem; they'll take the hit for it; 'just go!' I argued my case as far as I dared. We were 20 mins beyond departure time with passenger all on board. In the tone I was told to 'just go' I was confident that had I not just gone; I would be traveling to headquarters where I would be doing a carpet dance with questionable union representation. Knowing I would be at the receiving end of company hostilities; I went to maui.
Original NASA ASRS Text
Title: ETOPS FLT TO OGG DEPARTS WITH POSSIBLY ILLEGAL MAINT LOG DUE TO DEMANDS AND IMPLIED THREATS TO PIC SHOULD HE REFUSE TO DEPART.
Narrative: A CONTRACT MECH PERFORMED AN ETOPS CHK PRIOR TO DEP. ACFT LOGBOOK PRESENTED TO CREW 10 MINS BEFORE DEP TIME. THE FO AND I INSPECTED THE ACFT LOG IN PRESENCE OF THE MECH. I DISCOVERED THE REQUIRED 'LINE SVC' CHK HAD NOT BEEN COMPLETED. REVIEW OF PREVIOUS LOGBOOK INDICATED THE LAST PROPERLY ENTERED LINE SVC CHK WAS COMPLETED ON OCT/SUN/05. THE ACFT HAD A LOG ENTRY IN THE SECOND DISCREPANCY BOX INDICATING 'LINE SVC CHK WORK CARD DUE OCT/TUE/05.' THE CORRECTIVE ACTION SIGNED OFF; BUT THE WORDING OF 'LINE SVC COMPLETED' WAS NOT ENTERED. ALSO; NO 'LINE SVC MAINT CHK' OR 'AIRWORTHINESS RELEASE' WITH DATE AND SIGNATURE OF MECH IN THE APPROPRIATE BOXES IN THE UPPER R-HAND CORNER OF LOG HAD BEEN ENTERED; WHICH IS REQUIRED. THE MECH AGREED THE LOGBOOK WAS NOT LEGAL FOR FLT. WE CALLED MR Y IN COMPANY MAINT CTL. AFTER A DISCUSSION OF THE ISSUE; THEY WERE UNABLE TO RESOLVE THE LOGBOOK PROB; SO I WAS HANDED THE PHONE. THE MAINT CTLR STATED THE LINE SVC CHK HAD BEEN COMPLETED ON OCT/WED/05 EVEN THOUGH THE ACFT LOGBOOK DID NOT REFLECT THE WORK COMPLETED. I REQUESTED A FAX HARD COPY OF THE LOG PAGE IN QUESTION AND WAS INFORMED THE LOG PAGE WAS IN TRANSIT; BUT THE ENTRY WAS INDICATED IN THE MAINT COMPUTER -- A SYS THAT IS NOT RECOGNIZED BY THE FAA; THAT THE LINE SVC HAD BEEN COMPLIED AND COMPLETED. I REQUESTED A COMPUTER HARD COPY BE FAXED SO IT COULD BE PLACED IN THE ACFT LOG; EVEN THOUGH I KNEW THAT WASN'T LEGAL AND MAINT CTL FAILED TO PROVIDE IT AND WOULD NOT GIVE A DEFINITIVE ANSWER TO ITS LEGALITY. I REQUESTED TO SPEAK TO THE REGIONAL CHIEF PLT. THE REGIONAL CHIEF PLT ASSURED ME THE LINE SVC HAD BEEN COMPLETED AND THE ACFT LOG WAS LEGAL. I AGAIN QUESTIONED HOW IT WAS POSSIBLE FOR THE LOGBOOK TO BE LEGAL WITHOUT THE PROPER ENTRIES; AND WAS TOLD IT WAS CONCLUDED THE WORK WAS DONE; IF THERE IS ANY PROB; THEY'LL TAKE THE HIT FOR IT; 'JUST GO!' I ARGUED MY CASE AS FAR AS I DARED. WE WERE 20 MINS BEYOND DEP TIME WITH PAX ALL ON BOARD. IN THE TONE I WAS TOLD TO 'JUST GO' I WAS CONFIDENT THAT HAD I NOT JUST GONE; I WOULD BE TRAVELING TO HEADQUARTERS WHERE I WOULD BE DOING A CARPET DANCE WITH QUESTIONABLE UNION REPRESENTATION. KNOWING I WOULD BE AT THE RECEIVING END OF COMPANY HOSTILITIES; I WENT TO MAUI.
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.