Narrative:

Scheduled flight from ewr to las. The route of flight is bulk stored as: ewr..eliot.J80.etx.J60.hve.CROWE5.las. Due to en route WX etc, I asked for and received approval from cfcf to operate this flight along a route: ewr..lanna.J48..J230.air.J110.fmn.J64.tbc.J76.tbc.J76.right ennt..crowe.CROWE6.las. The J1120 routing was filed with center and the release was sent to the captain predicated on this route which required 1300 pounds less fuel than the bulk stored route. Company airlines knew the dispatch system delivered the correct release but it apparently gave the captain the wrong flight plan showing the original bulk stored routing. This problem of incorrect flight plans and bogus releases being delivered to company crews by the new dispatch system is well known and documented by the dispatchers, management, and the system vendor. In this particular case once again a crew could have accepted 'cleared as filed' and upon departure mistakenly operated into a traffic conflict situation. Secondly the crew could have departed and flown the routing on the flight plan mistakenly which would leave them 1300 pounds short of their planned fuel over las. A third problem is that the medium large transport requires 'terrain clearance' performance data along either of the rtes and the data for the route dispatched on could well be different than the data for the route flown. I am aware of these problems in company's dispatch system and as a dispatcher I do all I can to insure that they do not occur however the FAA approved dispatch system I am given to use still manages to defeat my efforts to maintain a safe and legal operation on my flts.

Related reports:

Google
 

Original NASA ASRS Text

Title: 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.

Data retrieved from NASA's ASRS site as of July 2007 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.