Narrative:

I was working the bvt high sector. We were being impacted by heavy WX. Bvt is a sector that has too much traffic, but nobody will do anything to help. I had approximately 18 aircraft on frequency and 3 controllers assisting. The situation was getting out of hand. I, at one point, had 4 possible sits going on at once, when we were told that the snitch had gone off. Our first question was, 'which one was it?' the deal was checked and an 'entap' showed slight target jump, so it was called a non occurrence. I personally doubt. Actually, I was more worried about 2 other sits because I knew the one the snitch caught was ok and they wouldn't hit. Our staffing is always low and the traffic is at times out of control, even without WX. Something should be done.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN ARTCC RADAR CTLR RECEIVED A CONFLICT ALARM BTWN 2 ACFT DURING A HVY TFC SESSION. ALTHOUGH AN INVESTIGATION DETERMINED THAT THERE WAS NO LOSS OF SEPARATION, THE RPTR CLAIMS THAT THE BVT HIGH SECTOR HAS TOO MUCH TFC AND DIFFICULT TO WORK.

Narrative: I WAS WORKING THE BVT HIGH SECTOR. WE WERE BEING IMPACTED BY HVY WX. BVT IS A SECTOR THAT HAS TOO MUCH TFC, BUT NOBODY WILL DO ANYTHING TO HELP. I HAD APPROX 18 ACFT ON FREQ AND 3 CTLRS ASSISTING. THE SIT WAS GETTING OUT OF HAND. I, AT ONE POINT, HAD 4 POSSIBLE SITS GOING ON AT ONCE, WHEN WE WERE TOLD THAT THE SNITCH HAD GONE OFF. OUR FIRST QUESTION WAS, 'WHICH ONE WAS IT?' THE DEAL WAS CHKED AND AN 'ENTAP' SHOWED SLIGHT TARGET JUMP, SO IT WAS CALLED A NON OCCURRENCE. I PERSONALLY DOUBT. ACTUALLY, I WAS MORE WORRIED ABOUT 2 OTHER SITS BECAUSE I KNEW THE ONE THE SNITCH CAUGHT WAS OK AND THEY WOULDN'T HIT. OUR STAFFING IS ALWAYS LOW AND THE TFC IS AT TIMES OUT OF CTL, EVEN WITHOUT WX. SOMETHING SHOULD BE DONE.

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.