Narrative:

Aircraft X checked in climbing to 14;000 feet on a 017-heading. The heading was unreadable to me. Radar controller cleared to climb; he was pointed out to sector 47 already. The pilot checked back and made a correction to the initial heading he gave us; he said instead he was on a 180 heading. The radar controller acknowledged and cleared the aircraft direct buzrd; on course. Aircraft read back and verified what sounded to us as buzrd. Shortly I noticed the aircraft was making a sharp right turn into sector 47's airspace. I notified the sector 18 radar controller immediately and initiated a call them with sector 47 radar controller. I initiated a point out as I didn't know what the aircraft was doing; heard the sector 18 radar controller issue a left turn which I passed along to 47; and the sector 47 radar controller stopped his traffic at 16;000 feet. After that call; we quizzed the pilot as to what had happened. He advised us that he was cleared via the BLZZR3 SID; while we showed him cleared via the SSOXS4 departure. Once we verified his routing; we got him back on course. It turns out the flight plan the aircraft showed as issued and what the pilot had in front of him were two different things. The pilot says he was cleared on the BLZZR3; and he was reading back direct blzzr. To us; the aircraft would have no reason to read back blzzr; it's not on the SSOXS4 departure and it sounded to me like an odd pronunciation of buzrd. Also note that it seemed that the co-pilot and pilot were sharing radio responsibilities and I remember hearing two distinct voices reading back at different times.the controller in charge (controller in charge) happened to be there to observe the whole event and he took over the situation of discovering what happened with the routing.change buzrd fix to something not similar to other departure fixes; in this case blzzr. This should never be an issue if the aircraft's routing is correct; but they sound very similar and this is now a confirmed issue.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZBW controller reported of a similar sounding fix that the pilot had entered and was flying towards. Aircraft was questioned and the confusion of the fix name was determined to be part of the problem. ATC had one clearance the crew had a different one.

Narrative: Aircraft X checked in climbing to 14;000 feet on a 017-heading. The heading was unreadable to me. RADAR controller cleared to climb; he was pointed out to sector 47 already. The pilot checked back and made a correction to the initial heading he gave us; he said instead he was on a 180 heading. The RADAR controller acknowledged and cleared the aircraft direct BUZRD; on course. Aircraft read back and verified what sounded to us as BUZRD. Shortly I noticed the aircraft was making a sharp right turn into sector 47's airspace. I notified the sector 18 RADAR controller immediately and initiated a call them with sector 47 RADAR controller. I initiated a point out as I didn't know what the aircraft was doing; heard the sector 18 RADAR controller issue a left turn which I passed along to 47; and the sector 47 RADAR controller stopped his traffic at 16;000 feet. After that call; we quizzed the pilot as to what had happened. He advised us that he was cleared via the BLZZR3 SID; while we showed him cleared via the SSOXS4 departure. Once we verified his routing; we got him back on course. It turns out the flight plan the aircraft showed as issued and what the pilot had in front of him were two different things. The pilot says he was cleared on the BLZZR3; and he was reading back direct BLZZR. To us; the aircraft would have no reason to read back BLZZR; it's not on the SSOXS4 departure and it sounded to me like an odd pronunciation of BUZRD. Also note that it seemed that the co-pilot and pilot were sharing radio responsibilities and I remember hearing two distinct voices reading back at different times.The Controller in Charge (CIC) happened to be there to observe the whole event and he took over the situation of discovering what happened with the routing.Change BUZRD fix to something not similar to other departure fixes; in this case BLZZR. This should never be an issue if the aircraft's routing is correct; but they sound very similar and this is now a confirmed issue.

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.