 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZFW controller voiced concern regarding the on going uret processing problem; indicating the uret system frequently adds fixes to the flight plan.
| Attributes | |
| ACN | 915875 |
| Time | |
| Date | 201010 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZFW.ARTCC |
| State Reference | TX |
| Aircraft 1 | |
| Make Model Name | ATR 72 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Flight Data / Clearance Delivery |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types |
Narrative:
Once again; another uret processing error. An AT72 was flying '...mlc..kfsm'; and not probing for an unknown reason. Once far enough north; I assigned H020/mlc to the flight and entered direct mlc via the route key; uret would not offer elements to amend. After I entered the route; the uret route; I forgot to check the host/NAS route; showed the following as the later portion of the route: 'mlc..MLC056020..fsm..kfsm'; this clearly added two fixes; the mlc radials and the fsm VOR which is about 5.1 NM northeast of the field. A previous route generated: '...mlc..kfsm'; the a second entry of direct mlc resulted in '..mlc..kfsm'; the correct route. We gotta solve these processing bugs. We have too many 'added fixes' to correct processing issues; and I suspect this is involved.
Original NASA ASRS Text
Title: ZFW Controller voiced concern regarding the on going URET processing problem; indicating the URET system frequently adds fixes to the flight plan.
Narrative: Once again; another URET Processing Error. An AT72 was flying '...MLC..KFSM'; and not probing for an unknown reason. Once far enough north; I assigned H020/MLC to the flight and entered direct MLC via the route key; URET would not offer elements to amend. After I entered the route; the URET route; I forgot to check the HOST/NAS route; showed the following as the later portion of the route: 'MLC..MLC056020..FSM..KFSM'; this clearly added two fixes; the MLC radials and the FSM VOR which is about 5.1 NM northeast of the field. A previous route generated: '...MLC..KFSM'; the a second entry of direct MLC resulted in '..MLC..KFSM'; the correct route. We gotta solve these processing bugs. We have too many 'added fixes' to correct processing issues; and I suspect this is involved.
Data retrieved from NASA's ASRS site as of April 2012 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.