Ase controller described a TCAS RA event between an visual approach arrival to runway 15 and an IFR ...

Attributes
ACN	959116
Time
Date	201107
Local Time Of Day	1201-1800
Place
Locale Reference	ASE.Airport
State Reference	CO
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Medium Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Route In Use	SID LINDZ6
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Transport Low Wing 2 Turbojet Eng
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	Local
Qualification	Air Traffic Control Developmental
Person 2
Function	Pilot Not Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

Narrative:

Aircraft Y was on a visual approach to ase runway 15. He was 7 miles out with aircraft X holding in position to depart runway 33. Aircraft X was cleared for take off and started his right hand turn heading 340 per the LINDZ6 departure procedure. Aircraft Y was flying towards ase from the northwest; west of final; following a valley inbound. Both aircraft were issued traffic. At three miles; aircraft Y over shot final east bound instead of lining up on final descending out of nine thousand four hundred. Aircraft X was east of final still on the departure procedure climbing out of eight thousand seven hundred. Since aircraft Y shot through final; a traffic alert was issued to aircraft X. Aircraft X said after the traffic alert he received a RA but was not going to respond to it. Aircraft X continued on the departure procedure and aircraft Y landed without incident. Maybe [I should] reiterate to an inbound pilot not to overfly final.

Original NASA ASRS Text

Title: ASE Controller described a TCAS RA event between an Visual Approach arrival to Runway 15 and an IFR departure from Runway 33; all developing due to a final turn overshoot by the arrival.

Narrative: Aircraft Y was on a visual approach to ASE Runway 15. He was 7 miles out with Aircraft X holding in position to depart Runway 33. Aircraft X was cleared for take off and started his right hand turn heading 340 per the LINDZ6 departure procedure. Aircraft Y was flying towards ASE from the northwest; west of final; following a valley inbound. Both aircraft were issued traffic. At three miles; Aircraft Y over shot final east bound instead of lining up on final descending out of nine thousand four hundred. Aircraft X was east of final still on the departure procedure climbing out of eight thousand seven hundred. Since Aircraft Y shot through final; a traffic alert was issued to Aircraft X. Aircraft X said after the traffic alert he received a RA but was not going to respond to it. Aircraft X continued on the departure procedure and Aircraft Y landed without incident. Maybe [I should] reiterate to an inbound pilot not to overfly final.

Data retrieved from NASA's ASRS site as of April 2012 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.

Ase controller described a TCAS RA event between an visual approach arrival to runway 15 and an IFR departure from runway 33; all developing due to a final turn overshoot by the arrival.