Date: 201407
Local time of day: 1801-2400
Location: ZDV.ARTCC, CO
Aircraft: Medium Transport
Operator: Military
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZDV
ATC / advisory: Center ZDV
Second aircraft: Small Transport; Low Wing; 2 Turboprop Eng
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Training / Qualification
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic
Contributing factors: Procedure; Equipment / Tooling
Primary problem: Procedure

Narrative: TAD radar search and beacon were out of service requiring non-radar routes for all aircraft at or below FL220. There were multiple areas of moderate to heavy precipitation in Sector 41 requiring aircraft to deviate. There were multiple aircraft in and out of PUB; ALS; MVI; COS; and RCA (non-radar). There were departures out the south gate as well. The radar outage required multiple position reports using multiple frequency sites (aircraft cannot hear each other and you depending on which transmitter site you use). Aircraft X was requesting a GPS practice approach into ALS; due to the radar outage; I was unable to provide this service (you are required to be in radar at the IAF for GPS approach). Aircraft X changed plans and requested direct CIM rest of flight plan to CVS. Aircraft Y was an APA arrival at FL220 direct BRK. Aircraft X was level FL180; requested FL230 and weather deviations. Aircraft Y was radar contact lost at this point; while Aircraft X was still in radar. I climbed Aircraft X and approved weather deviations knowing I would loose Aircraft X for a short period of time until reaching FL230. I had numerous other situations going on at this time. I called radar contact lost on Aircraft X. Shortly after; Aircraft Y popped up in radar close to the same time as Aircraft X. At this time; they were approximately 8 miles apart laterally enclosing and 400 FT apart vertically. I radar identified them; asked Aircraft X to expedite and report reaching FL230. He did this before separation was lost. Without the weather deviations; Aircraft X would never have been in conflict with Aircraft Y. If TAD had been in service; while this would have still been a complex session on Sector 41; it would have however been without question a very reasonable task. You cannot allow for weather deviations with non-radar situations. However; you cannot force an aircraft through weather. It is completely unacceptable to put controllers and aircraft into these situations on a daily basis with TAD being out of service. I know this is not the only unsafe situation that has occurred on that sector. All area 3 controllers know this is unsafe and cannot understand how it can take over 3 months to fix a radar outage. TAD needs to be back in service.




Synopsis: ZDV Controller reports of a radar outage that is causing problems in the sector. Two aircraft are being worked non-radar; then appear on the radar and are on a conflicting course. Controller resolves the issue without a separation loss.