Date: 201401
Local time of day: 1801-2400
Location: JAC.Airport, WY
Weather elements / visibility: Snow; 5
Aircraft: Airbus Industrie Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Dispatch
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Prior to dispatching a flight to JAC; I contacted JAC AIRPORT OPS/RWY CONDITIONS and pulled up the Jackson Hole Airport Runway Conditions PDF file on the internet. JAC MU readings for Runway 01/19 were reporting braking less than good. The Airbus requires MU 40 or above across the board or landing is not authorized. I briefed the crew; advised JAC would continue to groom runways and our plan was to return if unable to land JAC. After takeoff; I advised the crew of a severe turbulence report which was near his planned route of flight; gave him a route alternative with points that would keep him south of the event. He coordinated this new route with ATC. Shortly into the flight; I called JAC for a new braking action report and sent the following via ACARS: GOOD NEWS....AFTER BROOMING RUNWAY 19 MU REPORTING BETTER THAN 40 ACROSS THE BOARD...STILL -SN AND WIND...JAC WILL CONTINUE TO GROOM. I WILL CALL THEM AGAIN IN ABOUT AN HOUR AND FWD INFO TO YOU. LOOKS PROMISING FOR JAC LANDING. He acknowledged. At about 20 minutes from landing; the flight called and told me ATIS was reporting a general aviation braking action report less than good on the last half or third of the runway. He; along with the cockpit occupants; were concerned about the discrepancy between this report and the MU readings. I told him I would get JAC Tower on with us and see if we could get additional information. JAC FAA Tower employee picked up and I identified myself and asked if he would standby for just a moment. I brought the Captain on the line and he asked the employee what he could tell him about the less than braking report. At this point it was the communication between the two was almost unreadable to me; however I was able to understand the following...after communicating to the crew that MU values were; all better than 40; the Captain asked the employee another question. The employee responded with; I'm too busy to talk right now; I got to go and hung up. This wasn't the first time Dispatch has had communication problems with JAC FAA Tower. No dispatcher should be 'afraid' to call any FAA Tower facility when assistance is needed. Among other duties; it is the FAA Tower's responsibility to give advice based on their own observations and experience. This is especially important when; in my case; a diversion was being considered. In the event they're too busy to do their jobs maybe it's time to hire more people.




Synopsis: Air Carrier Dispatcher voiced a complaint regarding the 'Braking Action' reports at JAC; noting the uncooperative nature of ATC personnel regarding information clarification.