Narrative:

I was conducting ojti on the burbn d-side during a skill check. Aircraft did not check on immediately and leveled below our stratum at FL340. Aircraft was also approaching our lateral boundary with ZOB; blufton and geaugua sectors. Radar controller initiated a climb to FL370. Trainee made necessary point outs to two impacted ZID sectors and ZOB blufton sector. We initiated handoff to geaugua sector with approximately 90 seconds flying time to the lateral boundary. Geaugua chose to neither take the hand-off; nor effect any coordination that they had no intention of taking the handoff. The trainee attempted to call for a handoff about 60 seconds from the boundary. When the geaugua controller finally answered; I decided I should complete the coordination. The controller indicated that he did not intend to take the handoff. I asked him what he would like us to do with the aircraft. He replied that he would not take the handoff. I said 'point out turning to a north heading.' the geaugua controller then said he would take the hand-off if the aircraft were level in 2 and 1/2 minutes. As I was on the d-side and running out of time; I again said 'point out turning to a north heading.' he accepted the point out. I told the radar controller what had been coordinated and he turned the aircraft. I then appreqed (approval requested) the aircraft turning on course reaching FL370 and the controller approved this and said 'radar contact'. Recommendation; while the initiation of the hand-off may not have been as timely as we all may have liked; I feel the geaugua controller's handling of the situation was wholly inadequate; at best. He knew immediately which aircraft we were calling about. We could see limited data blocks about 50 miles into his sector; and there was no traffic that should have prevented him from taking the hand off. He had time to ask us to stop the aircraft below his stratum. He chose not to. He could have offered a heading to miss the non-existent traffic. He chose not to. He could have asked to expedite the aircraft. He chose not to. He could have pvd'ed his perceived traffic to us and asked us to miss it. He chose not to. He could have used one of many separation techniques to alter the route or altitude of his 'traffic.' he chose not to. He could have called us with a restriction or control instructions as our LOA with ZOB outlines. He chose not to. Since he had obviously been watching the data block flash; he could have noted the aircraft's rate of climb and known the aircraft would be level in time to miss his 'traffic.' he chose not to. Ultimately; he could have done the right thing and taken the hand-off or at least given us an out. He chose not to. All too often I find that ZOB uses questionable judgment on aircraft they flash to us. Most of the time; most of the controllers at ZAU shrug their shoulders; but make it work. Although no one in this situation violated the letter of the law; the geaugua controller's actions (or inaction) truly cast asunder the spirit of cooperation that I try to instill in my trainees. Perhaps a discussion on cooperation is not out of the question.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZAU Controller providing OJT on the Burbn D-side described a near airspace incursion event when the receiving controller refused a hand off and failed to exercise a number of alternative actions which would have solved the problem.

Narrative: I was conducting OJTI on the Burbn D-side during a skill check. Aircraft did not check on immediately and leveled below our stratum at FL340. Aircraft was also approaching our lateral boundary with ZOB; Blufton and Geaugua Sectors. RADAR Controller initiated a climb to FL370. Trainee made necessary point outs to two impacted ZID Sectors and ZOB Blufton Sector. We initiated handoff to Geaugua Sector with approximately 90 seconds flying time to the lateral boundary. Geaugua chose to neither take the hand-off; nor effect any coordination that they had no intention of taking the handoff. The Trainee attempted to call for a handoff about 60 seconds from the boundary. When the Geaugua Controller finally answered; I decided I should complete the coordination. The Controller indicated that he did not intend to take the handoff. I asked him what he would like us to do with the aircraft. He replied that he would not take the handoff. I said 'Point out turning to a north heading.' The Geaugua Controller then said he would take the hand-off if the aircraft were level in 2 and 1/2 minutes. As I was on the D-side and running out of time; I again said 'Point out turning to a north heading.' He accepted the point out. I told the RADAR Controller what had been coordinated and he turned the aircraft. I then APPREQED (Approval Requested) the aircraft turning on course reaching FL370 and the controller approved this and said 'RADAR contact'. Recommendation; while the initiation of the hand-off may not have been as timely as we all may have liked; I feel the Geaugua Controller's handling of the situation was wholly inadequate; at best. He knew immediately which aircraft we were calling about. We could see limited data blocks about 50 miles into his sector; and there was no traffic that should have prevented him from taking the hand off. He had time to ask us to stop the aircraft below his stratum. He chose not to. He could have offered a heading to miss the non-existent traffic. He chose not to. He could have asked to expedite the aircraft. He chose not to. He could have PVD'ed his perceived traffic to us and asked us to miss it. He chose not to. He could have used one of many separation techniques to alter the route or altitude of his 'traffic.' He chose not to. He could have called us with a restriction or control instructions as our LOA with ZOB outlines. He chose not to. Since he had obviously been watching the data block flash; he could have noted the aircraft's rate of climb and known the aircraft would be level in time to miss his 'traffic.' He chose not to. Ultimately; he could have done the right thing and taken the hand-off or at least given us an out. He chose not to. All too often I find that ZOB uses questionable judgment on aircraft they flash to us. Most of the time; most of the controllers at ZAU shrug their shoulders; but make it work. Although no one in this situation violated the letter of the law; the Geaugua Controller's actions (or inaction) truly cast asunder the spirit of cooperation that I try to instill in my trainees. Perhaps a discussion on cooperation is not out of the question.

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.