Narrative:

CRJ2 departed runway 36C. I was training a controller and he noticed that the CRJ2 did not appear to be heading to the initial way point of ebawi; which is the first fix for that runway. When the trainee asked the CRJ2 if they were heading to ebawi they replied that they were heading to kayfo which is the initial way point for runway 36R. A heading of 290 was immediately issued and traffic was called for a CRJ9 which had departed runway 36R and was on a vector for a subsequent departure.the first problem is RNAV off the ground. The pilot of the CRJ2; when he called the OM; said the ramp tower told them to expect runway 36R so they loaded that runway into their FMS. They were then taxied to runway 36C and didn't change it in their system so that when they engaged the auto pilot it turned to kayfo. This seems to be a semi-common problem. A runway change does not negate the responsibility of the pilot to ensure they have the correct departure runway keyed into their system. However; if clt did not use RNAV off the ground but instead used initial headings prior to rejoining he RNAV this would not be a factor. The second factor is the fusion radar we are using. At slow speeds it is hard to tell if the blue blob that represents the aircraft is turning correctly or not. Even though it updates at a faster rate it takes a bit longer to get a handle on whether the aircraft is turning or not.

Google
 

Original NASA ASRS Text

Title: CLT Controller described an incorrect turn taken by an IFR departure when the wrong departure runway had been programed in the FMS; noting this was not an isolated event.

Narrative: CRJ2 departed Runway 36C. I was training a Controller and he noticed that the CRJ2 did not appear to be heading to the initial way point of EBAWI; which is the first fix for that runway. When the trainee asked the CRJ2 if they were heading to EBAWI they replied that they were heading to KAYFO which is the initial way point for Runway 36R. A heading of 290 was immediately issued and traffic was called for a CRJ9 which had departed Runway 36R and was on a vector for a subsequent departure.The first problem is RNAV off the ground. The pilot of the CRJ2; when he called the OM; said the Ramp Tower told them to expect Runway 36R so they loaded that runway into their FMS. They were then taxied to Runway 36C and didn't change it in their system so that when they engaged the auto pilot it turned to KAYFO. This seems to be a semi-common problem. A runway change does not negate the responsibility of the pilot to ensure they have the correct departure runway keyed into their system. However; if CLT did not use RNAV off the ground but instead used initial headings prior to rejoining he RNAV this would not be a factor. The second factor is the FUSION RADAR we are using. At slow speeds it is hard to tell if the blue blob that represents the aircraft is turning correctly or not. Even though it updates at a faster rate it takes a bit longer to get a handle on whether the aircraft is turning or not.

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.