Date: 201501
Local time of day: 1801-2400
Location: ASE.Tower, CO
Flight conditions: VMC
Aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Operating under: Part 91
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class D ASE
ATC / advisory: Tower ASE
Second aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Distraction; Training / Qualification; Confusion
Second reporter function: Approach; Departure
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Aircraft X was cleared for takeoff when an aircraft was on a five mile final opposite direction (standard procedure). Aircraft X was instructed to maintain 12;000 feet; and not to exceed 230kts because Aircraft X was out performing the previous departure. Noticing that Aircraft X was out performing the first departure I told the pilot I will call your west bound turn. Pilot acknowledged and when I saw previous departure was no factor I thought I instructed Aircraft X to start his westbound turn on the LINDZ8 departure (to be westbound in front of Aircraft Y that was on a 12 mile final) and to contact departure. In fact after listening to the tapes I failed to resume his left turn. After switching to departure he told departure he was responding to a RA with Aircraft Y on a 10 mile final. I was still applying visual separation. What did not help the situation is an aircraft VFR calling multiple times even after not responding to that VFR aircraft.I will no longer switch aircraft to departure until I see the aircraft through the arrivals final approach course.


Second narrative: I was working numerous arrivals and departures. Aircraft that depart are on a SID; LINDZ8; that turns right heading 343 when off the runway then turns west reaching 9;100 feet to a 273 heading to join an IPKN outbound 303 heading. When aircraft reach the MVA departure will vector. Tower has automatic release for LINDZ8 departures. Aircraft X was stopped at 12;000 feet by tower due to additional traffic he was catching up to on the same departure procedure and coordinated via strip marking with radar. Aircraft X checks on with me at 12;000 feet; 6 miles north of airport and says on a 330 heading. I said turn westbound now heading 273 per the LINDZ8 departure; traffic 5 miles north descending out of 125; he said ok and started turning. I called traffic for the second time and said traffic one o'clock; 3 miles descending [aircraft type]; as Aircraft X was crossing his path and Aircraft X said he was responding to an RA and started descending. Tower controller said he had visual separation between the two aircraft. Aircraft X was then climbed to FL210 and turned on course. Tower had told Aircraft X that he would 'Call' his westbound turn and never did and switched the aircraft over to departure. I recommend tower needs to hold on to departures until they are established west of the final approach course.


Synopsis: ASE Controller describes an opposite-direction arrival and the loss of separation that ensued with a departure.