Narrative:

I had just returned back from a break and the flm asked me to sit at D76 because the volume was going to have a 10-15min spike that would warrant having a d-side controller at the sector; and that after the spike in traffic was over he would let me know when I could slide over and relieve the radar controller. Shortly after setting down at the sector (less than 4 to 5 min) I heard the R76 controller issue a descent to air carrier X to FL300. In scanning the uret I noticed that there were a number of red alerts and told the radar controller 'hey you have some reds over here). He acknowledged my comment by saying yeah they are ok. For me the biggest factor was I could not see the data blocks on the radar scope because the radar controller's brightness settings were to low to see unless you are setting directly in front of the scope and I would estimate less than 24' away. Just a few seconds after I had told the radar controller about the 'reds' conflict alert started going off between air carrier X and air carrier Y. Air carrier Y was in level flight on J134 westbound and air carrier X was northbound direct okk and his mode C showed the aircraft at FL347 descending to FL300. The radar controller issued air carrier Y a 30 degree right turn and then air carrier X a 30 degree left turn. The radar controller then asked air carrier X to report leaving FL330. Next the radar controller issued the traffic to air carrier Y and told the pilot that maybe a left turn would have been better to which the pilot responded with a comment I can not remember. After the traffic was clear; I asked the radar controller why he issued air carrier Y a right turn instead of a left turn that would ensure air carrier Y went behind air carrier X and he said he was try to delay the conflict point in hopes that air carrier X would be able to descend below FL330 before the confliction point occurred. The biggest change I would like to see implemented is a change that would prevent the radar scope brightness to be turned down so low that only the radar controller can see it from directly in front of the scope. Often when I have asked controllers to turn up there brightness because I can not see there scopes they have responded that I can just forward my calls to them. This negates the point of having a second pair of eyes to assist with ensuring safety. I also feel that the light level on the platform needs to be raised. I understand that years ago the light levels were turned down to prevent glare on the radar scopes but with the new technology there is no need for this to be continued. By leaving the light level low on the platform it allows controllers to turn there scope brightness way down and it also leads to fatigue.

Google
 

Original NASA ASRS Text

Title: ZID D-Side Controller witnessed a loss of separation by the R-Side; listing 'brightness' settings as a causal factor.

Narrative: I had just returned back from a break and the FLM asked me to sit at D76 because the volume was going to have a 10-15min spike that would warrant having a D-Side controller at the sector; and that after the spike in traffic was over he would let me know when I could slide over and relieve the RADAR Controller. Shortly after setting down at the sector (less than 4 to 5 min) I heard the R76 Controller issue a descent to Air Carrier X to FL300. In scanning the URET I noticed that there were a number of RED alerts and told the RADAR Controller 'hey you have some reds over here). He acknowledged my comment by saying yeah they are ok. For me the biggest factor was I could not see the Data Blocks on the RADAR scope because the RADAR controller's brightness settings were to low to see unless you are setting directly in front of the scope and I would estimate less than 24' away. Just a few seconds after I had told the RADAR Controller about the 'reds' conflict alert started going off between Air Carrier X and Air Carrier Y. Air Carrier Y was in level flight on J134 Westbound and Air Carrier X was Northbound direct OKK and his Mode C showed the aircraft at FL347 descending to FL300. The RADAR Controller issued Air Carrier Y a 30 degree right turn and then Air Carrier X a 30 degree left turn. The RADAR Controller then asked Air Carrier X to report leaving FL330. Next the RADAR Controller issued the traffic to Air Carrier Y and told the pilot that maybe a left turn would have been better to which the pilot responded with a comment I can not remember. After the traffic was clear; I asked the RADAR Controller why he issued Air Carrier Y a right turn instead of a left turn that would ensure Air Carrier Y went behind Air Carrier X and he said he was try to delay the conflict point in hopes that Air Carrier X would be able to descend below FL330 before the confliction point occurred. The biggest change I would like to see implemented is a change that would prevent the RADAR scope brightness to be turned down so low that only the RADAR Controller can see it from directly in front of the scope. Often when I have asked controllers to turn up there brightness because I can not see there scopes they have responded that I can just forward my calls to them. This negates the point of having a second pair of eyes to assist with ensuring safety. I also feel that the light level on the platform needs to be raised. I understand that years ago the light levels were turned down to prevent glare on the RADAR scopes but with the new technology there is no need for this to be continued. By leaving the light level low on the platform it allows controllers to turn there scope brightness way down and it also leads to fatigue.

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