Date: 201605
Local time of day: 1801-2400
Location: RVS.Airport, OK
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 2 Eng; Retractable Gear
Operator: Personal
Operating under: Part 91
Mission: Personal
Flight phase: Initial Approach
Airspace: Class D RVS
ATC / advisory: Tower RVS
Second aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Training / Qualification; Situational Awareness
Second reporter function: Ground; Supervisor / CIC
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Manuals; Human Factors; Airspace Structure; Procedure
Primary problem: Procedure

Narrative: I was working Local Control. I noticed a IFR business jet from the southeast and Aircraft X (incorrectly tagged on stars display by approach). Aircraft X was obviously being vectored by Approach and established on an approach opposite direction as was departing. Aircraft X was tagged in the stars data block; there was not anything regarding Opposite Direction procedures established in the Letter of Agreement. I tried calling Approach to find out what Aircraft X was doing as I had 3 aircraft in the east side pattern and multiple departures waiting. Approach did not answer the line. I figured Approach was trying to cheat the procedures with Aircraft X VFR and the IFR business jet now on the west side of the airport on the downwind; and had therefore told Aircraft X to 'track the approach inbound VFR'; and would break Aircraft X off the approach before entering Class Delta.  I cleared Aircraft Y for takeoff; runway heading; expecting Aircraft X to be far out of the way. Aircraft Y was requesting to go west. Approach finally called back a few minutes later; the ground controller answered the line; and asked what Aircraft X was doing. Approach advised that 'Aircraft X was VFR tracking the approach.' the ground controller said 'roger'.I had sequenced a few of the aircraft on the east side and now looked back to the radar display to find Aircraft X still on the approach opposite direction; now inside the Class Delta; with Aircraft Y now a mile south of the field climbing. I watched the data tag on the radar display change to a tag to indicate a frequency change from approach after Aircraft X was inside the Class Delta. As soon as Aircraft X checked on my frequency; I told him to cancel his approach clearance and enter the right downwind  and advised him of the opposite direction traffic. I then went to Aircraft Y; on upwind; advised him of a aircraft upwind off the parallel; and told him to turn SE to a 160 heading for the opposite direction traffic. There were several other traffic calls; but Aircraft X and Aircraft Y were the closest.  I was lucky in the sense that I had a hole to turn Aircraft Y to the SE. Regardless of what the approach controller was doing; we never approved anyone to come 'in the out gate'; or an opposite direction approach; or a late frequency change. My biggest recommendation is that Approach follow the Letter Of Agreement and Opposite Direction (ODO)  procedures established. This isn't the first time Approach has told a VFR aircraft on a 'practice approach' to track the approach inbound VFR. This has happened to me personally a few times over the past 6 weeks. The first time it happened; a supervisor was here; and called Approach on the phone to establish what ODO really means. Approach then had a briefing on exactly what ODO means and when they could and could not use it here; the proper ways to coordinate ODO; etc. We were then briefed using the exact same sheet Approach had made to brief their controllers; that way both facilities know what the other is expecting. On the bottom of this sheet; in big bold letters; it says that Approach SHALL NOT tell VFR aircraft to 'track the approach inbound' under any circumstance.


Second narrative: I was working Ground Control as well as Controller in Charge. Aircraft X which had an incorrect data tag appeared to be on the approach for the runway which was opposite direction for our departures. Aircraft X was not coordinated with us from Approach control and when we asked about it we were told that; 'He's VFR tracking the approach'. Local control made first contact with Aircraft X only 5 miles south of the airport and had to give him a westbound turn as soon as he did talk to him because of departing traffic that was opposite direction. I would recommend that Approach follows the Letter of Agreement and all prior briefings we have had on this subject and coordinates ALL opposite direction traffic regardless of whether or not they are on the approach or even tracking the approach. Either way it is still opposite direction traffic for our flow.


Synopsis: RVS Tower Controllers reported TUL TRACON permitted an aircraft to approach RVS opposite direction to the runway in use not in compliance with their local Letter of Agreement.