Narrative:

I noticed a flight plan on a C172 in my edst (uret) list because he was wafdof/iafdof at 5;000 ft northwest bound. The routing was X23..lbv..kmy. The first two fixes are in florida; and the destination is in alaska. I pulled up a route display on the radar display and it showed the aircraft route line southwest of oma approach's (R90) airspace. Some time later I realized that no one had called and appreqed the wafdof. At that time I pulled up the route display on the radar display and it showed the aircraft in the vicinity of olu; but there was no limited data block that I could see anywhere matching the beacon code assigned to the C172. The edst display showed the flight plan not tracking; but there was no overdue notification on it. I called oma approach (R90) to inquire whether they had worked the aircraft. They said they had a flight plan but didn't recall working the aircraft. I then called the adjacent sector and they told me that someone earlier had noticed the flight plan but had made no further inquiries about the aircraft. At that time I notified my supervisor about the missing aircraft. A while later; the edst flight plan grayed out and I assumed that someone had removed it. I then notified the supervisor that the flight plan had gotten removed. However; the next controller said the flight plan was still in the system. A flight plan readout (fr) revealed the flight plan was still in the system; it had merely been removed from my edst list automatically. One of the eram subject matter experts (smes) noticed the flight plan gray out and started investigating this as an anomaly. As far as I know; this flight plan should have showed up in my edst flight list overdue and not been automatically removed from the list. I believe the removal was due to an eram bug in the edst. So I told the supervisor I had been mistaken and that the flight plan had not gotten removed from the system. By the time the C172 reached ZMP's airspace; he would have flown over 1;000 miles (and through several artccs and approach controls). However; apparently I was the first controller to have noticed the aircraft wasn't on his route. This is an ongoing problem with edst/uret. Overdue aircraft are frequently overlooked for long periods of time because the notification systems don't draw enough attention to the problem. Eram bugs need to be fixed. Also; there needs to be a better notification system for overdue aircraft in the edst; it's too easy for controllers to overlook overdue aircraft with the current design of edst/uret.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZMP Controller described in detail an ERAM anomaly that reportedly fails to adequately notify controllers of overdue aircraft in the EDST.

Narrative: I noticed a flight plan on a C172 in my EDST (URET) list because he was WAFDOF/IAFDOF at 5;000 FT northwest bound. The routing was X23..LBV..KMY. The first two fixes are in Florida; and the destination is in Alaska. I pulled up a route display on the RADAR display and it showed the aircraft route line southwest of OMA Approach's (R90) airspace. Some time later I realized that no one had called and APPREQed the WAFDOF. At that time I pulled up the route display on the RADAR display and it showed the aircraft in the vicinity of OLU; but there was no limited Data Block that I could see anywhere matching the beacon code assigned to the C172. The EDST display showed the Flight Plan not tracking; but there was no overdue notification on it. I called OMA Approach (R90) to inquire whether they had worked the aircraft. They said they had a Flight Plan but didn't recall working the aircraft. I then called the adjacent sector and they told me that someone earlier had noticed the Flight Plan but had made no further inquiries about the aircraft. At that time I notified my supervisor about the missing aircraft. A while later; the EDST Flight Plan grayed out and I assumed that someone had removed it. I then notified the supervisor that the Flight Plan had gotten removed. However; the next controller said the Flight Plan was still in the system. A Flight Plan readout (FR) revealed the Flight Plan was still in the system; it had merely been removed from my EDST list automatically. One of the ERAM Subject Matter Experts (SMEs) noticed the Flight Plan gray out and started investigating this as an anomaly. As far as I know; this Flight Plan should have showed up in my EDST flight list overdue and not been automatically removed from the list. I believe the removal was due to an ERAM bug in the EDST. So I told the supervisor I had been mistaken and that the Flight Plan had not gotten removed from the system. By the time the C172 reached ZMP's airspace; he would have flown over 1;000 miles (and through several ARTCCs and Approach Controls). However; apparently I was the first controller to have noticed the aircraft wasn't on his route. This is an ongoing problem with EDST/URET. Overdue aircraft are frequently overlooked for long periods of time because the notification systems don't draw enough attention to the problem. ERAM bugs need to be fixed. Also; there needs to be a better notification system for overdue aircraft in the EDST; it's too easy for controllers to overlook overdue aircraft with the current design of EDST/URET.

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.