Narrative:

Staff specialist getting tmu currency. I plugged in and got very busy. Descended aircraft air carrier X to FL350. Route was vxv..gso.J14 to iad or dca. Normal restr is for aircraft to cross gso at FL330. I was working R28. I descended aircraft to FL350 and handed off to R33. Normally R33 would issue gso at FL330. I was getting very busy, strips piling up and d-side no help. Several aircraft head-on and climbing. As I was completing my scan, I saw the aircraft at ZDC boundary. I went to drop full data block and saw it cross boundary reading (on limited) 333 and changed to FL330 as it crossed the boundary. R33 did not coordinate anything with me at R28. So, I expected aircraft to cross gso at FL330 (well below ZDC-72). ZDC boundary is east of gso. It is possible that aircraft was above FL330 (assigned altitude) as it crossed ZDC boundary. As I said, I was very busy (for me, a tmu specialist with 8 hours per month) (for currency), especially since I was by myself. Aircraft may have been inside of protected boundary area. I was too busy with supervisor (in a rush) and not paying real close attention. Later, I asked for help and never got it. Very, very busy. Again, I'm not sure what R33 did about descent or pointout to ZDC-72. No coordination was done with me at R28.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZTL SECTOR 28 CTLR FALLS BEHIND IN COORD AND PLANNING AND ADJOINING ZTL SECTOR 33 APPARENTLY DSNDS ACR WITHOUT COORD TO MEET ZDC AIRSPACE XING RESTRS.

Narrative: STAFF SPECIALIST GETTING TMU CURRENCY. I PLUGGED IN AND GOT VERY BUSY. DSNDED ACFT ACR X TO FL350. RTE WAS VXV..GSO.J14 TO IAD OR DCA. NORMAL RESTR IS FOR ACFT TO CROSS GSO AT FL330. I WAS WORKING R28. I DSNDED ACFT TO FL350 AND HANDED OFF TO R33. NORMALLY R33 WOULD ISSUE GSO AT FL330. I WAS GETTING VERY BUSY, STRIPS PILING UP AND D-SIDE NO HELP. SEVERAL ACFT HEAD-ON AND CLBING. AS I WAS COMPLETING MY SCAN, I SAW THE ACFT AT ZDC BOUNDARY. I WENT TO DROP FULL DATA BLOCK AND SAW IT CROSS BOUNDARY READING (ON LIMITED) 333 AND CHANGED TO FL330 AS IT CROSSED THE BOUNDARY. R33 DID NOT COORDINATE ANYTHING WITH ME AT R28. SO, I EXPECTED ACFT TO CROSS GSO AT FL330 (WELL BELOW ZDC-72). ZDC BOUNDARY IS E OF GSO. IT IS POSSIBLE THAT ACFT WAS ABOVE FL330 (ASSIGNED ALT) AS IT CROSSED ZDC BOUNDARY. AS I SAID, I WAS VERY BUSY (FOR ME, A TMU SPECIALIST WITH 8 HRS PER MONTH) (FOR CURRENCY), ESPECIALLY SINCE I WAS BY MYSELF. ACFT MAY HAVE BEEN INSIDE OF PROTECTED BOUNDARY AREA. I WAS TOO BUSY WITH SUPVR (IN A RUSH) AND NOT PAYING REAL CLOSE ATTN. LATER, I ASKED FOR HELP AND NEVER GOT IT. VERY, VERY BUSY. AGAIN, I'M NOT SURE WHAT R33 DID ABOUT DSCNT OR POINTOUT TO ZDC-72. NO COORD WAS DONE WITH ME AT R28.

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.