ZJX Controller described a confused routing event allegedly caused by a unnecessary URET re-route; unnoticed by the Controller's involved. The ALERT functionality was inaccurate.
Synopsis
ZJX Controller described a confused routing event allegedly caused by a unnecessary URET re-route; unnoticed by the Controller's involved. The ALERT functionality was inaccurate.
Narrative
Issued direct routing (DIINO) to aircraft. Used URET to input routing. URET decided to change STAR from FISEL to GISSH. I didn't notice the change. Aircraft proceed to DIINO then previous routing. Recommendation; why do we need a machine to determine a route change is needed when the one the aircraft already has is acceptable? This is a known problem at ZJX and the 'powers that be' have decided to let it happen over and over. I've been told 'don't put direct DIINO in the machine.' This solves the problem of unnoticed route changes; however; it causes another problem. If the URET system doesn't have the actual track/route as in this case direct DIINO; then the ALERT portion of the URET system is inaccurate.
Second reporter narrative
Aircraft was enroute to FLL filed via the GISSH arrival. The RADAR trainee cleared the aircraft direct DIINO intersection and made an amendment in URET. The aircraft's route was changed to DIINO.FISEL2.FLL. The Trainee nor the Trainer noticed the change and the aircraft was handed off and switched. The aircraft went over to ZMA's frequency cleared via the GISSH [arrival] and the flight plan showed the aircraft on the FISEL arrival. Recommendation; Fix URET.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.