ZTL controller experienced a reported loss of separation; the reporter indicated computer detected e...

Narrative:

The two aircraft were both inbound to the same airport from over the same VORTAC. The A320 was in front and faster than the crj-200. I descended both aircraft and ended up with 4.79 miles and 700 ft between them according to the printout. In the FAA they used to round up .2ths of a mile and they would look for any target jumps when there was an 'event.' now it seems like they just take whatever information that the computer says that two aircraft printed with less than standard separation. Did the equipment get better in reporting events? I think there might have been a target jump involved in this event but I am not sure. Around the VORTAC target jumps have always been a reality. Of course for a while over 80% standard separation was a proximity event and was not considered an operational event. I guess that also has changed and now it seems like the FAA wants to have as many documented 'events' as possible on the books.

Original NASA ASRS Text

Title: ZTL Controller experienced a reported loss of separation; the reporter indicated computer detected error measurements within tenths of a mile are not discernible to controllers at the operational positions.

Narrative: The two aircraft were both inbound to the same airport from over the same VORTAC. The A320 was in front and faster than the CRJ-200. I descended both aircraft and ended up with 4.79 miles and 700 FT between them according to the printout. In the FAA they used to round up .2ths of a mile and they would look for any target jumps when there was an 'event.' Now it seems like they just take whatever information that the computer says that two aircraft printed with less than standard separation. Did the equipment get better in reporting events? I think there might have been a target jump involved in this event but I am not sure. Around the VORTAC target jumps have always been a reality. Of course for a while over 80% standard separation was a Proximity Event and was not considered an operational event. I guess that also has changed and now it seems like the FAA wants to have as many documented 'events' as possible on the books.

Data retrieved from NASA's ASRS site as of July 2013 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	1037905
Time
Date	201209
Local Time Of Day	1801-2400
Place
Locale Reference	ZTL.ARTCC
State Reference	GA
Aircraft 1
Make Model Name	Regional Jet 200 ER/LR (CRJ200)
Operating Under FAR Part	Part 121
Flight Phase	Descent
Flight Plan	IFR
Aircraft 2
Make Model Name	A320
Operating Under FAR Part	Part 121
Flight Phase	Descent
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict

ZTL controller experienced a reported loss of separation; the reporter indicated computer detected error measurements within tenths of a mile are not discernible to controllers at the operational positions.