ZAU controllers described an airspace incursion event when incorrect data block information; caused ...

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.

Original NASA ASRS Text

Title: 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.

Data retrieved from NASA's ASRS site as of April 2012 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.

Attributes
ACN	880898
Time
Date	201003
Local Time Of Day	1201-1800
Place
Locale Reference	ZAU.ARTCC
State Reference	IL
Aircraft 1
Make Model Name	Small Transport Low Wing 2 Turboprop Eng
Flight Phase	Cruise
Flight Plan	IFR
Aircraft 2
Make Model Name	Cessna Citation Undifferentiated or Other Model
Flight Phase	Climb
Flight Plan	IFR
Person 1
Function	Handoff / Assist
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Supervisor / CIC
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy

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.