Narrative:

I was working sector 48 alone. Sector 48 is an ultra low sector (10000 ft and below). It's really just a center run approach control. Aircraft #2 was inbound to clt from the north. Aircraft #2 was handed off to clt without incident. Clt called about 2 mins later to get control for turns (back toward where the aircraft was supposed to be). I cleared aircraft #1 from hky to clt via depart southwest, turn left heading 180 degrees per LOA. I coordinated with clt and clt approved it reference aircraft #2. During this time I was distraction, working aircraft #3. As clt does not approve overflts, I needed to rerte aircraft #3 into gso airspace. I did not recognize the airport, had to look it up. The computer did not recognize the airport and I had to enter the latitude/longitude. As I was clearing the aircraft and trying to educate the pilot about filing a route through non radar airspace, aircraft #1 departed. Because aircraft #3 and I were blocking the frequency, aircraft #1 couldn't check in. I had also forgotten to depart the aircraft in the computer so the data block didn't automatic acquire. Fortunately, I finally noticed the limited data block. I interrupted my conversation with aircraft #3 and called the aircraft #1. The pilot answered promptly and I turned the aircraft to a heading of 240 degrees. Clt had turned aircraft #2 almost 90 degrees to put him back in the arrival area, despite having approved direct to the airport. To complicate matters, this heading took aircraft #2 over the radar site so that I couldn't see the target.

Google
 

Original NASA ASRS Text

Title: OPDEV WHEN A BA31 DEP OFF HKY ENTERED CLT AIRSPACE REQUIRING EVASIVE ACTION BY RPTR AND CLT TO AVOID A DC3 BEING WORKED BY CLT. CLT HAD APPROVED THE HDG WITH REF TO THE DC3.

Narrative: I WAS WORKING SECTOR 48 ALONE. SECTOR 48 IS AN ULTRA LOW SECTOR (10000 FT AND BELOW). IT'S REALLY JUST A CTR RUN APCH CTL. ACFT #2 WAS INBOUND TO CLT FROM THE N. ACFT #2 WAS HANDED OFF TO CLT WITHOUT INCIDENT. CLT CALLED ABOUT 2 MINS LATER TO GET CTL FOR TURNS (BACK TOWARD WHERE THE ACFT WAS SUPPOSED TO BE). I CLRED ACFT #1 FROM HKY TO CLT VIA DEPART SW, TURN L HDG 180 DEGS PER LOA. I COORDINATED WITH CLT AND CLT APPROVED IT REF ACFT #2. DURING THIS TIME I WAS DISTR, WORKING ACFT #3. AS CLT DOES NOT APPROVE OVERFLTS, I NEEDED TO RERTE ACFT #3 INTO GSO AIRSPACE. I DID NOT RECOGNIZE THE ARPT, HAD TO LOOK IT UP. THE COMPUTER DID NOT RECOGNIZE THE ARPT AND I HAD TO ENTER THE LATITUDE/LONGITUDE. AS I WAS CLRING THE ACFT AND TRYING TO EDUCATE THE PLT ABOUT FILING A RTE THROUGH NON RADAR AIRSPACE, ACFT #1 DEPARTED. BECAUSE ACFT #3 AND I WERE BLOCKING THE FREQ, ACFT #1 COULDN'T CHK IN. I HAD ALSO FORGOTTEN TO DEPART THE ACFT IN THE COMPUTER SO THE DATA BLOCK DIDN'T AUTO ACQUIRE. FORTUNATELY, I FINALLY NOTICED THE LIMITED DATA BLOCK. I INTERRUPTED MY CONVERSATION WITH ACFT #3 AND CALLED THE ACFT #1. THE PLT ANSWERED PROMPTLY AND I TURNED THE ACFT TO A HDG OF 240 DEGS. CLT HAD TURNED ACFT #2 ALMOST 90 DEGS TO PUT HIM BACK IN THE ARR AREA, DESPITE HAVING APPROVED DIRECT TO THE ARPT. TO COMPLICATE MATTERS, THIS HDG TOOK ACFT #2 OVER THE RADAR SITE SO THAT I COULDN'T SEE THE TARGET.

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.