Narrative:

I was working the csg TRACON west sector as a radar controller. When I assumed the position, small aircraft X was one of the VFR aircraft which I assumed control of. The controller who I relieved said that he was heading 180 degree but she did not know his destination even though she had asked him about three times. At this point he was about 10 mi north of csg VORTAC, and navigating on his own. I was extremely busy during this time. During this period, I requested help by having the coordinator position staffed several different times. Due to staffing, it was manned only during the heaviest stints. Since the aircraft was not conflicting with my traffic, I did not notice as it left my sector along V321 and went into R3002B. When I noticed, he was about 7 mi into it and more than halfway through. Since it is active to 8000' there was little I could do except wait for him to clear it. Contributing factors. Aircraft was not mode C equipped. An altitude on the radar screen may have caused notice to be taken sooner. My workload. Although I could not have split off any sectors (only working one), I could have used more help from a coordinator or my radar associate controller. In this facility the radar associate also has the primary duty to man the FD10 flight strip printer and do flight data functions. Pilot's awareness of R3002 status. I was surprised to learn tonight that atl FSS does not maintain status information on R3002. I assumed that this was included in a pilot briefing. Pilot should have been aware of his planned route transiting the airspace and he should have inquired of its status.

Related reports:

Google
 

Original NASA ASRS Text

Title: SMA X UNAUTH PENETRATION OF R3002B PLTDEV.

Narrative: I WAS WORKING THE CSG TRACON W SECTOR AS A RADAR CTLR. WHEN I ASSUMED THE POS, SMA X WAS ONE OF THE VFR ACFT WHICH I ASSUMED CTL OF. THE CTLR WHO I RELIEVED SAID THAT HE WAS HDG 180 DEG BUT SHE DID NOT KNOW HIS DEST EVEN THOUGH SHE HAD ASKED HIM ABOUT THREE TIMES. AT THIS POINT HE WAS ABOUT 10 MI N OF CSG VORTAC, AND NAVING ON HIS OWN. I WAS EXTREMELY BUSY DURING THIS TIME. DURING THIS PERIOD, I REQUESTED HELP BY HAVING THE COORDINATOR POS STAFFED SEVERAL DIFFERENT TIMES. DUE TO STAFFING, IT WAS MANNED ONLY DURING THE HEAVIEST STINTS. SINCE THE ACFT WAS NOT CONFLICTING WITH MY TFC, I DID NOT NOTICE AS IT LEFT MY SECTOR ALONG V321 AND WENT INTO R3002B. WHEN I NOTICED, HE WAS ABOUT 7 MI INTO IT AND MORE THAN HALFWAY THROUGH. SINCE IT IS ACTIVE TO 8000' THERE WAS LITTLE I COULD DO EXCEPT WAIT FOR HIM TO CLR IT. CONTRIBUTING FACTORS. ACFT WAS NOT MODE C EQUIPPED. AN ALT ON THE RADAR SCREEN MAY HAVE CAUSED NOTICE TO BE TAKEN SOONER. MY WORKLOAD. ALTHOUGH I COULD NOT HAVE SPLIT OFF ANY SECTORS (ONLY WORKING ONE), I COULD HAVE USED MORE HELP FROM A COORDINATOR OR MY RADAR ASSOCIATE CTLR. IN THIS FAC THE RADAR ASSOCIATE ALSO HAS THE PRIMARY DUTY TO MAN THE FD10 FLT STRIP PRINTER AND DO FLT DATA FUNCTIONS. PLT'S AWARENESS OF R3002 STATUS. I WAS SURPRISED TO LEARN TONIGHT THAT ATL FSS DOES NOT MAINTAIN STATUS INFO ON R3002. I ASSUMED THAT THIS WAS INCLUDED IN A PLT BRIEFING. PLT SHOULD HAVE BEEN AWARE OF HIS PLANNED RTE TRANSITING THE AIRSPACE AND HE SHOULD HAVE INQUIRED OF ITS STATUS.

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.