ACR DISPATCHER'S COMPLAINT THAT THE FILED PLAN IS NOT ALWAYS DELIVERED TO THE FLC. PROBLEM IS EXACERBATED WHEN DISPATCH FILES FOR A RTE OTHER THAN THE BULK STORED RTE.

Narrative

SCHEDULED FLT FROM EWR TO LAS. THE RTE OF FLT IS BULK STORED AS: EWR..ELIOT.J80.ETX.J60.HVE.CROWE5.LAS. DUE TO ENRTE WX ETC; I ASKED FOR AND RECEIVED APPROVAL FROM CFCF TO OPERATE THIS FLT ALONG A RTE: EWR..LANNA.J48..J230.AIR.J110.FMN.J64.TBC.J76.TBC.J76.R ENNT..CROWE.CROWE6.LAS. THE J1120 ROUTING WAS FILED WITH CENTER AND THE RELEASE WAS SENT TO THE CAPT PREDICATED ON THIS RTE WHICH REQUIRED 1300 POUNDS LESS FUEL THAN THE BULK STORED RTE. COMPANY AIRLINES KNEW THE DISPATCH SYS DELIVERED THE CORRECT RELEASE BUT IT APPARENTLY GAVE THE CAPT THE WRONG FLT PLAN SHOWING THE ORIGINAL BULK STORED ROUTING. THIS PROBLEM OF INCORRECT FLT PLANS AND BOGUS RELEASES BEING DELIVERED TO COMPANY CREWS BY THE NEW DISPATCH SYS IS WELL KNOWN AND DOCUMENTED BY THE DISPATCHERS; MGMNT; AND THE SYS VENDOR. IN THIS PARTICULAR CASE ONCE AGAIN A CREW COULD HAVE ACCEPTED 'CLRED AS FILED' AND UPON DEP MISTAKENLY OPERATED INTO A TFC CONFLICT SITUATION. SECONDLY THE CREW COULD HAVE DEPARTED AND FLOWN THE ROUTING ON THE FLT PLAN MISTAKENLY WHICH WOULD LEAVE THEM 1300 POUNDS SHORT OF THEIR PLANNED FUEL OVER LAS. A THIRD PROBLEM IS THAT THE MLG REQUIRES 'TERRAIN CLRNC' PERFORMANCE DATA ALONG EITHER OF THE RTES AND THE DATA FOR THE RTE DISPATCHED ON COULD WELL BE DIFFERENT THAN THE DATA FOR THE RTE FLOWN. I AM AWARE OF THESE PROBLEMS IN COMPANY'S DISPATCH SYS AND AS A DISPATCHER I DO ALL I CAN TO INSURE THAT THEY DO NOT OCCUR HOWEVER THE FAA APPROVED DISPATCH SYS I AM GIVEN TO USE STILL MANAGES TO DEFEAT MY EFFORTS TO MAINTAIN A SAFE AND LEGAL OP ON MY FLTS.