Narrative:

During our turn I got the ATIS and aerodata info using FMS #2. Everything worked fine. The captain set up the flight plan using FMS #1. I verified the flight plan on FMS #1. We were cleared for the debie 6 departure off of runway 18C. I was the flying pilot and briefed the departure off of 18C. I talked about verifying the runway in the FMS and about 'gear up; LNAV.' I also briefed that we would takeoff pink needles and turn on the autopilot early so we could cross check the departure. We took off 18C. My FMS screen was on the aerodata page as has been my habit since the introduction of aerodata. On takeoff everything was normal until we armed the LNAV. At that point the flight director showed a hard right turn. I started turning right and a few seconds later the captain said; 'my flight director doesn't show that turn.' we took a few seconds to figure things out because both flight directors were showing a different course. While doing this we noticed the flight plan in FMS 2 was showing clt direct iah. We decided FMS 1 was right and started to turn back on course. ATC asked us what our heading was. We informed them we had a FMS issue and were turning back on course. They assigned us a new heading. I selected the FMS data from FMS number 1; and the pink needle turned yellow because we were now using shared data. A short time later they asked us if we could continue the departure. We said we could and continued the flight without further incident. RNAV departures are a big threat by themselves. I thought we did all the right things to mitigate the threat. Good brief; verified the runway; 'gear up LNAV'. The one thing I didn't do that would have solved the issue was to check that the flight plan was loaded on the right side FMS. I have never specifically done that before but after this experience it will now be a part of my routine. The undesired aircraft state was a lateral deviation that occurred as a result of following incorrect guidance from the flight director. This was initially corrected by us as we realized our error then assisted by ATC with the assignment of a new heading.one thing I mentioned earlier was to check the flight plan in both FMS units. The other thing I will do is take off with the flight plan in the FMS screen. It seems a lot more useful than the aerodata page I have been using.

Related reports:

Google
 

Original NASA ASRS Text

Title: An air carrier crew departed on the CLT DEBIE 6 departure and the First Officer followed the #2 FMS Flight Director command off track because the flight plan was entered in the #1 FMS but not verified in the #2 FMS.

Narrative: During our turn I got the ATIS and Aerodata info using FMS #2. Everything worked fine. The Captain set up the flight plan using FMS #1. I verified the flight plan on FMS #1. We were cleared for the DEBIE 6 departure off of Runway 18C. I was the Flying Pilot and briefed the departure off of 18C. I talked about verifying the runway in the FMS and about 'gear up; LNAV.' I also briefed that we would takeoff pink needles and turn on the autopilot early so we could cross check the departure. We took off 18C. My FMS screen was on the Aerodata page as has been my habit since the introduction of Aerodata. On takeoff everything was normal until we armed the LNAV. At that point the flight director showed a hard right turn. I started turning right and a few seconds later the Captain said; 'My flight director doesn't show that turn.' We took a few seconds to figure things out because both flight directors were showing a different course. While doing this we noticed the flight plan in FMS 2 was showing CLT direct IAH. We decided FMS 1 was right and started to turn back on course. ATC asked us what our heading was. We informed them we had a FMS issue and were turning back on course. They assigned us a new heading. I selected the FMS data from FMS number 1; and the pink needle turned yellow because we were now using shared data. A short time later they asked us if we could continue the departure. We said we could and continued the flight without further incident. RNAV departures are a big threat by themselves. I thought we did all the right things to mitigate the threat. Good brief; verified the runway; 'gear up LNAV'. The one thing I didn't do that would have solved the issue was to check that the flight plan was loaded on the right side FMS. I have never specifically done that before but after this experience it will now be a part of my routine. The undesired aircraft state was a lateral deviation that occurred as a result of following incorrect guidance from the flight director. This was initially corrected by us as we realized our error then assisted by ATC with the assignment of a new heading.One thing I mentioned earlier was to check the flight plan in both FMS units. The other thing I will do is take off with the flight plan in the FMS screen. It seems a lot more useful than the Aerodata page I have been using.

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.