MLG FLEW THE WRONG ROUTE.
Synopsis
MLG FLEW THE WRONG ROUTE.
Narrative
I CALLED CLRNC DELIVERY IN LAS FOR OUR CLRNC TO ORD. THERE WAS NO FLT PLAN IN THE COMPUTER. I CALLED OUR COMPANY OPS IN LAS AND ASKED THEM TO CALL DISPATCH AND REQUEST THEM TO FILE ANOTHER PLAN. MEANWHILE OUR SCHEDULED DEP TIME HAD COME AND GONE. CLRNC DELIVERY SUGGESTED THAT WE CALL RNO FSS AND FILE THE FLT PLAN OURSELVES; WHICH WE DID. THE ROUTING WE FILED WAS DIFFERENT THAN THE ONE FILED BY THE COMPANY. WE FILED J146 TO PAWNEE CITY; THE COMPANY FILED J146 TO BLUE MESA; THEN J128 DBQ. WHEN WE FINALLY RECEIVED OUR CLRNC WE RECEIVED THE STANDARD 'CLRED AS FILED' CLRNC; WE ASSUMED THAT THE CLRNC WAS FOR THE FLT PLAN WE FILED; BUT APPARENTLY IT WAS GENERATED FROM THE COMPANY FILED PLAN. FOR OBVIOUS REASONS AT BLUE MESA VORTAC WE PROCEEDED OUT J146 AS OPPOSED TO J128. AT APPROX 17 MI OUT OF BLUE MESA ON J146; ZDV CALLED US AND ASKED ABOUT OUR ROUTING. AFTER A SHORT DISCUSSION ABOUT OUR ROUTING; HE AMENDED OUR ROUTING TO J146 PAWNEE CITY; ETC. I DO NOT BELIEVE THERE WAS A CONFLICT OF TFC. SOLUTION: WHEN A POTENTIAL EXISTS FOR CONFUSION ON ROUTINGS OR ALTS; THE CREW SHOULD ASK FOR A FULL ROUTE CLRNC. THE CTLR WORKING CLRNC DELIVERY SHOULD ALSO BE AWARE OF POSSIBLE CONFUSION WHEN THE NORMALLY FILED FLT PLAN IS NOT IN THE COMPUTER AND HE REQUESTS THE CREW TO FILE IT.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.