Narrative:

I was working sector 91 which owns FL260 and above when combined with 65. I got a handoff from 42 the low sector on aircraft X; a very slow climbing aircraft; [westbound] to san. I climbed aircraft X to FL260.we have a problem with the LUCKI1 star; which goes from phx to bza on the way to san. It alerts all the time with the airspace in the yuma range as the system thinks it gets too close to the military airspace. We have turned it in many times but are told over and over by management and airspace that there is nothing we can do about it. I saw the usual alert and as he was climbing to my lowest altitude (FL260) westbound did not think much of it. He was climbing very slowly; my intuition kicked in; and I quickly looked [up] the low sector and the alert that we are taught to ignore. Aircraft Y was around bza at FL270 or so with clearance down to FL250 on the HYDRR1 arrival into phx. When I saw this; I immediately stopped aircraft X in sector 42's airspace at FL240 and coordinated with 42. If I had not looked and stopped him; his climb rate would have put both the aircraft at mohak intersection at FL250 at the same time. This made me upset because I have been telling management over and over about this and they just say 'there is nothing we can do.' I don't believe this is safe and this is a perfect example of what can go wrong if we keep ignoring this dangerous situation.recommendation: I can't believe that there is really no way to stop this departure from alerting red on every departure and desensitizing everyone to the alert. Someone needs to take the lead on this and make it happen even if it means a change to the departure. If it means changing the parameters of the alert; it would still be safer than the way it is now. Not only are controllers being taught to ignore this false alert (sometimes) it is getting them to become less aware of all red alerts as there are so many of them.

Google
 

Original NASA ASRS Text

Title: ZAB Controller reported being instructed to ignore alerts within the YUMA range airspace; consequently desensitizing controllers.

Narrative: I was working sector 91 which owns FL260 and above when combined with 65. I got a handoff from 42 the low sector on Aircraft X; a very slow climbing aircraft; [westbound] to SAN. I climbed Aircraft X to FL260.We have a problem with the LUCKI1 star; which goes from PHX to BZA on the way to SAN. It alerts all the time with the airspace in the YUMA range as the system thinks it gets too close to the military airspace. We have turned it in many times but are told over and over by management and airspace that there is nothing we can do about it. I saw the usual alert and as he was climbing to my lowest altitude (FL260) westbound did not think much of it. He was climbing very slowly; my intuition kicked in; and I quickly looked [up] the low sector and the alert that we are taught to ignore. Aircraft Y was around BZA at FL270 or so with clearance down to FL250 on the HYDRR1 arrival into PHX. When I saw this; I immediately stopped Aircraft X in sector 42's airspace at FL240 and coordinated with 42. If I had not looked and stopped him; his climb rate would have put both the aircraft at MOHAK intersection at FL250 at the same time. This made me upset because I have been telling management over and over about this and they just say 'there is nothing we can do.' I don't believe this is safe and this is a perfect example of what can go wrong if we keep ignoring this dangerous situation.Recommendation: I can't believe that there is really no way to stop this departure from alerting red on every departure and desensitizing everyone to the alert. Someone needs to take the lead on this and make it happen even if it means a change to the departure. If it means changing the parameters of the alert; it would still be safer than the way it is now. Not only are controllers being taught to ignore this false alert (sometimes) it is getting them to become less aware of all red alerts as there are so many of them.

Data retrieved from NASA's ASRS site 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.