FLC OF AN HVT CARGO FLT DEVIATED FROM THEIR PREFILED RTE DUE TO NOT VERIFYING THE RTE PROVIDED BY THE COMPANY WHICH WAS 'LOADED' IN THEIR LONG-RANGE NAV PROGRAM.

Narrative

THIS INCIDENT INVOLVED A DEV FROM A RECEIVED CLRNC FROM LAX INTL CLRNC DELIVERY. OUR LONG RANGE IS OUR PRIMARY NAV REF DURING CRUISE OPS. OUR LRN (LONG-RANGE-NAV) RADIO WAS 2 INDEPENDENT KING KNS 660 TYPES. IT HAS A INTERNAL DATABASE OF (VORTAC; ARPTS; INTXNS; AND A CUSTOMER DEFINED FLT PLAN DATABASE WE ARE ACCUSTOMED TO USING. IT WAS BROUGHT TO OUR ATTN BY ZAB ARTCC THAT WE WERE DEVIATING FROM OUR FILED AND CLRED RTE OF FLT. WITH FURTHER INSPECTION IT WAS REVEALED THAT THEY WERE CORRECT AS OUR COMPANY HAD FILED A NON-STANDARD FLT PLAN RTE WHICH I DID NOT NOTICE DURING THE COCKPIT PREFLT DUTIES. THE COMPANY HAD FILED AN AIRWAYS FLT PLAN RTE. THIS 'AS FILED' AIRWAYS RTE WAS DEVIATED FROM WHEN OUR LRN DIRECT RTING WAS FLOWN. THE INCIDENT OCCURRED DUE TO A LACK OF VIGILANCE ON MY PART AS THE FO. I FEEL THE STANDARD FLT PLAN RTE WAS SO COMMON THAT I PLACED IT IN THE LRN WITHOUT PROPER VERIFICATION. ADDITIONALLY THE CHANGE OF THE INITIAL CLRNC FROM LAXX2 TO SLI2. SLI DEP NECESSITATED ME CONCENTRATING ON EDITING THE INITIAL 3 LEGS OF THE FLT PLAN RTE WHICH MAY HAVE AIDED IN MY MISTAKE OF VERIFICATION OF THE FLT PLAN RTING.