Narrative:

Aircraft X was coordinated with new york ocean sector D16 at F360. Just prior to the new york/piarco boundary the aircraft logged onto his data-link ads/cpdlc and the aircraft reported at FL380. The pilot reported via HF over butux a few minutes later at F360. I sent an on-demand request to the aircraft and the ads confirmed F380. I send an altitude confirmation message to the pilot via HF and the pilot confirmed at FL380; different than his last report at FL360. I called piarco center and confirmed what they showed for the altitude clearance for aircraft X; and they responded with FL360. I told the pilot I showed him cleared to FL360; I re-cleared the aircraft to maintain FL380 (there was no traffic); and asked how long the aircraft was at FL380. The pilot responded that they were issued a clearance by dakar center (gooo) to climb to FL380. I passed this information to piarco center and they contacted dakar center; who responded that they didn't issue the climb clearance; and actually confirmed at aircraft X was at F360. Further investigation is being performed. Aircraft X flew through piarco's airspace; and entered ny airspace at FL380 when the flight was believed to be cleared to and maintaining FL360. I did not have any traffic at FL360 or FL380 and piarco said they didn't have any traffic at FL380 for the flight. It does not appear any loss of separation occurred. Shortly after entering ny airspace at an altitude other than what was expected; the fight was re-cleared to maintain FL380 and the aircraft's profile was updated and accurate. This appears to be a pilot deviation; climb without a clearance. The only notification that there was a problem was because the aircraft logged onto ads/cpdlc. Since the aircraft reported entering ny airspace at butux at FL360 originally; if I never received an ads report at FL380 I would have never known the aircraft was not at the expected altitude. Piarco center does not have ads/cpdlc capability; and I am unsure if dakar center (gooo) has that capability. Since the pilot was voice reporting FL360 via HF; piarco was unaware of the discrepancy.piarco center could gain ads/cpdlc ability to better conformance check the aircraft's cleared profile with information that comes directly from the FMS of the aircraft vs. Relying on HF voice reports.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZNY Controller reports of an aircraft that was not at the altitude it was supposed to be at.

Narrative: Aircraft X was coordinated with New York Ocean Sector D16 at F360. Just prior to the New York/Piarco boundary the aircraft logged onto his data-link ADS/CPDLC and the aircraft reported at FL380. The pilot reported via HF over BUTUX a few minutes later at F360. I sent an on-demand request to the aircraft and the ADS confirmed F380. I send an altitude confirmation message to the pilot via HF and the pilot confirmed at FL380; different than his last report at FL360. I called Piarco Center and confirmed what they showed for the altitude clearance for Aircraft X; and they responded with FL360. I told the pilot I showed him cleared to FL360; I re-cleared the aircraft to maintain FL380 (there was no traffic); and asked how long the aircraft was at FL380. The pilot responded that they were issued a clearance by Dakar Center (GOOO) to climb to FL380. I passed this information to Piarco Center and they contacted DAKAR Center; who responded that they didn't issue the climb clearance; and actually confirmed at Aircraft X was at F360. Further investigation is being performed. Aircraft X flew through Piarco's airspace; and entered NY airspace at FL380 when the flight was believed to be cleared to and maintaining FL360. I did not have any traffic at FL360 or FL380 and Piarco said they didn't have any traffic at FL380 for the flight. It does not appear any loss of separation occurred. Shortly after entering NY airspace at an altitude other than what was expected; the fight was re-cleared to maintain FL380 and the aircraft's profile was updated and accurate. This appears to be a pilot deviation; climb without a clearance. The only notification that there was a problem was because the aircraft logged onto ADS/CPDLC. Since the aircraft reported entering NY airspace at BUTUX at FL360 originally; if I never received an ADS report at FL380 I would have never known the aircraft was not at the expected altitude. Piarco Center does not have ADS/CPDLC capability; and I am unsure if Dakar center (GOOO) has that capability. Since the pilot was voice reporting FL360 via HF; Piarco was unaware of the discrepancy.Piarco center could gain ADS/CPDLC ability to better conformance check the aircraft's cleared profile with information that comes directly from the FMS of the aircraft vs. relying on HF voice reports.

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.