Narrative:

I was working the radar position tyi hi (R38) at XA32 when I issued a descent clearance to FL240 to air carrier X when I really meant to give it to air carrier Y (similar call sign to air carrier X). I then issued a frequency change to air carrier X when it was really meant for air carrier Y. Air carrier X was en route to chs at FL350 via direct. Air carrier Y was destined orf at FL250 and ready for an en route descent. Air carrier X's mode C read FL347 and I inquired about their altitude. I received no acknowledgement. Air carrier X's mode C now read FL345 and I asked the aircraft again to verify altitude. At this time I thought the aircraft had some kind of difficulty. Air carrier X now came into conflict with air carrier Z at FL330 nebound en route to bdl. I was unable to talk to air carrier Z because they already had a frequency change. At that time, the controller working R33 (fkn lo) called me and asked about air carrier X who was on his frequency descending to FL240. At that time I realized what had happened and told the R33 controller to just turn the airplane. The controller did that and stopped air carrier X's descent at FL310. Air carrier X then returned to my frequency. Evidently, I was looking at air carrier Y's data tag calling them air carrier X. It was a busy week of traffic, I was working my 28TH hour in 3 days, breaks were kept short due to staffing and the average temperature in the area is about 81-83 degrees because of ventilation problems.

Google
 

Original NASA ASRS Text

Title: A RADAR CTLR AT ZDC INADVERTENTLY ISSUED A DSCNT TO A SIMILAR SOUNDING ACR ACFT LEVEL AT FL350 AND GAVE A FREQ CHANGE. LOSS OF SEPARATION OCCURRED WITH ANOTHER ACR ACFT AT FL330.

Narrative: I WAS WORKING THE RADAR POS TYI HI (R38) AT XA32 WHEN I ISSUED A DSCNT CLRNC TO FL240 TO ACR X WHEN I REALLY MEANT TO GIVE IT TO ACR Y (SIMILAR CALL SIGN TO ACR X). I THEN ISSUED A FREQ CHANGE TO ACR X WHEN IT WAS REALLY MEANT FOR ACR Y. ACR X WAS ENRTE TO CHS AT FL350 VIA DIRECT. ACR Y WAS DESTINED ORF AT FL250 AND READY FOR AN ENRTE DSCNT. ACR X'S MODE C READ FL347 AND I INQUIRED ABOUT THEIR ALT. I RECEIVED NO ACKNOWLEDGEMENT. ACR X'S MODE C NOW READ FL345 AND I ASKED THE ACFT AGAIN TO VERIFY ALT. AT THIS TIME I THOUGHT THE ACFT HAD SOME KIND OF DIFFICULTY. ACR X NOW CAME INTO CONFLICT WITH ACR Z AT FL330 NEBOUND ENRTE TO BDL. I WAS UNABLE TO TALK TO ACR Z BECAUSE THEY ALREADY HAD A FREQ CHANGE. AT THAT TIME, THE CTLR WORKING R33 (FKN LO) CALLED ME AND ASKED ABOUT ACR X WHO WAS ON HIS FREQ DSNDING TO FL240. AT THAT TIME I REALIZED WHAT HAD HAPPENED AND TOLD THE R33 CTLR TO JUST TURN THE AIRPLANE. THE CTLR DID THAT AND STOPPED ACR X'S DSCNT AT FL310. ACR X THEN RETURNED TO MY FREQ. EVIDENTLY, I WAS LOOKING AT ACR Y'S DATA TAG CALLING THEM ACR X. IT WAS A BUSY WK OF TFC, I WAS WORKING MY 28TH HR IN 3 DAYS, BREAKS WERE KEPT SHORT DUE TO STAFFING AND THE AVERAGE TEMP IN THE AREA IS ABOUT 81-83 DEGS BECAUSE OF VENTILATION PROBS.

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.