ARTCC RADAR CTLR REACTS TO CONFLICT ALERT AFTER HE HAS DSNDED AN FK10 IN CONFLICT WITH AN A320. CTLR ADMITS TO HIS ERROR; STATES DISTR CAUSED BY DIVERTING TFC IN HIS SECTOR; AND MORE THAN USUAL 'CONFLICT' POINTS.

Narrative

ALTHOUGH NO WX WAS IMPACTING THE SECTOR INVOLVED; SEVERAL ACFT WERE RTED THROUGH THIS AIRSPACE ON 'SWAP' RTES NOT NORMALLY SEEN. THE EXTRA ACFT IN THE SECTOR CAUSED SOME 'CONFLICT POINTS' IN DIFFERENT LOCATIONS THAN USUALLY OCCUR. THE PROB AROSE WHEN 1 ACFT (ACFT #1 LNDG PHL) WAS NOTICED IN CONFLICT WITH ANOTHER XING AT FL330. AS THE PHL ARR WAS TO BE DSNDED IN THE NEXT SECTOR ANYWAY; I DECIDED TO HAND OFF THE ACFT AT FL290. THE SECTOR VOLUME WAS MODERATE TO HVY AT THE TIME AND THE NORMAL ROUTINE OF DSNDING METRO (IAD; DCA; BWI) ARRS WAS CONSUMING MOST OF MY ATTN. A HDOF CTLR WAS WORKING WITH ME AND I STATED MY INTENT TO DSND ACFT #1 BUT I COULDN'T DO IT NOW BECAUSE OF THE XING TFC AT FL310 (ACFT #2). I THEN ISSUED A FEW MORE CLRNCS TO ACFT ON THE OTHER SIDE OF THE SECTOR; THEN RETURNED TO DSND ACFT #1 TO FL290. CONFLICT ALERT ACTIVATED AND ACFT #1 WAS RECLRED TO CLB AND MAINTAIN FL330. CLOSEST PROX WAS 1200 FT VERT (FL310; FL322) AND +/-3.2 MI HORIZ. IN MY RUSH TO 'MAKE THINGS MOVE ALONG;' AN ERROR IN JUDGEMENT OCCURRED; RESULTING IN A LOSS OF ATC SEPARATION.