 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZAU controller voiced concern regarding an eram dropped data block; recommending a return to the host radar system.
| Attributes | |
| ACN | 1055726 |
| Time | |
| Date | 201212 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZAU.ARTCC |
| State Reference | IL |
| Aircraft 1 | |
| Make Model Name | Falcon 900 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types |
Narrative:
Aircraft X was preceding direct halie direct mdw; descending to cross 60 miles east of halie at FL240. When aircraft X was roughly 20 miles west of fwa; I noticed aircraft X was in coast track; with no altitude read out. There was a mode C intruder beneath the data block; showing FL296. I asked aircraft X to report his altitude; and the data block disappeared; I was left with only a mode C intruder; and the mode C intruder showed a transponder code one digit off from aircraft X's code. I tried to start a track; got some ridiculous fail message; I told aircraft X to reset his transponder; tried to start a track again; got a ridiculous fail message; coordinated with the two surrounding sectors (logan and bearz) and then aircraft X's data block reappeared. The logan controller was one of our eram smes and he said since the (incorrect) code is not recognized; eram will not display a data block. I recommend we fall back to host immediately. Fortunately; all my attention was directed at aircraft X while the episode occurred. Had my attention been directed elsewhere; it may have been some time before I recognized I was missing a crucial data block; that I had a mode C intruder; and the issue needed to be corrected by reassigning aircraft X the appropriate beacon code. For a data block to randomly drop off is unsafe. Controllers deserve a better system.
Original NASA ASRS Text
Title: ZAU Controller voiced concern regarding an ERAM dropped data block; recommending a return to the HOST RADAR system.
Narrative: Aircraft X was preceding direct HALIE direct MDW; descending to cross 60 miles East of HALIE at FL240. When Aircraft X was roughly 20 miles West of FWA; I noticed Aircraft X was in coast track; with no altitude read out. There was a Mode C intruder beneath the data block; showing FL296. I asked Aircraft X to report his altitude; and the data block disappeared; I was left with only a Mode C intruder; and the Mode C intruder showed a transponder code one digit off from Aircraft X's code. I tried to start a track; got some ridiculous fail message; I told Aircraft X to reset his transponder; tried to start a track again; got a ridiculous fail message; coordinated with the two surrounding sectors (LOGAN and BEARZ) and then Aircraft X's data block reappeared. The LOGAN Controller was one of our ERAM SMEs and he said since the (incorrect) code is not recognized; ERAM will not display a data block. I recommend we fall back to HOST immediately. Fortunately; all my attention was directed at Aircraft X while the episode occurred. Had my attention been directed elsewhere; it may have been some time before I recognized I was missing a crucial data block; that I had a Mode C intruder; and the issue needed to be corrected by reassigning Aircraft X the appropriate beacon code. For a data block to randomly drop off is unsafe. Controllers deserve a better system.
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.