Narrative:

Proceeded with completing the a-chk per our paperwork. Started attending to the various 'deferreds.' also on my list of assigned work was the installation of the new monthly revision of the navigation database load (software) into the flight management computer. I proceeded to load the software per our paperwork. As a habit I always make a point of writing down the software information on my sheet of assigned work so I can include that information in my signoff...which I did; however as I was checking and double-checking the software number as I was writing it down I failed to notice one digit (which is the reason for this form). The 'call-out' was to load new revision navigation database for august using 'Y-abcd' and the disk set that I loaded which was brought to me was 'X-abcd.' I did not catch the error reading it back to myself; verifying it off of the list or verifying it off of both FMC's. The aircraft accepted the load. I signed off this callout. Upon returning back to work today from my days off aug/thu/06 (working for aug/fri/06) I had an email in the company computer system from one of our system maintenance controllers on the B777 of my error. In the note the controller highlights that in my signoff I input the wrong software number and that maintenance control had asked the flight crew flying that aircraft right after the a-chk to verify what software that was installed. They did and found it to be the incorrect software. At that point maintenance control made a callout to have correct revision software installed and the technicians at ZZZ1 resolved the issue. I feel I read the disk label too fast and thereby missing the 1 wrong digit; had I caught the mistake I would not have loaded the incorrect software and advised my management to 'break' that particular item due to my station's lack of having any management type on that night who could make up navigation disks.

Related reports:

Google
 

Original NASA ASRS Text

Title: A B777-200 FLT MANAGEMENT COMPUTER WAS LOADED WITH THE INCORRECT NAV DATABASE. OUT OF DATE DOWNLOAD GIVEN TO TECHNICIAN FOR LOADING.

Narrative: PROCEEDED WITH COMPLETING THE A-CHK PER OUR PAPERWORK. STARTED ATTENDING TO THE VARIOUS 'DEFERREDS.' ALSO ON MY LIST OF ASSIGNED WORK WAS THE INSTALLATION OF THE NEW MONTHLY REVISION OF THE NAV DATABASE LOAD (SOFTWARE) INTO THE FLT MGMNT COMPUTER. I PROCEEDED TO LOAD THE SOFTWARE PER OUR PAPERWORK. AS A HABIT I ALWAYS MAKE A POINT OF WRITING DOWN THE SOFTWARE INFO ON MY SHEET OF ASSIGNED WORK SO I CAN INCLUDE THAT INFO IN MY SIGNOFF...WHICH I DID; HOWEVER AS I WAS CHKING AND DOUBLE-CHKING THE SOFTWARE NUMBER AS I WAS WRITING IT DOWN I FAILED TO NOTICE ONE DIGIT (WHICH IS THE REASON FOR THIS FORM). THE 'CALL-OUT' WAS TO LOAD NEW REVISION NAV DATABASE FOR AUGUST USING 'Y-ABCD' AND THE DISK SET THAT I LOADED WHICH WAS BROUGHT TO ME WAS 'X-ABCD.' I DID NOT CATCH THE ERROR READING IT BACK TO MYSELF; VERIFYING IT OFF OF THE LIST OR VERIFYING IT OFF OF BOTH FMC'S. THE ACFT ACCEPTED THE LOAD. I SIGNED OFF THIS CALLOUT. UPON RETURNING BACK TO WORK TODAY FROM MY DAYS OFF AUG/THU/06 (WORKING FOR AUG/FRI/06) I HAD AN EMAIL IN THE COMPANY COMPUTER SYS FROM ONE OF OUR SYS MAINT CTLRS ON THE B777 OF MY ERROR. IN THE NOTE THE CTLR HIGHLIGHTS THAT IN MY SIGNOFF I INPUT THE WRONG SOFTWARE NUMBER AND THAT MAINT CTL HAD ASKED THE FLT CREW FLYING THAT ACFT RIGHT AFTER THE A-CHK TO VERIFY WHAT SOFTWARE THAT WAS INSTALLED. THEY DID AND FOUND IT TO BE THE INCORRECT SOFTWARE. AT THAT POINT MAINT CTL MADE A CALLOUT TO HAVE CORRECT REVISION SOFTWARE INSTALLED AND THE TECHNICIANS AT ZZZ1 RESOLVED THE ISSUE. I FEEL I READ THE DISK LABEL TOO FAST AND THEREBY MISSING THE 1 WRONG DIGIT; HAD I CAUGHT THE MISTAKE I WOULD NOT HAVE LOADED THE INCORRECT SOFTWARE AND ADVISED MY MGMNT TO 'BREAK' THAT PARTICULAR ITEM DUE TO MY STATION'S LACK OF HAVING ANY MGMNT TYPE ON THAT NIGHT WHO COULD MAKE UP NAV DISKS.

Data retrieved from NASA's ASRS site as of January 2009 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.