B737 Undifferentiated or Other Model
Flight Crew Last 90 Days 177; Flight Crew Total 7700; Flight Crew Type 2150
Situational Awareness
Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance
Flight Crew Took Evasive Action
Equipment / Tooling; Human Factors
I received final weights before pushback. I appropriately carried over the final weight information and loaded the departure runway; 4L; and our gate weight and runway conditions. Moments later we received the takeoff data and I accepted the V Speeds prompt; then showed the Captain the weight message and Takeoff Data printouts side by side as I always do so both pilots verify the information. We agreed to commence the pushback checklist; but then he paused and suggested we review the Takeoff Data one more time; citing it didn't look quite right. After we both scrutinized the Takeoff Data Message for some time (at the gate; no pushback occurred); the Captain thought we may be looking at takeoff data FOR THE ARRIVAL CITY not the departure city. Runways at both airports have same numerical assignment (RWY 4L). We checked every single page of the ACARS initialization page and found the flight number; departure city; arrival city; all correct. Release correct. Before initiating any 'reset' or 'start all over' process; I suggested we call our dispatcher and describe the anomaly. Captain telephoned our dispatcher who had no answer as to the cause; but pushed the Takeoff Data 4L to the aircraft printer and we manually loaded the performance from the dispatcher's Takeoff Data printout into the Perf Page in ACARS. I attached images of the weight message; the erroneous Takeoff Data Message showing 4L at the arrival city; and the dispatcher's 4L Takeoff Data message for the actual departure airport he pushed to our printer himself. While standardization; proper CRM; and crew attention to detail resulted in a safe; legal departure; it is concerning that [the computer software] can give us Takeoff Data to the exact same numbered runway; but for the destination airport not the departure airport. In a rushed; fatigued; busy airport environment; or had there been an inexperienced crew in our shoes; a departure could have occurred without correct [though more conservative] takeoff data in the FMC.
Air Carrier First Officer; planning on departing Runway 4L reports receiving V speeds for Runway 4L at the arrival airport. The Captain caught the error during the takeoff briefing and the crew contacted their Dispatcher; who could not explain the error but sent new data.