Less than standard separation between corp jet and another aircraft. Operational error.

Attributes
ACN	187593
Time
Date	199108
Day	Sun
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : luk airport : cvg
State Reference	OH
Altitude	msl bound lower : 9600 msl bound upper : 10000
Environment
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zid tracon : luk
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	descent other
Route In Use	arrival star : star
Flight Plan	IFR
Aircraft 2
Operator	general aviation : corporate
Make Model Name	Medium Transport, Low Wing, 2 Turbojet Eng
Flight Phase	climbout : intermediate altitude
Route In Use	departure sid : sid
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	controller : radar
Experience	controller non radar : 1 controller radar : 11
ASRS Report	187593
Person 2
Function	flight crew : captain oversight : pic
Qualification	pilot : instrument
Events
Anomaly	conflict : airborne less severe non adherence : required legal separation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance none taken : insufficient time other
Consequence	faa : investigated
Miss Distance	horizontal : 18000 vertical : 400
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error Inter Facility Coordination Failure

Narrative:

I am a radar controller at ind ARTCC and have been an fpl for 12 yrs. There was an aircraft X inbound on the bucke 2 arrival to day airport (which is a published STAR). There was corp jet Y departing luk airport on the gaill (a published SID). This SID and STAR cross in my airspace and it is a very unsafe and confusing operation. An aircraft on the bucke STAR and an aircraft on the gaill SID can both be exactly where they are supposed to be and there can be a conflict, which happened in my situation. The radar controller has to take some sort of action whenever there is a gaill departure off cvg or luk. In this case, I called cvg approach, got no response. When the aircraft came on my frequency, the 2 in conflict were only 7 mi apart with separation decreasing rapidly. I had about 30 seconds from when the departure called to establish separation. I used a combination of a turn plus altitude, but there was just not enough time.

Original NASA ASRS Text

Title: LTSS BTWN CORP JET AND ANOTHER ACFT. OPERROR.

Narrative: I AM A RADAR CTLR AT IND ARTCC AND HAVE BEEN AN FPL FOR 12 YRS. THERE WAS AN ACFT X INBOUND ON THE BUCKE 2 ARR TO DAY ARPT (WHICH IS A PUBLISHED STAR). THERE WAS CORP JET Y DEPARTING LUK ARPT ON THE GAILL (A PUBLISHED SID). THIS SID AND STAR CROSS IN MY AIRSPACE AND IT IS A VERY UNSAFE AND CONFUSING OP. AN ACFT ON THE BUCKE STAR AND AN ACFT ON THE GAILL SID CAN BOTH BE EXACTLY WHERE THEY ARE SUPPOSED TO BE AND THERE CAN BE A CONFLICT, WHICH HAPPENED IN MY SITUATION. THE RADAR CTLR HAS TO TAKE SOME SORT OF ACTION WHENEVER THERE IS A GAILL DEP OFF CVG OR LUK. IN THIS CASE, I CALLED CVG APCH, GOT NO RESPONSE. WHEN THE ACFT CAME ON MY FREQ, THE 2 IN CONFLICT WERE ONLY 7 MI APART WITH SEPARATION DECREASING RAPIDLY. I HAD ABOUT 30 SECONDS FROM WHEN THE DEP CALLED TO ESTABLISH SEPARATION. I USED A COMBINATION OF A TURN PLUS ALT, BUT THERE WAS JUST NOT ENOUGH TIME.

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.