Flight plan did not reflect the current load of the aircraft.

Attributes
ACN	190774
Time
Date	199110
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : rbg
State Reference	OR
Altitude	msl bound lower : 34500 msl bound upper : 37000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zse
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Flight Phase	climbout : intermediate altitude
Route In Use	enroute airway : j589
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 250 flight time total : 5000 flight time type : 2500
ASRS Report	190774
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	non adherence : far other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

This problem is one of an operational matter. Paperwork for the flight received by the captain did not contain updated load information. The flight plan data generated and utilized by the flight crew showed cruise to be FL370 for the planned weight at time that dispatch filed flight plan. When crew pulled flight plan and tps data the tps data reflected a new load situation due to a cancellation of a flight prior to our departure. Basically what happened is that we didn't recognize the discrepancy in data that was used to generate the flight plan and tps until climbing to altitude. We then realized that we would be operationally unable to climb to altitude filed on original flight plan data. No safety problems were encountered but the potential for climb beyond operational performance ability of aircraft existed. Inquire after event found that dispatch had failed to update flight plan with new load data which would have restr use to a lower altitude. Suggested that a software remedy be implemented which would prevent pilot or anyone from pulling up flight plan and load simultaneously where input data used for both has such a large discrepancy.

Original NASA ASRS Text

Title: 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.

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