Narrative:

After takeoff, we were unable to contact departure control on the frequency assigned by the ACARS obtained pre-departure clearance. By switching back to tower frequency we obtained the correct departure control frequency. Ny departure inquired as to our reasons for maintaining 2000 ft and squawking the incorrect transponder code. Further examination of our ACARS pre-departure clearance revealed that we had received the clearance for flight XXX, lax to ewr instead of the correct flight YYY, ewr-lax. Both the FMC loaded flight plan and ACARS preflight data contained the proper data for our flight. Subsequent requests for flight plan clrncs produced the correct clearance. The reason for the incorrect clearance is undetermined at this time. In the future, increased attention to detail will prevent this incident from reoccurring.

Google
 

Original NASA ASRS Text

Title: FLC ACCEPTED A CLRNC MEANT FOR ANOTHER FLT ON THEIR ACARS.

Narrative: AFTER TKOF, WE WERE UNABLE TO CONTACT DEP CTL ON THE FREQ ASSIGNED BY THE ACARS OBTAINED PRE-DEP CLRNC. BY SWITCHING BACK TO TWR FREQ WE OBTAINED THE CORRECT DEP CTL FREQ. NY DEP INQUIRED AS TO OUR REASONS FOR MAINTAINING 2000 FT AND SQUAWKING THE INCORRECT XPONDER CODE. FURTHER EXAMINATION OF OUR ACARS PRE-DEP CLRNC REVEALED THAT WE HAD RECEIVED THE CLRNC FOR FLT XXX, LAX TO EWR INSTEAD OF THE CORRECT FLT YYY, EWR-LAX. BOTH THE FMC LOADED FLT PLAN AND ACARS PREFLT DATA CONTAINED THE PROPER DATA FOR OUR FLT. SUBSEQUENT REQUESTS FOR FLT PLAN CLRNCS PRODUCED THE CORRECT CLRNC. THE REASON FOR THE INCORRECT CLRNC IS UNDETERMINED AT THIS TIME. IN THE FUTURE, INCREASED ATTN TO DETAIL WILL PREVENT THIS INCIDENT FROM REOCCURRING.

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.