Narrative:

I am sending this because of naming issue of an 'arrival' which did not result in any problem or conflicts; but to make a recommendation on the naming of that arrival. I was on an IFR flight plan at 8;000 ft; about 50 miles south of atlanta VOR (atl) and outside the class B. I was in contact with atlanta center and following a clearance of direct to my destination airport 4a4 (polk county - cedartown). ATC contacted me for a change in clearance. What I thought I heard was 'you are cleared to the nancy intersection; join V51; direct (4a4). I had the ATC controller spell out the intersection; which was really nannc. I entered it in the GPS as he spelled it; and it found it immediately so and I replied with 'cleared to nannc (spelling it out); intercept V51; direct'. The nannc intersection was approximately 40 miles away; so steered toward it. It was at night; so I started scanning my enroute chart to find the intersection and how it was going to intercept V51. I couldn't find either the intersection or V51 nearby (although I was familiar with the airway; but couldn't place where); even though my garmin 530W clearly showed the intersection location with no problem. There was only about a couple of minutes after receiving this clearance; when the controller came back and said that it wouldn't work; and would give a new one in a couple of minutes. I figured it was due the same problem I was having with V51. I suggested that after nannc; go direct to 4a4; which he replied he was working on. About minute later; he gave me a new clearance 'after nannc; direct 4a4.' this was no problem; so I ended my search V51. After the flight; I wanted to know why I couldn't find the intersection or V51 on my enroute maps right away. When that didn't work; I finally figured out that since the GPS found it; it must be on a STAR; SID or approach plate. It turned out that nannc is a fix for the 'diffi one arrival' atlanta arrival. I don't know why I thought I heard 'victor'; but the diffi one; sounded like '51'; and I don't remember ever hearing the word 'arrival' in the clearance. Interesting enough; I repeated the instructions as 'after nannc intersection; intercept V51; then direct'; which ATC controller didn't catch the victor or the missing word 'arrival' either. I guess; by the book; I shouldn't have accepted the clearance until I found it on the map; or responded that I couldn't find it; but since I clearly had the intersection and almost 20 minutes to find V51; it wouldn't be a problem; and the ATC controller didn't question my reply either. It was resolved so quickly; it became a non-issue. Bottom line; I think the name 'diffi one' sounds too close to '51'; which started and caused the confusion in the first place; so I would recommend that the name be changed. As a side note; on my side; reception of ATC radio was very clear; as was the controller's speech. I had no problem understanding instructions. Thank you for your help.

Google
 

Original NASA ASRS Text

Title: A pilot reported confusion about his clearance reroute from ZTL which included the words DIFFI ONE which he heard as Victor 51.

Narrative: I am sending this because of naming issue of an 'Arrival' which did not result in any problem or conflicts; but to make a recommendation on the naming of that arrival. I was on an IFR flight plan at 8;000 FT; about 50 miles south of Atlanta VOR (ATL) and outside the Class B. I was in contact with Atlanta Center and following a clearance of direct to my destination airport 4A4 (Polk County - Cedartown). ATC contacted me for a change in clearance. What I thought I heard was 'You are cleared to the NANCY Intersection; join V51; direct (4A4). I had the ATC Controller spell out the intersection; which was really NANNC. I entered it in the GPS as he spelled it; and it found it immediately so and I replied with 'Cleared to NANNC (spelling it out); intercept V51; Direct'. The NANNC Intersection was approximately 40 miles away; so steered toward it. It was at night; so I started scanning my Enroute Chart to find the intersection and how it was going to intercept V51. I couldn't find either the intersection or V51 nearby (although I was familiar with the airway; but couldn't place where); even though my Garmin 530W clearly showed the intersection location with no problem. There was only about a couple of minutes after receiving this clearance; when the Controller came back and said that it wouldn't work; and would give a new one in a couple of minutes. I figured it was due the same problem I was having with V51. I suggested that after NANNC; go direct to 4A4; which he replied he was working on. About minute later; he gave me a new clearance 'After NANNC; direct 4A4.' This was no problem; so I ended my search V51. After the flight; I wanted to know why I couldn't find the intersection or V51 on my Enroute Maps right away. When that didn't work; I finally figured out that since the GPS found it; it must be on a STAR; SID or Approach Plate. It turned out that NANNC is a fix for the 'DIFFI ONE ARRIVAL' Atlanta arrival. I don't know why I thought I heard 'Victor'; but the DIFFI ONE; sounded like '51'; and I don't remember ever hearing the word 'Arrival' in the clearance. Interesting enough; I repeated the instructions as 'After NANNC Intersection; intercept V51; then direct'; which ATC Controller didn't catch the Victor or the missing word 'Arrival' either. I guess; by the book; I shouldn't have accepted the clearance until I found it on the map; or responded that I couldn't find it; but since I clearly had the intersection and almost 20 minutes to find V51; it wouldn't be a problem; and the ATC Controller didn't question my reply either. It was resolved so quickly; it became a non-issue. Bottom line; I think the name 'DIFFI One' sounds too close to '51'; which started and caused the confusion in the first place; so I would recommend that the name be changed. As a side note; on my side; reception of ATC radio was very clear; as was the Controller's speech. I had no problem understanding instructions. Thank You for your help.

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.