 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Cak controller described an airspace incursion event when unknown/unidentified traffic appeared in his/her airspace; the reporter suggesting a process be developed to allow a search of an adjacent facility's data.
| Attributes | |
| ACN | 1032175 |
| Time | |
| Date | 201208 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | CAK.TRACON |
| State Reference | OH |
| Aircraft 1 | |
| Make Model Name | Skyhawk 172/Cutlass 172 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach Departure |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
After position transfer I went to check on the traffic. I noticed an untagged discreet beacon code at 70 over dalts northeast bound. I asked the radar controller who that was. His replied - no idea. I requested a full route on the beacon code to try and determine the aircraft identity. There was none in our system. I then tagged the aircraft with a point out tag and instructed the radar controller to separate from him as though he was IFR. A few miles past aco the aircraft called us. We had an IFR strip on him but with a different beacon code. He would have come from ZID to ZOB computer system. We changed his beacon code and successfully handed him off before he left our airspace. After discussion with cpcs they are unsure if they took the hand off and if so how the tag may have dropped. I do not believe separation was lost. After I instructed the cpc to provide separation; separation was provided. When aircraft cross over from center to center often beacon codes must be changed. Develop a method for facilities to access the neighboring center computer to search for unknown or unrecognized beacon codes. Simply having a second fdio labeled the appropriate center in facilities that border other centers would allow access to time critical information to help quickly solve/prevent situations such as these.
Original NASA ASRS Text
Title: CAK Controller described an airspace incursion event when unknown/unidentified traffic appeared in his/her airspace; the reporter suggesting a process be developed to allow a search of an adjacent facility's data.
Narrative: After position transfer I went to check on the traffic. I noticed an untagged discreet beacon code at 70 over DALTS northeast bound. I asked the RADAR Controller who that was. His replied - no idea. I requested a full route on the beacon code to try and determine the aircraft identity. There was none in our system. I then tagged the aircraft with a point out tag and instructed the RADAR Controller to separate from him as though he was IFR. A few miles past ACO the aircraft called us. We had an IFR strip on him but with a different beacon code. He would have come from ZID to ZOB computer system. We changed his beacon code and successfully handed him off before he left our airspace. After discussion with CPCs they are unsure if they took the hand off and if so how the tag may have dropped. I do not believe separation was lost. After I instructed the CPC to provide separation; separation was provided. When aircraft cross over from Center to Center often beacon codes must be changed. Develop a method for facilities to access the neighboring Center computer to search for unknown or unrecognized beacon codes. Simply having a second FDIO labeled the appropriate Center in facilities that border other Centers would allow access to time critical information to help quickly solve/prevent situations such as these.
Data retrieved from NASA's ASRS site as of July 2013 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.