Narrative:

I observed this situation from d-side position. Having just been relieved from radar, I was 'cleaning up' before taking a break. Low altitude sector (110-190). The twin cessna was sbound at FL180. The DC9 was nwbound, climbing out of 12000 ft for FL190. The twin requested FL200 for turbulence. After coordinating, radar controller climbed the twin to FL200, projecting twin to be level before DC9, and ample time and airspace to turn one or both aircraft prior to point of confliction. At this point, the frequency failed, although we were not aware of it until the twin appeared to leveloff at FL190. Since the twin's altitude put him in conflict with the DC9, the radar controller attempted to call the twin, then the DC9, with no response from either aircraft. As the DC9 leveled at FL190, the radar vector lines indicated imminent loss of separation, and the possibility of an near midair collision. The vscs indicated that we were transmitting (I tried to, from d-side), but lack of response (radio and radar) proved that aircraft were not receiving our xmissions. Radar controller attempted to select standby equipment, but vscs would not allow this. Multiple attempts by radar and data controllers to select buec resulted in messages of 'buec unavailable.' by going through other sectors, we had other aircraft broadcast control instructions and frequency changes over our frequency. DC9 pilot later reported that he observed the twin on TCASII and did not believe they were a factor. Notes: as far as I can determine, the vscs report of 'buec unavailable' was in error. I haven't been able to find other sectors using buec at that time, let alone our sites. (Maintenance was eventually able to return our buec so we could select it.) technicians reported that our line to the transmitter was lost. We got no notification, nor indication. Frequency was out for 5 mins. Twin cessna climbed 1000 FPM to FL185, then 3000 FPM to FL200. TCASII probably would have activated if aircraft had been any closer. We could have had a local tower or approach control use their emergency radios to call aircraft directly. Radar controller panicked, and allowed that to cloud her response.

Google
 

Original NASA ASRS Text

Title: ARTCC RADAR CTLR CLBED A SBOUND TWIN CESSNA TO FL200 FROM FL180 AND HAD AN ACR DC9 CLBING TO FL190 NWBOUND. THE CTLR ANTICIPATED THE CESSNA BEING LEVEL BEFORE THE DC9 GOT TO FL190 AND HAD TIME TO VECTOR IF IT DIDN'T WORK. THE CESSNA SLOWED ITS CLB AND THE CTLR HAD A RADIO FAILURE ABOUT THE SAME TIME. CTLR UNABLE TO SELECT BUEC OR GET RADIO TO WORK AS THE VSCS SYS QUIT. ADJACENT SECTOR WAS ABLE TO CONTACT THE ACFT, BUT NOT BEFORE SEPARATION WAS LOST.

Narrative: I OBSERVED THIS SIT FROM D-SIDE POS. HAVING JUST BEEN RELIEVED FROM RADAR, I WAS 'CLEANING UP' BEFORE TAKING A BREAK. LOW ALT SECTOR (110-190). THE TWIN CESSNA WAS SBOUND AT FL180. THE DC9 WAS NWBOUND, CLBING OUT OF 12000 FT FOR FL190. THE TWIN REQUESTED FL200 FOR TURB. AFTER COORDINATING, RADAR CTLR CLBED THE TWIN TO FL200, PROJECTING TWIN TO BE LEVEL BEFORE DC9, AND AMPLE TIME AND AIRSPACE TO TURN ONE OR BOTH ACFT PRIOR TO POINT OF CONFLICTION. AT THIS POINT, THE FREQ FAILED, ALTHOUGH WE WERE NOT AWARE OF IT UNTIL THE TWIN APPEARED TO LEVELOFF AT FL190. SINCE THE TWIN'S ALT PUT HIM IN CONFLICT WITH THE DC9, THE RADAR CTLR ATTEMPTED TO CALL THE TWIN, THEN THE DC9, WITH NO RESPONSE FROM EITHER ACFT. AS THE DC9 LEVELED AT FL190, THE RADAR VECTOR LINES INDICATED IMMINENT LOSS OF SEPARATION, AND THE POSSIBILITY OF AN NMAC. THE VSCS INDICATED THAT WE WERE XMITTING (I TRIED TO, FROM D-SIDE), BUT LACK OF RESPONSE (RADIO AND RADAR) PROVED THAT ACFT WERE NOT RECEIVING OUR XMISSIONS. RADAR CTLR ATTEMPTED TO SELECT STANDBY EQUIP, BUT VSCS WOULD NOT ALLOW THIS. MULTIPLE ATTEMPTS BY RADAR AND DATA CTLRS TO SELECT BUEC RESULTED IN MESSAGES OF 'BUEC UNAVAILABLE.' BY GOING THROUGH OTHER SECTORS, WE HAD OTHER ACFT BROADCAST CTL INSTRUCTIONS AND FREQ CHANGES OVER OUR FREQ. DC9 PLT LATER RPTED THAT HE OBSERVED THE TWIN ON TCASII AND DID NOT BELIEVE THEY WERE A FACTOR. NOTES: AS FAR AS I CAN DETERMINE, THE VSCS RPT OF 'BUEC UNAVAILABLE' WAS IN ERROR. I HAVEN'T BEEN ABLE TO FIND OTHER SECTORS USING BUEC AT THAT TIME, LET ALONE OUR SITES. (MAINT WAS EVENTUALLY ABLE TO RETURN OUR BUEC SO WE COULD SELECT IT.) TECHNICIANS RPTED THAT OUR LINE TO THE XMITTER WAS LOST. WE GOT NO NOTIFICATION, NOR INDICATION. FREQ WAS OUT FOR 5 MINS. TWIN CESSNA CLBED 1000 FPM TO FL185, THEN 3000 FPM TO FL200. TCASII PROBABLY WOULD HAVE ACTIVATED IF ACFT HAD BEEN ANY CLOSER. WE COULD HAVE HAD A LCL TWR OR APCH CTL USE THEIR EMER RADIOS TO CALL ACFT DIRECTLY. RADAR CTLR PANICKED, AND ALLOWED THAT TO CLOUD HER RESPONSE.

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.