Narrative:

After takeoff at XA22Z on mar/xa/01, a navigation error occurred with eddf departure. The autoplt was engaged, first officer was flying. We departed on 'nord 5 lima' SID (NDG5L). We were filed for the nordlingen 6 sierra (NDG6S). Prior when clearance was given it was read back '6S' departure off runway 18. But, earlier I'd tried to put in the '6S' departure, but it was not in the SID choices. This is all refer to a commercial chart plate. The error occurred when the left turn to kng NDB was not established at the 12 DME of rid VOR. Departure control at frequency change asked us what departure we were flying. I read back '5L.' then the first officer said 'no it was the 6S' at which time we started to turn to kng NDB. The controller gave us the frequency then asked again 'you are on the 6S, confirm' I said 'yes,' but it was too late. The controller seemed very calm and there was no traffic conflict. I feel the contributing factors were ndg 6S was not a choice in the database (although) it was buildable not a quick choice. Not getting clearance until 5 mins prior to push. I was on the phone with company in the office and not in cockpit 30 mins prior only 15 mins prior rushing. A breakdown in CRM with basic flight plan checking. Language barrier heavy accents. Thinking I was going to get something and got something else (didn't catch it). Finally, fatigue -- went from an 11 hour 30 min duty day (during daytime) then to a 2 leg nighttime trip. Unfamiliar -- only second time through there. Training aloft from paris to frankfurt and return would really help. The first officer and I worked well together all week. This just got by us.

Related reports:

Google
 

Original NASA ASRS Text

Title: A310-200 CREW HAD TRACK DEV CAUSED BY MISPROGRAMMED FMC IN EDDF CLASS B AIRSPACE.

Narrative: AFTER TKOF AT XA22Z ON MAR/XA/01, A NAV ERROR OCCURRED WITH EDDF DEP. THE AUTOPLT WAS ENGAGED, FO WAS FLYING. WE DEPARTED ON 'NORD 5 LIMA' SID (NDG5L). WE WERE FILED FOR THE NORDLINGEN 6 SIERRA (NDG6S). PRIOR WHEN CLRNC WAS GIVEN IT WAS READ BACK '6S' DEP OFF RWY 18. BUT, EARLIER I'D TRIED TO PUT IN THE '6S' DEP, BUT IT WAS NOT IN THE SID CHOICES. THIS IS ALL REFER TO A COMMERCIAL CHART PLATE. THE ERROR OCCURRED WHEN THE L TURN TO KNG NDB WAS NOT ESTABLISHED AT THE 12 DME OF RID VOR. DEP CTL AT FREQ CHANGE ASKED US WHAT DEP WE WERE FLYING. I READ BACK '5L.' THEN THE FO SAID 'NO IT WAS THE 6S' AT WHICH TIME WE STARTED TO TURN TO KNG NDB. THE CTLR GAVE US THE FREQ THEN ASKED AGAIN 'YOU ARE ON THE 6S, CONFIRM' I SAID 'YES,' BUT IT WAS TOO LATE. THE CTLR SEEMED VERY CALM AND THERE WAS NO TFC CONFLICT. I FEEL THE CONTRIBUTING FACTORS WERE NDG 6S WAS NOT A CHOICE IN THE DATABASE (ALTHOUGH) IT WAS BUILDABLE NOT A QUICK CHOICE. NOT GETTING CLRNC UNTIL 5 MINS PRIOR TO PUSH. I WAS ON THE PHONE WITH COMPANY IN THE OFFICE AND NOT IN COCKPIT 30 MINS PRIOR ONLY 15 MINS PRIOR RUSHING. A BREAKDOWN IN CRM WITH BASIC FLT PLAN CHKING. LANGUAGE BARRIER HVY ACCENTS. THINKING I WAS GOING TO GET SOMETHING AND GOT SOMETHING ELSE (DIDN'T CATCH IT). FINALLY, FATIGUE -- WENT FROM AN 11 HR 30 MIN DUTY DAY (DURING DAYTIME) THEN TO A 2 LEG NIGHTTIME TRIP. UNFAMILIAR -- ONLY SECOND TIME THROUGH THERE. TRAINING ALOFT FROM PARIS TO FRANKFURT AND RETURN WOULD REALLY HELP. THE FO AND I WORKED WELL TOGETHER ALL WK. THIS JUST GOT BY US.

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.