Beechjet 400
Air Traffic Control Fully Certified
ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Human Factors; Procedure
I was working and it was busy. I cleared a Beechjet for the ILS Runway X/Y. While the Beechjet was on the arc; I cleared a Westwind off [the airport] via the SID departure procedure with a void time of 2 minutes. Right before I cleared the Westwind; another aircraft cancelled on about a 1 mile final. I saw [the Westwind] on RADAR departing Runway Y/X and realized it wouldn't work. I told the Beechjet approach clearance was canceled and to climb immediately to FL190. At that time the Beechjet was at 084 and the Westwind was at 064. He didn't respond. I broadcasted for him two more times before he responded by which time it was too late so I just called traffic to each aircraft. My recommendation would be that everybody have a chance to 'warm up' in the Simulator Lab before we get busy. Our area has such low traffic volume all summer long that by the time the busy time comes around we all feel rusty because we haven't worked busy traffic like this for 9 months.
A Beechjet was cleared for the ILS X approach into the airport. A Westwind was released via the SID departure out of the airport. The aircraft was given a void time but the aircraft was not assigned a runway to depart therefore he was a head on conflict with the arrival traffic; the Beechjet. Assign a runway to depart.
Enroute controllers describe an unsafe event involving an IFR departure from a non-towered airport and an inbound IFR aircraft.