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.
Synopsis
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.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.