Date: 201602
Local time of day: 1801-2400
Location: PCT.TRACON, VA
Aircraft: Military
Operator: Military
Flight plan: VFR
Mission: Tactical
Flight phase: Cruise
Airspace: Special Use SFRA
ATC / advisory: TRACON PCT
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Communication Breakdown
Second reporter function: Approach
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance; General Police / Security Involved
Contributing factors: Airspace Structure; Aircraft; Manuals; Procedure
Primary problem: Procedure

Narrative: I was given a relief briefing. The briefing included IFR traffic landing at the airports and did NOT include information about Aircraft X. Aircraft X asked for a frequency change. I asked Aircraft X if he was leaving the SFRA. Aircraft X informed me he was in the SFRA and would like a frequency change. I told Aircraft X his frequency changed was approved. I assumed this SFRA aircraft was on his discrete beacon code and he was flying below my radar coverage. I did not observe his call sign or radar track; nor was I aware of where he was in reference to my video map. Around that time another sector tracked up a primary radar target in the SFRA. I was not made aware by the supervisor that there was an aircraft in the SFRA that was a target of interest. I was later informed that Aircraft X did not have his transponder on at all and several security measures were taken including a scramble of fighter planes. In the future; I would recommend taking better action to all SFRA aircraft when they are requesting a frequency change. I would also encourage to have a procedure put in place when an aircraft is on a discrete beacon code and on your frequency for SFRA tracking purposes. This could be something as easy as tagging up the aircraft or putting a 'bat' on this aircraft. Furthermore; have the Front Line manager be aware of that immediately and to notify controllers of this.


Second narrative: While working the sector I received a call from Aircraft X asking for entry into the SFRA. I looked for the transponder code and asked the pilot about his specific location and altitude but there was no target seen around the area that the pilot had indicated which led me to believe that he has too low for radar coverage. The pilot then requested entry into the SFRA once again and I did authorize his entry but requested them to advise me whenever they required a frequency change. I usually do this as a reminder to myself of the presence of aircraft transiting the SFRA. Aircraft with pre-assigned discrete codes such as Aircraft X come in and out the area on a daily basis and are very familiar with procedures. Aircraft X obviously entered the SFRA and was not squawking or his transponder was not working properly so the primary target was detected and the authorities launched an intercept. Transponder observation is required regardless of aircraft or company that transits the SFRA; no exceptions. I relied on the pilot for a reminder to which he also forgot apparently and it caused an unnecessary disturbance.


Synopsis: A Controller allowed an aircraft to enter SFRA without an operating transponder. The Controller failed to brief the relieving Controller about the traffic in the SFRA.