ZNY controlled described a route error made by a corporate jet; the causal factor traced back to an ...

Narrative:

This was a non radar atops sector. At the time of event; sector 87 and 89 were combined. There was significant weather in airspace and I started falling behind with the deviation requests along with the coordination and approvals. I requested the sector be split and at the time of this event; another cpc was waiting for a briefing to split the sector. It took about 15 minutes to get the time to brief as I was trying to get the sector caught up. The flight was cgrle; a CL60 from teb to tbpb at FL370. The atops showed he had rtg savik l459 caffe guyro on to tbpb. An error message popped up in the sector saying that the position report was accepted with points other than expected and please verify route of flight. This is a common message that the atops sends out since there are many fixes on a route and often the next estimated fix is not the one the computer is looking for. I would say that 98% of those messages are deleted because they are useless. The aircraft is on the route and they just estimated an earlier at/later fix. When this message came up; I was involved worrying about other issues that I looked at it quickly and dismissed it thinking that it was just another errant message. This was that 2% time that it was valid and I missed it. Instead of flying the l459 route; the aircraft went darux direct to caffe down in sju airspace. Instead of entering bda airspace at daser; the aircraft stayed west of bda airspace and would have come close to a westbound air carrier out of bermuda had not the air carrier requested a climb from FL370 to FL380 for weather.not much you can do with atops. Seventy five percent (75%) of all messages that come into the sector are useless and are deleted;; hundreds a day. It's not hard to get lulled into thinking messages are useless by just reading the first few lines and saying 'oh its one of these things again' and then delete it.

Original NASA ASRS Text

Title: ZNY Controlled described a route error made by a corporate jet; the causal factor traced back to an incorrect Clearance Read Back and route clerical error made prior to take off.

Narrative: This was a non RADAR ATOPS sector. At the time of event; Sector 87 and 89 were combined. There was significant weather in airspace and I started falling behind with the deviation requests along with the coordination and approvals. I requested the sector be split and at the time of this event; another CPC was waiting for a briefing to split the sector. It took about 15 minutes to get the time to brief as I was trying to get the sector caught up. The flight was CGRLE; A CL60 from TEB to TBPB at FL370. The ATOPS showed he had RTG SAVIK l459 CAFFE GUYRO on to TBPB. An error message popped up in the sector saying that the position report was accepted with points other than expected and please verify route of flight. This is a common message that the ATOPS sends out since there are many fixes on a route and often the next estimated fix is not the one the computer is looking for. I would say that 98% of those messages are deleted because they are useless. The aircraft is on the route and they just estimated an earlier at/later fix. When this message came up; I was involved worrying about other issues that I looked at it quickly and dismissed it thinking that it was just another errant message. This was that 2% time that it was valid and I missed it. Instead of flying the l459 route; the aircraft went DARUX direct to CAFFE down in SJU airspace. Instead of entering BDA airspace at DASER; the aircraft stayed West of BDA airspace and would have come close to a Westbound air carrier out of Bermuda had not the air carrier requested a climb from FL370 to FL380 for weather.Not much you can do with ATOPS. Seventy Five percent (75%) of all messages that come into the sector are useless and are deleted;; hundreds a day. It's not hard to get lulled into thinking messages are useless by just reading the first few lines and saying 'oh its one of these things again' and then delete it.

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.

Attributes
ACN	975594
Time
Date	201110
Local Time Of Day	1201-1800
Place
Locale Reference	ZNY.ARTCC
State Reference	NY
Aircraft 1
Make Model Name	Challenger CL600
Flight Phase	Cruise
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Pilot Not Flying Check Pilot
Qualification	Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine
Experience	Flight Crew Last 90 Days 100 Flight Crew Total 11500 Flight Crew Type 100
Events
Anomaly	ATC Issue All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types

ZNY controlled described a route error made by a corporate jet; the causal factor traced back to an incorrect clearance read back and route clerical error made prior to take off.