P50 controller described a loss of separation event when facility controllers misapplied pre-arrange...

Narrative:

Once again our facility misapplied prearranged coordination procedures; except this time it lead to a loss of separation. I observed traffic directly in front of an air carrier X at the same altitude and converging. The limited data block was a small transport and I went over to apache to ask if he was ok with the two aircraft. Prior to reaching the apache position the conflict alert activated and the apache specialist; who just relieved the position; was providing a traffic alert and a turn to the air carrier X. I then went over to navajo to ask if he was ok with the small transport where he was and he appeared to be talking to the small transport and issuing traffic as well. The navajo specialist elected to climb the small transport to 10;000 on his route (phx.V105.drk) instead running the aircraft per the SOP; which would have been at 7;000. Once the small transport is on the west side of the STAR; is where these types of aircraft are normally climbed to 10;000. The air carrier X was descending via the MAIER5 STAR and was to cross kards between 8;000 and 10;000. I had previously filed a report on the misuse of prearranged coordination procedures and a loss of separation between two air carrier jets; one climbing and the other descending. This is a common occurrence here at P50 and there has been no refresher training provided. It is basically jungle rules at times. There is plenty of airspace for the departure controllers to climb within their own airspace; above or below the arrivals descending via the stars. We are having more and more of these types of close calls with no improvement. Specialists are not taught to remain in their airspace and misapply prearranged coordination procedures all the time. I have previously reported the misuse of prearranged coordination procedures to management and nothing has changed. I recommend that prearranged coordination procedures between navajo and apache; as well as between santan and quartz; be suspended/terminated and the controllers are required to make a point out or stay in their own airspace.

Original NASA ASRS Text

Title: P50 Controller described a loss of separation event when facility controllers misapplied pre-arranged coordination procedures; the reporter noting this was a repeat of a similar same type event earlier in the year.

Narrative: Once again our facility misapplied prearranged coordination procedures; except this time it lead to a loss of separation. I observed traffic directly in front of an Air Carrier X at the SAME ALTITUDE and converging. The limited Data Block was a Small Transport and I went over to Apache to ask if he was OK with the two aircraft. Prior to reaching the Apache position the Conflict Alert activated and the Apache Specialist; who just relieved the position; was providing a traffic alert and a turn to the Air Carrier X. I then went over to Navajo to ask if he was OK with the Small Transport where he was and he appeared to be talking to the Small Transport and issuing traffic as well. The Navajo specialist elected to climb the Small Transport to 10;000 on his route (PHX.V105.DRK) instead running the aircraft per the SOP; which would have been at 7;000. Once the Small Transport is on the west side of the STAR; is where these types of aircraft are normally climbed to 10;000. The Air Carrier X was descending via the MAIER5 STAR and was to cross KARDS between 8;000 and 10;000. I had previously filed a report on the misuse of prearranged coordination procedures and a loss of separation between two Air Carrier jets; one climbing and the other descending. This is a common occurrence here at P50 and there has been no refresher training provided. It is basically jungle rules at times. There is plenty of airspace for the Departure controllers to climb within their own airspace; above or below the arrivals descending via the STARs. We are having more and more of these types of close calls with no improvement. Specialists are not taught to remain in their airspace and misapply prearranged coordination procedures all the time. I have previously reported the misuse of prearranged coordination procedures to management and NOTHING has changed. I recommend that prearranged coordination procedures between Navajo and Apache; as well as between Santan and Quartz; be suspended/terminated and the controllers are required to make a point out or stay in their own airspace.

Data retrieved from NASA's ASRS site as of July 2013 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	1019673
Time
Date	201206
Local Time Of Day	1201-1800
Place
Locale Reference	P50.TRACON
State Reference	AZ
Aircraft 1
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	Descent
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Transport
Operating Under FAR Part	Part 135
Flight Phase	Cruise
Flight Plan	IFR
Person 1
Function	Approach Departure
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy

P50 controller described a loss of separation event when facility controllers misapplied pre-arranged coordination procedures; the reporter noting this was a repeat of a similar same type event earlier in the year.