37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1658567 |
Time | |
Date | 201906 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZTL.ARTCC |
State Reference | GA |
Environment | |
Flight Conditions | Marginal |
Light | Night |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 7 |
Person 2 | |
Function | Enroute Handoff / Assist |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 12 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Inflight Event / Encounter Weather / Turbulence |
Narrative:
I was the radar controller working aircraft X. They were direct on flight plan and about to enter a sector's airspace at 28;000 feet. Before I called on a handoff I noticed conflict alert was going off between the aircraft X and another aircraft in the next sector's airspace at 28;000 feet. I called them and said 'I am going to take my aircraft X down to FL260 to miss the traffic; handoff.' the controller stated they were too busy to accept a handoff on the aircraft even though they were in conflict with one of their airplanes. They stated they would 'watch him though'. I didn't have time to argue for separation purposes so I hung up the line. Aircraft X needed to deviate for weather; so I cleared him to deviate and descended them to 26;000 feet expeditiously for the traffic. My d-side had to call back later and verify they were too busy to work the aircraft.what added to this situation was the complexity of the airspace. Center traffic management unit had routed 'off-loads' into my sector to 'get in before the weather.' the problem was that the meter numbers were 4-7 on each aircraft coming in; so speed and vectors needed to be applied to each aircraft to comply with the A80 LOA (letter of agreement). No guidance or relief was given to us by calling ZJX to slow atl arrivals down. We had to shut them off ourselves. By the time the off loads were at our sector; approach cut our arrivals off and I was forced to put several aircraft; already on vectors; into holding; while other traffic situations were present. In the middle of this situation we were getting aircraft that were routed through the middle of our arrivals holding. I have worked at this center for over 10 years now and that was as unsafe a situation that should have been helped by tmu (traffic management unit) as I can remember. For a facet of ATC that has the 'big picture' to drop the ball and reroute that many aircraft into an already saturated sector when they should have had the foresight to know that the weather would be over the field before they landed is unacceptable.also the supervisor for our area needs to be held accountable for not splitting the sector due to volume. I was also told by my supervisor on that shift that the two offloads coming from adjacent areas should have been held in their airspace but that was either not communicated to the controllers by management or the request was simply not followed.
Original NASA ASRS Text
Title: ZJX Center Controllers reported sector workload was excessive due to lack of effective traffic flow management during a period of weather deviations.
Narrative: I was the Radar Controller working Aircraft X. They were direct on flight plan and about to enter a sector's airspace at 28;000 feet. Before I called on a handoff I noticed Conflict Alert was going off between the Aircraft X and another aircraft in the next sector's airspace at 28;000 feet. I called them and said 'I am going to take my Aircraft X down to FL260 to miss the traffic; handoff.' The Controller stated they were too busy to accept a handoff on the aircraft even though they were in conflict with one of their airplanes. They stated they would 'watch him though'. I didn't have time to argue for separation purposes so I hung up the line. Aircraft X needed to deviate for weather; so I cleared him to deviate and descended them to 26;000 feet expeditiously for the traffic. My D-side had to call back later and verify they were too busy to work the aircraft.What added to this situation was the complexity of the airspace. Center Traffic Management Unit had routed 'off-loads' into my sector to 'get in before the weather.' The problem was that the meter numbers were 4-7 on each aircraft coming in; so speed and vectors needed to be applied to each aircraft to comply with the A80 LOA (Letter of Agreement). No guidance or relief was given to us by calling ZJX to slow ATL arrivals down. We had to shut them off ourselves. By the time the off loads were at our sector; Approach cut our arrivals off and I was forced to put several aircraft; already on vectors; into holding; while other traffic situations were present. In the middle of this situation we were getting aircraft that were routed through the middle of our arrivals holding. I have worked at this Center for over 10 years now and that was as unsafe a situation that should have been helped by TMU (Traffic Management Unit) as I can remember. For a facet of ATC that has the 'big picture' to drop the ball and reroute that many aircraft into an already saturated sector when they should have had the foresight to know that the weather would be over the field before they landed is unacceptable.Also the Supervisor for our Area needs to be held accountable for not splitting the sector due to volume. I was also told by my Supervisor on that shift that the two offloads coming from adjacent areas should have been held in their airspace but that was either not communicated to the controllers by management or the request was simply not followed.
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.