Narrative:

I was standing behind the adjacent sector (R68) in my capacity as supervisor. I observed conflict alert initiate on R67. I investigated and observed a 5 mile hoop around one of the aircraft and observed that less than standard separation was being provided. It appeared vectors had been issued because both aircraft appeared to be in slight turns. Aircraft X was descending southbound from FL400 to FL340 to comply with the SOP for traffic landing at his airport. Aircraft Y was in level flight at FL370. Aircraft X descended through the altitude of aircraft Y. I was not advised of any TCAS RA.the sector was busy with high volume. The sector was restricted with a lot of warning airspace released to the military. Additionally; weather in some other sectors had caused traffic to be rerouted into this sector. It was not unusually busy. I believe this was the cpc's (certified professional controller) first session of the day. A radar associate (d-side) was assigned. He said he was unaware that a suspected loss had happened. One reason being; the radar controllers map and target settings were to dim for him to see the scope clearly.a lowering of the sector map [monitor alert parameter] numbers when warning airspace is released. When a sector is basically cut in half with most of the airspace released to the military; the map numbers should reflect that. This would trigger tmu to initiate procedures that would reduce the traffic volume in an airspace restricted sector.

Related reports:

Google
 

Original NASA ASRS Text

Title: Front Line Manager reports of a loss of separation due to an aircraft descending through another aircraft's altitude. The D-Side was unaware of the loss of separation; due to the R-Side's dimly lit map and targets. The reporter also suggests the Monitor Alert Parameters MAP be lowered when military airspace is given away.

Narrative: I was standing behind the adjacent sector (R68) in my capacity as supervisor. I observed conflict alert initiate on R67. I investigated and observed a 5 mile hoop around one of the aircraft and observed that less than standard separation was being provided. It appeared vectors had been issued because both aircraft appeared to be in slight turns. Aircraft X was descending southbound from FL400 to FL340 to comply with the SOP for traffic landing at his airport. Aircraft Y was in level flight at FL370. Aircraft X descended through the altitude of Aircraft Y. I was not advised of any TCAS RA.The sector was busy with high volume. The sector was restricted with a lot of Warning airspace released to the military. Additionally; weather in some other sectors had caused traffic to be rerouted into this sector. It was not unusually busy. I believe this was the CPC's (Certified Professional Controller) first session of the day. A Radar Associate (D-Side) was assigned. He said he was unaware that a suspected loss had happened. One reason being; the radar controllers map and target settings were to dim for him to see the scope clearly.A lowering of the Sector MAP [Monitor Alert Parameter] numbers when warning airspace is released. When a sector is basically cut in half with most of the airspace released to the military; the MAP numbers should reflect that. This would trigger TMU to initiate procedures that would reduce the traffic volume in an airspace restricted sector.

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.