ZAU Controllers described an airspace incursion event when incorrect data block information; caused by the wrong CID usage; coupled with a faulty track drop procedure; resulted the unauthorized airspace entry.
Synopsis
ZAU Controllers described an airspace incursion event when incorrect data block information; caused by the wrong CID usage; coupled with a faulty track drop procedure; resulted the unauthorized airspace entry.
Narrative
Aircraft Y was a departure off Burlington; IA. The R-Side departed him; then started a track at BRL with the wrong CID by accident. The CID belonged to Aircraft X; an overflight in the sector. When Aircraft Y called off BRL; we saw that Aircraft X was there instead. The R-Side then dropped the track of Aircraft X; and replaced it with Aircraft Y. We didn't put it together that he had dropped the track of the overflight. A few minutes later; the BRL Sector R-Side brought the LDB of Aircraft X to our attention at FL190; in the DBQ Sector. Aircraft X had entered DBQ's airspace without a data block or hand off. We figured out what had happened; restarted the track of Aircraft X; and coordinated with DBQ. No loss of separation occurred. Recommendation; as the D-Side; I should have been more aware of the traffic in the sector. I knew something was fishy when Aircraft X was at BRL. I did look up his flight plan. I thought that he was still in ZMP airspace; and that he would re-track when he entered ZAU. I should have researched it further.
Second reporter narrative
The Controller attempted to start a track for a departure. He used the wrong callsign causing the wrong tag to move over the BRL airport. This left the actual target untagged. The aircraft penetrated the DBQ Sector. I checked with the North Area FLM (Flight Line Manager) and said that the DBQ Controller had seen the aircraft and was protecting the altitude. He advised me that no further notification was necessary. Recommendation; the partial qualified Controller did have a D-Side. Greater attention to detail may have averted this.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.