Operational error -- misidented aircraft.

Attributes
ACN	284243
Time
Date	199409
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : mem
State Reference	TN
Altitude	msl bound lower : 3000 msl bound upper : 3000
Environment
Flight Conditions	IMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : mem
Operator	common carrier : air carrier
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 121
Flight Phase	climbout : intermediate altitude climbout : takeoff
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 121
Flight Phase	climbout : intermediate altitude climbout : takeoff
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : departure
Qualification	controller : radar
Experience	controller radar : 4
ASRS Report	284243
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	non adherence : published procedure non adherence : required legal separation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance none taken : detected after the fact other
Consequence	Other
Miss Distance	horizontal : 4080 vertical : 200
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

I was working departure east and decombining the position (briefing the arrival controller), when the first aircraft called (aircraft a). I told him he was radar contact and turned him right to 100 degrees and climbed him to 16000 ft. I noticed the aircraft I idented was squawking the wrong transponder code, so I told him to squawk the right code, he replied 'I'm showing the right code, standby 1 second.' I thought he was going to fix this problem. Well, a few seconds passed (about 15) and then a second aircraft called (aircraft B). At this moment the first aircraft tagged up and was headed right for the aircraft I had mistakenly idented. I idented aircraft B and told aircraft B to squawk the appropriate transponder code. I then immediately turned aircraft a further right heading 120 degrees and expedited his climb. Aircraft a passed behind aircraft B. Aircraft a was 200 ft above and climbing and 68 mi behind aircraft B. There were 3 or 4 factors that caused this to happen. The main problem was I misidented an aircraft, but additionally, aircraft B was on the wrong code, aircraft B was supposed to call me on departure first but didn't.

Original NASA ASRS Text

Title: OPERROR -- MISIDENTED ACFT.

Narrative: I WAS WORKING DEP E AND DECOMBINING THE POS (BRIEFING THE ARR CTLR), WHEN THE FIRST ACFT CALLED (ACFT A). I TOLD HIM HE WAS RADAR CONTACT AND TURNED HIM R TO 100 DEGS AND CLBED HIM TO 16000 FT. I NOTICED THE ACFT I IDENTED WAS SQUAWKING THE WRONG XPONDER CODE, SO I TOLD HIM TO SQUAWK THE RIGHT CODE, HE REPLIED 'I'M SHOWING THE RIGHT CODE, STANDBY 1 SECOND.' I THOUGHT HE WAS GOING TO FIX THIS PROB. WELL, A FEW SECONDS PASSED (ABOUT 15) AND THEN A SECOND ACFT CALLED (ACFT B). AT THIS MOMENT THE FIRST ACFT TAGGED UP AND WAS HEADED RIGHT FOR THE ACFT I HAD MISTAKENLY IDENTED. I IDENTED ACFT B AND TOLD ACFT B TO SQUAWK THE APPROPRIATE XPONDER CODE. I THEN IMMEDIATELY TURNED ACFT A FURTHER R HDG 120 DEGS AND EXPEDITED HIS CLB. ACFT A PASSED BEHIND ACFT B. ACFT A WAS 200 FT ABOVE AND CLBING AND 68 MI BEHIND ACFT B. THERE WERE 3 OR 4 FACTORS THAT CAUSED THIS TO HAPPEN. THE MAIN PROB WAS I MISIDENTED AN ACFT, BUT ADDITIONALLY, ACFT B WAS ON THE WRONG CODE, ACFT B WAS SUPPOSED TO CALL ME ON DEP FIRST BUT DIDN'T.

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.