Narrative:

Reverse flow. Dal was north; dfw was south. This is unusual and complex. East satellite position (dallas north; north) works the dal departures and hands them off to DR1 [departure radar 1] on a heading. DR1 then climbs them; gets them on course and sequences them with the other traffic. In this situation; I was distracted by two imminent issues; there was an overtake with 2 dfw departures on the same route and I had to turn one; and I received a departure directly from dal rather than from dallas north; and noticing many ldbs [limited data blocks] in dallas north's airspace; I was quickly searching their traffic and coordinating with them. I had stopped aircraft X for some other crossing dal crossing traffic so he leveled at 130. When I realized I had not climbed him and observed aircraft Y crossing underneath him; I turned aircraft X right; but I believe he got together with the aircraft Y climbing out below him. I probably needed a handoff based on my experience level and lack of proficiency time on departures. Definitely recommend 5 miles in trail (mit) off dfw for same routes because those two that almost got together were an unneeded distraction. When we go to a very unusual configuration like that; the flm's [front line manager's] need to keep a close watch and control flow if needed. My supervisor did ask if I wanted departures stopped; but at that point it wasn't needed. I overheard another controller complaining that they were unsure of the airspace; I was extremely unsure of the airspace.

Google
 

Original NASA ASRS Text

Title: D10 Controller reports of a loss of separation between two aircraft. Controller did not turn aircraft soon enough to avoid other traffic and reported he was unsure of what airspace he had due to an airport configuration that he was not too sure of.

Narrative: Reverse flow. DAL was north; DFW was south. This is unusual and complex. East satellite position (Dallas North; N) works the DAL departures and hands them off to DR1 [Departure Radar 1] on a heading. DR1 then climbs them; gets them on course and sequences them with the other traffic. In this situation; I was distracted by two imminent issues; there was an overtake with 2 DFW departures on the same route and I had to turn one; and I received a departure directly from DAL rather than from Dallas North; and noticing many LDBs [Limited Data Blocks] in Dallas North's airspace; I was quickly searching their traffic and coordinating with them. I had stopped Aircraft X for some other crossing DAL crossing traffic so he leveled at 130. When I realized I had not climbed him and observed Aircraft Y crossing underneath him; I turned Aircraft X right; but I believe he got together with the Aircraft Y climbing out below him. I probably needed a handoff based on my experience level and lack of proficiency time on departures. Definitely recommend 5 Miles in Trail (MIT) off DFW for same routes because those two that almost got together were an unneeded distraction. When we go to a very unusual configuration like that; the FLM's [Front Line Manager's] need to keep a close watch and control flow if needed. My supervisor did ask if I wanted departures stopped; but at that point it wasn't needed. I overheard another controller complaining that they were unsure of the airspace; I was extremely unsure of the airspace.

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.