Narrative:

An A320 was given a luaw clearance on runway 27R. When separation was assured with the preceding departure; I scanned the runway and cleared the A320 for takeoff; with instructions to 'RNAV to futbl'. The A320 responded quickly; yet completely; with 'cleared to futbl' and his call sign. After clearing him; I resumed my normal operations and luaw the next aircraft; informing that aircraft I would be crossing down field prior to their departure. As the A320 passed the intersections; I started crossing at taxiway N5; T; and P with a total of 4 aircraft. Right as I finished crossing the last aircraft; I observed the A320 in a hard right turn. I transmitted 'flight XXX turn left immediately'. The A320 acknowledged and the aircraft rolled left into the turn. I asked the A320 to verify if he was going to 'RNAV to futbl' and he replied in the affirmative with his call sign. At this time; I observed an A330 climbing off of runway 26L. The A320 was still sliding north; but had banked left so I did not call traffic and provided visual separation from the tower; the two aircraft started to separate with my closest estimate of 2 miles during visual separation. The A320 was about 3 miles off the runway end and I switched him to dr-south. I continued to observe the target on the racd and saw he had not continued south towards futbl; but upon looking out the window; saw he had leveled his wings after switching to departure and was tracking straight out again. I called dr-south to inform them of his non-compliance. Recommendation; stop using RNAV until a fix can be completed for closely spaced parallel runways. After observing the incorrect turn; I should have given the A320 a 240 heading to ensure no issues with flying towards futbl; as I later found out that the A320 said he was having FMS problems.

Google
 

Original NASA ASRS Text

Title: ATL Controller witnessed an air carrier initiate a wrong after departing Runway 27R that was assigned a 'RNAV To FUTBL' clearance; with a correct read back; the reporter listing FMS problems as a possible causal factor.

Narrative: An A320 was given a LUAW clearance on Runway 27R. When separation was assured with the preceding departure; I scanned the runway and cleared the A320 for takeoff; with instructions to 'RNAV TO FUTBL'. The A320 responded quickly; yet completely; with 'CLEARED TO FUTBL' and his call sign. After clearing him; I resumed my normal operations and LUAW the next aircraft; informing that aircraft I would be crossing down field prior to their departure. As the A320 passed the intersections; I started crossing at Taxiway N5; T; and P with a total of 4 aircraft. Right as I finished crossing the last aircraft; I observed the A320 in a hard right turn. I transmitted 'Flight XXX TURN LEFT IMMEDIATELY'. The A320 acknowledged and the aircraft rolled left into the turn. I asked the A320 to verify if he was going to 'RNAV TO FUTBL' and he replied in the affirmative with his call sign. At this time; I observed an A330 climbing off of Runway 26L. The A320 was still sliding north; but had banked left so I did not call traffic and provided visual separation from the Tower; the two aircraft started to separate with my closest estimate of 2 miles during visual separation. The A320 was about 3 miles off the runway end and I switched him to DR-S. I continued to observe the target on the RACD and saw he had not continued South towards FUTBL; but upon looking out the window; saw he had leveled his wings after switching to departure and was tracking straight out again. I called DR-S to inform them of his non-compliance. Recommendation; stop using RNAV until a fix can be completed for closely spaced parallel runways. After observing the incorrect turn; I should have given the A320 a 240 heading to ensure no issues with flying towards FUTBL; as I later found out that the A320 said he was having FMS problems.

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