Narrative:

We experienced a malfunction of the ice protection system; both cowl and wing; after departing gso. While we were investigating this malfunction; ATC advised that we would soon be receiving a reroute of our course. A short time later; ATC issued the reroute (probably assuming we were ready to copy since we had been advised it was forthcoming). As the non-flying pilot; I was not ready to copy but the reroute seemed simple enough to me that it was not an issue. The controller phonetically spelled the fixes but I was busy with the ice protection issue. I heard 'direct collins; pxt paats arrival' and entered 'colns' in the FMS as the first fix and; sure enough; it appeared on the mfd. Almost immediately after this; the alert controller asked if we were going to 'colin' and gave us a heading while we corrected the error. There were no TCAS alerts or any traffic observed in the area. We never got that far off course thanks to the controller.I accept responsibility for the error. The first thing I plan to do is slow down when I know I am distracted by any issue and assure I am totally clear on the clearance. However; I would also like to comment on the fact that this type of error has been encountered by other crews in other locations (I believe there was a recent communication of confusion between similar fixes in ny and dca). It would help trap errors such as this if fixes in close geographic proximity didn't share the same name with different spelling. Otherwise; crews lose the ability to self-diagnose the error.

Related reports:

Google
 

Original NASA ASRS Text

Title: Pilot reported of being occupied with a minor problem and having ATC issue a reroute. Pilot did not write clearance down and entered it from memory into the FMS. Pilot put in incorrect waypoint and aircraft deviated slightly. ATC corrected asked if they were going to COLIN and gave them a heading. Pilot corrected the error.

Narrative: We experienced a malfunction of the ice protection system; both cowl and wing; after departing GSO. While we were investigating this malfunction; ATC advised that we would soon be receiving a reroute of our course. A short time later; ATC issued the reroute (probably assuming we were ready to copy since we had been advised it was forthcoming). As the non-flying pilot; I was not ready to copy but the reroute seemed simple enough to me that it was not an issue. The controller phonetically spelled the fixes but I was busy with the ice protection issue. I heard 'Direct Collins; PXT PAATS arrival' and entered 'COLNS' in the FMS as the first fix and; sure enough; it appeared on the MFD. Almost immediately after this; the alert controller asked if we were going to 'COLIN' and gave us a heading while we corrected the error. There were no TCAS alerts or any traffic observed in the area. We never got that far off course thanks to the controller.I accept responsibility for the error. The first thing I plan to do is slow down when I know I am distracted by any issue and assure I am totally clear on the clearance. However; I would also like to comment on the fact that this type of error has been encountered by other crews in other locations (I believe there was a recent communication of confusion between similar fixes in NY and DCA). It would help trap errors such as this if fixes in close geographic proximity didn't share the same name with different spelling. Otherwise; crews lose the ability to self-diagnose the error.

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