Small Transport
Air Traffic Control Fully Certified
Air Traffic Control Time Certified In Pos 1 (yrs) 30
Time Pressure; Situational Awareness; Human-Machine Interface; Distraction; Communication Breakdown; Confusion
ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Procedure; Human Factors; ATC Equipment / Nav Facility / Buildings
Aircraft X was landing DPA.  I descended Aircraft X from 11;000 feet to 4;000 feet.  I was handing aircraft off to C90.  The required routing is JOT..DPA.  We have no depictions of C90's airspace on our radar screens.  I initiated the hand off to C90 and it flashed to the Sector 2.  When Aircraft X approached the boundary I called for a handoff.  The Sector 2 controller said Aircraft X was in Sector's 1 airspace.  I said I do not know about that but the aircraft flashed to his sector.Previously during the shift; I work two other DPA landers the same way over JOT and the Sector 2 controller accepted the aircraft; not an issue.The sector 2 controller should accept aircraft and not wait till the boundary. Maybe the Sector 2 controller's trainer should have stepped in and bought the hand off in a timely manner.We treat all the approach controls the same way.  There is no mapping of their internal sectors on our radar screens or overhead maps.  Their configurations can change with runway usage.  If the data block flashes to a specific sector at the approach control we ship the aircraft to that appropriate frequency.  I was following the rules.  We have been taught that there is no notice holding in ATC and the receiving controller needs to coordinate in a timely manner.
ZAU Controller describes handing off an aircraft but the receiving facility doesn't take it. He then calls the facility and the other facility tells the Controller the aircraft is in another sector's airspace without a handoff.