|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||1201 To 1800|
|Locale Reference||navaid : mol.vor|
|Altitude||msl single value : 35000|
|Controlling Facilities||artcc : zid.artcc|
|Operator||common carrier : air carrier|
|Make Model Name||Embraer Jet Undifferentiated or Other Model|
|Operating Under FAR Part||Part 121|
|Flight Phase||climbout : intermediate altitude|
|Affiliation||government : faa|
|Function||controller : radar|
|Qualification||controller : radar|
|Experience||controller limited radar : 6|
controller non radar : 7
controller radar : 4
|Anomaly||non adherence : published procedure|
non adherence : required legal separation
other spatial deviation
|Independent Detector||other controllera|
|Resolutory Action||none taken : anomaly accepted|
|Problem Areas||ATC Human Performance|
|Primary Problem||ATC Human Performance|
|Air Traffic Incident||Operational Deviation|
Among WX deviations and rertes; and after entering route updates to uret/ccld; I was charged an operational deviation for not entering a route amendment I was certain was amended via our uret/ccld. I believe the process for entering updates from uret/ccld is time-consuming and fallible in the processing of data in and out of the FAA's host flight plan equipment. In this situation the aircraft was issued a WX rerte; read it back correctly; and data entered via manual controller keyboard to uret/ccld. Flight data did not update and aircraft went via 1 route while flight plan showed another in another center's airspace. No aircraft were in conflict.
Original NASA ASRS Text
Title: ZID CTLR EXPERIENCED OPDEV WHEN ENTERING INCORRECT DATA VIA URET EQUIP ROUTING ACFT THROUGH AIRSPACE WITHOUT REQUIRED COORD.
Narrative: AMONG WX DEVS AND RERTES; AND AFTER ENTERING RTE UPDATES TO URET/CCLD; I WAS CHARGED AN OPDEV FOR NOT ENTERING A RTE AMENDMENT I WAS CERTAIN WAS AMENDED VIA OUR URET/CCLD. I BELIEVE THE PROCESS FOR ENTERING UPDATES FROM URET/CCLD IS TIME-CONSUMING AND FALLIBLE IN THE PROCESSING OF DATA IN AND OUT OF THE FAA'S HOST FLT PLAN EQUIP. IN THIS SIT THE ACFT WAS ISSUED A WX RERTE; READ IT BACK CORRECTLY; AND DATA ENTERED VIA MANUAL CTLR KEYBOARD TO URET/CCLD. FLT DATA DID NOT UPDATE AND ACFT WENT VIA 1 RTE WHILE FLT PLAN SHOWED ANOTHER IN ANOTHER CTR'S AIRSPACE. NO ACFT WERE IN CONFLICT.
Data retrieved from NASA's ASRS site as of January 2009 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.