Narrative:

This report is a direct result of the series of briefings we; nationally; have all received regarding the 'opposite direction' procedures. At ZZZ; we have received at least 4 mandatory/pre-duty/verbal briefings about the latest status of what is and what is not allowed in regard to opposite direction approaches and procedures. A BE40; on an IFR flight plan was in holding at the ZZZ1 VOR at 4;000. He intended to hold for 2 complete turns; then fly one more IFR ILS13 approach at ZZZ1 (which was the advertised runway and approach); and then depart the area on a subsequent flight plan. A glex; on a VFR flight plan was in our 'west practice area' (which is basically an area where they can navigate unrestricted doing aircraft testing); and asked for a VFR localizer back course runway 31 under his own navigation to join an arc. After that he wanted a missed approach to then depart the area for ZZZ. The cpc-it told the glex to 'proceed as requested; maintain VFR; advise established on the arc'. At approximately the same time the BE40 asked for vectors for his ILS 13 approach. The BE40 was closer to the airport; so the cpc-it vectored him with the intent to sequence him first to the airport. The glex was still approximately 25-30 miles from ZZZ1 airport at this time. We (both the training and I) explained that due to new rules regarding opposite direction approaches; we'd need to delay the glex until the BE40 had completed his approach. We then called ZZZ1 tower personnel and asked them; 'is it ok to run this VFR back course 31 approach after the BE40 has completed his ILS13?' we also issued climb out instructions to the BE40 to 'turn directly to the ZZZ1 VOR to hold' and advised ZZZ1 tower personnel that we had issued that. ZZZ1 tower personnel advised that it was approved and that 'he had no other aircraft on the airport or in the airport vicinity'. The glex executed a 360 degree turn while on the arc to delay his inbound turn. After we determined that the spacing was adequate; we advised the glex to 'proceed inbound on the approach; practice approach approved; no separation services provided; maintain VFR'. When the glex reached approximately an 11 mile final to runway 31; ZZZ1 tower personnel called and advised 'the BE40 is executing missed approach; coming to you'. At that point; the trainee transferred communication to the tower. When the BE40 reported on frequency; the trainee instructed him to 'turn right to the VOR immediately; climb and maintain 50'. The closest these 2 aircraft got was 5 miles apart. I honestly can't tell if this is a violation of the latest procedural directives regarding opposite direction or not. I understand we have to amend our procedures to avoid the latest 'near miss' that happened back east. Please encourage the decision-makers to come up with a clear set of rules that won't change and to do it quickly; for our sake.

Related reports:

Google
 

Original NASA ASRS Text

Title: TRACON Controller voiced concern regarding the varying interpretations and frequent changes to the new 'Opposite Direction' procedures; imploring the decision makes to solidify the procedures once and for all.

Narrative: This report is a direct result of the series of briefings we; nationally; have all received regarding the 'opposite direction' procedures. At ZZZ; we have received at least 4 Mandatory/Pre-Duty/Verbal briefings about the latest status of what is and what is not allowed in regard to opposite direction approaches and procedures. A BE40; on an IFR flight plan was in holding at the ZZZ1 VOR at 4;000. He intended to hold for 2 complete turns; then fly one more IFR ILS13 approach at ZZZ1 (which was the advertised runway and approach); and then depart the area on a subsequent flight plan. A GLEX; on a VFR flight plan was in our 'West Practice Area' (which is basically an area where they can navigate unrestricted doing aircraft testing); and asked for a VFR Localizer Back Course Runway 31 under his own navigation to join an arc. After that he wanted a missed approach to then depart the area for ZZZ. The CPC-IT told the GLEX to 'proceed as requested; maintain VFR; advise established on the arc'. At approximately the same time the BE40 asked for vectors for his ILS 13 approach. The BE40 was closer to the airport; so the CPC-IT vectored him with the intent to sequence him first to the airport. The GLEX was still approximately 25-30 miles from ZZZ1 airport at this time. We (both the training and I) explained that due to new rules regarding opposite direction approaches; we'd need to delay the GLEX until the BE40 had completed his approach. We then called ZZZ1 Tower personnel and asked them; 'Is it ok to run this VFR Back Course 31 approach after the BE40 has completed his ILS13?' We also issued climb out instructions to the BE40 to 'turn directly to the ZZZ1 VOR to hold' and advised ZZZ1 Tower personnel that we had issued that. ZZZ1 Tower personnel advised that it was approved and that 'he had no other aircraft on the airport or in the airport vicinity'. The GLEX executed a 360 degree turn while on the arc to delay his inbound turn. After we determined that the spacing was adequate; we advised the GLEX to 'proceed inbound on the approach; practice approach approved; no separation services provided; maintain VFR'. When the GLEX reached approximately an 11 mile final to Runway 31; ZZZ1 Tower personnel called and advised 'The BE40 is executing missed approach; coming to you'. At that point; the trainee transferred communication to the Tower. When the BE40 reported on frequency; the trainee instructed him to 'turn right to the VOR immediately; climb and maintain 50'. The closest these 2 aircraft got was 5 miles apart. I honestly can't tell if this is a violation of the latest procedural directives regarding opposite direction or not. I understand we have to amend our procedures to avoid the latest 'near miss' that happened back east. Please encourage the decision-makers to come up with a clear set of rules that won't change and to do it quickly; for our sake.

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.