 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZMP controller voiced concern regarding uret system with regard to populating the aircraft list with appropriate information.
| Attributes | |
| ACN | 1012125 |
| Time | |
| Date | 201205 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZMP.ARTCC |
| State Reference | MN |
| Aircraft 1 | |
| Make Model Name | A319 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types |
Narrative:
Chicago sector G76 called to appreq an A319 at FL360; iafdof at FL370 as he was requesting FL380 but had crossing traffic at both FL360 and FL380. G76 controller pvded the data block to me. I approved the iafdof; but noticed there was no flight plan for the A319 in my uret aircraft list. When this bug occurs; normally the flight plan populates the aircraft list when the data block is put into hand off mode. However; this time the aircraft flight plan didn't enter my uret list until after I had accepted the aircraft hand off. There was no way for me to perform a proper traffic search without a flight plan for that aircraft in my uret aircraft list; yet I had to accept a hand off before the flight plan populated the list. Uret bugs need to be fixed. This as well as other bugs in uret have existed for years. Since my understanding is that the edst in eram is the same program code as uret; this means that even with eram these bugs will exist.
Original NASA ASRS Text
Title: ZMP Controller voiced concern regarding URET system with regard to populating the aircraft list with appropriate information.
Narrative: Chicago Sector G76 called to APPREQ an A319 at FL360; IAFDOF at FL370 as he was requesting FL380 but had crossing traffic at both FL360 and FL380. G76 Controller PVDed the Data Block to me. I approved the IAFDOF; but noticed there was no flight plan for the A319 in my URET aircraft list. When this bug occurs; normally the flight plan populates the aircraft list when the Data Block is put into hand off mode. However; this time the aircraft flight plan didn't enter my URET list until after I had accepted the aircraft hand off. There was no way for me to perform a proper traffic search without a flight plan for that aircraft in my URET aircraft list; yet I had to accept a hand off before the flight plan populated the list. URET bugs need to be fixed. This as well as other bugs in URET have existed for years. Since my understanding is that the EDST in ERAM is the same program code as URET; this means that even with ERAM these bugs will exist.
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.