Departure controller failed to provide standard IFR separation between 2 aircraft under his control.

Attributes
ACN	144472
Time
Date	199004
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : cvg
State Reference	OH
Altitude	msl bound lower : 6000 msl bound upper : 6000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : cvg
Operator	general aviation : personal
Make Model Name	Small Aircraft, Low Wing, 1 Eng, Retractable Gear
Flight Phase	cruise other
Flight Plan	IFR
Aircraft 2
Operator	general aviation : personal
Make Model Name	Light Transport, Low Wing, 2 Turboprop Eng
Flight Phase	climbout : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : departure
Qualification	controller : radar
ASRS Report	144472
Person 2
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private pilot : instrument
Events
Anomaly	conflict : airborne less severe non adherence : published procedure non adherence : required legal separation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

Small aircraft X was an overflt on V128 approaching cvg VOR from the southeast. Light transport Y was a departure from cvg airport turned to a heading to join V128 sebnd. Both aircraft were at 6000'. I, as the controller, saw the problem and took immediate action to resolve the situation by using radar vectors, climb and descend instructions, and finally visibility sep. At the time I was working 2 positions combined. I was working a lot of traffic with several other distrs such as the control tower calling me on the landline to discuss one of the VFR departures. Also ndz calling on the land line for approval request and pointouts. My radar display was also very cluttered with data blocks because I was working departures out under the airspace owned by the arrival controller. There were several arrs and our procedure are to quick look the arrival data blocks so you may use arrival airspace if arrival has no traffic. My data blocks were covered by arrs data blocks. This could possibly be avoided by disallowing 6000' overflts. Because 6000' is a commonly used level-off altitude for our departures. It would also help to have positions decombined.

Original NASA ASRS Text

Title: DEP CTLR FAILED TO PROVIDE STANDARD IFR SEPARATION BETWEEN 2 ACFT UNDER HIS CONTROL.

Narrative: SMA X WAS AN OVERFLT ON V128 APCHING CVG VOR FROM THE SE. LTT Y WAS A DEP FROM CVG ARPT TURNED TO A HDG TO JOIN V128 SEBND. BOTH ACFT WERE AT 6000'. I, AS THE CTLR, SAW THE PROB AND TOOK IMMEDIATE ACTION TO RESOLVE THE SITUATION BY USING RADAR VECTORS, CLB AND DSND INSTRUCTIONS, AND FINALLY VIS SEP. AT THE TIME I WAS WORKING 2 POSITIONS COMBINED. I WAS WORKING A LOT OF TFC WITH SEVERAL OTHER DISTRS SUCH AS THE CTL TWR CALLING ME ON THE LANDLINE TO DISCUSS ONE OF THE VFR DEPS. ALSO NDZ CALLING ON THE LAND LINE FOR APPROVAL REQUEST AND POINTOUTS. MY RADAR DISPLAY WAS ALSO VERY CLUTTERED WITH DATA BLOCKS BECAUSE I WAS WORKING DEPS OUT UNDER THE AIRSPACE OWNED BY THE ARR CTLR. THERE WERE SEVERAL ARRS AND OUR PROC ARE TO QUICK LOOK THE ARR DATA BLOCKS SO YOU MAY USE ARR AIRSPACE IF ARR HAS NO TFC. MY DATA BLOCKS WERE COVERED BY ARRS DATA BLOCKS. THIS COULD POSSIBLY BE AVOIDED BY DISALLOWING 6000' OVERFLTS. BECAUSE 6000' IS A COMMONLY USED LEVEL-OFF ALT FOR OUR DEPS. IT WOULD ALSO HELP TO HAVE POSITIONS DECOMBINED.

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.