D01 controller reported a request for opposite direction operation (odo) from bjc tower. The control...

Narrative:

Working DR1/SR1 combined. I sent aircraft X over to bjc on a visual approach to 30R. I receive a call from bjc requesting opposite direction operation (odo) aircraft Y VFR climb direct fooot; I responded with hold for release. I asked the supervisor if I missed a briefing while we were on vacation on odo and she wasn't sure. I asked the room what our current requirements were on odo and no one knew. The last briefing I had received was that odo was only approved when coordinating with den. The general consensus in the room was that odo was still suspended with satellites; but also that a VFR climb was not odo unless I had another IFR inbound. Bjc called again to ask how long for a release on aircraft Y; when I told her I may not be current on odo; she proceeded to tell me why I could do it. Aircraft X had landed so I issued a VFR climb release without saying the odo phraseology. After I was relieved from position the supervisor recommended I go to the procedures office to find out what I was supposed to do.in the procedures office; they said what I did was correct. Operations manager was also present. They said odo is only odo for me if I have another IFR inbound; though I am unclear when that aircraft becomes a factor. All satellite airports are commencing regular odo procedures and are in compliance by coordinating with the odo phraseology; even though we are not to repeat it back because we aren't allowed to conduct odo with anyone other than den. I would like a thorough briefing on the above mentioned statements so that I feel confident in how to handle future situations like this one. I would like bjc to be reminded that we aren't allowed to approve odo and that when they call with odo in the coordination; our controllers may be hesitant to respond with other than unable. I would like a procedure or a best practice to be developed so that everyone is coordinating the same way.

Original NASA ASRS Text

Title: D01 Controller reported a request for Opposite Direction Operation (ODO) from BJC Tower. The Controller was not sure how to handle it; and neither did anyone on duty. Eventually one of the aircraft had landed so it was no longer on ODO; so the reporter released the VFR aircraft.

Narrative: Working DR1/SR1 combined. I sent Aircraft X over to BJC on a visual approach to 30R. I receive a call from BJC requesting Opposite Direction Operation (ODO) Aircraft Y VFR climb direct FOOOT; I responded with hold for release. I asked the supervisor if I missed a briefing while we were on vacation on ODO and she wasn't sure. I asked the room what our current requirements were on ODO and no one knew. The last briefing I had received was that ODO was only approved when coordinating with DEN. The general consensus in the room was that ODO was still suspended with satellites; but also that a VFR climb was not ODO unless I had another IFR inbound. BJC called again to ask how long for a release on Aircraft Y; when I told her I may not be current on ODO; she proceeded to tell me why I could do it. Aircraft X had landed so I issued a VFR climb release without saying the ODO phraseology. After I was relieved from position the supervisor recommended I go to the procedures office to find out what I was supposed to do.In the procedures office; they said what I did was correct. Operations Manager was also present. They said ODO is only ODO for me if I have another IFR inbound; though I am unclear when that aircraft becomes a factor. All satellite airports are commencing regular ODO procedures and are in compliance by coordinating with the ODO phraseology; even though we are not to repeat it back because we aren't allowed to conduct ODO with anyone other than DEN. I would like a thorough briefing on the above mentioned statements so that I feel confident in how to handle future situations like this one. I would like BJC to be reminded that we aren't allowed to approve ODO and that when they call with ODO in the coordination; our controllers may be hesitant to respond with other than unable. I would like a procedure or a best practice to be developed so that everyone is coordinating the same way.

Data retrieved from NASA's ASRS site 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	1335037
Time
Date	201602
Local Time Of Day	1201-1800
Place
Locale Reference	D01.TRACON
State Reference	CO
Environment
Light	Daylight
Aircraft 1
Make Model Name	Commercial Fixed Wing
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	Light Transport Low Wing 2 Turbojet Eng
Flight Phase	Taxi
Route In Use	None
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 3.9
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance

D01 controller reported a request for opposite direction operation (odo) from bjc tower. The controller was not sure how to handle it; and neither did anyone on duty. Eventually one of the aircraft had landed so it was no longer on odo; so the reporter released the VFR aircraft.