Narrative:

First let me begin with some background information. I am a lead avionics technician working line maintenance for air carrier X at ZZZ international airport. Part of my duties is to review all inbound flts for MEL items for repair. On this morning, my review showed aircraft X and Y (both aircraft are A321's) inbound to ZZZ with an FMGC on MEL. I reviewed the history for both aircraft and found that both were programmed for replacement of an xxxxxx (company part number) by moc (maintenance control). I confirmed the affectivity of aircraft Y and found that this aircraft did require the xxxxxx computer. Since both aircraft were A321's, I assumed X also used an xxxxxx. Unfortunately X requires an xxxxxy computer (same computer with a different cam software). Once at the aircraft and after the attempted reset of the #2 FGC failed to bring the computer back on line, I installed a new computer. I used an xxxxxx computer by mistake. I accomplished the task in accordance with maintenance manual procedures 22-83-34-000-001 (removal) and 22-83-34-400-001 (install). All bite checks and a navigation data load were accomplished with no faults detected. The MEL was removed and the aircraft was certified CAT ii/III/IIIB status. No ECAM or maintenance status messages were displayed and the aircraft was released for service. When I returned to the office I started to enter the item into the computer using dde (direct data entry). The system flagged the installation of the computer as not in confign for this aircraft. I confirmed that I had indeed installed an incorrect computer. As the aircraft had already departed ZZZ, I immediately advised moc and my supervisor of the problem. Moc MEL'ed the computer at the next station, ZZZ1, and had the computer replaced 1 leg later at the first maintenance station (ZZZ1). The aircraft flew normally and generated no ECAM or maintenance status messages -- the pfr (postflt report) in ZZZ1 was clean.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN AIRBUS 321 WAS DISPATCHED IN NON COMPLIANCE WITH THE INCORRECT #2 AUTOPLT FLT GUIDANCE COMPUTER INSTALLED.

Narrative: FIRST LET ME BEGIN WITH SOME BACKGROUND INFO. I AM A LEAD AVIONICS TECHNICIAN WORKING LINE MAINT FOR ACR X AT ZZZ INTL ARPT. PART OF MY DUTIES IS TO REVIEW ALL INBOUND FLTS FOR MEL ITEMS FOR REPAIR. ON THIS MORNING, MY REVIEW SHOWED ACFT X AND Y (BOTH ACFT ARE A321'S) INBOUND TO ZZZ WITH AN FMGC ON MEL. I REVIEWED THE HISTORY FOR BOTH ACFT AND FOUND THAT BOTH WERE PROGRAMMED FOR REPLACEMENT OF AN XXXXXX (COMPANY PART NUMBER) BY MOC (MAINT CTL). I CONFIRMED THE AFFECTIVITY OF ACFT Y AND FOUND THAT THIS ACFT DID REQUIRE THE XXXXXX COMPUTER. SINCE BOTH ACFT WERE A321'S, I ASSUMED X ALSO USED AN XXXXXX. UNFORTUNATELY X REQUIRES AN XXXXXY COMPUTER (SAME COMPUTER WITH A DIFFERENT CAM SOFTWARE). ONCE AT THE ACFT AND AFTER THE ATTEMPTED RESET OF THE #2 FGC FAILED TO BRING THE COMPUTER BACK ON LINE, I INSTALLED A NEW COMPUTER. I USED AN XXXXXX COMPUTER BY MISTAKE. I ACCOMPLISHED THE TASK IN ACCORDANCE WITH MAINT MANUAL PROCS 22-83-34-000-001 (REMOVAL) AND 22-83-34-400-001 (INSTALL). ALL BITE CHKS AND A NAV DATA LOAD WERE ACCOMPLISHED WITH NO FAULTS DETECTED. THE MEL WAS REMOVED AND THE ACFT WAS CERTIFIED CAT II/III/IIIB STATUS. NO ECAM OR MAINT STATUS MESSAGES WERE DISPLAYED AND THE ACFT WAS RELEASED FOR SVC. WHEN I RETURNED TO THE OFFICE I STARTED TO ENTER THE ITEM INTO THE COMPUTER USING DDE (DIRECT DATA ENTRY). THE SYS FLAGGED THE INSTALLATION OF THE COMPUTER AS NOT IN CONFIGN FOR THIS ACFT. I CONFIRMED THAT I HAD INDEED INSTALLED AN INCORRECT COMPUTER. AS THE ACFT HAD ALREADY DEPARTED ZZZ, I IMMEDIATELY ADVISED MOC AND MY SUPVR OF THE PROB. MOC MEL'ED THE COMPUTER AT THE NEXT STATION, ZZZ1, AND HAD THE COMPUTER REPLACED 1 LEG LATER AT THE FIRST MAINT STATION (ZZZ1). THE ACFT FLEW NORMALLY AND GENERATED NO ECAM OR MAINT STATUS MESSAGES -- THE PFR (POSTFLT RPT) IN ZZZ1 WAS CLEAN.

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.