Small Transport; Low Wing; 2 Turbojet Eng
Air Traffic Control Fully Certified
Air Traffic Control Time Certified In Pos 1 (yrs) 25.4
Situational Awareness; Human-Machine Interface; Distraction; Confusion; Training / Qualification; Communication Breakdown
ATC Issue All Types; Airspace Violation All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Human Factors; Procedure
I was working BEARZ and noticed two aircraft flashing in conflict alert; one was an aircraft that CRIBB (sector 81) had PVDed (displaying an aircraft data tag on another Controller's radar scope) to me; Aircraft X; a LOT departure. I suppressed the conflict alert but kept the data block on Aircraft X. Aircraft X then flashed in conflict alert with another departure in C90's airspace. I suppressed that as well; then watched as Aircraft X climbed through C90's airspace; into my airspace without coordination. CRIBB (sector 81) had track control and entered an interim altitude of FL200 to prevent further conflict alert with an aircraft at FL210. I asked the FLM if he was aware of the procedures East departures uses and who was violating my airspace. He walked to the East area; C90 had requested higher on Aircraft X and CRIBB had approved FL200; but C90 is unaware of the airspace immediately abutting their facility; and everything else; and completely incurious.C90 should surrender all airspace to ZAU until controllers there can figure out what airspace their neighbors own and how to use appropriate landlines procedures.
ZAU Controller reported of an airspace violation by C90 TRACON.