Flight Crew Air Transport Pilot (ATP)
Human-Machine Interface; Confusion; Situational Awareness; Fatigue
ATC Issue All Types; Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Flight Deck / Cabin / Aircraft Event Other / Unknown
Air Traffic Control Provided Assistance; Flight Crew Became Reoriented; Flight Crew Requested ATC Assistance / Clarification
Human Factors
We were holding in position on Runway 18L; the Tower cleared us 'RNAV RIBZZ; cleared for takeoff Runway 18L'. I replied that we had WESTN in our FMS; and the Controller replied that WESTN was for BBKNG1 departure; and we were supposed to be on the BBKNG2. Takeoff clearance was canceled; and we were given instructions to clear the runway and contact Clearance Delivery for a new departure. After clearing the runway we discovered the FMS Nav database to be out of date. With the parking brake set the Captain swapped databases and reloaded the flight plan with the new departure. We verified the waypoints; re-ran the checklists; and departed uneventfully.I was complacent in my departure brief (this was the 4th day in a row of [same airport] out and backs); and didn't verify the BBKNG2 vs. BBKNG1. Very surprised I didn't catch the wrong initial waypoint in the FMS vs. the Commercial Chart EFB. [We] should have been more deliberate in the departure briefing.
Although I did look at the database during the setup; I missed that FEB - MAR was selected vs. MAR - APR.
An MD-10 flight crew had to refuse their takeoff clearance when they discovered they had an out of date FMS active database. After exiting the runway the retrieved and activated the current database and subsequently completed the trip without further incident.