Narrative:

We downloaded via datalink our route per the new sabre flight plan. When we received our clearance by radio from mex clearance delivery; it was slightly different from what we were filed. We were filed apn UJ15 tam J177.... We were cleared BETER4 departure to beter then as filed (which is what was read back). During climbout; after passing beter; ATC asked if we were proceeding direct tam. We responded we were proceeding to xosox; UJ15 to tam. Nothing else was said by ATC; but we thought is was a strange question; so we looked back at the departure; and noted that beter intersection is not on UJ15. We concluded that we possibly should have joined J177 at beter and proceeded via J177 to tam. I think a combination of clearance delivery ambiguity and non-standard delivery may have lead to the confusion. Also; the fact that we were having additional trouble obtaining revised takeoff data via ACARS; may have lead to the distraction of not entering the correct routing.

Google
 

Original NASA ASRS Text

Title: An Airbus crew new to the SABRE format; misread a SABRE flight plan FMGC presentation and after departing MEX. They had a track deviation because they failed to recognized a difference in the Clearance Delivery routing.

Narrative: We downloaded via datalink our route per the new Sabre flight plan. When we received our clearance by radio from MEX clearance delivery; it was slightly different from what we were filed. We were filed APN UJ15 TAM J177.... We were cleared BETER4 departure to BETER then as filed (which is what was read back). During climbout; after passing BETER; ATC asked if we were proceeding direct TAM. We responded we were proceeding to XOSOX; UJ15 to TAM. Nothing else was said by ATC; but we thought is was a strange question; so we looked back at the departure; and noted that BETER intersection is not on UJ15. We concluded that we possibly should have joined J177 at BETER and proceeded via J177 to TAM. I think a combination of Clearance Delivery ambiguity and non-standard delivery may have lead to the confusion. Also; the fact that we were having additional trouble obtaining revised Takeoff Data via ACARS; may have lead to the distraction of not entering the correct routing.

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