HDG TRACK POS DEV.

Narrative

OUR DISPATCHER FILED US ON AN APPARENTLY IRREGULAR; UNAUTH FLT RTE. THERE WAS A NOTE ON OUR FLT PLAN TO GET A FULL READBACK ON OUR CLRNC. OUR PDC CONCURRED WITH OUR FLT PLAN OVER SEVERAL FIXES AND ONTO A VICTOR AIRWAY; THEN AS FILED. THIS SEEMED TO BE IN CONCURRENCE WITH OUR FLT PLAN SO WE PROCEEDED ON THE VICTOR AIRWAY TO FAK; THEN RIC; WHEN ATC ASKED IF WE WERE HDG DIRECT TO RIC. WHEN WE SAID 'NO;' ATC ASKED WHAT OUR FLT PLANNED RTE WAS; WE TOLD THEM. ATC INFORMED US THAT OUR ROUTING WAS WRONG AND CONFLICTED WITH WHAT THEY HAD IN THE COMPUTER. THEY ASKED US TO LET OUR FLT CTLRS KNOW THAT OUR ROUTING WAS NONSTANDARD AND WRONG. WE SAID WE WOULD. SUPPLEMENTAL INFO FROM ACN 301326: THE IFR CLRNC WE RECEIVED FROM OPS WAS A REVISED CLRNC (ATL-EAONE-SPA-J14-GSO-FAK-V16-RIC- KRIC). TO MAKE SURE ATC ROUTING WAS THE SAME; WE CHKED ACARS AND IT INDICATED 'CLRED AS FILED.' WE SHOULD HAVE CONTACTED ATC VIA CLRNC DELIVERY AS THE FAA ROUTING WAS ATL-EAONE-SPA-J14-RIC. OUR FIRST INDICATION WE WERE ON A DIFFERENT RTE CAME WITH A DSCNT CLRNC TO CROSS JAXSN INTXN AT FL190. THIS INTXN WAS NOT ON OUR RTE AS WE WERE NAVING DIRECT FAK. EVIDENTLY; ATC DID NOT HAVE THE 'REVISED' CLRNC; BUT THE ORIGINAL ONE.