Narrative:

While working south radar, I had a BE55 that was on a flight plan (en route) from iag to tlh. His flight strip was unsuccessful with the next sector, ozr approach. An unsuccessful flight progress strip indicates that a manual handoff must take place, as well as passing manual flight information to the next facility. This happens when one host computer doesn't agree with the next, usually taking place when 2 different ctrs are involved. In this case, ZTL and ZJX. I was working approximately 6 aircraft, 4 arrs to primary airport, and 2 to secondary, as well as the BE55 en route. About 7 mi north of the boundary to ozr airspace, I called to manually coordinate the unsuccessful flight plan. The ozr controller said she was busy and she would call me right back. Subsequently, I went back to sequencing my arrs and forgot to call ozr back, and she didn't call me 'right back.' the BE55 ended up 3 mi into ozr airspace before the ozr controller called. I then realized the baron had entered ozr airspace without a proper handoff. Causal factors were the jax computer not recognizing the flight plan, my failure to ensure a handoff, and the ozr controller not taking the information when initially called.

Related reports:

Google
 

Original NASA ASRS Text

Title: APCH CTLR FORGOT TO MAKE A MANUAL HDOF TO HIS NEXT SECTOR DUE TO THE NEXT CTLR BEING BUSY ON THE FIRST TRY AND THEN SUBSEQUENTLY BOTH PARTIES FORGETTING TO CALL EACH OTHER.

Narrative: WHILE WORKING S RADAR, I HAD A BE55 THAT WAS ON A FLT PLAN (ENRTE) FROM IAG TO TLH. HIS FLT STRIP WAS UNSUCCESSFUL WITH THE NEXT SECTOR, OZR APCH. AN UNSUCCESSFUL FLT PROGRESS STRIP INDICATES THAT A MANUAL HDOF MUST TAKE PLACE, AS WELL AS PASSING MANUAL FLT INFO TO THE NEXT FACILITY. THIS HAPPENS WHEN ONE HOST COMPUTER DOESN'T AGREE WITH THE NEXT, USUALLY TAKING PLACE WHEN 2 DIFFERENT CTRS ARE INVOLVED. IN THIS CASE, ZTL AND ZJX. I WAS WORKING APPROX 6 ACFT, 4 ARRS TO PRIMARY ARPT, AND 2 TO SECONDARY, AS WELL AS THE BE55 ENRTE. ABOUT 7 MI N OF THE BOUNDARY TO OZR AIRSPACE, I CALLED TO MANUALLY COORDINATE THE UNSUCCESSFUL FLT PLAN. THE OZR CTLR SAID SHE WAS BUSY AND SHE WOULD CALL ME RIGHT BACK. SUBSEQUENTLY, I WENT BACK TO SEQUENCING MY ARRS AND FORGOT TO CALL OZR BACK, AND SHE DIDN'T CALL ME 'RIGHT BACK.' THE BE55 ENDED UP 3 MI INTO OZR AIRSPACE BEFORE THE OZR CTLR CALLED. I THEN REALIZED THE BARON HAD ENTERED OZR AIRSPACE WITHOUT A PROPER HDOF. CAUSAL FACTORS WERE THE JAX COMPUTER NOT RECOGNIZING THE FLT PLAN, MY FAILURE TO ENSURE A HDOF, AND THE OZR CTLR NOT TAKING THE INFO WHEN INITIALLY CALLED.

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.