Narrative:

Aircraft Y departing VFR to the northwest departed runway 35L and I put him on a 300 degree heading until exiting class D airspace because I was putting aircraft X going IFR to the southwest on runway heading off the same runway. I ensured there was adequate separation between the 2 aircraft before I shipped either of them to rdr; our parent IFR facility.I didn't have much going on so I was looking at my scope and I saw that aircraft Y was going straight north level at 4;400 feet about 5 miles west of the runway and about 7 miles north or so. He was probably going to gaf; a little airport north of here that the university uses to practice landings or what not. I then saw that rdr was turning aircraft X toward aircraft Y when aircraft X was around 4;000 feet and I got a collision alert on the stars as aircraft X continued to climb past 4;000 feet. I promptly called rdr to let them know what was going on when the aircraft were about 2 nm apart and was told that they were; 'okay.'I thought this was garbage separation. Aircraft X literally climbed and turned right at aircraft Y leaving aircraft Y with few options to avoid a collision. Aircraft X's pilot sounded annoyed that rdr did this to them as well. Military or not; this was a bet in slow traffic that could have resulted in something very bad. Aircraft X totally buzzed aircraft Y so I'm sure the wake turbulence alone was a lot of fun.it seemed that the rdr controller attempted to use visual separation very poorly. They did not take into account aircraft performance; or allow any room for anyone to escape a collision. There was no need to even turn and climb aircraft X at the same time. There was nothing going on when this happened. There was a total disregard for the VFR aircraft which was much slower than the IFR one. The controller should be trained on proper visual separation and aircraft performance. They should also learn to communicate with the tower more to let me know what exact hair brained maneuver they are doing so I don't have to guess as to why my collision alert is going off. There was no need for this.

Related reports:

Google
 

Original NASA ASRS Text

Title: GFK Controller reported a NMAC situation caused by RDR Approach.

Narrative: Aircraft Y departing VFR to the NW departed Runway 35L and I put him on a 300 degree heading until exiting class D airspace because I was putting Aircraft X going IFR to the SW on runway heading off the same runway. I ensured there was adequate separation between the 2 aircraft before I shipped either of them to RDR; our parent IFR facility.I didn't have much going on so I was looking at my scope and I saw that Aircraft Y was going straight north level at 4;400 feet about 5 miles west of the runway and about 7 miles north or so. He was probably going to GAF; a little airport north of here that the university uses to practice landings or what not. I then saw that RDR was turning Aircraft X toward Aircraft Y when Aircraft X was around 4;000 feet and I got a collision alert on the STARS as Aircraft X continued to climb past 4;000 feet. I promptly called RDR to let them know what was going on when the aircraft were about 2 nm apart and was told that they were; 'Okay.'I thought this was garbage separation. Aircraft X literally climbed and turned right at Aircraft Y leaving Aircraft Y with few options to avoid a collision. Aircraft X's pilot sounded annoyed that RDR did this to them as well. Military or not; this was a bet in slow traffic that could have resulted in something very bad. Aircraft X totally buzzed Aircraft Y so I'm sure the wake turbulence alone was a lot of fun.It seemed that the RDR controller attempted to use visual separation very poorly. They did not take into account aircraft performance; or allow any room for anyone to escape a collision. There was no need to even turn and climb Aircraft X at the same time. There was nothing going on when this happened. There was a total disregard for the VFR aircraft which was much slower than the IFR one. The controller should be trained on proper visual separation and aircraft performance. They should also learn to communicate with the tower more to let me know what exact hair brained maneuver they are doing so I don't have to guess as to why my collision alert is going off. There was no need for this.

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.