Salt lake city tower controller instructs departing light aircraft to make left turn. When aircraft ...

Narrative:

I was working the local east position. I cleared aircraft X for takeoff with instructions to 'turn left; enter left downwind.' these instructions were to set the aircraft up for the barn transition through salt lake bravo airspace. The pilot of aircraft X turned right instead of left at the departure end of runway 17. I noticed the aircraft in the right turn and also noticed aircraft Y lifting off the runway. I was unsure as to the flight path of aircraft Y so I notified the local center controller who gave the traffic alert to aircraft Y who replied he had aircraft X in sight and would maintain visual. At first I issued an immediate left turn thinking that the aircraft Y was departing straight out. I then noticed the data tag acquire and that aircraft Y was a PECOP2 departure; meaning he was turning out to the west. I then went back to aircraft X and instructed the pilot to continue the right turn and cross the airport midfield back over to the east side of the airport. Between the flm and myself; all required coordination was accomplished. I then put aircraft X on the correct routing and transferred control to the departure controller. We in slc depend on the pilots knowing the procedures and being familiar with them enough to fly them. If you look at the VFR sectionals; there is not much guidance on how to fly either the barn transition (south flow) or the I-80 transition (north flow). Also the altitude for the transition inbound is 6000 MSL and 5500 MSL outbound. The MVA in the area is 6000 MSL; so in the event of an IFR aircraft going around with someone in the VFR corridor directly over the runway; our choices are to send the aircraft around; maintain some altitude below the MVA; or try to move the VFR aircraft. Neither of these options is acceptable in my opinion. I believe that more detail should be made than is currently underway to interface with pilots and get the message out as to what we need from them. A controller/pilot meeting one on one or in small groups would be useful. Perhaps a controller could attend the users' pilot meetings. We have several flight schools and flying clubs in the area. We should be working on making this safer together.

Original NASA ASRS Text

Title: Salt Lake City Tower Controller instructs departing light aircraft to make left turn. When aircraft turns right instead; conflict develops with large air carrier jet departing the parallel runway.

Narrative: I was working the Local East position. I cleared Aircraft X for takeoff with instructions to 'turn left; enter left downwind.' These instructions were to set the aircraft up for the Barn Transition through Salt Lake Bravo Airspace. The Pilot of Aircraft X turned right instead of left at the departure end of Runway 17. I noticed the aircraft in the right turn and also noticed Aircraft Y lifting off the runway. I was unsure as to the flight path of Aircraft Y so I notified the Local Center Controller who gave the traffic alert to Aircraft Y who replied he had Aircraft X in sight and would maintain visual. At first I issued an immediate left turn thinking that the Aircraft Y was departing straight out. I then noticed the data tag acquire and that Aircraft Y was a PECOP2 departure; meaning he was turning out to the west. I then went back to Aircraft X and instructed the Pilot to continue the right turn and cross the airport midfield back over to the east side of the airport. Between the FLM and myself; all required coordination was accomplished. I then put Aircraft X on the correct routing and transferred control to the Departure Controller. We in SLC depend on the pilots knowing the procedures and being familiar with them enough to fly them. If you look at the VFR sectionals; there is not much guidance on how to fly either the Barn transition (south flow) or the I-80 transition (north flow). Also the altitude for the transition inbound is 6000 MSL and 5500 MSL outbound. The MVA in the area is 6000 MSL; so in the event of an IFR aircraft going around with someone in the VFR corridor directly over the runway; our choices are to send the aircraft around; maintain some altitude below the MVA; or try to move the VFR aircraft. Neither of these options is acceptable in my opinion. I believe that more detail should be made than is currently underway to interface with pilots and get the message out as to what we need from them. A controller/pilot meeting one on one or in small groups would be useful. Perhaps a controller could attend the users' pilot meetings. We have several flight schools and flying clubs in the area. We should be working on making this safer together.

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.

Attributes
ACN	875560
Time
Date	201002
Local Time Of Day	1201-1800
Place
Locale Reference	SLC.Airport
State Reference	UT
Aircraft 1
Make Model Name	Small Aircraft Low Wing 1 Eng Fixed Gear
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Route In Use	VFR Route
Flight Plan	VFR
Aircraft 2
Make Model Name	Medium Large Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Route In Use	SID PECOP2
Flight Plan	IFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Track / Heading All Types
Miss Distance	Horizontal 3000 Vertical 0

Salt lake city tower controller instructs departing light aircraft to make left turn. When aircraft turns right instead; conflict develops with large air carrier jet departing the parallel runway.