37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1443003 |
Time | |
Date | 201704 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | D01.TRACON |
State Reference | CO |
Aircraft 1 | |
Make Model Name | Medium Transport Low Wing 2 Turboprop Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Medium Transport Low Wing 2 Turboprop Eng |
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) 1 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
I was working the r-side at sector 13; and had fed a few den arrivals to denver approach when we went into a shutoff situation due to wind shear at den airport. I was working the den arrivals into a holding stack at wooky when I observed an IFR aircraft (aircraft X) approaching and then entering my airspace without coordination. I brought up the data tag; and called the ramms/tomsn arrival controller at denver approach to determine the aircraft's intentions. The controller who answered the line was not aware of the aircraft's intentions. It appeared the aircraft was on a downwind or delay vector. I then approved a point-out on that aircraft. I notified the controller in charge (controller in charge) of the situation. Within the next few minutes; I observed a second IFR aircraft (aircraft Y) approaching and then entering my airspace without coordination; also apparently on a downwind or delay vector. I called the ramms/tomsn arrival controller to determine the second aircraft's intentions and approve another point-out. Within another few minutes; I observed a third IFR aircraft (aircraft X; a second time) approaching and entering my airspace without coordination; apparently still on vectors to final or a delay vector. I called the ramms/tomsn arrival controller to approve the third point-out. The controller in charge observed these events as they occurred; and reported them to ZDV management.I understood that the denver approach controllers were experiencing a high workload due to wind shear and the precipitation that was displayed southeast of ramms/tomsn inside denver approach's airspace. The uncertain response from the controller who answered the ramms/tomsn line; and the lack of pro-active coordination was apparently due to lack of controller staffing/lack of assistance provided to the controller working the position; such as from a coordinator or assist controller. In the event of a den arrival shutoff by denver approach; which suggests a high workload; it would seem to make sense that arrival controllers be supported by a coordinator or assist controller.
Original NASA ASRS Text
Title: Denver Center Controller reported uncoordinated airspace violations due to windshear and high workload into DEN Airport.
Narrative: I was working the R-side at Sector 13; and had fed a few DEN arrivals to Denver Approach when we went into a shutoff situation due to wind shear at DEN airport. I was working the DEN arrivals into a holding stack at WOOKY when I observed an IFR aircraft (Aircraft X) approaching and then entering my airspace without coordination. I brought up the data tag; and called the RAMMS/TOMSN arrival controller at Denver Approach to determine the aircraft's intentions. The controller who answered the line was not aware of the aircraft's intentions. It appeared the aircraft was on a downwind or delay vector. I then approved a point-out on that aircraft. I notified the Controller in Charge (CIC) of the situation. Within the next few minutes; I observed a second IFR aircraft (Aircraft Y) approaching and then entering my airspace without coordination; also apparently on a downwind or delay vector. I called the RAMMS/TOMSN arrival controller to determine the second aircraft's intentions and approve another point-out. Within another few minutes; I observed a third IFR aircraft (Aircraft X; a second time) approaching and entering my airspace without coordination; apparently still on vectors to final or a delay vector. I called the RAMMS/TOMSN arrival controller to approve the third point-out. The CIC observed these events as they occurred; and reported them to ZDV management.I understood that the Denver Approach controllers were experiencing a high workload due to wind shear and the precipitation that was displayed southeast of RAMMS/TOMSN inside Denver Approach's airspace. The uncertain response from the controller who answered the RAMMS/TOMSN line; and the lack of pro-active coordination was apparently due to lack of controller staffing/lack of assistance provided to the controller working the position; such as from a coordinator or assist controller. In the event of a DEN arrival shutoff by Denver Approach; which suggests a high workload; it would seem to make sense that arrival controllers be supported by a coordinator or assist controller.
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.