A departing atx was issued a climb and vector that conflicted with opposite direction traffic.

Attributes
ACN	118214
Time
Date	198907
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : mkc airport : mci
State Reference	MO
Altitude	msl bound lower : 10000 msl bound upper : 11000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : mci tower : oma
Operator	general aviation : personal
Make Model Name	Small Aircraft, High Wing, 1 Eng, Retractable Gear
Flight Phase	cruise other
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air taxi
Make Model Name	Light Transport, High Wing, 2 Turboprop Eng
Flight Phase	climbout : intermediate altitude
Route In Use	departure other
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
ASRS Report	118214
Person 2
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : instrument
Events
Anomaly	conflict : airborne less severe non adherence : published procedure non adherence : required legal separation
Independent Detector	atc equipment other atc equipment : unspecified other controllera
Resolutory Action	none taken : detected after the fact
Consequence	Other
Miss Distance	horizontal : 15000 vertical : 500
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

I was working west radar (departure and arrival) at the time of the operational error. I had taken a handoff from kansas city ARTCC over bowlr which is northwest of kansas city approach's airspace on small aircraft X at 11,000 MSL sebnd. I advised small aircraft X to maintain 11,000 and issued the altimeter. Atx Y departed kansas city int'l heading 230 degree climbing to 6000 MSL to go out over st joseph, mo. I saw atx Y and told him to turn right to heading of 270 degree and climb to 12,000. I had to keep atx Y out wide to miss final airspace for runway 19 which was open. I advised small aircraft X to turn right heading 190 degree. When atx Y cleared final airspace I turned him to a heading of 360 degree. About 20 wnw of mkc VOR, atx Y climbed through altitude of small aircraft X. How was the problem discovered: conflict alert going off. What actions were taken: none. Was evasive action required: no. Why do you believe the situation occurred: watching other descending inbnds over bowlr and vectoring to runway 9 final.

Original NASA ASRS Text

Title: A DEPARTING ATX WAS ISSUED A CLIMB AND VECTOR THAT CONFLICTED WITH OPPOSITE DIRECTION TRAFFIC.

Narrative: I WAS WORKING WEST RADAR (DEP AND ARR) AT THE TIME OF THE OPERATIONAL ERROR. I HAD TAKEN A HANDOFF FROM KANSAS CITY ARTCC OVER BOWLR WHICH IS NW OF KANSAS CITY APCH'S AIRSPACE ON SMA X AT 11,000 MSL SEBND. I ADVISED SMA X TO MAINTAIN 11,000 AND ISSUED THE ALTIMETER. ATX Y DEPARTED KANSAS CITY INT'L HDG 230 DEG CLIMBING TO 6000 MSL TO GO OUT OVER ST JOSEPH, MO. I SAW ATX Y AND TOLD HIM TO TURN RIGHT TO HDG OF 270 DEG AND CLIMB TO 12,000. I HAD TO KEEP ATX Y OUT WIDE TO MISS FINAL AIRSPACE FOR RWY 19 WHICH WAS OPEN. I ADVISED SMA X TO TURN RIGHT HDG 190 DEG. WHEN ATX Y CLRED FINAL AIRSPACE I TURNED HIM TO A HDG OF 360 DEG. ABOUT 20 WNW OF MKC VOR, ATX Y CLIMBED THROUGH ALT OF SMA X. HOW WAS THE PROBLEM DISCOVERED: CONFLICT ALERT GOING OFF. WHAT ACTIONS WERE TAKEN: NONE. WAS EVASIVE ACTION REQUIRED: NO. WHY DO YOU BELIEVE THE SITUATION OCCURRED: WATCHING OTHER DESCENDING INBNDS OVER BOWLR AND VECTORING TO RWY 9 FINAL.

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.