New york center controllers reported a bad progress report on an aircraft that put it in conflict wi...

Attributes
ACN	1419009
Time
Date	201701
Local Time Of Day	1801-2400
Place
Locale Reference	ZNY.ARTCC
State Reference	NY
Aircraft 1
Make Model Name	Widebody Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Flight Plan	IFR
Aircraft 2
Make Model Name	Widebody Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 7
Person 2
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 23
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance

Narrative:

I took manual coordination from piarco center for aircraft X at FL400. In the coordination window I entered time XA23 for position glaas. Once the positon report became overdue the next controller requested the position report. At which time the aircraft showed a automatic dependent surveillance (ads) position report discrepant from what aircraft Y was protecting. The controller verified the position again realizing the glaas progress was XA33+10. A conflict with aircraft Z became apparent and the controller took action to solve it. Always pay attention to the 'blue data' and the read back. I recommend full air traffic services inter-facility data communications (aidc) implementation with piarco center. Automated coordination can alleviate these issues.

Original NASA ASRS Text

Title: New York Center Controllers reported a bad progress report on an aircraft that put it in conflict with another aircraft. Both reporters requested a land line to the foreign ATC Center.

Narrative: I took manual coordination from Piarco Center for Aircraft X at FL400. In the coordination window I entered time XA23 for position GLAAS. Once the positon report became overdue the next controller requested the position report. At which time the aircraft showed a Automatic Dependent Surveillance (ADS) position report discrepant from what Aircraft Y was protecting. The controller verified the position again realizing the GLAAS progress was XA33+10. A conflict with Aircraft Z became apparent and the controller took action to solve it. Always pay attention to the 'blue data' and the read back. I recommend full Air Traffic Services Inter-facility Data Communications (AIDC) implementation with Piarco Center. Automated coordination can alleviate these issues.

Data retrieved from NASA's ASRS site 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.

New york center controllers reported a bad progress report on an aircraft that put it in conflict with another aircraft. Both reporters requested a land line to the foreign ATC center.