Jcf controller reports of an opposite direction operation that worked out fine; but he critiqued his...

Narrative:

Aircraft Y was being vectored for a practice ILS runway 17 circle to active runway 35 at vcv airport. Vcv tower asked on a 15 mile base to hold him and allow an IFR aircraft to back taxi and depart runway 35; aircraft X; heavy. Aircraft Y was advised he would be vectored through the localizer to allow spacing. Aircraft X was released with a turn out towards pmd. Aircraft Y was vectored back towards the localizer and asked to reduce to final approach speed. Aircraft Y was advised the aircraft X was taking a longer than expected time and would be turned to localizer after crossing for additional spacing. Aircraft Y was given a turn to 140 from a 9.5 mile base and told to maintain an altitude of 4;600 feet. Aircraft X was radar identified and observed in his left turn towards pmd VORTAC. After observing the turn; aircraft Y was told to maintain assigned and altitude until established on the localizer; then he was cleared for the ILS runway 17 circle to runway 35 at vcv airport. Aircraft Y was on vectors until aircraft X was no longer opposite direction and was not issued a clearance to vcv airport until aircraft X was no longer opposite direction. As the aircraft was not cleared to the vcv airport or any runway; there could not have been any infringement of the opposite direction operation section of our vcv airport letter of agreement.the event could have been better handled or more positively controlled by issuing the aircraft Y a right turn to 150 to join the localizer from their initial 250 heading; which would have allowed an extra minute and 2 additional miles of spacing; but the LOA was not clear on how to handle a situation with a VFR aircraft on vectors expecting additional services and the controller awaiting a brief to take the position and the supervisor at the time on the desk were unsure as well I asked while on position. I'd suggest a more in depth brief on opposite direction operations for all controllers to ensure sound understanding of what can and cannot be done.

Original NASA ASRS Text

Title: JCF Controller reports of an Opposite Direction Operation that worked out fine; but he critiqued his operation and determined it could have been done better.

Narrative: Aircraft Y was being vectored for a practice ILS runway 17 circle to active runway 35 at VCV airport. VCV Tower asked on a 15 mile base to hold him and allow an IFR aircraft to back taxi and depart runway 35; Aircraft X; Heavy. Aircraft Y was advised he would be vectored through the localizer to allow spacing. Aircraft X was released with a turn out towards PMD. Aircraft Y was vectored back towards the localizer and asked to reduce to final approach speed. Aircraft Y was advised the Aircraft X was taking a longer than expected time and would be turned to localizer after crossing for additional spacing. Aircraft Y was given a turn to 140 from a 9.5 mile base and told to maintain an altitude of 4;600 feet. Aircraft X was radar identified and observed in his left turn towards PMD VORTAC. After observing the turn; Aircraft Y was told to maintain assigned and altitude until established on the localizer; then he was cleared for the ILS runway 17 circle to runway 35 at VCV airport. Aircraft Y was on vectors until Aircraft X was no longer opposite direction and was not issued a clearance to VCV airport until Aircraft X was no longer opposite direction. As the aircraft was not cleared to the VCV airport or any runway; there could not have been any infringement of the Opposite Direction Operation section of our VCV airport Letter of Agreement.The event could have been better handled or more positively controlled by issuing the Aircraft Y a right turn to 150 to join the localizer from their initial 250 heading; which would have allowed an extra minute and 2 additional miles of spacing; but the LOA was not clear on how to handle a situation with a VFR aircraft on vectors expecting additional services and the controller awaiting a brief to take the position and the Supervisor at the time on the desk were unsure as well I asked while on position. I'd suggest a more in depth brief on opposite direction operations for all controllers to ensure sound understanding of what can and cannot be done.

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	1252901
Time
Date	201503
Local Time Of Day	1801-2400
Place
Locale Reference	JCF.TRACON
State Reference	CA
Environment
Light	Dusk
Aircraft 1
Make Model Name	Military Transport
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Route In Use	None
Flight Plan	IFR
Aircraft 2
Make Model Name	Military Transport
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Route In Use	Vectors
Flight Plan	VFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 1.2
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy

Jcf controller reports of an opposite direction operation that worked out fine; but he critiqued his operation and determined it could have been done better.