Narrative:

We had begun our let down into bna on the VOLLS7 arrival. Our clearance from ZZZ was ...atl.gqo.Volls7 into bna. Before reaching atl; a center controller recleared us to atl and the Volls7 arrival. At this point; I checked the FMS and noted we were already going direct atl and gqo was the next waypoint. Everything seemed fine. A couple of minutes after crossing the atl VOR; center asked where we were proceeding. I replied to gqo (choo-choo VOR). She stated that there was another point on the arrival; but to contact the next center frequency. We contacted the next frequency and all seemed forgotten. Normal flight. While proceeding to gqo; I studied the Volls7 arrival more closely and saw for the first time (onxuv) between atl and gqo. It has different symbology than other intersections; and is in parentheses unlike all other intersections on the arrival into bna. I asked the controller if he knew about this intersection; and he replied to let him check on it. Later; I believe he said he did not. He did not complain about us not going over it or any other traffic conflict in the area. It would have been only a very minor turn for a very short distance for our flight that day on the arrival. Also; this fix is almost impossible to pronounce. I believe everyone would need it spelled out to get this programmed correctly. After landing and studying the flight; I should have been more diligent upon receiving a re-clearance to atl and the VOLLS7 arrival. I took the clearance for granted as local knowledge. We almost always get direct volls or gqo; however that day; we had to do the entire transition from atl VOR. I will cross reference the chart and FMS more as a result. Callback conversation with reporter revealed the following information: the reporter states that the subtle difference between the original clearance and the new clearance went unnoticed causing the way point to be bypassed.

Google
 

Original NASA ASRS Text

Title: CE750 Captain reports bypassing ONXUV way point on the VOLLS7 to BNA. Original clearance was ATL GQO VOLLS7 and flight was recleared ATL VOLLS7. Way point name is unpronounceable.

Narrative: We had begun our let down into BNA on the VOLLS7 arrival. Our clearance from ZZZ was ...ATL.GQO.Volls7 into BNA. Before reaching ATL; a Center Controller recleared us to ATL and the Volls7 arrival. At this point; I checked the FMS and noted we were already going direct ATL and GQO was the next waypoint. Everything seemed fine. A couple of minutes after crossing the ATL VOR; Center asked where we were proceeding. I replied to GQO (Choo-Choo VOR). She stated that there was another point on the arrival; but to contact the next Center frequency. We contacted the next frequency and all seemed forgotten. Normal flight. While proceeding to GQO; I studied the Volls7 arrival more closely and saw for the first time (ONXUV) between ATL and GQO. It has different symbology than other intersections; and is in parentheses unlike all other intersections on the arrival into BNA. I asked the Controller if he knew about this intersection; and he replied to let him check on it. Later; I believe he said he did not. He did not complain about us not going over it or any other traffic conflict in the area. It would have been only a very minor turn for a very short distance for our flight that day on the arrival. Also; this fix is almost impossible to pronounce. I believe everyone would need it spelled out to get this programmed correctly. After landing and studying the flight; I should have been more diligent upon receiving a re-clearance to ATL and the VOLLS7 arrival. I took the clearance for granted as local knowledge. We almost always get direct VOLLS or GQO; however that day; we had to do the entire transition from ATL VOR. I will cross reference the chart and FMS more as a result. Callback conversation with Reporter revealed the following information: The Reporter states that the subtle difference between the original clearance and the new clearance went unnoticed causing the way point to be bypassed.

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.