Narrative:

Picked up A320 aircraft X for flight abcd at XA00. Saw maintenance log that aircraft had diverted to jfk due engine failure and was ferried after engine change on jul/sun/01 and had been signed off by maintenance. First officer and I joked that maintenance had probably hung a DC9 engine on it. On engine start, got ECAM 'check engine type.' had already checked initial page and saw proper data base and engine type. No further action on ECAM page was designated, but also checked our QRH and went into pilot's handbook which stated 'for crew awareness' and no further action. We thought 'just a glitch in computer program' as engine parameters on start looked normal when both had been started. Flew to bos, normal flight, 1 engine burning approximately 200 pounds less than other. Landed in bos, and saw maintenance personnel on deck and asked him about ECAM and he said probably some pins on computer needed tweaking and left it at that. Didn't write up ECAM because had cleared it and didn't show up on status. Flew back -- got same ECAM and wrote up aircraft for maintenance to look at it, because I didn't want to go through another day with getting ECAM. Maintenance took aircraft and gave us another aircraft as they were going to look at my aircraft X. Turns out aircraft X had gotten new engine, but maintenance hadn't set pins for A320, but had pins set for A319. Aircraft had been signed off by maintenance, so we assumed quality assurance was working. Training doesn't go into engine parameters for specific types of engine. Long and short of it -- we flew aircraft with engine intermix without knowing it.

Google
 

Original NASA ASRS Text

Title: A320 FLC FLEW ACFT WITH INTERMIXED ENGS DUE TO MAINT DISCREPANCY WHEN CHANGING ONE OF THE ENGS DUE TO PREVIOUS INFLT ENG FAILURE.

Narrative: PICKED UP A320 ACFT X FOR FLT ABCD AT XA00. SAW MAINT LOG THAT ACFT HAD DIVERTED TO JFK DUE ENG FAILURE AND WAS FERRIED AFTER ENG CHANGE ON JUL/SUN/01 AND HAD BEEN SIGNED OFF BY MAINT. FO AND I JOKED THAT MAINT HAD PROBABLY HUNG A DC9 ENG ON IT. ON ENG START, GOT ECAM 'CHK ENG TYPE.' HAD ALREADY CHKED INITIAL PAGE AND SAW PROPER DATA BASE AND ENG TYPE. NO FURTHER ACTION ON ECAM PAGE WAS DESIGNATED, BUT ALSO CHKED OUR QRH AND WENT INTO PLT'S HANDBOOK WHICH STATED 'FOR CREW AWARENESS' AND NO FURTHER ACTION. WE THOUGHT 'JUST A GLITCH IN COMPUTER PROGRAM' AS ENG PARAMETERS ON START LOOKED NORMAL WHEN BOTH HAD BEEN STARTED. FLEW TO BOS, NORMAL FLT, 1 ENG BURNING APPROX 200 LBS LESS THAN OTHER. LANDED IN BOS, AND SAW MAINT PERSONNEL ON DECK AND ASKED HIM ABOUT ECAM AND HE SAID PROBABLY SOME PINS ON COMPUTER NEEDED TWEAKING AND LEFT IT AT THAT. DIDN'T WRITE UP ECAM BECAUSE HAD CLRED IT AND DIDN'T SHOW UP ON STATUS. FLEW BACK -- GOT SAME ECAM AND WROTE UP ACFT FOR MAINT TO LOOK AT IT, BECAUSE I DIDN'T WANT TO GO THROUGH ANOTHER DAY WITH GETTING ECAM. MAINT TOOK ACFT AND GAVE US ANOTHER ACFT AS THEY WERE GOING TO LOOK AT MY ACFT X. TURNS OUT ACFT X HAD GOTTEN NEW ENG, BUT MAINT HADN'T SET PINS FOR A320, BUT HAD PINS SET FOR A319. ACFT HAD BEEN SIGNED OFF BY MAINT, SO WE ASSUMED QUALITY ASSURANCE WAS WORKING. TRAINING DOESN'T GO INTO ENG PARAMETERS FOR SPECIFIC TYPES OF ENG. LONG AND SHORT OF IT -- WE FLEW ACFT WITH ENG INTERMIX WITHOUT KNOWING IT.

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.