Medium Large Transport; Low Wing; 2 Turbojet Eng
Air Traffic Control Fully Certified
Air Traffic Control Time Certified In Pos 1 (yrs) 6.0
Situational Awareness; Workload; Communication Breakdown
ATC Issue All Types; Airspace Violation All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Issued Advisory / Alert; Air Traffic Control Provided Assistance
Procedure; Weather; Airspace Structure
I took a verbal point out from the X sector. The aircraft went through my airspace and was handed to the Y sector. Z Sector controller called and said they had traffic for the pointed out aircraft. I said I took a point out. I tried to figure out who was speaking to the aircraft. Sector X had just opened and the rides were horrible; that is the reason for the abnormal descent on the Toronto lander. I also heard that another sector had just split into separate sectors also (the low sectors) which I believe also accounted for some confusion. Z Sector did not get a point out on the aircraft descending and they had traffic for the pointed out aircraft. From X Sector that is a normal practice to point aircraft out in that area out to Y Sector and go straight to Z Sector. I'm guessing with the bad rides the controller got unexpectedly busy; it looked that way from my sector.I don't have any recommendations; we usually hand the aircraft to Brecksville; not on to the low side.
One sector pointed out an aircraft to another sector and handed it off to the subsequent sector. The sector the aircraft was being handed off to had conflicting traffic and attempted to coordinate control instructions to the Controller working the aircraft. Due to weather complexities; sectors that were combined were being split to alleviate the workload. In the ensuing confusion of closed sectors being opened and busy traffic; the aircraft was not pointed out to one of the newly opened sectors.