Narrative:

A B1 was flying a high altitude radar bomb sortie. The route was in and around a large area of WX. The route also went back and forth between 2 sectors in ZDV. Denver arrs were not getting in the arrival gates to the southeast of denver unless they were coming in high over the WX, or were forced west of hgo VORTAC, west of the WX. Almost all aircraft in the sector were deviating for WX. Traffic management reroutes were a distraction. Just as we were finished rerouting an aircraft to ord we were told to give him a different route. The supervisor advised us of a plan for arrs to denver and the ultra-high sector wasn't following the plan as we were told. I could tell this was irritating the radar controller. It was going to cause us a lot of work trying to sequence them with aircraft on the west side of the WX who were much faster with the wind. The arrs wouldn't be able to make the crossing restrs, since they were so high coming in over the WX. A learjet departed pueblo eastbound. The B1 requested climb from FL280 to FL310 on the other sector's frequency. My sector accepted the handoff on the B1. The B1 was not shipped to our frequency, nor was coordination completed by the time the aircraft entered our sector to allow the other sector to keep talking to the B1 even though it was in our airspace. The other sector climbed the B1 to FL310 just as I was calling that sector to climb him because he wasn't on our frequency yet. The radar person climbed the eastbound lear to FL290. The lear was southwest of hgo and wanted higher because of moderate turbulence. The radar person queried an overflt at FL330 about deviating south for WX. The overflt was not needing to deviate for at least 60 mi so the radar person climbed the lear to FL330 (requesting FL370). The B1 was near hgo and had started a south turn. The radar person forgot that the B1 was making a south turn at hgo and by climbing the lear caused a potential conflict. The data block of the B1 was overlapping the data block of an overflt making it harder to see the information. The sector talking to the B1 called shortly thereafter and asked to keep the B1. The radar associate approved that request and also didn't notice the potential confliction. Shortly thereafter, separation was lost. The radar associate was held contributory for not noticing the confliction.

Google
 

Original NASA ASRS Text

Title: ZDV CTLR'S INVOLVED IN OPERROR WHEN NOT RECOGNIZING POTENTIAL CONFLICT DUE TO WX DEVS.

Narrative: A B1 WAS FLYING A HIGH ALT RADAR BOMB SORTIE. THE RTE WAS IN AND AROUND A LARGE AREA OF WX. THE RTE ALSO WENT BACK AND FORTH BTWN 2 SECTORS IN ZDV. DENVER ARRS WERE NOT GETTING IN THE ARR GATES TO THE SE OF DENVER UNLESS THEY WERE COMING IN HIGH OVER THE WX, OR WERE FORCED W OF HGO VORTAC, W OF THE WX. ALMOST ALL ACFT IN THE SECTOR WERE DEVIATING FOR WX. TFC MGMNT REROUTES WERE A DISTR. JUST AS WE WERE FINISHED REROUTING AN ACFT TO ORD WE WERE TOLD TO GIVE HIM A DIFFERENT RTE. THE SUPVR ADVISED US OF A PLAN FOR ARRS TO DENVER AND THE ULTRA-HIGH SECTOR WASN'T FOLLOWING THE PLAN AS WE WERE TOLD. I COULD TELL THIS WAS IRRITATING THE RADAR CTLR. IT WAS GOING TO CAUSE US A LOT OF WORK TRYING TO SEQUENCE THEM WITH ACFT ON THE W SIDE OF THE WX WHO WERE MUCH FASTER WITH THE WIND. THE ARRS WOULDN'T BE ABLE TO MAKE THE XING RESTRS, SINCE THEY WERE SO HIGH COMING IN OVER THE WX. A LEARJET DEPARTED PUEBLO EBOUND. THE B1 REQUESTED CLB FROM FL280 TO FL310 ON THE OTHER SECTOR'S FREQ. MY SECTOR ACCEPTED THE HDOF ON THE B1. THE B1 WAS NOT SHIPPED TO OUR FREQ, NOR WAS COORD COMPLETED BY THE TIME THE ACFT ENTERED OUR SECTOR TO ALLOW THE OTHER SECTOR TO KEEP TALKING TO THE B1 EVEN THOUGH IT WAS IN OUR AIRSPACE. THE OTHER SECTOR CLBED THE B1 TO FL310 JUST AS I WAS CALLING THAT SECTOR TO CLB HIM BECAUSE HE WASN'T ON OUR FREQ YET. THE RADAR PERSON CLBED THE EBOUND LEAR TO FL290. THE LEAR WAS SW OF HGO AND WANTED HIGHER BECAUSE OF MODERATE TURB. THE RADAR PERSON QUERIED AN OVERFLT AT FL330 ABOUT DEVIATING S FOR WX. THE OVERFLT WAS NOT NEEDING TO DEVIATE FOR AT LEAST 60 MI SO THE RADAR PERSON CLBED THE LEAR TO FL330 (REQUESTING FL370). THE B1 WAS NEAR HGO AND HAD STARTED A S TURN. THE RADAR PERSON FORGOT THAT THE B1 WAS MAKING A S TURN AT HGO AND BY CLBING THE LEAR CAUSED A POTENTIAL CONFLICT. THE DATA BLOCK OF THE B1 WAS OVERLAPPING THE DATA BLOCK OF AN OVERFLT MAKING IT HARDER TO SEE THE INFO. THE SECTOR TALKING TO THE B1 CALLED SHORTLY THEREAFTER AND ASKED TO KEEP THE B1. THE RADAR ASSOCIATE APPROVED THAT REQUEST AND ALSO DIDN'T NOTICE THE POTENTIAL CONFLICTION. SHORTLY THEREAFTER, SEPARATION WAS LOST. THE RADAR ASSOCIATE WAS HELD CONTRIBUTORY FOR NOT NOTICING THE CONFLICTION.

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