Narrative:

I was monitor for trainee on local. Primary in use runway 08; secondary runway 35L. Aircraft Y was performing instrument practice approaches to runway 35L. Radar east coordinated his tagged climbout indicated K but was actually direct craig. Afterwards radar requested an ILS 17R for inbound aircraft X flight still 30 miles out to the northwest.we had 2 departures taxiing to runway 08. The first aircraft was launched when he got to the runway. As the [aircraft] was rolling we look at the tag for aircraft Y and he is tagged for T2J; no coordination for this approach had been done; so we talked about it; watched it; then continued scanning our active traffic.aircraft X called ready to depart at runway 08. We looked and noticed that aircraft Y appeared to be in a procedure turn as if executing the full procedure for the T2 approach. Talked about it again. Trainee asked me what to do in this situation; I told him to launch aircraft X and to send the strip a couple moments early to let radar know that we were still launching traffic off of runway 08. Aircraft Y was now appearing to be joining the inbound course; not tagged or coordinated as an opposite direction operation or approach.aircraft X rolls and when airborne was told to contact departure just as aircraft Y was checking in. I asked aircraft Y if he was cleared for the approach; the pilot answered in the affirmative; I then instructed him to cancel the approach; turn south (away from departing traffic) and maintain altitude for sequence back to the field. Ground control assisted in making sure that we had both aircraft in sight before any loss of separation occurred (if any).re-training on opposite direction procedures. Possible re-evaluation of when opposite direction approaches can/should be approved.

Google
 

Original NASA ASRS Text

Title: Lubbock Tower Controller reported an unsafe opposite direction operation.

Narrative: I was monitor for trainee on Local. Primary in use Runway 08; secondary Runway 35L. Aircraft Y was performing instrument practice approaches to Runway 35L. Radar East coordinated his tagged climbout indicated K but was actually direct CRAIG. Afterwards Radar requested an ILS 17R for inbound Aircraft X flight still 30 miles out to the northwest.We had 2 departures taxiing to Runway 08. The first aircraft was launched when he got to the runway. As the [Aircraft] was rolling we look at the tag for Aircraft Y and he is tagged for T2J; no coordination for this approach had been done; so we talked about it; watched it; then continued scanning our active traffic.Aircraft X called ready to depart at Runway 08. We looked and noticed that Aircraft Y appeared to be in a procedure turn as if executing the full procedure for the T2 approach. Talked about it again. Trainee asked me what to do in this situation; I told him to launch Aircraft X and to send the strip a couple moments early to let Radar know that we were still launching traffic off of Runway 08. Aircraft Y was now appearing to be joining the inbound course; not tagged or coordinated as an opposite direction operation or approach.Aircraft X rolls and when airborne was told to contact departure just as Aircraft Y was checking in. I asked Aircraft Y if he was cleared for the approach; the pilot answered in the affirmative; I then instructed him to cancel the approach; turn south (away from departing traffic) and maintain altitude for sequence back to the field. Ground Control assisted in making sure that we had both aircraft in sight before any loss of separation occurred (if any).Re-training on Opposite Direction procedures. Possible re-evaluation of when opposite direction approaches can/should be approved.

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.