37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1428070 |
Time | |
Date | 201703 |
Local Time Of Day | 1201-1800 |
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 | Cruise |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter Weather / Turbulence |
Narrative:
I was working all sectors in my area with midnight operations. I received a few reports of moderate chop from some heavy aircraft near the syr VOR; so I decided to call cleveland ARTCC as well as ZNY to let them know that I was receiving very poor riders in that area; and that I'd prefer if they started sending me aircraft below FL310 to avoid the bad rides. I called ZNY and in the process of trying to inform the controller of the rides; he abruptly interrupted me and informed me that he was 'getting moderate everywhere'; and had a holding stack of 7 or 8 aircraft. It sounded like the controller was quite busy; so I tried to quickly convey that I wanted the aircraft from him delivered to me below FL310. Around this time; I took a handoff on a ewr arrival on the western half of my sector. I issued the aircraft to cross hnk VOR at FL180; per the normal crossing restriction. A few minutes later; an aircraft checked onto my frequency at FL210. I had no idea who the aircraft was; and at the same time; I received a phone call from ZNY trying to reach me on the shout line.during all of this; I was quite busy; due to trying to convey the ride conditions to several aircraft; and if I recall correctly I was also sequencing several aircraft for cyul. I picked up the land line as soon as I was able; and ZNY informed me that he shipped me the aircraft accidentally; to which I responded I'll take radar and sort it out. The problem that I identified was that the aircraft was in direct confliction with my ewr arrival; especially since the ZNY controller had erroneously left the aircraft on a heading. I immediately amended the altitude of my ewr arrival; and resolved the situation. I feel if I had been busier; or not as vigilant in my identification of the confliction that it could have led to an operational error.the ZNY controller seemed quite busy so I might suggest if he was working several combined sectors that he either be provided a d-side; or another controller to help him out by taking some of his sectors. I was also quite busy at the time and I feel perhaps it would be better to have 3 controllers on the midnight shift instead of just 2. With only 2 controllers on ZBW's mid shifts; we are essentially forced to divide the shift into two 3+ hour shifts; which is extremely fatiguing especially when issues are compounded by bad rides; deviations; or simply unusual situations (that happen with regularity as any cpc knows).
Original NASA ASRS Text
Title: ZBW Center Controller reported another Controller mistakenly transferred him an aircraft that was in conflict with his traffic.
Narrative: I was working all sectors in my area with midnight operations. I received a few reports of moderate chop from some heavy aircraft near the SYR VOR; so I decided to call Cleveland ARTCC as well as ZNY to let them know that I was receiving very poor riders in that area; and that I'd prefer if they started sending me aircraft below FL310 to avoid the bad rides. I called ZNY and in the process of trying to inform the controller of the rides; he abruptly interrupted me and informed me that he was 'getting moderate everywhere'; and had a holding stack of 7 or 8 aircraft. It sounded like the controller was quite busy; so I tried to quickly convey that I wanted the aircraft from him delivered to me below FL310. Around this time; I took a handoff on a EWR arrival on the western half of my sector. I issued the aircraft to cross HNK VOR at FL180; per the normal crossing restriction. A few minutes later; an aircraft checked onto my frequency at FL210. I had no idea who the aircraft was; and at the same time; I received a phone call from ZNY trying to reach me on the shout line.During all of this; I was quite busy; due to trying to convey the ride conditions to several aircraft; and if I recall correctly I was also sequencing several aircraft for CYUL. I picked up the land line as soon as I was able; and ZNY informed me that he shipped me the aircraft accidentally; to which I responded I'll take radar and sort it out. The problem that I identified was that the aircraft was in direct confliction with my EWR arrival; especially since the ZNY controller had erroneously left the aircraft on a heading. I immediately amended the altitude of my EWR arrival; and resolved the situation. I feel if I had been busier; or not as vigilant in my identification of the confliction that it could have led to an operational error.The ZNY controller seemed quite busy so I might suggest if he was working several combined sectors that he either be provided a d-side; or another controller to help him out by taking some of his sectors. I was also quite busy at the time and I feel perhaps it would be better to have 3 controllers on the midnight shift instead of just 2. With only 2 controllers on ZBW's mid shifts; we are essentially forced to divide the shift into two 3+ hour shifts; which is extremely fatiguing especially when issues are compounded by bad rides; deviations; or simply unusual situations (that happen with regularity as any CPC knows).
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.