37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1422921 |
Time | |
Date | 201702 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZBW.ARTCC |
State Reference | NH |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Light Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Descent |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Light Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Descent |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 6 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
I accepted the handoff on aircraft X descending to 27000 feet. I noticed the aircraft in a right turn and was called by ZNY N56 stating that they are going to spin aircraft X because of aircraft Y. I said roger but did not see the aircraft they were referring to. This was because this aircraft; aircraft Y was still at 36000 feet landing bos. This aircraft should have been at 27000 feet. Nothing was coordinated with this descent from N56. What made this scenario dangerous was the N56 controller spun aircraft X into the rest of their line of bos arrivals that were at 27000 feet.the conflict alert was going off constantly during this time with no coordination from N56 controller as to what the plan was for this aircraft that I had the handoff on. I was pointing out aircraft Y to other sectors down the line and N56 ran another aicraft into my airspace at 27000 feet without a handoff. I do not know if point-outs were made to other appropriate sectors from N56 but given their lack of coordination; I would assume other sectors were not coordinated with as well. This problem seemed like it was a typical issue. Either aircraft Y went NORDO; controller didn't realize aircraft Y was landing bos or aircraft Y did not start his/her descent. The part that makes this dangerous is the lack of coordination from N56. I have been at ZBW for just under 10 years and it seems like myself and the rest of the controllers here at ZBW have just accepted that ZNY does not like to use landlines and are very hard to get on the landline. This culture is the same with N90. I don't know how to fix this long-standing issue. But this lack of coordination and communication to other controllers as to what N56's plan was for this bos scenario is what made this scenario reportable and dangerous. I could not help to solve the problem because I could not find out what the controllers plan was. From my end of the scenario; it appears that if the N56 controller spun aircraft Y who was too high anyway; this would have been a lot less dangerous.
Original NASA ASRS Text
Title: ZBW Center Controller reported communication issues with ZNY leading to an aircraft entering his sector without coordination.
Narrative: I accepted the handoff on Aircraft X descending to 27000 feet. I noticed the aircraft in a right turn and was called by ZNY N56 stating that they are going to spin Aircraft X because of Aircraft Y. I said roger but did not see the aircraft they were referring to. This was because this aircraft; Aircraft Y was still at 36000 feet landing BOS. This aircraft should have been at 27000 feet. Nothing was coordinated with this descent from N56. What made this scenario dangerous was the N56 controller spun Aircraft X into the rest of their line of BOS arrivals that were at 27000 feet.The conflict alert was going off constantly during this time with no coordination from N56 controller as to what the plan was for this aircraft that I had the handoff on. I was pointing out Aircraft Y to other sectors down the line and N56 ran another aicraft into my airspace at 27000 feet without a handoff. I do not know if point-outs were made to other appropriate sectors from N56 but given their lack of coordination; I would assume other sectors were not coordinated with as well. This problem seemed like it was a typical issue. Either Aircraft Y went NORDO; controller didn't realize Aircraft Y was landing BOS or Aircraft Y did not start his/her descent. The part that makes this dangerous is the lack of coordination from N56. I have been at ZBW for just under 10 years and it seems like myself and the rest of the controllers here at ZBW have just accepted that ZNY does not like to use landlines and are very hard to get on the landline. This culture is the same with N90. I don't know how to fix this long-standing issue. But this lack of coordination and communication to other controllers as to what N56's plan was for this BOS scenario is what made this scenario reportable and dangerous. I could not help to solve the problem because I could not find out what the controllers plan was. From my end of the scenario; it appears that if the N56 controller spun Aircraft Y who was too high anyway; this would have been a lot less dangerous.
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.