WHILE IN PRECIPITATION STATIC; AN ACR MLG MISUNDERSTOOD 'COLNS' INTXN FOR 'COLIN.'

Narrative

WE WERE ABOUT TO CROSS THE RICHMOND VOR FOR THE IRONS 2 ARR TO DCA. A LINE OF TSTMS WAS BEGINNING TO IMPACT THE ARRS TO ARPTS IN THE D.C. AREA. WE WERE AT FL220 IN THE CLOUDS AND THE STATIC ON THE ZDC VHF FREQ WE WERE USING WAS SO SEVERE THAT IT WAS ALMOST IMPOSSIBLE TO UNDERSTAND CTR XMISSIONS. WHILE THE FO WAS OFF THE CTR FREQ TRYING TO GET THE DCA ATIS; I THOUGHT I HEARD ZDC ISSUE A CLRNC TO US TO FLY V16 TO COLNS INTXN AND THEN V33 TO A FIX WHICH WAS UNINTELLIGIBLE. I THOUGHT THE CLRNC WAS TAKING US TO THE COLNS INTXN (LDN 275/046) IN ORDER TO FIT US IN WITH TFC DEVIATING FOR THE WX. I TURNED TO INTERCEPT THE RICHMOND 283 DEG RADIAL ON V16. THE FO INFORMED ME THAT THERE WAS A COLIN INTXN (PXT 238/017) ON V16 THAT MADE MORE SENSE. ZDC ISSUED US A TURN TO A 180 DEG HDG AS WE WERE TRYING TO CLARIFY THE CLRNC AND THEN ISSUED FURTHER VECTORS TO PXT. BECAUSE THERE ARE 2 DIFFERENT INTXNS WITH IDENTICAL SOUNDING NAMES AND THE FACT THAT WE WERE EXPERIENCING EXTREME DIFFICULTY WITH COMS; I MADE THE TURN TOWARD THE INTXN THAT I WAS FAMILIAR WITH. THE CLRNC WAS RECEIVED VERY CLOSE TO THE RIC VOR SO I HAD ALMOST NO TIME TO ANALYZE THE RTE CAREFULLY AND I TURNED IN THE WRONG DIRECTION. THERE IS NO REASON TO HAVE INTXNS WITH SUCH SIMILAR NAMES SO CLOSE TOGETHER EVEN THOUGH ONE IS ON THE HIGH CHART AND THE OTHER IS ON THE LOW CHART.