A320 flight crew concerned with location and identify of en route fix to mmun.

Attributes
ACN	726054
Time
Date	200702
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : mmun.airport
Altitude	msl single value : 15000
Environment
Flight Conditions	VMC
Aircraft 1
Controlling Facilities	tracon : mmmx.tracon
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	climbout : intermediate altitude
Route In Use	departure sid : mapan2
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain
Experience	flight time last 90 days : 210 flight time total : 16000 flight time type : 3500
ASRS Report	726054
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	other anomaly other
Independent Detector	other flight crewa other flight crewb
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	Chart Or Publication
Primary Problem	Chart Or Publication

Narrative:

Cancun has moved a navigation intersection; otuni; and reused the previous name of the intersection causing confusion. All databases and charts reflect the 'old' intersection; otuni; location. Cancun is using this 'new' intersection for most arrs. Numerous air carrier's are requiring 2-3 repeats and clarifications of the clearance. Typical clearance is 'cleared direct to otuni and track the cun 316 degree radial to cun.' the 'old' charted otuni is not on the 316 degree radial; so carriers are asking how to transition to the cun 316 degree radial. The 'new' otuni location is on the cun 316 degree radial. There is an airway NOTAM that indicates the intersection has moved and will be corrected in the revised database. Unfortunately; that NOTAM comes at the very end of the flight paperwork after information that is 'old' has reprinted for months (yrs?) and is historical and been incorporated. Cancun references the otuni intersection by radial and DME from cun but the NOTAM refers to the new otuni by latitude and longitude and between existing fixes. Every carrier on the frequency was having trouble with this intersection change.

Original NASA ASRS Text

Title: A320 FLT CREW CONCERNED WITH LOCATION AND IDENT OF ENRTE FIX TO MMUN.

Narrative: CANCUN HAS MOVED A NAV INTXN; OTUNI; AND REUSED THE PREVIOUS NAME OF THE INTXN CAUSING CONFUSION. ALL DATABASES AND CHARTS REFLECT THE 'OLD' INTXN; OTUNI; LOCATION. CANCUN IS USING THIS 'NEW' INTXN FOR MOST ARRS. NUMEROUS ACR'S ARE REQUIRING 2-3 REPEATS AND CLARIFICATIONS OF THE CLRNC. TYPICAL CLRNC IS 'CLRED DIRECT TO OTUNI AND TRACK THE CUN 316 DEG RADIAL TO CUN.' THE 'OLD' CHARTED OTUNI IS NOT ON THE 316 DEG RADIAL; SO CARRIERS ARE ASKING HOW TO TRANSITION TO THE CUN 316 DEG RADIAL. THE 'NEW' OTUNI LOCATION IS ON THE CUN 316 DEG RADIAL. THERE IS AN AIRWAY NOTAM THAT INDICATES THE INTXN HAS MOVED AND WILL BE CORRECTED IN THE REVISED DATABASE. UNFORTUNATELY; THAT NOTAM COMES AT THE VERY END OF THE FLT PAPERWORK AFTER INFO THAT IS 'OLD' HAS REPRINTED FOR MONTHS (YRS?) AND IS HISTORICAL AND BEEN INCORPORATED. CANCUN REFS THE OTUNI INTXN BY RADIAL AND DME FROM CUN BUT THE NOTAM REFERS TO THE NEW OTUNI BY LATITUDE AND LONGITUDE AND BTWN EXISTING FIXES. EVERY CARRIER ON THE FREQ WAS HAVING TROUBLE WITH THIS INTXN CHANGE.

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