DISPATCHER RPT ON DISPATCH RELEASE PROCEDURAL PROBS WITHIN HIS COMPANY.

Narrative

FLT EWR-BUF WITH A B737-300 UNDER PART 121 DOMESTIC. RELIEVED DUTY DISPATCHER WHO HAD DISPATCHED FLT WITH AN ALTERNATE OF SYR. AFTER THE RELIEF AND AN HR BEFORE DEP THE SYR FORECAST AND WX WENT BELOW ALTERNATE MINIMUMS AND BUF RPTED BRAKING ACTION FAIR TO POOR. I AMENDED THE RELEASE AND CHANGED THE RELEASE FUEL TO 1000 LBS TO INHIBIT THE AUTOMATED WT AND BAL SYS FROM PROVIDING THE CAPT ANY PERFORMANCE DATA UNTIL THE CAPT CALLED ME (THE DISPATCHER) TO DISCUSS THE ALTERNATE CHANGE AND THE CURRENT BUF FIELD CONDITIONS. MY ACR USES AN AUTOMATED WT AND BAL SYS THAT WILL GENERATE PAPER WORK TO THE CAPT FOR DEP AND THE DISPATCHER HAS BEEN PROVIDED NO FACILITY TO STOP THIS PROCESS. THE SENDING OF A RELEASE WITH A 1000 LB FUEL LOAD HAS HISTORICALLY BEEN THE ONLY WAY TO STOP A FLT FROM RECEIVING TKOF DATA AND DEPARTING IF THE DISPATCHER NEEDS TO TALK TO THE CAPT BEFORE DEP. UNBEKNOWNST TO THE DISPATCHERS OR THEIR MGMNT SOME OTHER DEPT'S MGMNT HAS HAD THE SYS MODIFIED TO ALLOW THE PAPER WORK TO GO TO THE CAPT IN SPITE OF DISPATCH'S EFFORTS IN A WITLESS ATTEMPT TO REDUCE DELAYS. THE CAPT NOT REALIZING THAT A NEW RELEASE AND REQUEST TO CALL DISPATCH HAD BEEN SENT DEPARTED USING THE OLD RELEASE AND ALTERNATE. ATTEMPTS TO CONTACT THE FLT THROUGH ARINC WERE FRUITLESS AND DISPATCH WAS ONLY ABLE TO CONTACT THE FLT THROUGH BUF OPS RADIO WHEN THE FLT WAS IN RANGE BUF. DISPATCH GAVE THE CURRENT FIELD CONDITIONS AND BRAKING ACTION RPTS BUF AND AMENDED THE RELEASE TO SHOW A SUITABLE ALTERNATE AT THAT TIME. AUTOMATED WT AND BAL SYS THAT DO NOT ALLOW DISPATCHERS OR LOAD PLANNERS TO ABORT THE AUTOMATED PROCESS UNTIL THEY ARE SATISFIED THE CAPT HAS ALL THE NECESSARY INFO REQUIRED FOR SAFETY ARE A CLR AND PRESENT DANGER TO THE SAFETY OF FLT. THE FAA REQUIRES STC'S AND TSO'S FOR EVERY DEVICE ON AN ACFT; BUT HAS NO SPECIFICATIONS FOR COMPUTERIZED SYS THAT ARE USED BY DISPATCH TO PLAN FLTS; OR PROVIDE CRITICAL PERFORMANCE DATA TO THE CREW.