Narrative:

Incident occurred during my first time entering; landing and departing from the dc sfra. Sfra flight plans were filed for both arrival and departure segments and correct codes were squawked. With VFR flight following on inbound leg direct EMI - lucke - jyo; was directed by potomac TRACON to proceed direct from EMI to jyo. Landed without incident. Upon egress later the same day; while departing along runway heading of 350; picked up flight following and advised potomac appr of VFR departure from jyo and request to proceed direct EMI. Pct directed to 'proceed on course'. Pct later directed to change squawk to another discrete code. I changed codes as directed even before exiting the dc sfra. I don't know if the code change had anything to do with FAA perception of any fault in how I exercised my PIC responsibilities. Near the point that I was to exit the sfra I was advised by TRACON to call them once I landed. During that call it was explained to me that I had violated the maneuvering area and entered the sfra without authorization. The controller I spoke with referred to the fact that I was on flight following by saying 'even though I know you were on VFR flight following ...'. I'm not sure what action the FSDO will choose to take in this matter but I thought it may be important for other pilots operating within the dc sfra that this disparity between controller discretion and PIC responsibility to remain within the maneuvering area be clarified such that a PIC does not inadvertently violate sfra airspace while believing he has been legitimately directed to do so by TRACON or any FAA authorized controller. I had studied all the material available prior to entering the sfra this first time; and nowhere can I find any reference to this type of circumstance where; apparently; the PIC could be faulted for following TRACON direction while receiving VFR advisories.

Google
 

Original NASA ASRS Text

Title: PA28 pilot reports being admonished by PCT for flying outside the maneuvering area after departing JOY and requesting direct EMI. Reporter is cleared on course by PCT which apparently means as filed and not as requested. Reporter had been cleared from EMI direct JOY on the inbound leg by PCT.

Narrative: Incident occurred during my first time entering; landing and departing from the DC SFRA. SFRA Flight plans were filed for both arrival and departure segments and correct codes were squawked. With VFR flight following on inbound leg direct EMI - LUCKE - JYO; was directed by Potomac TRACON to proceed direct from EMI to JYO. Landed without incident. Upon egress later the same day; while departing along runway heading of 350; picked up flight following and advised POTOMAC APPR of VFR departure from JYO and request to proceed direct EMI. PCT directed to 'proceed on course'. PCT later directed to change squawk to another discrete code. I changed codes as directed even before exiting the DC SFRA. I don't know if the code change had anything to do with FAA perception of any fault in how I exercised my PIC responsibilities. Near the point that I was to exit the SFRA I was advised by TRACON to call them once I landed. During that call it was explained to me that I had violated the maneuvering area and entered the SFRA without authorization. The controller I spoke with referred to the fact that I was on flight following by saying 'even though I know you were on VFR flight following ...'. I'm not sure what action the FSDO will choose to take in this matter but I thought it may be important for other pilots operating within the DC SFRA that this disparity between controller discretion and PIC responsibility to remain within the maneuvering area be clarified such that a PIC does not inadvertently violate SFRA airspace while believing he has been legitimately directed to do so by TRACON or any FAA authorized controller. I had studied all the material available prior to entering the SFRA this first time; and nowhere can I find any reference to this type of circumstance where; apparently; the PIC could be faulted for following TRACON direction while receiving VFR advisories.

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