Narrative:

Before departure from dfw; I loaded the triss 2 RNAV departure with runway 17R as the active runway. I followed it up with a route and legs check with no discrepancies found. The departure proceeded normally to triss intersection and then apparently we went direct to txk. ATC advised us that we were left of course and queried if we flew over shero intersection. We checked the progress page and found the last point to be triss. I do not know when shero fell out of the route; we did not modify the route after it was loaded. ATC notified us that there was no traffic conflict but that they would file an RNAV route anomaly report.

Google
 

Original NASA ASRS Text

Title: MD80 EXPERIENCES TRACK DEV ON ENRTE TRANSITION PORTION OF TRISS RNAV SID FROM DFW.

Narrative: BEFORE DEP FROM DFW; I LOADED THE TRISS 2 RNAV DEP WITH RWY 17R AS THE ACTIVE RWY. I FOLLOWED IT UP WITH A RTE AND LEGS CHK WITH NO DISCREPANCIES FOUND. THE DEP PROCEEDED NORMALLY TO TRISS INTXN AND THEN APPARENTLY WE WENT DIRECT TO TXK. ATC ADVISED US THAT WE WERE L OF COURSE AND QUERIED IF WE FLEW OVER SHERO INTXN. WE CHKED THE PROGRESS PAGE AND FOUND THE LAST POINT TO BE TRISS. I DO NOT KNOW WHEN SHERO FELL OUT OF THE RTE; WE DID NOT MODIFY THE RTE AFTER IT WAS LOADED. ATC NOTIFIED US THAT THERE WAS NO TFC CONFLICT BUT THAT THEY WOULD FILE AN RNAV RTE ANOMALY RPT.

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.