Narrative:

About 45 minutes after getting airborne we logged into moncton via cpdlc; and were accepted. Prior to entry into moncton; cpdlc went active and we proceeded with several frequency change request via cpdlc. We received our oceanic clearance via ACARS; and commenced our initial cross checks for coast out. At xa:17 we were advised by moncton via VHF to switch frequencies from moncton to gander radio. The controller informed us that there had been or are issues with the message he sent to us that he had requested via ads/cpdlc to switch frequencies. He told us we may get a delayed message from them and to disregard. We thanked him and noted his comment. We switched to gander; and we were cleared direct to our second oceanic fix n51w050; having already been cleared direct to allry by a previous controller which was our initial entry point. We checked in and received our HF frequencies and received a SELCAL check and confirmed proper operation; and advised we were cpdlc. We coasted out with no abnormal indications; all systems appeared to be operating nominally. We monitored 123.45 and 121.50 and were now squawking 2000 on the transponder. We crossed n51w050 at xb:46Z about two hours after our initial gander contact we received an ATC message '/contact gander center on 133.90' having already coasted out; and in cpdlc/HF contact and remembering the previous controller having informed us that an erroneous message may be forthcoming; sent a message response as 'unable' so it was not in an affirmative response to the system. That way if there was an actual need to contact us; it would be thru non VHF sources since we were beyond VHF range at this point. Ten minutes later we got a flurry of messages (3) '/message not supported by this at facility' at this time I suspected that the cpdlc buffer may be 'jammed' or locked up. I told the PF that we need to do a 'control-altitude-delete' to the cpdlc because I suspected that based on the types of messages ATC is not sending them and anything we are attempting to send is getting bounced by the system. Around this exact time; on VHF 121.5 another aircraft called us and told us to contact gander on HF 8864; they were trying to reach us. Apparently gander had sent a SELCAL; but it was not received by the plane. When we tried reaching gander on 8864; we were unable and transmission was at best 1/5. We switched to our secondary on 11279 and established good contact with them and they informed us that they did not receive our n51w050 position report via cpdlc. I informed them that we had just noticed that our cpdlc may need to be logged off and then back on. I relayed at this time our n51w050 position report. I had the first officer log off the cpdlc and re-login; ATC communication was immediately accepted. I asked ATC via HF to confirm cpdlc contact and that we had just sent a position report to them via cpdlc. Eighteen minutes later we received a cpdlc/ATC message confirming contact via cpdlc. One minute later we responded to the customary route confirmation message. All operations with cpdlc were normal from this point forward and flight was uneventful. A couple things come to mind in all this. First; we fell for a false expectation of accepting a communication failure with moncton as 'normal'. There is a lack of affirmative information to the crew that cpdlc is operating; in our case it was the multiple failure messages that gave us the indication of a cpdlc failure which we immediately acted on to rectify. I was somewhat surprised at how rapidly 8864 HF had grown weak; normally gander has very good reception out in this area; thankfully the procedure of a secondary worked and we regained contact. Following procedures and having our air to air and guard frequencies dialed in; worked as advertised! I'm open to what I can do differently next time to identify a cpdlc buffer is sue like this and prevent a delayed or even missed position report.

Google
 

Original NASA ASRS Text

Title: Air carrier Captain on a North Atlantic track reported contacting Moncton then Gander via CPDLC. Later; ATC requested the crew check in via HF because CPDLC was not reporting its position. A CPDLC reset reestablished contact.

Narrative: About 45 minutes after getting airborne we logged into Moncton via CPDLC; and were accepted. Prior to entry into Moncton; CPDLC went active and we proceeded with several frequency change request via CPDLC. We received our Oceanic Clearance via ACARS; and commenced our initial cross checks for coast out. At XA:17 we were advised by Moncton via VHF to switch frequencies from Moncton to Gander Radio. The controller informed us that there had been or are issues with the message he sent to us that he had requested via ADS/CPDLC to switch frequencies. He told us we may get a delayed message from them and to disregard. We thanked him and noted his comment. We switched to Gander; and we were cleared direct to our second oceanic fix N51W050; having already been cleared direct to ALLRY by a previous controller which was our initial entry point. We checked in and received our HF frequencies and received a SELCAL check and confirmed proper operation; and advised we were CPDLC. We coasted out with no abnormal indications; all systems appeared to be operating nominally. We monitored 123.45 and 121.50 and were now squawking 2000 on the transponder. We crossed N51W050 at XB:46Z About two hours after our initial Gander contact we received an ATC message '/CONTACT GANDER CENTER ON 133.90' Having already coasted out; and in CPDLC/HF contact and remembering the previous controller having informed us that an erroneous message may be forthcoming; sent a message response as 'Unable' so it was not in an affirmative response to the system. That way if there was an actual need to contact us; It would be thru non VHF sources since we were beyond VHF range at this point. Ten minutes later we got a flurry of messages (3) '/MESSAGE NOT SUPPORTED BY THIS AT FACILITY' At this time I suspected that the CPDLC buffer may be 'jammed' or locked up. I told the PF that we need to do a 'Control-ALT-Delete' to the CPDLC because I suspected that based on the types of messages ATC is not sending them and anything we are attempting to send is getting bounced by the system. Around this exact time; on VHF 121.5 another aircraft called us and told us to contact Gander on HF 8864; they were trying to reach us. Apparently Gander had sent a SELCAL; but it was not received by the plane. When we tried reaching Gander on 8864; we were unable and transmission was at best 1/5. We switched to our secondary on 11279 and established good contact with them and they informed us that they did not receive our N51W050 position report via CPDLC. I informed them that we had just noticed that our CPDLC may need to be logged off and then back on. I relayed at this time our N51W050 position report. I had the FO log off the CPDLC and re-login; ATC communication was immediately accepted. I asked ATC via HF to confirm CPDLC contact and that we had just sent a position report to them via CPDLC. Eighteen minutes later we received a CPDLC/ATC message confirming contact via CPDLC. One minute later we responded to the customary route confirmation message. All operations with CPDLC were normal from this point forward and flight was uneventful. A Couple things come to mind in all this. First; we fell for a false expectation of accepting a communication failure with Moncton as 'Normal'. There is a lack of affirmative information to the crew that CPDLC is operating; in our case it was the multiple failure messages that gave us the indication of a CPDLC failure which we immediately acted on to rectify. I was somewhat surprised at how rapidly 8864 HF had grown weak; normally Gander has very good reception out in this area; thankfully the procedure of a secondary worked and we regained contact. Following procedures and having our Air to Air and Guard frequencies dialed in; worked as advertised! I'm open to what I can do differently next time to identify a CPDLC buffer is sue like this and prevent a delayed or even missed position report.

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.