A300
Maintenance Avionics
Time Pressure; Situational Awareness; Confusion; Communication Breakdown; Troubleshooting
Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
General Maintenance Action
Aircraft; Chart Or Publication; Manuals; MEL; Incorrect / Not Installed / Unavailable Part; Human Factors
Went out [during] pre departure to load a Navigation (NAV) Database update and loaded XX5-0006 and should have loaded XX3-0006. [Approximately] four hours later; flight crew noticed there was a problem loading the ZZZ1 identifier into the flight plan. I was dispatched to the aircraft and placed the NAV Database on MEL. After completing the database load; checked the Control Display Unit (CDU) for the current software load. I was looking for the -0006 in the software code as documented in the Maintenance item and it was there for both Flight Management Computers (FMCs).Recommend: 1) They need to state the whole number of the NAV Database software: example XX3-0006 on the Maintenance item. 2) The software disks XX3-0006 and the XX5-0006 were in the same drawer and were the same color.  NOTE* since this mistake happened; a divider has been incorporated to separate XX3-0006 and XX5-0006 disks from each other. Also; on the divider it is clearly labeled 'FMS FERRY'. This label helps identify what is in the divider drawer. The Lead and I decided to take these corrective actions to prevent future mistakes.
An Avionics Technician reports that he mistakenly loaded incorrect Navigation (NAV) Database software into the FMCs on an A300 aircraft.