Narrative:

On the morning in question, data blocks were jumping and the supervisor in charge thought she witnessed a system error. I informed her that the targets were jumping and I felt that 5 mi had never been compromised. The aedp did not register a loss of sep. She however ordered an n-tap!. The n-tap was missing data, so this event was categorized a 'non-occurrence.' the remainder of the morning I reported similar losses of flight data in roughly the same area. This continued the rest of my shift, with no corrective action taken.

Related reports:

Google
 

Original NASA ASRS Text

Title: SUPVR CTLR QUESTIONED CTLR WHEN TRACK JUMP APPEARED TO PUT ACFT LESS THAN 5 MILES.

Narrative: ON THE MORNING IN QUESTION, DATA BLOCKS WERE JUMPING AND THE SUPVR IN CHARGE THOUGHT SHE WITNESSED A SYS ERROR. I INFORMED HER THAT THE TARGETS WERE JUMPING AND I FELT THAT 5 MI HAD NEVER BEEN COMPROMISED. THE AEDP DID NOT REGISTER A LOSS OF SEP. SHE HOWEVER ORDERED AN N-TAP!. THE N-TAP WAS MISSING DATA, SO THIS EVENT WAS CATEGORIZED A 'NON-OCCURRENCE.' THE REMAINDER OF THE MORNING I RPTED SIMILAR LOSSES OF FLT DATA IN ROUGHLY THE SAME AREA. THIS CONTINUED THE REST OF MY SHIFT, WITH NO CORRECTIVE ACTION TAKEN.

Data retrieved from NASA's ASRS site as of August 2007 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.