Narrative:

Departed W41 (crisfield; md) planning to [a nearby airport] VFR. Shortly after departure I contacted patuxent control tower and asked if R4005 was hot. Tower said 'not hot.' I acknowledged that transmission and proceeded direct to whino intersection; my filed sfra flight plan entry point into the sfra airspace. I climbed to 6;500 feet crossing the chesapeake bay. About 8 miles southeast of whino; potomac approach control gave me approval to proceed direct [destination]. Shortly thereafter; potomac approach control told me [I have a phone number] to call upon landing pertaining to a possible airspace violation. After landing; I called and talked to a controller at patuxent approach control. He asked me if I was familiar with the restricted airspace in the patuxent area; in particular R4005. I advised him yes and that I had called the control tower and they told me that R4005 was 'not hot' and I proceeded direct to whino. He advised me that the R4005 was active above 3;500 MSL (it is usually surface to but not including FL250). He told me there was no issue and no action would be taken. He was not aware of my radio call to the tower. Upon reflection; contacting the approach control would have been appropriate as; apparently; the tower controller was not aware of the status of the restricted area. It would have been helpful if the tower controller had directed me to contact approach or verified the status of R4005 with approach before responding. If R4005 was cold approach control most likely would have given me flight following across the bay; which would have also been a good idea.

Related reports:

Google
 

Original NASA ASRS Text

Title: Pilot reported of violating a restricted area. Pilot called Tower near restricted area; ATC advised Restricted area was not hot. Pilot continued on course. Pilot then was advised after landing by approach control that he had violated restricted area in question.

Narrative: Departed W41 (Crisfield; MD) planning to [a nearby airport] VFR. Shortly after departure I contacted Patuxent Control Tower and asked if R4005 was hot. Tower said 'not hot.' I acknowledged that transmission and proceeded direct to WHINO intersection; my filed SFRA Flight Plan entry point into the SFRA airspace. I climbed to 6;500 feet crossing the Chesapeake Bay. About 8 miles southeast of WHINO; Potomac Approach Control gave me approval to proceed direct [destination]. Shortly thereafter; Potomac Approach Control told me [I have a phone number] to call upon landing pertaining to a possible airspace violation. After landing; I called and talked to a controller at Patuxent Approach Control. He asked me if I was familiar with the restricted airspace in the Patuxent area; in particular R4005. I advised him yes and that I had called the Control Tower and they told me that R4005 was 'not hot' and I proceeded direct to WHINO. He advised me that the R4005 was active above 3;500 MSL (it is usually surface to but not including FL250). He told me there was no issue and no action would be taken. He was not aware of my radio call to the Tower. Upon reflection; contacting the Approach Control would have been appropriate as; apparently; the Tower Controller was not aware of the status of the restricted area. It would have been helpful if the tower controller had directed me to contact approach or verified the status of R4005 with approach before responding. If R4005 was cold Approach Control most likely would have given me flight following across the Bay; which would have also been a good idea.

Data retrieved from NASA's ASRS site 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.