Narrative:

Let me start by saying that this was non-radar airspace; utilizing atops as a separation and information system. Air carrier X was southbound on L455. There was weather at southern part of airspace. Aircraft requested climb from FL350 to FL390. I was able to issue climb with a restriction to maintain FL350 until XA50z then climb to FL390. Just before the time to climb; aircraft requested deviation to the west 20 miles. I probed the deviation; atops showed no conflictions; I issued the clearance. After issuance; I noticed a target on a flight on L454; next sector over; just west of air carrier X. I punched up the flight and noticed he was at FL370. To make matters worse; that flight wanted to deviate east so the controller issued him a reroute that turned him eastbound toward air carrier X to L455. Atops once again showed it was ok with no conflictions. Apparently with atops; if you give a clearance that takes effect in the future; and then you issue deviation clearance; the previous clearance gets wiped out from the computer as if the aircraft never had it but the pilot still has that clearance. This is very dangerous! Had I not noticed that target; the computer would have showed air carrier X level at FL350 with a 20 mile west deviation and the other aircraft at FL370 was showing no conflictions heading east into air carrier X while unknowingly to the computer that air carrier X was to climb at XA50z. At XA48z I got on a phone patch with air carrier X and stopped his climb clearance. The other flight at FL370 ended up right near air carrier X on the same airway right above him. Recommendation; fix atops! There have been many issues with atops since we started using it years ago. Maybe if they would fix the issues we encounter; instead of numerous workarounds; it would be safer. This seems like just a programming issue. Don't let the computer wipe out clearances on its own. This apparently has been happening for the past 5 years.

Google
 

Original NASA ASRS Text

Title: ZNY controller described near loss of separation event with an aircraft in adjacent Non-RADAR sector at FL370; reportedly because ATOPS equipment software deletes clearances when in fact they are still active.

Narrative: Let me start by saying that this was Non-RADAR airspace; utilizing ATOPS as a separation and information system. Air Carrier X was southbound on L455. There was weather at southern part of airspace. Aircraft requested climb from FL350 to FL390. I was able to issue climb with a restriction to maintain FL350 until XA50z then climb to FL390. Just before the time to climb; aircraft requested deviation to the west 20 miles. I probed the deviation; ATOPS showed no conflictions; I issued the clearance. After issuance; I noticed a target on a flight on L454; next sector over; just west of Air Carrier X. I punched up the flight and noticed he was at FL370. To make matters worse; that flight wanted to deviate east so the Controller issued him a reroute that turned him eastbound toward Air Carrier X to L455. ATOPS once again showed it was OK with no conflictions. Apparently with ATOPS; if you give a clearance that takes effect in the future; and then you issue deviation clearance; the previous clearance gets wiped out from the computer as if the aircraft never had it but the pilot still has that clearance. This is very dangerous! Had I not noticed that target; the computer would have showed Air Carrier X level at FL350 with a 20 mile west deviation and the other aircraft at FL370 was showing no conflictions heading east into Air Carrier X while unknowingly to the computer that Air Carrier X was to climb at XA50z. At XA48z I got on a phone patch with Air Carrier X and stopped his climb clearance. The other flight at FL370 ended up right near Air Carrier X on the same airway right above him. Recommendation; fix ATOPS! There have been many issues with ATOPS since we started using it years ago. Maybe if they would fix the issues we encounter; instead of numerous workarounds; it would be safer. This seems like just a programming issue. Don't let the computer wipe out clearances on its own. This apparently has been happening for the past 5 years.

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.