37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1324517 |
Time | |
Date | 201601 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | GPT.TRACON |
State Reference | MS |
Aircraft 1 | |
Make Model Name | Fighter |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Approach Departure |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 3.0 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy |
Narrative:
Practice approaches being conducted almost continuously by varying types of aircraft as well as numerous system failures such as aircraft data tags not acquiring on targets or automated handoffs failing. After aircraft X's second approach; I gave him his beacon code for the next leg of his flight and terminated the existing data tag. I then turned my attention to sequencing several other aircraft. For some reason aircraft X never tagged up on new beacon code and was left runway heading and at 2;000 feet. After a few minutes; ARTCC called wondering about him being in their airspace and I began work on getting him back into my airspace as well as making his data tag acquire somehow. Eventually he just had to be manually tagged and handed of manually.many aircraft conduct practice approaches at this airport but differ greatly in how they file flight plans. Sometimes it takes a lot of time and effort for controllers to make the correct flight plan active which takes their eyes and attention off the radar scope. When traffic reaches a certain level; it would be nice if someone could make sure flight plans were in the system properly before practice approaches are ready to continue the rest of their flight plan when radar controller is too busy to do so. I think stars (new ATC software/hardware) will help as well.
Original NASA ASRS Text
Title: A departing aircraft radar data tag did not acquire on the target. The Controller did not notice and forgot about the aircraft. The adjacent sector noticed the target in their airspace and reminded the previous Controller about the aircraft.
Narrative: Practice approaches being conducted almost continuously by varying types of aircraft as well as numerous system failures such as aircraft data tags not acquiring on targets or automated handoffs failing. After Aircraft X's second approach; I gave him his beacon code for the next leg of his flight and terminated the existing data tag. I then turned my attention to sequencing several other aircraft. For some reason Aircraft X never tagged up on new beacon code and was left runway heading and at 2;000 feet. After a few minutes; ARTCC called wondering about him being in their airspace and I began work on getting him back into my airspace as well as making his data tag acquire somehow. Eventually he just had to be manually tagged and handed of manually.Many aircraft conduct practice approaches at this airport but differ greatly in how they file flight plans. Sometimes it takes a lot of time and effort for controllers to make the correct flight plan active which takes their eyes and attention off the radar scope. When traffic reaches a certain level; it would be nice if someone could make sure flight plans were in the system properly before practice approaches are ready to continue the rest of their flight plan when radar controller is too busy to do so. I think STARS (New ATC software/hardware) will help as well.
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.