37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 956707 |
Time | |
Date | 201006 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZTL.ARTCC |
State Reference | GA |
Aircraft 1 | |
Make Model Name | No Aircraft |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types |
Narrative:
I reported for duty and began conducting OJT at the clt high sector (33) and then the high rock sector (28). As time passed I noticed strange alerts; or lack of alerts; in uret. I also noticed the timing of aircraft entries into the acl seemed to be off. I reviewed several trajectories using the gpd and realized many of the flights showed eight to twenty minutes behind where they actually were. The uret status menu showed no outage. I reported this to the flm who called the watch desk (OM). After ten minutes or so; the OM on duty came to the area and told us they had known all day there was a problem with the conflict probe feature of uret and couldn't do anything about it until the mid shift. This is absolutely safety critical information that the controllers should have been briefed on before assuming a control position but we were left out of the loop. This is unacceptable malfeasance on behalf of the management of the busiest air traffic control facility in the world.
Original NASA ASRS Text
Title: A ZTL Controller expressed concern regarding the failure of management to properly brief personnel of the known limitations of the Conflict Probe functionality of the URET.
Narrative: I reported for duty and began conducting OJT at the CLT High Sector (33) and then the High Rock Sector (28). As time passed I noticed strange alerts; or lack of alerts; in URET. I also noticed the timing of aircraft entries into the ACL seemed to be off. I reviewed several trajectories using the GPD and realized many of the flights showed eight to twenty minutes behind where they actually were. The URET Status menu showed no outage. I reported this to the FLM who called the watch desk (OM). After ten minutes or so; the OM on duty came to the area and told us they had known all day there was a problem with the Conflict Probe feature of URET and couldn't do anything about it until the mid shift. This is absolutely safety critical information that the controllers should have been briefed on before assuming a control position but we were left out of the loop. This is unacceptable malfeasance on behalf of the management of the busiest air traffic control facility in the world.
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.