FLT PLAN DID NOT REFLECT THE CURRENT LOAD OF THE ACFT.
Synopsis
FLT PLAN DID NOT REFLECT THE CURRENT LOAD OF THE ACFT.
Narrative
THIS PROBLEM IS ONE OF AN OPERATIONAL MATTER. PAPERWORK FOR THE FLT RECEIVED BY THE CAPT DID NOT CONTAIN UPDATED LOAD INFO. THE FLT PLAN DATA GENERATED AND UTILIZED BY THE FLC SHOWED CRUISE TO BE FL370 FOR THE PLANNED WT AT TIME THAT DISPATCH FILED FLT PLAN. WHEN CREW PULLED FLT PLAN AND TPS DATA THE TPS DATA REFLECTED A NEW LOAD SITUATION DUE TO A CANCELLATION OF A FLT PRIOR TO OUR DEP. BASICALLY WHAT HAPPENED IS THAT WE DIDN'T RECOGNIZE THE DISCREPANCY IN DATA THAT WAS USED TO GENERATE THE FLT PLAN AND TPS UNTIL CLBING TO ALT. WE THEN REALIZED THAT WE WOULD BE OPERATIONALLY UNABLE TO CLB TO ALT FILED ON ORIGINAL FLT PLAN DATA. NO SAFETY PROBLEMS WERE ENCOUNTERED BUT THE POTENTIAL FOR CLB BEYOND OPERATIONAL PERFORMANCE ABILITY OF ACFT EXISTED. INQUIRE AFTER EVENT FOUND THAT DISPATCH HAD FAILED TO UPDATE FLT PLAN WITH NEW LOAD DATA WHICH WOULD HAVE RESTR USE TO A LOWER ALT. SUGGESTED THAT A SOFTWARE REMEDY BE IMPLEMENTED WHICH WOULD PREVENT PLT OR ANYONE FROM PULLING UP FLT PLAN AND LOAD SIMULTANEOUSLY WHERE INPUT DATA USED FOR BOTH HAS SUCH A LARGE DISCREPANCY.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.