Beech 1900
Air Traffic Control Fully Certified
Situational Awareness
ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
ATC Equipment / Nav Facility / Buildings
A Beech 1900 departed ANI on an IFR flight plan to ANC assigned altitude of FL210. All appeared normal. The aircraft data block showed the aircraft climbing and displayed a normal speed yet the data block did not move off of ANI. The aircraft traveled over one hundred thirty miles and was approximately 30 miles Northeast of SQA before there was any indication of a target on the RADAR display. Sector 5 had a strip and a flight plan but was waiting for a RADAR handoff from Sector 13. The Beech 1900 was level at FL210 and should have been tracked on RADAR.  The MEARTS software has a problem that prevented even a limited data block from being displayed at the actual location of the aircraft. This was unexpected and allowed the aircraft to enter Sector 5 for nearly 35 miles without being detected. There was no traffic at FL210 in that area of Sector 5. Do not allow the MEARTS software to block the raw RADAR data from being displayed. An indication of a Mode C intruder or limited data block is better than thinking you have good RADAR coverage and having a blocked target.
ZAN Controller described an unsafe equipment issued noting due to the MEARTS software an aircraft traversed a sector for about 35 miles without being detected.