An air carrier large transport crew flew the wrong routing with the wrong transponder squawk.

Attributes
ACN	251969
Time
Date	199309
Day	Tue
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : phx
State Reference	AZ
Altitude	agl bound lower : 0 agl bound upper : 8000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	artcc : zab
Operator	common carrier : air carrier
Make Model Name	Large Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other Other
Flight Phase	climbout : initial ground : preflight
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : flight engineer
Experience	flight time last 90 days : 210 flight time total : 10000 flight time type : 2500
ASRS Report	251969
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	non adherence : clearance other anomaly other other anomaly other
Independent Detector	other controllera
Resolutory Action	other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation
Situations
ATC Facility	procedure or policy : unspecified

Narrative:

The flight crew was given correct flight plan, WX, fuel slip, weight and balance but the wrong printed pre departure clearance. The first officer checked it, inserted the squawk for another flight due out about the same time. I checked and read the pre departure clearance, checked the squawk and departure control frequency, but somehow missed that the information was for a different flight. At takeoff, I called departure control, climbing to 3000 ft. Departure rogered with no other comment. Shortly, he began calling another flight (the flight whose squawk we were on I later realized). I sensed something amiss and called approaching 8000 ft. Departure said call departure on another frequency and 'you're on the wrong squawk.' the new departure frequency had us change to the correct code and nothing more was said about a conflict or problem. Solutions: we both check for just such a foul up, but this event will make me even more vigilant. Some airports require aircraft to call for taxi, with the squawk. This is a good xchk, and really should be required everywhere. Also, departure could have been a little more vigilant. I did call the correct flight number climbing to 3000 ft. If he saw a blip labeled as a different flight climbing to 3000 ft, I wish he had questioned it.

Original NASA ASRS Text

Title: AN ACR LGT CREW FLEW THE WRONG ROUTING WITH THE WRONG XPONDER SQUAWK.

Narrative: THE FLC WAS GIVEN CORRECT FLT PLAN, WX, FUEL SLIP, WT AND BAL BUT THE WRONG PRINTED PDC. THE FO CHKED IT, INSERTED THE SQUAWK FOR ANOTHER FLT DUE OUT ABOUT THE SAME TIME. I CHKED AND READ THE PDC, CHKED THE SQUAWK AND DEP CTL FREQ, BUT SOMEHOW MISSED THAT THE INFO WAS FOR A DIFFERENT FLT. AT TKOF, I CALLED DEP CTL, CLBING TO 3000 FT. DEP ROGERED WITH NO OTHER COMMENT. SHORTLY, HE BEGAN CALLING ANOTHER FLT (THE FLT WHOSE SQUAWK WE WERE ON I LATER REALIZED). I SENSED SOMETHING AMISS AND CALLED APCHING 8000 FT. DEP SAID CALL DEP ON ANOTHER FREQ AND 'YOU'RE ON THE WRONG SQUAWK.' THE NEW DEP FREQ HAD US CHANGE TO THE CORRECT CODE AND NOTHING MORE WAS SAID ABOUT A CONFLICT OR PROB. SOLUTIONS: WE BOTH CHK FOR JUST SUCH A FOUL UP, BUT THIS EVENT WILL MAKE ME EVEN MORE VIGILANT. SOME ARPTS REQUIRE ACFT TO CALL FOR TAXI, WITH THE SQUAWK. THIS IS A GOOD XCHK, AND REALLY SHOULD BE REQUIRED EVERYWHERE. ALSO, DEP COULD HAVE BEEN A LITTLE MORE VIGILANT. I DID CALL THE CORRECT FLT NUMBER CLBING TO 3000 FT. IF HE SAW A BLIP LABELED AS A DIFFERENT FLT CLBING TO 3000 FT, I WISH HE HAD QUESTIONED IT.

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.