Date: 201504
Local time of day: 1801-2400
Location: D01.TRACON, CO
Light: Night
Aircraft: Helicopter
Operator: Military
Operating under: Part 91
Flight plan: IFR
Mission: Training
Flight phase: Final Approach
Airspace: Class B DEN
ATC / advisory: TRACON D01
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Troubleshooting; Training / Qualification; Distraction; Confusion
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Air Traffic Control; Person Air Traffic Control
When detected: In-flight
Contributing factors: Procedure; Human Factors
Primary problem: Procedure

Narrative: I was working SR4 and had Aircraft X request ODO (Opposite Direction Operation) ILS 35R; I asked the tower who said unable. I then asked the tower for a point out to allow Aircraft X a segment of the approach with the intent to break him out early; they released the airspace to me up to a four mile final. The tower then requested a release to which I gave runway heading. I intended to inquire Aircraft X as to which direction he would terminate the approach; at which point I would amend the heading for the departure aircraft as needed. Afterwards I asked for supervisor [name removed] for clarification on the situation. He called the tower to review our expectations based on what is reported in the IDS4 for ODO and we reviewed the procedures. I was unclear to our obligations for ODO and thought I was covered when the tower approved a point out. But after reviewing the procedures I interpreted my arrival clearance in addition to the release for departure constituted ODO and I was putting the tower in a bad situation. There was no loss of separation.About two hours later; I was working the same position and the same aircraft requested ODO ILS 35R; I explained that I could not clear him on the approach but I could let him track the localizer for training. I also told him to expect a turn at CASSE. I did not coordinate with the tower as the aircraft would not hit their airspace. I released a departure and gave him a heading that would constitute reciprocal divergence as an added layer of safety. I believed I was abiding by all the rules of ODO and providing the [pilot] a service at the same time. However; the subject came up again the next day and I'm being advised by management that it is still not a safe operation; but I've been given no clear guidance on why or what exactly defines it. I've been ordered to cease an assist ODO; to which I will abide. I am concerned now what specifically defines ODO; we have aircraft that request to hold at the outer marker and at different altitudes. I'm not sure if this could be considered ODO based on what runway is advertised.We need further clarification on ODO; the letter is unclear and causes just as many questions as it does answers. More specifically we need to know what is and what isn't ODO. In order to provide a service to aircraft; we need specifics on how we can operate within safe parameters as tower and approach controllers. We need training to be sure that everyone is clear on expectations; it seems everyone has a different interpretation; we need to be consistent.




Synopsis: D01 controller describes an Opposite Direction Operation [ODO]; which he wasn't sure if it was legal to do or not. Later that day he does another ODO like operation; then after review is told to cease ODO's.  Controller asks for clarification on what he can and can't do reference ODO's.