Narrative:

Because of an inoperative performance computer; we sent an ACARS message to dispatch just before pushback requesting the numbers. The message was formatted like this; providing the zero fuel weight and takeoff weight. Performance computer inoperative: 115755; 143654; runway xx left/right please. We received a message back with this data: assumed temperature 55 degrees; flaps 5 degrees; V1 121; VFR vr 121; V2 126. The message began with the assumed temperature and finished with the single engine procedure. We entered the numbers; accomplished the pushback and took off. As we were accelerating; the thought crossed my mind that we were not accelerating quite as quickly as normal; but I dismissed it because we were very heavy; so it was not going to exactly jump off the runway. When the first officer rotated; the airplane flew but again I had that feeling that we were not performing like normal and it was kind of 'mushy' or nose-high. Once we got to altitude; we discussed it and discovered we both had the same thoughts and impressions. I pulled out the fom to see if I could double-check the numbers and found there are no tables or graphs that would supply a rotation speed or a V2 speed based on weight. Additionally; the fom specifies what information we need to receive back from dispatch and we received what is specified in the fom. However; I also noticed that when we took off from lax the leg prior; the first part of the message from dispatch included the input data where the message did not. I am sure you know what we thought next! We must have taken off with data based on the zero fuel weight of 115755 instead of our actual takeoff weight of 143654! Could that really be what happened? Yes; that is exactly what happened and a series of messages with dispatch confirmed that. Here is what I think happened and the human factors involved. My first question to dispatch was if they need both the zero fuel weight and the takeoff weight from us or just the takeoff weight. It turns out they only need the takeoff weight; even though we supplied both numbers because that is what we need when we run the performance computer. I also asked about how the numbers get from their on-screen 'performance computer surrogate' to the ACARS screen and they have to perform a 'copy and paste;' just like I do in microsoft word as I type this up. Dispatch also pointed out that they supply the input data as part of the return message as a crosscheck to avoid any problems or confusion. Let me point out here that the fom doesn't currently require that information to be included; even though I think it is excellent to have it. So; bottom line; the dispatcher was probably busy or in a hurry and grabbed the first number from our initial message -- the zero fuel weight of 115755 instead of the takeoff weight of 143654 and ran the number with that. Next; during the 'copy and paste' process; the result on screen got highlighted from the 'assumed temperature' to the end of the output instead of from the very beginning where it shows the input data. I don't know if that was intentional because it still included the required data or if the dispatcher intended to highlight the whole thing and it just didn't happen. I would like to think that we would have noticed during the review of the data that the wrong weight was used (can't guarantee it!) but the way it occurred; we had no chance at all. Dispatch later confirmed that the correct numbers should have been: assumed temperature 48 degrees; flaps 5 degrees; V1 127; VFR vr 137; V2 140. We rotated 16 KTS slow! Had the rotation been abrupt we could have drug the tail. Worse; had we lost an engine we could have ended up in the water. I later beat myself up for not noticing the numbers just didn't look right. I thought back to the 'old days' when the first officer did the data out of a book and I had some mental math (long since forgotten!) on what the V2 speed should be as a quick check of his work. I even won a few beer

Related reports:

Google
 

Original NASA ASRS Text

Title: After sluggish takeoff and initial climb; B737 flight crew discovered that takeoff data received over ACARS was for their zero fuel weight and not the actual takeoff weight. Chain of errors between crew and dispatch is discussed.

Narrative: Because of an inoperative performance computer; we sent an ACARS message to Dispatch just before pushback requesting the numbers. The message was formatted like this; providing the Zero Fuel Weight and Takeoff Weight. Performance computer inoperative: 115755; 143654; Runway XX left/right please. We received a message back with this data: Assumed temperature 55 degrees; flaps 5 degrees; V1 121; VFR VR 121; V2 126. The message began with the assumed temperature and finished with the single engine procedure. We entered the numbers; accomplished the pushback and took off. As we were accelerating; the thought crossed my mind that we were not accelerating quite as quickly as normal; but I dismissed it because we were very heavy; so it was not going to exactly jump off the runway. When the First Officer rotated; the airplane flew but again I had that feeling that we were not performing like normal and it was kind of 'mushy' or nose-high. Once we got to altitude; we discussed it and discovered we both had the same thoughts and impressions. I pulled out the FOM to see if I could double-check the numbers and found there are no tables or graphs that would supply a rotation speed or a V2 speed based on weight. Additionally; the FOM specifies what information we need to receive back from Dispatch and we received what is specified in the FOM. However; I also noticed that when we took off from LAX the leg prior; the first part of the message from Dispatch included the input data where the message did not. I am sure you know what we thought next! We must have taken off with data based on the Zero Fuel Weight of 115755 instead of our actual Takeoff Weight of 143654! Could that really be what happened? Yes; that is exactly what happened and a series of messages with Dispatch confirmed that. Here is what I think happened and the human factors involved. My first question to Dispatch was if they need both the Zero Fuel Weight and the Takeoff Weight from us or just the Takeoff Weight. It turns out they only need the Takeoff Weight; even though we supplied both numbers because that is what we need when we run the performance computer. I also asked about how the numbers get from their on-screen 'Performance Computer Surrogate' to the ACARS screen and they have to perform a 'copy and paste;' just like I do in Microsoft Word as I type this up. Dispatch also pointed out that they supply the input data as part of the return message as a crosscheck to avoid any problems or confusion. Let me point out here that the FOM doesn't currently require that information to be included; even though I think it is excellent to have it. So; bottom line; the Dispatcher was probably busy or in a hurry and grabbed the first number from our initial message -- the Zero Fuel Weight of 115755 instead of the Takeoff Weight of 143654 and ran the number with that. Next; during the 'copy and paste' process; the result on screen got highlighted from the 'Assumed Temperature' to the end of the output instead of from the very beginning where it shows the input data. I don't know if that was intentional because it still included the required data or if the Dispatcher intended to highlight the whole thing and it just didn't happen. I would like to think that we would have noticed during the review of the data that the wrong weight was used (can't guarantee it!) but the way it occurred; we had no chance at all. Dispatch later confirmed that the correct numbers should have been: Assumed Temperature 48 degrees; flaps 5 degrees; V1 127; VFR VR 137; V2 140. We rotated 16 KTS slow! Had the rotation been abrupt we could have drug the tail. Worse; had we lost an engine we could have ended up in the water. I later beat myself up for not noticing the numbers just didn't look right. I thought back to the 'old days' when the First Officer did the data out of a book and I had some mental math (long since forgotten!) on what the V2 speed should be as a quick check of his work. I even won a few beer

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.