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

Date: 1991-11 · Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng

Anomalies: deviation-discrepancy-procedural-far

Synopsis

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.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.