 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZJX controller voiced concern regarding a known uret anomaly that assigns STAR routings that are different than those issued to the aircraft.
| Attributes | |
| ACN | 975077 |
| Time | |
| Date | 201110 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZJX.ARTCC |
| State Reference | FL |
| Aircraft 1 | |
| Make Model Name | HS 125 Series |
| Flight Phase | Cruise |
| Route In Use | STAR FISEL TWO |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Developmental |
| Events | |
| Anomaly | ATC Issue All Types |
Narrative:
A hawker checked on our frequency going direct omn. My r-side issued the hawker a shortcut to the diino intersection which is on both the gissh and fisel arrivals to fxe. I opened the uret drop down menu and clicked on diino. It automatically applied the GISSH2 arrival in the typing buffer and I thought that was what he had. Apparently the hawker was previously cleared the FISEL2. Miami center called my supervisor about an hour later letting us know that the hawker was flying the FISEL2 arrival when the computer showed the aircraft on the GISSH2. This is a known issue with the uret system; especially for aircraft going to the palm beach; fort lauderdale and miami areas. Routes that go to the palm beach area airports can be qu to the next fix after omn. Fort lauderdale and miami have to be applied through the uret drop down; doing this sometimes will automatically apply the preferred route; causing the arrival the aircraft has been cleared; and the arrival that is in the computer; to be different.
Original NASA ASRS Text
Title: ZJX Controller voiced concern regarding a known URET anomaly that assigns STAR routings that are different than those issued to the aircraft.
Narrative: A Hawker checked on our frequency going direct OMN. My R-Side issued the Hawker a shortcut to the DIINO Intersection which is on both the GISSH and FISEL arrivals to FXE. I opened the URET drop down menu and clicked on DIINO. It automatically applied the GISSH2 arrival in the typing buffer and I thought that was what he had. Apparently the Hawker was previously cleared the FISEL2. Miami Center called my supervisor about an hour later letting us know that the Hawker was flying the FISEL2 arrival when the computer showed the aircraft on the GISSH2. This is a known issue with the URET system; especially for aircraft going to the Palm Beach; Fort Lauderdale and Miami areas. Routes that go to the Palm Beach area airports can be QU to the next fix after OMN. Fort Lauderdale and Miami have to be applied through the URET drop down; doing this sometimes will automatically apply the preferred route; causing the arrival the aircraft has been cleared; and the arrival that is in the computer; to be different.
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.