Controller climbed air carrier X through atx Y's altitude with less than standard separation. System...

Attributes
ACN	121564
Time
Date	198909
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : pit
State Reference	PA
Altitude	msl bound lower : 5000 msl bound upper : 6000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : pit
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other
Flight Phase	climbout : intermediate altitude
Route In Use	enroute : direct
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air taxi
Make Model Name	Small Transport, Low Wing, 2 Turboprop Eng
Flight Phase	cruise other
Route In Use	enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : departure
Qualification	controller : radar
ASRS Report	121564
Person 2
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	conflict : nmac non adherence : published procedure non adherence : required legal separation
Independent Detector	other controllera other flight crewa
Resolutory Action	flight crew : took evasive action none taken : insufficient time
Consequence	faa : investigated
Miss Distance	vertical : 400
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error Intra Facility Coordination Failure

Narrative:

Air carrier X, medium large transport, departed pit and climbed to 5000 MSL. Atx Y, small transport, inbound on another frequency. I called traffic for air carrier X descending, to 6000 MSL (company). As air carrier X and company passed I climbed air carrier X to 7000 and issued traffic (en route at 8000). Behind and to the right of the company traffic was atx Y. The data blocks must have been overlapped as I did not see the atx Y data block not did I observe the radar target. I went back to air carrier X to issue a turn, when I observed the atx Y radar target and mode C at 6000. Air carrier X was at 5400 or 5500 MSL. I reissued 5000 to air carrier X but as quickly as it happened, the targets passed. Atx Y took evasive action. Workload at the time was heavy. I was coordinating. Local control forgot to turn a departure over to my frequency. Other aircraft were on vectors around traffic. The climb was initiated in another controller's airspace (SOP climbs). Workload and the overlapping data block caused me to loose concentration on the medium large transport (no excuse). More attention should have been given to the traffic.

Original NASA ASRS Text

Title: CTLR CLIMBED ACR X THROUGH ATX Y'S ALT WITH LESS THAN STANDARD SEPARATION. SYSTEM ERROR.

Narrative: ACR X, MLG, DEPARTED PIT AND CLIMBED TO 5000 MSL. ATX Y, SMT, INBND ON ANOTHER FREQ. I CALLED TFC FOR ACR X DESCENDING, TO 6000 MSL (COMPANY). AS ACR X AND COMPANY PASSED I CLIMBED ACR X TO 7000 AND ISSUED TFC (ENRTE AT 8000). BEHIND AND TO THE RIGHT OF THE COMPANY TFC WAS ATX Y. THE DATA BLOCKS MUST HAVE BEEN OVERLAPPED AS I DID NOT SEE THE ATX Y DATA BLOCK NOT DID I OBSERVE THE RADAR TARGET. I WENT BACK TO ACR X TO ISSUE A TURN, WHEN I OBSERVED THE ATX Y RADAR TARGET AND MODE C AT 6000. ACR X WAS AT 5400 OR 5500 MSL. I REISSUED 5000 TO ACR X BUT AS QUICKLY AS IT HAPPENED, THE TARGETS PASSED. ATX Y TOOK EVASIVE ACTION. WORKLOAD AT THE TIME WAS HEAVY. I WAS COORDINATING. LCL CTL FORGOT TO TURN A DEP OVER TO MY FREQ. OTHER ACFT WERE ON VECTORS AROUND TFC. THE CLIMB WAS INITIATED IN ANOTHER CTLR'S AIRSPACE (SOP CLIMBS). WORKLOAD AND THE OVERLAPPING DATA BLOCK CAUSED ME TO LOOSE CONCENTRATION ON THE MLG (NO EXCUSE). MORE ATTN SHOULD HAVE BEEN GIVEN TO THE TFC.

Data retrieved from NASA's ASRS site as of August 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.

Controller climbed air carrier X through atx Y's altitude with less than standard separation. System error.