Narrative:

Release 1 was planned by midnight shift with fob 16.8. Scheduled departure xa:00. Captain called at xa:29 to advise that fob was 28.0 in iah. (Flight was already late due to no ground power hooked up to aircraft; and had a faulty APU). In sabre I created rlse (3) to show updated fob of 28.0. At approximately xa:45 captain called and was upset that he was sent weights by load planning there were 'dangerously incorrect.' I confirmed the weight manifest in ACARS still showed the original fob of 16.8I called load planning (omitted) and asked him if he had received a new fuel slip or message that showed the new fob. (Omitted) stated that he had not received anything to show the fob of 16.8. I created rlse 4 in sabre to again show 28.0 fob. I asked omitted if anything had been generated (fuel slip or otherwise) to show the new fob. Omitted stated that nothing was received. Omitted manually updated the dpwm to show 28.0. New weights were sent to the pilot.captain was concerned that this was a dangerous situation; because had he gone based off the weights that load planning had sent them; it would have been a 'bad situation.' I generally don't like to assume; but I was under the assumption that sabre generates a new fuel 'slip' or message to load planning anytime the fob changes. The question being; why didn't anybody in load planning; or ACARS catch these changes? Hindsight; I should have sent a meter to called load planning to advise them of the fob; so that this may have been caught before the weight manifest was sent out to the pilot. Is this an automation issue?

Related reports:

Google
 

Original NASA ASRS Text

Title: Dispatcher encountered difficulty getting the weight and balance program to accept a new fuel load in calculating aircraft weight and takeoff data sent to the crew during preflight. Coordination between the crew and the Dispatcher ensured that Load Planning manually entered the correct fuel load.

Narrative: Release 1 was planned by midnight shift with FOB 16.8. Scheduled departure XA:00. Captain called at XA:29 to advise that FOB was 28.0 in IAH. (Flight was already late due to no ground power hooked up to aircraft; and had a faulty APU). In SABRE I created RLSE (3) to show updated FOB of 28.0. At approximately XA:45 Captain called and was upset that he was sent weights by load planning there were 'dangerously incorrect.' I confirmed the weight manifest in ACARS still showed the original FOB of 16.8I called load planning (Omitted) and asked him if he had received a new fuel slip or message that showed the new FOB. (Omitted) stated that he had not received anything to show the FOB of 16.8. I created RLSE 4 in SABRE to again show 28.0 FOB. I asked Omitted if anything had been generated (fuel slip or otherwise) to show the new FOB. Omitted stated that nothing was received. Omitted manually updated the DPWM to show 28.0. New weights were sent to the pilot.Captain was concerned that this was a dangerous situation; because had he gone based off the weights that load planning had sent them; it would have been a 'bad situation.' I generally don't like to assume; but I was under the assumption that SABRE generates a new fuel 'slip' or MSG to load planning anytime the FOB changes. The question being; why didn't anybody in load planning; or ACARS catch these changes? Hindsight; I should have sent a meter to called Load planning to advise them of the FOB; so that this may have been caught before the weight manifest was sent out to the pilot. Is this an automation issue?

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