Narrative:

During the process of preparing for a late departure from phl, approximately 35 mins late, we accepted weight and balance data intended for another aircraft. Weight and balance data was normally sent by ACARS. That night we had to receive it by radio via company operations. Traffic on the radio was heavy as usual. We were nearing the #1 position for takeoff. The captain called the company for the weight and balance data. He read out the numbers, I plugged them into the FMC and monitored ATC. The numbers seem to match very closely to what I had previously figured out with passenger count, estimated cargo, etc, so nothing seemed strange until we got a message to call dispatch on arrival at our destination. The dispatcher said we left without our data. We did not understand what he was talking about until after further discussion we realize what probably happened. By not verifying our call sign with operations, the captain copied someone else's data. That just happened to be close to ours. The aircraft felt ok, the data was very close to our own precalculations so it seemed correct. In the future we discussed the need, always even with the company along with ATC, to use your complete call sign and verify receiving data with your full call sign.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR MLG MADE A TKOF FROM PHL WITHOUT THE CORRECT WT AND BAL NUMBERS.

Narrative: DURING THE PROCESS OF PREPARING FOR A LATE DEP FROM PHL, APPROX 35 MINS LATE, WE ACCEPTED WT AND BAL DATA INTENDED FOR ANOTHER ACFT. WT AND BAL DATA WAS NORMALLY SENT BY ACARS. THAT NIGHT WE HAD TO RECEIVE IT BY RADIO VIA COMPANY OPS. TFC ON THE RADIO WAS HVY AS USUAL. WE WERE NEARING THE #1 POS FOR TKOF. THE CAPT CALLED THE COMPANY FOR THE WT AND BAL DATA. HE READ OUT THE NUMBERS, I PLUGGED THEM INTO THE FMC AND MONITORED ATC. THE NUMBERS SEEM TO MATCH VERY CLOSELY TO WHAT I HAD PREVIOUSLY FIGURED OUT WITH PAX COUNT, ESTIMATED CARGO, ETC, SO NOTHING SEEMED STRANGE UNTIL WE GOT A MESSAGE TO CALL DISPATCH ON ARR AT OUR DEST. THE DISPATCHER SAID WE LEFT WITHOUT OUR DATA. WE DID NOT UNDERSTAND WHAT HE WAS TALKING ABOUT UNTIL AFTER FURTHER DISCUSSION WE REALIZE WHAT PROBABLY HAPPENED. BY NOT VERIFYING OUR CALL SIGN WITH OPS, THE CAPT COPIED SOMEONE ELSE'S DATA. THAT JUST HAPPENED TO BE CLOSE TO OURS. THE ACFT FELT OK, THE DATA WAS VERY CLOSE TO OUR OWN PRECALCULATIONS SO IT SEEMED CORRECT. IN THE FUTURE WE DISCUSSED THE NEED, ALWAYS EVEN WITH THE COMPANY ALONG WITH ATC, TO USE YOUR COMPLETE CALL SIGN AND VERIFY RECEIVING DATA WITH YOUR FULL CALL SIGN.

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.