Narrative:

On jul/xa/01 approximately XA40, the lead avionics technician assigned me to aircraft xyz at gate to repair a TCASII problem. The lead avionics technician handed me a slip of paper indicating aircraft type, gate location, problem, departure time, part number and location of part. I proceeded to pick up the TCASII processor unit. Upon receiving the part, I checked the company number against the part number the lead technician gave me from our part number books located on the lead's desk. I then opened the box and checked the parts tag for the part number and serial number. All numbers were correct. I then proceeded to the aircraft at the gate. Inside the cockpit of the aircraft I reviewed the logbook discrepancy. I then proceeded to troubleshoot the TCASII system. On the TCASII radar indicator a message was displayed 'TCASII data fails #1 and #2 transponder mode.' the TCASII display was placed in the TCASII position in order to detect this failure. I then proceeded to the main equipment bay and a failure display was indicated on the TCASII processor computer. I returned to the cockpit of the aircraft and opened the circuit breakers on the panel. I returned to the main equipment center and removed the TCASII processor computer. I then installed the new TCASII processor computer. I then proceeded to the cockpit and reset the circuit breakers and performed the TCASII system self test. All TCASII system of the self test checked satisfactory. The logbooks on the B767-200ER flts are always removed from the aircraft and stored in the mechanic's office. I signed off my logbook discrepancy in the office. The mechanic told me not to pull the log sheet because he had other entries to enter himself. I then left the office leaving both the log sheet and parts tag with the mechanic to enter into the computer. Please note that whoever signs off the last item in the logbook is responsible for entering all logbook write-ups. This is a common practice in ZZZ. I then returned the old bad TCASII processor computer to maintenance. Approximately XD00 hours I was informed by my lead avionics technician that inspector found out through the logbook sheet that the wrong TCASII processor unit was installed on the aircraft. The part number removed from the aircraft was xyzabc. The part number installed was xxyyzz. Maintenance notified the flight crew of the aircraft of the problem and issued an in-flight MEL to inoperative the TCASII system from further use until the correct part could be sent out to be installed. I feel the corrective actions to prevent a recurrence, or correct the situation is as follows: the use of part number books should be updated or not allowed. Air carrier part number plate should be installed on all parts. Standardize all parts to include a painted or decal number on the side of all the parts. Also, installation of a metal plate on updated TCASII processor computer, preventing wrong part numbers from being installed on aircraft.

Google
 

Original NASA ASRS Text

Title: A B767-200ER WAS DISPATCHED IN NON COMPLIANCE DUE TO THE INCORRECT TCASII PROCESSOR COMPUTER BEING INSTALLED. CAUSED BY A CONFUSING PART NUMBER PUB DEFICIENCY.

Narrative: ON JUL/XA/01 APPROX XA40, THE LEAD AVIONICS TECHNICIAN ASSIGNED ME TO ACFT XYZ AT GATE TO REPAIR A TCASII PROB. THE LEAD AVIONICS TECHNICIAN HANDED ME A SLIP OF PAPER INDICATING ACFT TYPE, GATE LOCATION, PROB, DEP TIME, PART NUMBER AND LOCATION OF PART. I PROCEEDED TO PICK UP THE TCASII PROCESSOR UNIT. UPON RECEIVING THE PART, I CHKED THE COMPANY NUMBER AGAINST THE PART NUMBER THE LEAD TECHNICIAN GAVE ME FROM OUR PART NUMBER BOOKS LOCATED ON THE LEAD'S DESK. I THEN OPENED THE BOX AND CHKED THE PARTS TAG FOR THE PART NUMBER AND SERIAL NUMBER. ALL NUMBERS WERE CORRECT. I THEN PROCEEDED TO THE ACFT AT THE GATE. INSIDE THE COCKPIT OF THE ACFT I REVIEWED THE LOGBOOK DISCREPANCY. I THEN PROCEEDED TO TROUBLESHOOT THE TCASII SYS. ON THE TCASII RADAR INDICATOR A MESSAGE WAS DISPLAYED 'TCASII DATA FAILS #1 AND #2 XPONDER MODE.' THE TCASII DISPLAY WAS PLACED IN THE TCASII POS IN ORDER TO DETECT THIS FAILURE. I THEN PROCEEDED TO THE MAIN EQUIP BAY AND A FAILURE DISPLAY WAS INDICATED ON THE TCASII PROCESSOR COMPUTER. I RETURNED TO THE COCKPIT OF THE ACFT AND OPENED THE CIRCUIT BREAKERS ON THE PANEL. I RETURNED TO THE MAIN EQUIP CTR AND REMOVED THE TCASII PROCESSOR COMPUTER. I THEN INSTALLED THE NEW TCASII PROCESSOR COMPUTER. I THEN PROCEEDED TO THE COCKPIT AND RESET THE CIRCUIT BREAKERS AND PERFORMED THE TCASII SYS SELF TEST. ALL TCASII SYS OF THE SELF TEST CHKED SATISFACTORY. THE LOGBOOKS ON THE B767-200ER FLTS ARE ALWAYS REMOVED FROM THE ACFT AND STORED IN THE MECH'S OFFICE. I SIGNED OFF MY LOGBOOK DISCREPANCY IN THE OFFICE. THE MECH TOLD ME NOT TO PULL THE LOG SHEET BECAUSE HE HAD OTHER ENTRIES TO ENTER HIMSELF. I THEN LEFT THE OFFICE LEAVING BOTH THE LOG SHEET AND PARTS TAG WITH THE MECH TO ENTER INTO THE COMPUTER. PLEASE NOTE THAT WHOEVER SIGNS OFF THE LAST ITEM IN THE LOGBOOK IS RESPONSIBLE FOR ENTERING ALL LOGBOOK WRITE-UPS. THIS IS A COMMON PRACTICE IN ZZZ. I THEN RETURNED THE OLD BAD TCASII PROCESSOR COMPUTER TO MAINT. APPROX XD00 HRS I WAS INFORMED BY MY LEAD AVIONICS TECHNICIAN THAT INSPECTOR FOUND OUT THROUGH THE LOGBOOK SHEET THAT THE WRONG TCASII PROCESSOR UNIT WAS INSTALLED ON THE ACFT. THE PART NUMBER REMOVED FROM THE ACFT WAS XYZABC. THE PART NUMBER INSTALLED WAS XXYYZZ. MAINT NOTIFIED THE FLC OF THE ACFT OF THE PROB AND ISSUED AN INFLT MEL TO INOP THE TCASII SYS FROM FURTHER USE UNTIL THE CORRECT PART COULD BE SENT OUT TO BE INSTALLED. I FEEL THE CORRECTIVE ACTIONS TO PREVENT A RECURRENCE, OR CORRECT THE SIT IS AS FOLLOWS: THE USE OF PART NUMBER BOOKS SHOULD BE UPDATED OR NOT ALLOWED. ACR PART NUMBER PLATE SHOULD BE INSTALLED ON ALL PARTS. STANDARDIZE ALL PARTS TO INCLUDE A PAINTED OR DECAL NUMBER ON THE SIDE OF ALL THE PARTS. ALSO, INSTALLATION OF A METAL PLATE ON UPDATED TCASII PROCESSOR COMPUTER, PREVENTING WRONG PART NUMBERS FROM BEING INSTALLED ON ACFT.

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.