Air carrier crew reported a CPDLC datalink communication issue when entering oceanic airspace resulting in not reporting a compulsory reporting point. The CPDLC and ADS-C connected and normal automatic ADS position reporting communications were established.
Synopsis
Air carrier crew reported a CPDLC datalink communication issue when entering oceanic airspace resulting in not reporting a compulsory reporting point. The CPDLC and ADS-C connected and normal automatic ADS position reporting communications were established.
Narrative
After takeoff from ZZZZ logged into ZZZZ CPDLC worked fine for a while. While logged into active center showing EGGX as the next CPDLC center approaching Sunot. CPDLC did not connect to EGGX. Y Sunot. It did connect afterwards; therefore didn't make the ADS-C (Automatic Dependent Surveilance - Contract) position report. Received a HF SELCAL (Select Calling) from Shanwick saying ADSC and CPDLC are required in the NAT (North Atlantic Track) region. I know that they are both required in the Atlantic and told him we knew. Some aircraft were told to log off EISN PRIOR to the oceanic entry fix. We were not told to log off. EGGX showing next center did not switch at the appropriate time. It did connect afterwards few minutes after crossing Sunot. Received a HF call from Shanwick asking us to log off and back in. Watched the connecting message for 4 minutes. Finally connected and started getting the Set uplink 300; confirmed route; resume normal speed. Shanwick selcalled us 4 times. Not a very good time to keep calling us while establishing an off set making sure procedures are followed to prevent errors on the track.ATC advised to log off and back on. After a log connection n period we finally connected to EGGX. If ATC operations were consistent thing might work better. we were not told to log off and EGGX was next sector but did not automatically switch as every other sector did from takeoff. Per the oceanic track message; we are not required to preemptively log off EISN and log into EGGX if connected to a prior domestic sector. So we were not intentionally non compliant or not at fault for entering not logged in. Most of the time ATC will preemptively ask us to switch or it works automatically. Bottom line we ALL need to log off the active center ahead of time and log into EGGX or the automatic switch should work properly. COME UP WITH A PROCEDURE THAT WORKS EVERY TIME AND STICK WITH IT.
Second reporter narrative
Enroute from ZZZZ to ZZZ1; we were assigned to enter Shanwick Oceanic at SUNOT. Prior to hitting SUNOT; we were automatically disconnected from CPDLC but logged back on immediately to EGGX. After crossing SUNOT we established communications with Shanwick Oceanic and we were instructed via HF voice to log back off CPDLC and to log back on. Once we logged off and tried logging back on; we began having issues trying to reestablish CPDLC with EGGX. We were contacted via SELCAL and told that is it a requirement for the NAT airspace to have CPDLC active and connected. We informed him that not only were we aware of said rules and regulations pertaining to the airspace but that we were logged on previously but instructed to log off and had been attempting to reestablish our CPDLC. After about the third attempt; we managed to get our CDPLC connected with EGGX. We began receiving the required messages (CONFIRM ASSIGNED ROUTE; RESUME NORMAL SPEED; SET 300 sec etc.). We also verified via HF with Shanwick that we were indeed now in compliance and he was able to confirm so. We continued with the flight as normal from that point on.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.