Widebody; Low Wing; 2 Turbojet Eng
Air Traffic Control Fully Certified
Air Traffic Control Time Certified In Pos 1 (yrs) 7
Communication Breakdown; Confusion; Human-Machine Interface; Situational Awareness
ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Air Traffic Control Separated Traffic
Procedure; Human Factors; ATC Equipment / Nav Facility / Buildings
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.
Aircraft X had coordination time of XA23 at GLAAS at FL400. Routing GLAAS to 23n050w. Aircraft X progressed at XA33; after confirming that it was the actual progress; The data block jumped back ten minutes which then put the aircraft in conflict with Aircraft Z which was westbound from 20n50w to GLAAS at FL400. At this point we took corrective action to descend the Aircraft X to FL390.If we were on line with Piarco we would not have had this incident. Which is exactly what I asked for 25 years ago when a similar situation happened. Here is progress for you.
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.