Tys controller reported of a loss of separation with a small aircraft behind a heavy. Controller was...

Narrative:

I was working radar west with aircraft X the IFR pattern for practice approaches. Traffic was somewhat complex at the time with 2 satellite departures off dkx picking up IFR clearances airborne and in conflict with aircraft X's downwind; 2 satellite arrivals being vectored for approaches into gkt crossing the tys final; and several other tys arrivals. When aircraft Y popped up and requested his clearance still in a 3800 MVA; I climbed aircraft X from 4000 to 5000 so that I could give aircraft Y his IFR climbing to 4000 westbound converging with aircraft X. I informed aircraft Y of the traffic. I then spent some amount of time dealing with the 2nd IFR popup off dkx and getting a couple of arrivals onto the tys final. When it appeared that aircraft Y was clear of aircraft X's previous path; I climbed aircraft Y to a higher altitude and moved on to other duties.I was shown a replay that indicated aircraft Y flew through aircraft X's 'wake remnant'; with the falcon replay indicating the conflict for 2 sweeps with 900 feet of vertical separation from the wake.as radar controllers we do not have the luxury of the bright white track line on the falcon to give us proof that an aircraft is clear of the 'wake remnant'. And of course even the falcon does not show the wake remnant area; only the location of target hits. Until a tool is designed and incorporated that gives controllers a visual indication of the airspace impacted by the wake remnant; incidents such as this will continue. 2 sweeps of our radar is less than 10 seconds; and we normally run with our scopes looking at a 50-60 mile range. It is just not possible for the human eyeball to make that minute judgment. Then add in a complex situation where an aircraft needs to be climbed/descended as soon as possible to clear other traffic; and there is your recipe for this kind of encounter.recommendation: give us an effective wake remnant visual reminder on the radar scope.

Original NASA ASRS Text

Title: TYS Controller reported of a loss of separation with a small aircraft behind a heavy. Controller was charged with a 'Wake Remnant' separation error. Controller would like a wake remnant indicator to be able to be used by controllers.

Narrative: I was working Radar West with Aircraft X the IFR pattern for practice approaches. Traffic was somewhat complex at the time with 2 satellite departures off DKX picking up IFR clearances airborne and in conflict with Aircraft X's downwind; 2 satellite arrivals being vectored for approaches into GKT crossing the TYS final; and several other TYS arrivals. When Aircraft Y popped up and requested his clearance still in a 3800 MVA; I climbed Aircraft X from 4000 to 5000 so that I could give Aircraft Y his IFR climbing to 4000 westbound converging with Aircraft X. I informed Aircraft Y of the traffic. I then spent some amount of time dealing with the 2nd IFR popup off DKX and getting a couple of arrivals onto the TYS final. When it appeared that Aircraft Y was clear of Aircraft X's previous path; I climbed Aircraft Y to a higher altitude and moved on to other duties.I was shown a replay that indicated Aircraft Y flew through Aircraft X's 'wake remnant'; with the Falcon replay indicating the conflict for 2 sweeps with 900 feet of vertical separation from the wake.As radar controllers we do not have the luxury of the bright white track line on the Falcon to give us proof that an aircraft is clear of the 'wake remnant'. And of course even the Falcon does not show the wake remnant area; only the location of target hits. Until a tool is designed and incorporated that gives controllers a visual indication of the airspace impacted by the wake remnant; incidents such as this will continue. 2 sweeps of our radar is less than 10 seconds; and we normally run with our scopes looking at a 50-60 mile range. It is just not possible for the human eyeball to make that minute judgment. Then add in a complex situation where an aircraft needs to be climbed/descended as soon as possible to clear other traffic; and there is your recipe for this kind of encounter.Recommendation: Give us an effective wake remnant visual reminder on the radar scope.

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.

Attributes
ACN	1343634
Time
Date	201603
Local Time Of Day	1801-2400
Place
Locale Reference	TYS.TRACON
State Reference	TN
Environment
Light	Dusk
Aircraft 1
Make Model Name	Military
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Aircraft
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 25
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

Tys controller reported of a loss of separation with a small aircraft behind a heavy. Controller was charged with a 'wake remnant' separation error. Controller would like a wake remnant indicator to be able to be used by controllers.