Narrative:

While loading the multi function control display unit (mcdu) database, #1 multi function control display unit would not update and #2 did. This was written up and deferred, but no MEL reference was on the dispatch release and no MEL sticker in the cockpit. It's a CAT C item and was deferred 10 days. Dec/xa/97, lgb-dfw flew the aircraft. First officer loaded the database, he was PF. His database was current. I failed to notice my database not current because I was managing other write-ups and delays. System operated normally, I had no reason to suspect a problem. Dec/xb/97, dfw-lgb. Again, first officer's leg. First officer loaded the database, he was PF. I was distracted by aircraft weight and balance manual in error. I was in the office on the phone the whole time dealing with getting a current version to the weight and balance manual. Lgb- dfw, outcome -- captain discovered problem. Called dispatch and got a current sticker for the logbook, aircraft and MEL data for the dispatch release. Callback conversation with reporter revealed the following information: reporter captain said he was very upset with his company and has since quit it. The problem initially started with lack of current database in the #1 mcdu, but he didn't notice it because he was distracted trying to get a current weight and balance. The first officer loaded the #2 mcdu, it was current and the first officer was to be the PF, so it appeared to function normally. It was discovered later that the #1 mcdu did not have the current database because when the ground crew was loading it the loader went inoperative and they didn't finish updating. Consequently, it was not included on the MEL which it should have been. There were other issues which were not very clear to either the reporter or this analyst.

Related reports:

Google
 

Original NASA ASRS Text

Title: A320 ACFT PRIOR TO FLT WHEN LOADING MCDU THE # 1 WOULDN'T UPDATE, BUT THE FO WAS PF, SO FLC PROCEEDED. RPTR CAPT DIDN'T NOTICE THE DATABASE DATE NOR KNEW THAT IT WAS NOT ON THE DISPATCH RELEASE OR MEL.

Narrative: WHILE LOADING THE MULTI FUNCTION CTL DISPLAY UNIT (MCDU) DATABASE, #1 MULTI FUNCTION CTL DISPLAY UNIT WOULD NOT UPDATE AND #2 DID. THIS WAS WRITTEN UP AND DEFERRED, BUT NO MEL REF WAS ON THE DISPATCH RELEASE AND NO MEL STICKER IN THE COCKPIT. IT'S A CAT C ITEM AND WAS DEFERRED 10 DAYS. DEC/XA/97, LGB-DFW FLEW THE ACFT. FO LOADED THE DATABASE, HE WAS PF. HIS DATABASE WAS CURRENT. I FAILED TO NOTICE MY DATABASE NOT CURRENT BECAUSE I WAS MANAGING OTHER WRITE-UPS AND DELAYS. SYS OPERATED NORMALLY, I HAD NO REASON TO SUSPECT A PROB. DEC/XB/97, DFW-LGB. AGAIN, FO'S LEG. FO LOADED THE DATABASE, HE WAS PF. I WAS DISTRACTED BY ACFT WT AND BAL MANUAL IN ERROR. I WAS IN THE OFFICE ON THE PHONE THE WHOLE TIME DEALING WITH GETTING A CURRENT VERSION TO THE WT AND BAL MANUAL. LGB- DFW, OUTCOME -- CAPT DISCOVERED PROB. CALLED DISPATCH AND GOT A CURRENT STICKER FOR THE LOGBOOK, ACFT AND MEL DATA FOR THE DISPATCH RELEASE. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR CAPT SAID HE WAS VERY UPSET WITH HIS COMPANY AND HAS SINCE QUIT IT. THE PROB INITIALLY STARTED WITH LACK OF CURRENT DATABASE IN THE #1 MCDU, BUT HE DIDN'T NOTICE IT BECAUSE HE WAS DISTRACTED TRYING TO GET A CURRENT WT AND BAL. THE FO LOADED THE #2 MCDU, IT WAS CURRENT AND THE FO WAS TO BE THE PF, SO IT APPEARED TO FUNCTION NORMALLY. IT WAS DISCOVERED LATER THAT THE #1 MCDU DID NOT HAVE THE CURRENT DATABASE BECAUSE WHEN THE GND CREW WAS LOADING IT THE LOADER WENT INOP AND THEY DIDN'T FINISH UPDATING. CONSEQUENTLY, IT WAS NOT INCLUDED ON THE MEL WHICH IT SHOULD HAVE BEEN. THERE WERE OTHER ISSUES WHICH WERE NOT VERY CLR TO EITHER THE RPTR OR THIS ANALYST.

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.