An md-10 flight crew had to refuse their takeoff clearance when they discovered they had an out of d...

Attributes
ACN	1077061
Time
Date	201303
Local Time Of Day	1201-1800
Place
Locale Reference	MEM.Airport
State Reference	TN
Aircraft 1
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	Takeoff
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	First Officer Pilot Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Person 2
Function	Captain Pilot Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	ATC Issue All Types Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Flight Deck / Cabin / Aircraft Event Other / Unknown

Narrative:

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.

Original NASA ASRS Text

Title: 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.

Narrative: 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.

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

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.