Narrative:

During preflight on nov dd 1996 for flight from jfk-phx, I was involved with correcting oversight by maintenance. When I checked the FMC database, the active data was oct cc 1996-nov dd 1996 and the previous data was sep zz 1996-oct bb 1996. I wrongly assumed that it was still current. After departure, I verified the route data with the en route charts (which were still oct cc 1996 data). Our previous procedures allowed us to use old data as long as we verified it. New procedures require a logbook entry prior to departure, even though non current data can be used if verified. Maintenance was notified en route so a new database could be loaded upon arrival in phx.

Google
 

Original NASA ASRS Text

Title: AN ACR B757-200 CAPT DEPARTED WITH ONE OUTDATED FMC DATABASE AND THE CURRENT ONE GOOD FOR THAT DAY ONLY.

Narrative: DURING PREFLT ON NOV DD 1996 FOR FLT FROM JFK-PHX, I WAS INVOLVED WITH CORRECTING OVERSIGHT BY MAINT. WHEN I CHKED THE FMC DATABASE, THE ACTIVE DATA WAS OCT CC 1996-NOV DD 1996 AND THE PREVIOUS DATA WAS SEP ZZ 1996-OCT BB 1996. I WRONGLY ASSUMED THAT IT WAS STILL CURRENT. AFTER DEP, I VERIFIED THE RTE DATA WITH THE ENRTE CHARTS (WHICH WERE STILL OCT CC 1996 DATA). OUR PREVIOUS PROCS ALLOWED US TO USE OLD DATA AS LONG AS WE VERIFIED IT. NEW PROCS REQUIRE A LOGBOOK ENTRY PRIOR TO DEP, EVEN THOUGH NON CURRENT DATA CAN BE USED IF VERIFIED. MAINT WAS NOTIFIED ENRTE SO A NEW DATABASE COULD BE LOADED UPON ARR IN PHX.

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.