37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1335393 |
Time | |
Date | 201602 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | PCT.TRACON |
State Reference | VA |
Aircraft 1 | |
Make Model Name | Military |
Flight Phase | Cruise |
Route In Use | None |
Flight Plan | VFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 1.0 |
Person 2 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 6.5 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Clearance Deviation - Procedural FAR Deviation - Procedural Published Material / Policy |
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.
Original NASA ASRS Text
Title: 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.
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.
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.