Narrative:

I was working meacham south. I had just started talking to aircraft X west bound on the south airway at 8;000 feet. I descended him to 6;000 feet on initial contact because it was coordinated to leave him at 6;000 feet and hand him off to meacham north to by-pass all the gky traffic I was working. Unknown to me; and my hand-off; there was aircraft Y level at 6;000 feet right under aircraft X. Aircraft Y was going to gky; but we didn't see him since he wasn't in hand-off status and there were numerous aircraft tags in the same area. Once we seaw aircraft Y; aircraft X was descending through 7;200 feet; and I told him to maintain 7;000 feet. He was descending too rapidly and went down to 6;600 feet then climbed back up. Dallas south turned aircraft Y north to avoid aircraft X.the whole gky arrival push was the busiest I've seen since I've been here; busier than the super bowl! The traffic display over-head was completely full of gky traffic! We needed to open meacham north; meacham west; meacham south; hand-off meacham south and AR9. There was no pre-planning for this event at all. ZFW had to stop the corners a couple times for the gky arrivals because we had too many aircraft landing there in our airspace. We had to slow aircraft to 170 knots on initial contact; and I was vectoring into 2 down-winds. Aircraft were being vectored so many more miles; a lot declared minimum fuel; and a few had to divert to other airports. The south airway crossing traffic (southeast corner to ftw; afw; etc. And southwest corner to dal; ads; etc.) should have been routed around outside of our airspace to eliminate the crossing of traffic and the congestion by gky. During major events at at&T stadium; more needs to be done to set flow in gky and eliminate the congestion around the gky airport. The crossing traffic on the south airway should not be occurring either. The meacham positions need to be split and opened a lot sooner.

Related reports:

Google
 

Original NASA ASRS Text

Title: TRACON Controller reported a loss of separation due to traffic volume and workload.

Narrative: I was working Meacham South. I had just started talking to Aircraft X west bound on the south airway at 8;000 feet. I descended him to 6;000 feet on initial contact because it was coordinated to leave him at 6;000 feet and hand him off to Meacham North to by-pass all the GKY traffic I was working. Unknown to me; and my hand-off; there was Aircraft Y level at 6;000 feet right under Aircraft X. Aircraft Y was going to GKY; but we didn't see him since he wasn't in hand-off status and there were numerous aircraft tags in the same area. Once we seaw Aircraft Y; Aircraft X was descending through 7;200 feet; and I told him to maintain 7;000 feet. He was descending too rapidly and went down to 6;600 feet then climbed back up. Dallas South turned Aircraft Y north to avoid Aircraft X.The whole GKY arrival push was the busiest I've seen since I've been here; busier than the Super Bowl! The traffic display over-head was completely full of GKY traffic! We needed to open Meacham North; Meacham West; Meacham South; Hand-off Meacham South and AR9. There was no pre-planning for this event at all. ZFW had to stop the corners a couple times for the GKY arrivals because we had too many aircraft landing there in our airspace. We had to slow aircraft to 170 knots on initial contact; and I was vectoring into 2 down-winds. Aircraft were being vectored so many more miles; a lot declared minimum fuel; and a few had to divert to other airports. The south airway crossing traffic (southeast corner to FTW; AFW; etc. and southwest corner to DAL; ADS; etc.) should have been routed around outside of our airspace to eliminate the crossing of traffic and the congestion by GKY. During major events at AT&T stadium; more needs to be done to set flow in GKY and eliminate the congestion around the GKY airport. The crossing traffic on the south airway should not be occurring either. The Meacham positions need to be split and opened a lot sooner.

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.