B737 crew was given the wrong performance data for takeoff.

Attributes
ACN	413360
Time
Date	199809
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : slc
State Reference	UT
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	climbout : takeoff
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : cfi pilot : flight engineer
Experience	flight time last 90 days : 250 flight time total : 10000 flight time type : 6500
ASRS Report	413360
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact none taken : insufficient time
Consequence	Other
Supplementary
Air Traffic Incident	other

Narrative:

On takeoff in slc, I noticed that our takeoff roll seemed very long compared to the available runway. This is unusual for our B737 which usually is airborne by midfield. The last 2327 ft of runway 16L was closed and under construction. We rotated at our vr speed and became airborne about 1000 ft prior to the barricades. Upon closer inspection of our paperwork, I noticed our flight plan was based on the shortened runway, but our weight and balance was not. It was based on the full length runway. As one of the pilots, I can say ultimately we were responsible. If we would have gone over our weight manifest with a fine tooth comb, we would have caught the error. However, with all the paperwork, ATC, passenger, maintenance, etc, there are so many things to check, one item is easily overlooked. I think acrs and dispatchers should be extra careful to give us, as pilots, accurate numbers. After takeoff we had a completely uneventful flight to ewr.

Original NASA ASRS Text

Title: B737 CREW WAS GIVEN THE WRONG PERFORMANCE DATA FOR TKOF.

Narrative: ON TKOF IN SLC, I NOTICED THAT OUR TKOF ROLL SEEMED VERY LONG COMPARED TO THE AVAILABLE RWY. THIS IS UNUSUAL FOR OUR B737 WHICH USUALLY IS AIRBORNE BY MIDFIELD. THE LAST 2327 FT OF RWY 16L WAS CLOSED AND UNDER CONSTRUCTION. WE ROTATED AT OUR VR SPD AND BECAME AIRBORNE ABOUT 1000 FT PRIOR TO THE BARRICADES. UPON CLOSER INSPECTION OF OUR PAPERWORK, I NOTICED OUR FLT PLAN WAS BASED ON THE SHORTENED RWY, BUT OUR WT AND BAL WAS NOT. IT WAS BASED ON THE FULL LENGTH RWY. AS ONE OF THE PLTS, I CAN SAY ULTIMATELY WE WERE RESPONSIBLE. IF WE WOULD HAVE GONE OVER OUR WT MANIFEST WITH A FINE TOOTH COMB, WE WOULD HAVE CAUGHT THE ERROR. HOWEVER, WITH ALL THE PAPERWORK, ATC, PAX, MAINT, ETC, THERE ARE SO MANY THINGS TO CHK, ONE ITEM IS EASILY OVERLOOKED. I THINK ACRS AND DISPATCHERS SHOULD BE EXTRA CAREFUL TO GIVE US, AS PLTS, ACCURATE NUMBERS. AFTER TKOF WE HAD A COMPLETELY UNEVENTFUL FLT TO EWR.

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.