Narrative:

We potentially departed [runway] 14L intersection U2 with invalid takeoff performance data. Upon taxi out; ground gave us a confusing taxi clearance. I attempted to write it down; but the controller was too fast. We asked for a re-issuance and were abruptly told to stop; let an rj in front of us; and follow them to 14L. The captain asked for read back of the specific route; but the ground controller directed us again to follow that rj. I wound up glued to the airport page to make sure we were going the right way.just prior to reaching 14L I noticed that 14L was not on our original takeoff performance data. I got a 14L takeoff performance data from ACARS. Then using the QRH I entered X/14L for the intersection and also the code for the wet runway conditions. The V speeds were corrected and entered in the FMC. The captain also asked to remove the data for max power; which I did. The aircraft used an abnormal amount of runway getting to rotation speed. Enroute it became clear after discussion with the captain and getting additional info once at our destination that we needed 14LX data; not 14L.we need increased attention to performance details. I have to say; our manuals don't say a lot about intersection takeoffs other than how to obtain and enter data. It frankly wasn't clear to me until now that 14L and 14LX in this case are two separate runways and two separate sets of takeoff performance data. We had recently been issued guidance on using the QRH in the FMC to correct V speeds for changing runway and weather conditions. I assumed the intersection entry would cover the fact that we were indeed using the intersection and the QRH V speeds would reflect that. I see now that unique performance data is needed for each runway; also another obvious choice to take the full length if in doubt since we did indeed have full length data.

Google
 

Original NASA ASRS Text

Title: A B737NG flight crew recounted problems they encountered while attempting--and failing--to develop accurate takeoff performance data for an intersection takeoff at ORD; using computerized flight deck resources for which they concluded they had not been adequately trained.

Narrative: We potentially departed [Runway] 14L Intersection U2 with invalid takeoff performance data. Upon taxi out; Ground gave us a confusing taxi clearance. I attempted to write it down; but the Controller was too fast. We asked for a re-issuance and were abruptly told to stop; let an RJ in front of us; and follow them to 14L. The Captain asked for read back of the specific route; but the Ground Controller directed us again to follow that RJ. I wound up glued to the airport page to make sure we were going the right way.Just prior to reaching 14L I noticed that 14L was not on our original takeoff performance data. I got a 14L takeoff performance data from ACARS. Then using the QRH I entered X/14L for the intersection and also the code for the wet runway conditions. The V speeds were corrected and entered in the FMC. The Captain also asked to remove the data for max power; which I did. The aircraft used an abnormal amount of runway getting to rotation speed. Enroute it became clear after discussion with the Captain and getting additional info once at our destination that we needed 14LX data; not 14L.We need increased attention to performance details. I have to say; our manuals don't say a lot about intersection takeoffs other than how to obtain and enter data. It frankly wasn't clear to me until now that 14L and 14LX in this case are two separate runways and two separate sets of takeoff performance data. We had recently been issued guidance on using the QRH in the FMC to correct V speeds for changing runway and weather conditions. I assumed the intersection entry would cover the fact that we were indeed using the intersection and the QRH V speeds would reflect that. I see now that unique performance data is needed for each runway; also another obvious choice to take the full length if in doubt since we did indeed have full length data.

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.