TRACON controller described a conflict event when releasing opposite direction traffic; an arrival a...

Narrative:

An astra jet was a departure off of runway 34 which I released via rundown list. A G150 was an arrival; inbound to runway 34. While waiting on the astra to depart; the G150 made a request for landing runway 16. I called and for; and received approval from tower; to use runway 16 for the G150. I then vectored the G150 for a visual approach to runway 16 and asked him to keep his speed up due to traffic landing on active runway 34 which the G150 was going to beat in. Subsequent to that the astra departed runway 34 checked in; which I did not hear; as I was talking to another aircraft. I cleared the G150 for a visual approach and noticed the G150 was going to conflict with him. I radar identified the astra and gave him an immediate right turn; turned the G150 and descended him. The G150 acknowledged his instructions; informed me he had his traffic in sight; I then instructed him to maintain visual separation; which he acknowledged; cleared him for visual approach and transferred him to tower. Recommendation; insure satellite towers get their departures rolling in a more timely manner. Be a little less willing to approve opposite direction operations. Move 'rundown list' to a more prominent place on radar scope.

Original NASA ASRS Text

Title: TRACON Controller described a conflict event when releasing opposite direction traffic; an arrival and departure; operating to/from a satellite airport; necessitating the use of visual separation.

Narrative: An Astra Jet was a departure off of Runway 34 which I released via rundown list. A G150 was an arrival; inbound to Runway 34. While waiting on the Astra to depart; the G150 made a request for landing Runway 16. I called and for; and received approval from Tower; to use Runway 16 for the G150. I then vectored the G150 for a Visual Approach to Runway 16 and asked him to keep his speed up due to traffic landing on active Runway 34 which the G150 was going to beat in. Subsequent to that the Astra departed Runway 34 checked in; which I did not hear; as I was talking to another aircraft. I cleared the G150 for a Visual Approach and noticed the G150 was going to conflict with him. I RADAR identified the Astra and gave him an immediate right turn; turned the G150 and descended him. The G150 acknowledged his instructions; informed me he had his traffic in sight; I then instructed him to maintain visual separation; which he acknowledged; cleared him for Visual Approach and transferred him to Tower. Recommendation; insure satellite Towers get their departures rolling in a more timely manner. Be a little less willing to approve opposite direction operations. Move 'rundown list' to a more prominent place on RADAR scope.

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

Attributes
ACN	973134
Time
Date	201109
Local Time Of Day	0001-0600
Place
Locale Reference	ZZZ.TRACON
State Reference	US
Aircraft 1
Make Model Name	Gulfstream G100/G150 (IAI 1125 Astra)
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	IAI1125 (Astra)
Flight Phase	Initial Climb
Route In Use	None
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict

TRACON controller described a conflict event when releasing opposite direction traffic; an arrival and departure; operating to/from a satellite airport; necessitating the use of visual separation.