Narrative:

Air carrier X on the EAGUL3 RNAV STAR; entered my sector 50 at FL340. [I] handed off to sector 38 via a flash-through procedure. The sector 38 controller gave air carrier X a 'descend via' clearance. Air carrier X was supposed to cross tinis intersection at FL300 to clear enroute traffic in sector 50. Sector 50 had traffic at FL330 that was passing 7 NM south of tinis; tinis intersection was purposely placed on the arrival 7 NM north of the J74 corridor and with a FL300 restriction to clear enroute traffic. I noticed that air carrier X was approaching tinis and was still at FL340. Air carrier Y was eastbound at FL330. I alerted the sector 38 controller; who then turned air carrier X to a 270 heading and I turned air carrier Y 20 degrees right. Air carrier X had failed to comply with the tinis at FL300 restriction. The air carrier Y pilot asked me 'where was that guy going?' I told him that the aircraft had missed his restriction. The aircraft passed about 6.5 to 7 miles laterally. Separation would have been lost without the turns. There is an inherent problem with the way the sectors are set up in regards to this arrival. Phx landing traffic enter sector 50 as high as FL360 and are then flashed to sector 38 who then give the aircraft the descend via clearance. Sector 50 is an enroute sector and should never get involved with arrival aircraft; especially this close to a major airport (phx). The flash-through procedure also causes problems. When sector 50 gets the hand off on an arrival aircraft; they do a traffic scan; and then flash the aircraft to sector 38 who issues the descend via clearance. Sector 50 may then; 3 or 4 minutes later; get a hand off on an aircraft that will now be traffic with the arrival aircraft; but sector 50 will not be talking to the arrival aircraft. The bottom line is that sector 50; an enroute sector; should not see any arrival aircraft. These aircraft should be below sector 50; but in our push to help out the airlines; letting arrival aircraft stay higher; longer and closer to the airport; we have compromised safety. The radar controllers on sectors 38 and 50 were very experienced and we barely saw it in time to avoid a loss of separation. Less experienced controllers may not have seen the situation in time as there were no warnings. Recommendation; phx arrival aircraft should be at or below FL300 and be handed off directly to sector 38. Entering an enroute sector at FL360; this close in to a major airport; is asking for trouble and adds unnecessary complexity.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZAB Controller voiced concern regarding a PHX arrival procedure that displays aircraft to an enroute sector that allegedly should not be involved or see the subject aircraft.

Narrative: Air Carrier X on the EAGUL3 RNAV STAR; entered my Sector 50 at FL340. [I] handed off to Sector 38 via a flash-through procedure. The Sector 38 Controller gave Air Carrier X a 'descend via' clearance. Air Carrier X was supposed to cross TINIS Intersection at FL300 to clear enroute traffic in Sector 50. Sector 50 had traffic at FL330 that was passing 7 NM south of TINIS; TINIS Intersection was purposely placed on the arrival 7 NM north of the J74 corridor and with a FL300 restriction to clear enroute traffic. I noticed that Air Carrier X was approaching TINIS and was still at FL340. Air Carrier Y was eastbound at FL330. I alerted the Sector 38 Controller; who then turned Air Carrier X to a 270 heading and I turned Air Carrier Y 20 degrees right. Air Carrier X had failed to comply with the TINIS at FL300 restriction. The Air Carrier Y pilot asked me 'where was that guy going?' I told him that the aircraft had missed his restriction. The aircraft passed about 6.5 to 7 miles laterally. Separation would have been lost without the turns. There is an inherent problem with the way the sectors are set up in regards to this arrival. PHX landing traffic enter Sector 50 as high as FL360 and are then flashed to Sector 38 who then give the aircraft the descend via clearance. Sector 50 is an enroute sector and should never get involved with arrival aircraft; especially this close to a major airport (PHX). The flash-through procedure also causes problems. When Sector 50 gets the hand off on an arrival aircraft; they do a traffic scan; and then flash the aircraft to Sector 38 who issues the descend via clearance. Sector 50 may then; 3 or 4 minutes later; get a hand off on an aircraft that will now be traffic with the arrival aircraft; but Sector 50 will not be talking to the arrival aircraft. The bottom line is that Sector 50; an enroute sector; should not see any arrival aircraft. These aircraft should be below Sector 50; but in our push to help out the airlines; letting arrival aircraft stay higher; longer and closer to the airport; we have compromised safety. The RADAR Controllers on Sectors 38 and 50 were very experienced and we barely saw it in time to avoid a loss of separation. Less experienced controllers may not have seen the situation in time as there were no warnings. Recommendation; PHX arrival aircraft should be at or below FL300 and be handed off directly to Sector 38. Entering an enroute sector at FL360; this close in to a major airport; is asking for trouble and adds unnecessary complexity.

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.