TRACON controller described a conflict event when failing to note the release issued was from other ...

Narrative:

I was the radar approach controller for four combined sectors. I had worked the sector earlier in the day and class D airport; during that period; was departing runway 14. I took for granted that the tower was still departing runway 14. My plan was to have a BE58 fly directly over the class D airport. The BE58 en route at 2;000; heading 050; vector for the ILS; was approximately 9 miles southeast of the class D airport. Tower called for release on the 'shout-line'. Tower asked for release on a FA20. I inquired if the aircraft was ready to go without delay. Tower responded in the affirmative. I release the FA20. The BE58 progressed to 5 SM southeast of the class D airport. I call tower for permission to transit their class 'D' airspace. I realized the FA20 was departing runway 23 opposite direction. I instructed tower to turn the FA20 to the right heading 290. Tower said 'if they are still talking to aircraft; wilco. I turn the BE58 right heading 130'. The FA20 checked-in approximately 2 miles off the departure end of runway 23 reporting both level at 1;500 AGL and with the BE58 in sight. The BE58 was never given a traffic advisory. Aircraft were 500 ft and approximately 1 mile apart; diverging courses. When asking for an IFR release; tower controller should reiterate departing runway to be used with release request.

Original NASA ASRS Text

Title: TRACON Controller described a conflict event when failing to note the release issued was from other that the expected runway resulting in an opposite direction operation; the reporter failing to note the runway change from a previous session.

Narrative: I was the RADAR Approach Controller for four combined sectors. I had worked the sector earlier in the day and Class D airport; during that period; was departing Runway 14. I took for granted that the Tower was still departing Runway 14. My plan was to have a BE58 fly directly over the Class D airport. The BE58 en route at 2;000; heading 050; vector for the ILS; was approximately 9 miles southeast of the Class D airport. Tower called for release on the 'shout-line'. Tower asked for release on a FA20. I inquired if the aircraft was ready to go without delay. Tower responded in the affirmative. I release the FA20. The BE58 progressed to 5 SM southeast of the Class D airport. I call Tower for permission to transit their Class 'D' airspace. I realized the FA20 was departing Runway 23 opposite direction. I instructed Tower to turn the FA20 to the right heading 290. Tower said 'if they are still talking to aircraft; WILCO. I turn the BE58 right heading 130'. The FA20 checked-in approximately 2 miles off the departure end of Runway 23 reporting both level at 1;500 AGL and with the BE58 in sight. The BE58 was never given a traffic advisory. Aircraft were 500 FT and approximately 1 mile apart; diverging courses. When asking for an IFR release; Tower Controller should reiterate departing runway to be used with release request.

Data retrieved from NASA's ASRS site as of July 2013 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	1008063
Time
Date	201205
Local Time Of Day	1201-1800
Place
Locale Reference	ZZZ.Airport
State Reference	US
Aircraft 1
Make Model Name	Baron 58/58TC
Flight Phase	Descent
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Falcon 20FJF/20C/20D/20E/20F
Flight Phase	Initial Climb
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Approach Departure
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy

TRACON controller described a conflict event when failing to note the release issued was from other that the expected runway resulting in an opposite direction operation; the reporter failing to note the runway change from a previous session.