 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
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.
| Attributes | |
| ACN | 1312911 |
| Time | |
| Date | 201511 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZOB.ARTCC |
| State Reference | OH |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Medium Large Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | Direct |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 6.0 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
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.
Original NASA ASRS Text
Title: 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.
Narrative: 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.
Data retrieved from NASA's ASRS site 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.