Narrative:

I was training a cpc/it on atop [advanced technologies and oceanic procedures] when sector 69 called to apreq (approval request) aircraft X at FL360 instead of FL350 going to oakland ARTCC airspace. We advised we would call them back when the coordination with ZOA had gone through. I saw the trainee open the coordination window and saw that the altitude was FL360 and blue which means coordinated. So the trainee called sector 69 back and informed him that FL360 was approved. We did not realize at the time that the coordination we had looked at was from paza [anchorage center oceanic] to us; not from us to kzak [oceanic ATC operations]. So FL350 was still the coordinated altitude to kzak. A message did show up a few minutes later stated that the coordinated altitude and cleared altitude were discrepant. Aircraft X was still in the climb at this point so the message was deleted because we get that message all of the time going to [a foreign center] when an aircraft is in the process of climbing. Kzak never called to question the discrepant altitude.this was a case of trainee and trainer error. I just did not notice that the facility in the coordination window was not correct for what we were trying to do. It would have been nice if the oakland controller had called to question what altitude the aircraft was going to be at as I am sure they received coordination discrepant messages as well.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZAN Controller described a situation where the trainee he was instructing did not ensure the correct facility was coordinated with. This caused an error of altitude to be coordinated with another Center.

Narrative: I was training a CPC/IT on ATOP [Advanced Technologies and Oceanic Procedures] when Sector 69 called to apreq (Approval Request) Aircraft X at FL360 instead of FL350 going to Oakland ARTCC airspace. We advised we would call them back when the coordination with ZOA had gone through. I saw the trainee open the coordination window and saw that the altitude was FL360 and blue which means coordinated. So the trainee called Sector 69 back and informed him that FL360 was approved. We did not realize at the time that the coordination we had looked at was from PAZA [Anchorage Center Oceanic] to us; not from us to KZAK [Oceanic ATC Operations]. So FL350 was still the coordinated altitude to KZAK. A message did show up a few minutes later stated that the coordinated altitude and cleared altitude were discrepant. Aircraft X was still in the climb at this point so the message was deleted because we get that message all of the time going to [a foreign Center] when an aircraft is in the process of climbing. KZAK never called to question the discrepant altitude.This was a case of trainee and trainer error. I just did not notice that the facility in the coordination window was not correct for what we were trying to do. It would have been nice if the Oakland controller had called to question what altitude the aircraft was going to be at as I am sure they received coordination discrepant messages as well.

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.