Narrative:

I was working local control and tower controller in charge (controller in charge); and I changed the active runway from runway 35 to runway 17 due to wind change. I put visual approach runway 17 on the ATIS and coordinated that with the radar approach controller. A few minutes later a local controller and a ground controller came up to the tower to man those positions. I was still the tower controller in charge. I briefed them that I had changed the runway; and runway 17 was now the active.soon after they took those positions; 3 or 4 departures called ground control who I was actively monitoring along with local control and ground control taxied them to runway 35. During this time; that the aircraft were taxiing a VFR helicopter called ground control to depart to the southwest; then the helicopter called local control for departure. Local control launched the helicopter from the ramp on course to the southwest. Then the local controller launched [a global express] off runway 35 without coordination with the radar controller.at the time the [global express] got airborne; a beech bonanza was approximately 7 miles northeast of the airport on a visual approach to runway 17. In our facility SOP; the cutoff point for odo (opposite direct operations) with jets is 15 miles and for propellers it is 10 miles. When ground control taxied the departures to runway 35; I didn't catch that. And when local control launched the global express from runway 35; I didn't catch that.a supervisor relieved me as tower controller in charge; and realized the odo problem soon after the briefing I gave him; which included that runway 17 was the active. The visual approach clearance for [beech bonanza] was cancelled and they were told to enter the downwind for runway 35 and cleared for a visual approach runway 35. I recommend extra memory aids when switching runways; especially when one particular runway has been in constant use for several days or weeks.

Related reports:

Google
 

Original NASA ASRS Text

Title: Tower Controllers reported they had less than required separation criteria for an Opposite Direction Operation.

Narrative: I was working Local Control and Tower CIC (Controller in Charge); and I changed the active runway from Runway 35 to Runway 17 due to wind change. I put Visual Approach Runway 17 on the ATIS and coordinated that with the Radar Approach Controller. A few minutes later a Local Controller and a Ground Controller came up to the Tower to man those positions. I was still the Tower CIC. I briefed them that I had changed the runway; and Runway 17 was now the active.Soon after they took those positions; 3 or 4 departures called ground control who I was actively monitoring along with Local Control and Ground Control taxied them to Runway 35. During this time; that the aircraft were taxiing a VFR Helicopter called Ground Control to depart to the southwest; then the Helicopter called Local Control for departure. Local Control launched the Helicopter from the Ramp on course to the southwest. Then the Local controller launched [A Global Express] off Runway 35 without coordination with the Radar Controller.At the time the [Global Express] got airborne; A Beech Bonanza was approximately 7 miles northeast of the airport on a Visual Approach to Runway 17. In our facility SOP; the cutoff point for ODO (Opposite Direct Operations) with jets is 15 miles and for propellers it is 10 miles. When Ground Control taxied the departures to Runway 35; I didn't catch that. And when Local control launched the Global Express from Runway 35; I didn't catch that.A Supervisor relieved me as Tower CIC; and realized the ODO problem soon after the briefing I gave him; which included that Runway 17 was the active. The Visual Approach clearance for [Beech Bonanza] was cancelled and they were told to enter the downwind for Runway 35 and cleared for a Visual Approach Runway 35. I recommend extra memory aids when switching runways; especially when one particular runway has been in constant use for several days or weeks.

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.