Narrative:

I was working 3 sectors (rdu hi, tyi hi, and hpw hi) combined at sector 36. Most of the traffic was in hpw hi and I was having to call sector 12 on every handoff since the R12 controller was being uncooperative in accepting the handoffs in a timely manner. I accepted the handoff on cpr X from ZTL at FL330 (this aircraft had been given direct tyi from irq 350015 without prior approval; these aircraft should be on J209. The aircraft was about 10 mi south of where he should have been, putting him closer to any traffic coming from ZJX. With no other full data tags observed approaching rdu hi or tyi hi, I returned my attention to ensuring that sector 12 was going to take my handoffs prior to the boundary. I also commented to my d-side how difficult the R12 controller was making this and had my d-side call on one of the handoffs. The first time I saw air carrier Y full data block, he was inside my airspace, in handoff status, and also in conflict alert with cpr X, both aircraft at FL330. As I started to descend cpr X, I heard ZJX yell over the land line that they were descending air carrier Y to FL310. I then turned cpr X 30 degree left to help ensure horizontal separation until air carrier Y was level at FL310. After I observed air carrier Y level at FL310, I took the handoff. While this was going on, I was still having to monitor whether or not sector 12 was going to accept my handoffs. When I was satisfied the situation had been resolved, I gave cpr X direct to tyi.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR X ENTERED ZDC AIRSPACE PRIOR TO RADAR HDOF. UNAUTH UNCOORD AIRSPACE ENTRY. ARTCC ARTCC INTERFAC COORD. ACR X HAS POSSIBLE LTSS FROM CPR Y. POSSIBLE SYS ERROR.

Narrative: I WAS WORKING 3 SECTORS (RDU HI, TYI HI, AND HPW HI) COMBINED AT SECTOR 36. MOST OF THE TFC WAS IN HPW HI AND I WAS HAVING TO CALL SECTOR 12 ON EVERY HDOF SINCE THE R12 CTLR WAS BEING UNCOOPERATIVE IN ACCEPTING THE HDOFS IN A TIMELY MANNER. I ACCEPTED THE HDOF ON CPR X FROM ZTL AT FL330 (THIS ACFT HAD BEEN GIVEN DIRECT TYI FROM IRQ 350015 WITHOUT PRIOR APPROVAL; THESE ACFT SHOULD BE ON J209. THE ACFT WAS ABOUT 10 MI S OF WHERE HE SHOULD HAVE BEEN, PUTTING HIM CLOSER TO ANY TFC COMING FROM ZJX. WITH NO OTHER FULL DATA TAGS OBSERVED APCHING RDU HI OR TYI HI, I RETURNED MY ATTN TO ENSURING THAT SECTOR 12 WAS GOING TO TAKE MY HDOFS PRIOR TO THE BOUNDARY. I ALSO COMMENTED TO MY D-SIDE HOW DIFFICULT THE R12 CTLR WAS MAKING THIS AND HAD MY D-SIDE CALL ON ONE OF THE HDOFS. THE FIRST TIME I SAW ACR Y FULL DATA BLOCK, HE WAS INSIDE MY AIRSPACE, IN HDOF STATUS, AND ALSO IN CONFLICT ALERT WITH CPR X, BOTH ACFT AT FL330. AS I STARTED TO DSND CPR X, I HEARD ZJX YELL OVER THE LAND LINE THAT THEY WERE DSNDING ACR Y TO FL310. I THEN TURNED CPR X 30 DEG L TO HELP ENSURE HORIZ SEPARATION UNTIL ACR Y WAS LEVEL AT FL310. AFTER I OBSERVED ACR Y LEVEL AT FL310, I TOOK THE HDOF. WHILE THIS WAS GOING ON, I WAS STILL HAVING TO MONITOR WHETHER OR NOT SECTOR 12 WAS GOING TO ACCEPT MY HDOFS. WHEN I WAS SATISFIED THE SITUATION HAD BEEN RESOLVED, I GAVE CPR X DIRECT TO TYI.

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.