Narrative:

Aircraft X had departed bos and had deviated to the northeast to avoid WX. For traffic, I issued a vector to aircraft X to 070 degrees and climbed him to FL350. Traffic was beginning to pick up and several aircraft checked on and began asking about WX and rides. Due to bad WX west of bos, all arrs were being rerted over ene -- scupp. The sector west of me called to coordinate a traffic situation and then an aircraft I had pointed out to another sector requested a WX deviation and I had to coordinate with that sector. The frequency was becoming congested and aircraft were taking the wrong calls. I turned aircraft X north and then northwest thinking I had cleared the traffic. I then saw aircraft X was in conflict with aircraft Y at FL330. The aircraft X was only out of FL334 and converging with aircraft Y. I issued a turn to aircraft Y to the southeast and turned aircraft X to the north. Aircraft Y saw aircraft X on TCASII and aircraft X saw aircraft Y visually and the point separation was lost. Just prior to the deviation, I received several handoffs from the other sector and overlapping data block caused some confusion as to aircraft identify. Additionally, I let frequency congestion distract me from my traffic scan. As traffic began building, I should have requested the sector be split to eliminate some of the frequency problems and to take advantage of better range on the radar.

Related reports:

Google
 

Original NASA ASRS Text

Title: RPTR STATES THAT SECTOR WAS BUSY AND STANDARD SEPARATION WAS LOST BTWN ACFT X AND Y.

Narrative: ACFT X HAD DEPARTED BOS AND HAD DEVIATED TO THE NE TO AVOID WX. FOR TFC, I ISSUED A VECTOR TO ACFT X TO 070 DEGS AND CLBED HIM TO FL350. TFC WAS BEGINNING TO PICK UP AND SEVERAL ACFT CHKED ON AND BEGAN ASKING ABOUT WX AND RIDES. DUE TO BAD WX W OF BOS, ALL ARRS WERE BEING RERTED OVER ENE -- SCUPP. THE SECTOR W OF ME CALLED TO COORDINATE A TFC SIT AND THEN AN ACFT I HAD POINTED OUT TO ANOTHER SECTOR REQUESTED A WX DEV AND I HAD TO COORDINATE WITH THAT SECTOR. THE FREQ WAS BECOMING CONGESTED AND ACFT WERE TAKING THE WRONG CALLS. I TURNED ACFT X N AND THEN NW THINKING I HAD CLRED THE TFC. I THEN SAW ACFT X WAS IN CONFLICT WITH ACFT Y AT FL330. THE ACFT X WAS ONLY OUT OF FL334 AND CONVERGING WITH ACFT Y. I ISSUED A TURN TO ACFT Y TO THE SE AND TURNED ACFT X TO THE N. ACFT Y SAW ACFT X ON TCASII AND ACFT X SAW ACFT Y VISUALLY AND THE POINT SEPARATION WAS LOST. JUST PRIOR TO THE DEV, I RECEIVED SEVERAL HDOFS FROM THE OTHER SECTOR AND OVERLAPPING DATA BLOCK CAUSED SOME CONFUSION AS TO ACFT IDENT. ADDITIONALLY, I LET FREQ CONGESTION DISTRACT ME FROM MY TFC SCAN. AS TFC BEGAN BUILDING, I SHOULD HAVE REQUESTED THE SECTOR BE SPLIT TO ELIMINATE SOME OF THE FREQ PROBS AND TO TAKE ADVANTAGE OF BETTER RANGE ON THE RADAR.

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.