P50 controller providing OJT described a TCAS event when developmental failed to issue VFR traffic t...

Narrative:

I was providing OJT to a developmental who was working to several aircraft. While he was attempting to accommodate a photo mission pilot's request that would be close to the primary airport (phx) and coordinate that operation with the neighboring sector and dvt ATCT; a VFR aircraft climbed into the path of aircraft X that had been given a descent near carefree airport 15 NM northwest of sdl. There are numerous VFR aircraft that conduct airwork in and transition this very busy area north of the sdl and dvt airports. I am always issuing traffic advisories and restrictions/vectors to avoid these aircraft in my normal operation. In this case; I was explaining the requirements of coordinating with adjacent sectors and facilities to the developmental controller for the photo mission as well as for all the other traffic we had at the moment. Traffic was not issued to the pilot of aircraft X regarding the VFR aircraft that caused the TCAS alert. Recommendation; I would recommend that during ojti sessions; the ojti ensure that the radar display is set to his/her standards. In this case; the limited and full data blocks were at a different setting than I am used to and the data tag was leading the radar target instead of trailing the target as I normally adjust them to do.

Original NASA ASRS Text

Title: P50 Controller providing OJT described a TCAS event when Developmental failed to issue VFR traffic to an IFR aircraft; the Reporter indicating he/she was explaining required coordination to the Developmental during the occurrence.

Narrative: I was providing OJT to a Developmental who was working to several aircraft. While he was attempting to accommodate a photo mission pilot's request that would be close to the primary airport (PHX) and coordinate that operation with the neighboring sector and DVT ATCT; a VFR aircraft climbed into the path of Aircraft X that had been given a descent near Carefree Airport 15 NM NW of SDL. There are numerous VFR aircraft that conduct airwork in and transition this very busy area North of the SDL and DVT airports. I am always issuing traffic advisories and restrictions/vectors to avoid these aircraft in my normal operation. In this case; I was explaining the requirements of coordinating with adjacent sectors and facilities to the Developmental Controller for the photo mission as well as for all the other traffic we had at the moment. Traffic was not issued to the pilot of Aircraft X regarding the VFR aircraft that caused the TCAS alert. Recommendation; I would recommend that during OJTI sessions; the OJTI ensure that the RADAR display is set to his/her standards. In this case; the limited and full data blocks were at a different setting than I am used to and the data tag was leading the RADAR target instead of trailing the target as I normally adjust them to do.

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	872712
Time
Date	201002
Local Time Of Day	1801-2400
Place
Locale Reference	P50.TRACON
State Reference	AZ
Aircraft 1
Make Model Name	Global Express (BD700)
Flight Phase	Descent
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Person 1
Function	Approach Instructor
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

P50 controller providing OJT described a TCAS event when developmental failed to issue VFR traffic to an IFR aircraft; the reporter indicating he/she was explaining required coordination to the developmental during the occurrence.