Narrative:

I was working both the southwest and southeast arrival gates. In the southeast we were on route over quail descending via the bosss arrival. Weather started to build southeast of quail and ZDV called to inform me that an aircraft was going to be deviating west of course. This takes the aircraft out of my airspace and into DR4's. I informed the tmu what was happening. Several minutes later the tmu came to me and said that you own over to stakr which is about 15 miles west of quail. I told him that that would still increase my workload in that gate because I would need all of the aircraft to turn north just west of quail so that I could get them on a base for the runway or I would have to coordinate every aircraft with the controllers working final because I wouldn't be able to comply with the SOP. He told me it was only a few planes and to make it work. I still have no idea what altitudes I own and what transfer of control I have from ZDV because stakr is another ZDV sector then the sector working the arrival gate. ZDV stopped coordinating with me so aircraft were just checking on saying that they were deviating.I asked the supervisor to call ZDV and ask that their controller coordinate so I know what they are doing. ZDV called me up and coordinated that all aircraft would be deviating west and direct to bostn on the bosss arrival then descending via. Also; the dunnn satellite arrival comes in from the southeast and passes just south of stakr. When I saw the first dunnn arrival I asked the tmu what the plan was with the dunnn and he said he didn't know. My traffic at the time didn't conflict with it so everything was fine. About 10 minutes later aircraft Y comes in on the dunnn. Aircraft X comes in from the southeast only a few miles ahead. I don't talk to aircraft X until he is right at the boundary with ZDV and he informs me that he is too high to make the restriction at bostn because he was held up. There is a standard set by tmu that if an arrival can't make it into the arrival gate then they take away airspace from departures so that planes can keep coming into D01's airspace. All the coordination is that arrivals owns to a certain fix. There is nothing that defines what altitude arrivals owns to or what boundary line splits the departure and arrival airspace. Arrival also doesn't know what they have control for or where they have control. All of these could be assumed or further coordinated but I would expect that if someone coordinates with me that all of that would be defined. If there is coordination like that done then the dunnns should have been discontinued or some other coordination should be accomplished to separate the route so that the aircraft are not being held up. Also; if the aircraft can't make it into the gate then maybe they should be rerouted to another arrival to get into denver.

Related reports:

Google
 

Original NASA ASRS Text

Title: D01 TRACON Controller reported aircraft were deviating due to weather; TMU took airspace from the departure area; told reporter he had the airspace. Controller was not sure how aircraft should enter or exit the area and what exactly the procedures were for him to follow.

Narrative: I was working both the southwest and southeast arrival gates. In the southeast we were on route over QUAIL descending via the BOSSS arrival. Weather started to build southeast of QUAIL and ZDV called to inform me that an aircraft was going to be deviating west of course. This takes the aircraft out of my airspace and into DR4's. I informed the TMU what was happening. Several minutes later the TMU came to me and said that you own over to STAKR which is about 15 miles west of QUAIL. I told him that that would still increase my workload in that gate because I would need all of the aircraft to turn north just west of QUAIL so that I could get them on a base for the runway or I would have to coordinate every aircraft with the controllers working final because I wouldn't be able to comply with the SOP. He told me it was only a few planes and to make it work. I still have no idea what altitudes I own and what transfer of control I have from ZDV because STAKR is another ZDV sector then the sector working the arrival gate. ZDV stopped coordinating with me so aircraft were just checking on saying that they were deviating.I asked the supervisor to call ZDV and ask that their controller coordinate so I know what they are doing. ZDV called me up and coordinated that all aircraft would be deviating west and direct to BOSTN on the BOSSS arrival then descending via. Also; the DUNNN satellite arrival comes in from the southeast and passes just south of STAKR. When I saw the first DUNNN arrival I asked the TMU what the plan was with the DUNNN and he said he didn't know. My traffic at the time didn't conflict with it so everything was fine. About 10 minutes later Aircraft Y comes in on the DUNNN. Aircraft X comes in from the southeast only a few miles ahead. I don't talk to Aircraft X until he is right at the boundary with ZDV and he informs me that he is too high to make the restriction at BOSTN because he was held up. There is a standard set by TMU that if an arrival can't make it into the arrival gate then they take away airspace from departures so that planes can keep coming into D01's airspace. All the coordination is that arrivals owns to a certain fix. There is nothing that defines what altitude arrivals owns to or what boundary line splits the departure and arrival airspace. Arrival also doesn't know what they have control for or where they have control. All of these could be assumed or further coordinated but I would expect that if someone coordinates with me that all of that would be defined. If there is coordination like that done then the DUNNNs should have been discontinued or some other coordination should be accomplished to separate the route so that the aircraft are not being held up. Also; If the aircraft can't make it into the gate then maybe they should be rerouted to another arrival to get into Denver.

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.