Narrative:

Event: opc database out of date. I was notified on nov/xg/00 that I had flown a flight with an opc database that was out-of-date on nov/xa/00. The database was dated sep/xg/00 to nov/xg/00. This event was inadvertent and unintentional. Sometimes we are all affected by 'hurry-up' syndrome, and I believe that may have contributed to this situation. To keep this event from happening again, I will be more diligent in my preflight duties, and try not to be influenced by the 'hurry-up' bug and rushing through my duties.

Google
 

Original NASA ASRS Text

Title: A B737 FO RPTED THAT HE FOUND OUT, 3 DAYS AFTER THE FACT, THAT HE HAD FLOWN WITH THE OPC DATABASE OUT-OF-DATE.

Narrative: EVENT: OPC DATABASE OUT OF DATE. I WAS NOTIFIED ON NOV/XG/00 THAT I HAD FLOWN A FLT WITH AN OPC DATABASE THAT WAS OUT-OF-DATE ON NOV/XA/00. THE DATABASE WAS DATED SEP/XG/00 TO NOV/XG/00. THIS EVENT WAS INADVERTENT AND UNINTENTIONAL. SOMETIMES WE ARE ALL AFFECTED BY 'HURRY-UP' SYNDROME, AND I BELIEVE THAT MAY HAVE CONTRIBUTED TO THIS SIT. TO KEEP THIS EVENT FROM HAPPENING AGAIN, I WILL BE MORE DILIGENT IN MY PREFLT DUTIES, AND TRY NOT TO BE INFLUENCED BY THE 'HURRY-UP' BUG AND RUSHING THROUGH MY DUTIES.

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.