An airspace infraction occurred when a data block was accidentally dropped. The reporter noted differing URET practices that likely contributed to the event.
Synopsis
An airspace infraction occurred when a data block was accidentally dropped. The reporter noted differing URET practices that likely contributed to the event.
Narrative
I noticed a limited data block at FL380 northwest bound in my airspace and initially thought it was a ring around target from another aircraft northbound over URSUS. When I realized it was not ring around I did a flight plan read out on the code and realized it was Aircraft X. I then started a track and attempted to call on frequency for the aircraft and he did not acknowledge. I then called Sector 60 and 62 to attempt to get the aircraft on our frequency. When Aircraft X did call; a couple of minutes later; we had him IDENT for identification verification. Later asked what was the last frequency Aircraft X was on he advised he was on 132 something and he noticed he was out of range and went to 126.27 because he heard the controller on the other frequency sending other aircraft to that frequency and they sent him to 126.32. I was sure we took the hand off and dropped track by mistake. In URET a lot of people use the drop track delete feature. If this was not used the aircraft would remain in URET with the call sign turning brown because the aircraft is not tracked. When drop track delete is selected the aircraft falls out of URET. Also must be aware of limited data blocks in your airspace or close to the boundary.
Second reporter narrative
When the track on Aircraft X was dropped I was on the line with Santo Domingo coordinating a route deviation on an aircraft soon to enter Santo Domingo's airspace. From the time the track was dropped on Aircraft X until the time the aircraft reached the R62 boundary I was on and off the coordination line organizing my strip bay and working with strips coming off the printer. Recommendation: Scan for Mode-C intruders.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.