Narrative:

Had six aircraft holding over the menin intersection at varying altitudes between 15000 MSL and FL280. About 5 minutes after relieving controller; D-31 called the high sector (who owns FL290 and above) and let them know that they could send the next aircraft down (they had one holding in their airspace at same intersection at FL290). They flashed aircraft X to my sector and I accepted the handoff. I knew I had traffic at FL260 so when aircraft X checked on I gave him a descent clearance to FL270 and a new efc. In my scan I looked right over the aircraft at FL280. I believe there were several items that contributed to this error. This was the second session I had worked at this sector in several hours and in both sessions aircraft that were in hold were having multiple bad mode C hits. We were getting either bad altitudes or excessive-rate descents (3 digits with X following). During each bad hit I would verify altitudes with affected aircraft. Conflict alert was also going off because of the bad mode C hits. I made at least a half dozen calls to verify altitudes; something that is a time consumer when the sector was as complex as it was at the time. When the error occurred I wasn't totally confident that was I was seeing was real because of all of the bad information I had been seeing throughout morning. I also feel that the stmp (special traffic management program) that was suppose to be in progress at the time was not effectively used. At the time of the error there where only 7 aircraft holding. During the earlier session; there was an average of 8 aircraft holding.again; something about the eram program needs to be adjusted. I shouldn't have to feel like I am given bad information; especially when the only separation I can offer is vertical. I need a program that is efficient and reliable all of the time. When a sector is complex and holding is going on; I really shouldn't have to wait for accurate information to arrive or ask pilots for information I should already know. The stmp program needs to be used accordingly so that it can be efficient.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZLC Controllers report that automation issues with ERAM and an ineffective Special Traffic Management Program (STMP) contribute to a loss of separation event.

Narrative: Had six aircraft holding over the MENIN intersection at varying altitudes between 15000 MSL and FL280. About 5 minutes after relieving Controller; D-31 called the high sector (who owns FL290 and above) and let them know that they could send the next aircraft down (they had one holding in their airspace at same intersection at FL290). They flashed Aircraft X to my sector and I accepted the handoff. I knew I had traffic at FL260 so when Aircraft X checked on I gave him a descent clearance to FL270 and a new EFC. In my scan I looked right over the aircraft at FL280. I believe there were several items that contributed to this error. This was the second session I had worked at this sector in several hours and in both sessions aircraft that were in hold were having multiple bad Mode C hits. We were getting either bad altitudes or excessive-rate descents (3 digits with X following). During each bad hit I would verify altitudes with affected aircraft. Conflict alert was also going off because of the bad Mode C hits. I made at least a half dozen calls to verify altitudes; something that is a time consumer when the sector was as complex as it was at the time. When the error occurred I wasn't totally confident that was I was seeing was real because of all of the bad information I had been seeing throughout morning. I also feel that the STMP (Special Traffic Management Program) that was suppose to be in progress at the time was not effectively used. At the time of the error there where only 7 aircraft holding. During the earlier session; there was an average of 8 aircraft holding.Again; something about the ERAM program needs to be adjusted. I shouldn't have to feel like I am given bad information; especially when the only separation I can offer is vertical. I need a program that is efficient and reliable all of the time. When a sector is complex and holding is going on; I really shouldn't have to wait for accurate information to arrive or ask pilots for information I should already know. The STMP program needs to be used accordingly so that it can be efficient.

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