Phx tower controller; providing OJT; experienced operational error at 1400 with two arrival aircraft...

Attributes
ACN	833158
Time
Date	200904
Local Time Of Day	1201-1800
Place
Locale Reference	PHX.Airport
State Reference	AZ
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Bombardier/Canadair Undifferentiated or Other Model
Operating Under FAR Part	Part 91
Flight Phase	Initial Approach
Route In Use	Visual Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	PC-12
Operating Under FAR Part	Part 91
Flight Phase	Initial Approach
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	Instructor Local
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Military 4 Air Traffic Control Radar 11 Air Traffic Control Time Certified In Pos 1 (yrs) 10
Events
Anomaly	ATC Issue All Types
Miss Distance	Horizontal 3420 Vertical 1400

Narrative:

Providing training on local control south. Local control south requested and received a release on a northbound turbo off runway 26. When the turbo got airborne he was actually southbound. I took the position from my trainee and spent the next few minutes prying apart the turbo from a southbound air carrier as well as telling local control south what to do. Meanwhile a CL60 was inbound for runway 25L with a PC12 in trail. The PC12 was faster and not visually separated from the CL60. As I was coordinating with approach control; the PC12 checked in on local control south frequency. I did not hear him; so I did not reply. Approach control called local control south and said I can turn the PC12 to a 180 degree heading and 4;000 ft if I need it. I replied I wasn't even talking to him and confirmed this with my trainee. Approach never called back; so I assumed they applied the appropriate separation. On a 2 mile final; my trainee reached out to the PC12 and cleared him to land. The supervisor pulled the tapes and called the operational error on local control south.

Original NASA ASRS Text

Title: PHX Tower Controller; providing OJT; experienced operational error at 1400 with two arrival aircraft in an overtake scenario; complicated by another developing event involving two departing aircraft.

Narrative: Providing training on Local Control South. Local Control South requested and received a release on a northbound turbo off Runway 26. When the turbo got airborne he was actually southbound. I took the position from my trainee and spent the next few minutes prying apart the turbo from a southbound air carrier as well as telling Local Control South what to do. Meanwhile a CL60 was inbound for Runway 25L with a PC12 in trail. The PC12 was faster and not visually separated from the CL60. As I was coordinating with Approach Control; the PC12 checked in on Local Control South frequency. I did not hear him; so I did not reply. Approach Control called Local Control South and said I can turn the PC12 to a 180 degree heading and 4;000 FT if I need it. I replied I wasn't even talking to him and confirmed this with my trainee. Approach never called back; so I assumed they applied the appropriate separation. On a 2 mile final; my trainee reached out to the PC12 and cleared him to land. The Supervisor pulled the tapes and called the operational error on Local Control South.

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.

Phx tower controller; providing OJT; experienced operational error at 1400 with two arrival aircraft in an overtake scenario; complicated by another developing event involving two departing aircraft.