Narrative:

The captain noticed the bow (basic operating weight) in the preliminary flight data package (pfdp) tool did not match the bow in the weight and balance record in the maintenance log. The maintenance log showed 44;996.49 and the pfdp tool showed 44;996 and the FMS showed 44;997. Since we always round up to the next highest weight for balance purposes we needed the pfdp tool to be updated and show 44;997. We called dispatch so they could contact our flight planning service and have the number changed. Dispatch contacted maintenance I presume to verify the aircraft weight because we were not challenging the weight of the aircraft; we were challenging the weight as shown by the pfdp. What should have been a quick phone call to our flight planning service to change the number turned into a 30 minute delay. We were under the impression that since the numbers was not in agreement one of them needed to be changed. After contacting the chief; who agreed with us that the pfdp number need to be rounded up to 44;997; we were told the numbers were good as they were (at 44;996) and we should complete the flight. Since we were not close to matog it really wasn't an issue so we departed. Maintenance has since changed the maintenance log to read 44;997.00 but that doesn't fix the problem. The pfdp still shows 44;996 as the bow so the pfdp and the maintenance log are still not in agreement only now the difference is higher.

Google
 

Original NASA ASRS Text

Title: A CRJ-700 flight was delayed while the flight crew attempted to obtain weight and balance numbers that met technical requirements for consistency.

Narrative: The Captain noticed the BOW (Basic Operating Weight) in the Preliminary Flight Data Package (PFDP) tool did not match the BOW in the Weight and Balance record in the maintenance log. The Maintenance log showed 44;996.49 and the PFDP tool showed 44;996 and the FMS showed 44;997. Since we ALWAYS round up to the next highest weight for balance purposes we needed the PFDP tool to be updated and show 44;997. We called Dispatch so they could contact our flight planning service and have the number changed. Dispatch contacted Maintenance I presume to verify the aircraft weight because we were not challenging the weight of the aircraft; we were challenging the weight as shown by the PFDP. What should have been a quick phone call to our flight planning service to change the number turned into a 30 minute delay. We were under the impression that since the numbers was not in agreement one of them needed to be changed. After contacting the Chief; who agreed with us that the PFDP number need to be rounded up to 44;997; we were told the numbers were good as they were (at 44;996) and we should complete the flight. Since we were not close to MATOG it really wasn't an issue so we departed. Maintenance has since changed the maintenance log to read 44;997.00 but that doesn't fix the problem. The PFDP still shows 44;996 as the BOW so the PFDP and the maintenance log are still not in agreement only now the difference is higher.

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