Narrative:

After logging on to oakland cpdlc with a good SELCAL check we continued on our planned route of flight uneventfully. After one of the reporting points we got an ATC message to send a position report. We complied and sent an additional (manual) position report via cpdlc. I resent all subsequent reporting points manually to ensure oakland was receiving the required position reporting data. At approximately XA20Z we were expecting and awaiting a frequency message from oakland to contact honolulu approach. We received an 'ATC comm terminated' message with no frequency change for honolulu. We immediately began trying to contact honolulu via the published frequencies on the pacific ocean commercial chart. We quickly made contact with honolulu on 119.3. While talking to honolulu on that frequency we received a guard call to switch to 127.6 to speak to honolulu approach. When we made contact with the controller; she said she had been trying to contact our aircraft for a while. We informed the controller that we were cpdlc data communication established and had gotten no messages nor had we heard anything on the radios or VHF guard. She then talked to oakland and asked us to standby while she spoke with them. She relayed later that oakland had not had good data link with us for quite a while and had tried to contact us via data link. We continued the flight on our assigned flight plan uneventfully. I am concerned that every indication we had via radios (we monitored 123.45 and 121.5) and only ATC communication established indications; that we were not actually able to be contacted by data link via oakland and were late in contacting honolulu control for entry into their airspace.

Google
 

Original NASA ASRS Text

Title: A large transport aircraft on a transpacific flight under CPDLC procedures found out at the end of the flight they had been out of CPDLC contact for some time with no indication of same.

Narrative: After logging on to Oakland CPDLC with a good SELCAL check we continued on our planned route of flight uneventfully. After one of the reporting points we got an ATC message to send a position report. We complied and sent an additional (manual) position report via CPDLC. I resent all subsequent reporting points manually to ensure Oakland was receiving the required position reporting data. At approximately XA20Z we were expecting and awaiting a frequency message from Oakland to contact Honolulu Approach. We received an 'ATC COMM TERMINATED' message with no frequency change for Honolulu. We immediately began trying to contact Honolulu via the published frequencies on the Pacific Ocean Commercial chart. We quickly made contact with Honolulu on 119.3. While talking to Honolulu on that frequency we received a guard call to switch to 127.6 to speak to Honolulu Approach. When we made contact with the Controller; she said she had been trying to contact our aircraft for a while. We informed the Controller that we were CPDLC data communication established and had gotten no messages nor had we heard anything on the radios or VHF guard. She then talked to Oakland and asked us to standby while she spoke with them. She relayed later that Oakland had not had good data link with us for quite a while and had tried to contact us via data link. We continued the flight on our assigned flight plan uneventfully. I am concerned that every indication we had via radios (we monitored 123.45 and 121.5) and only ATC communication established indications; that we were not actually able to be contacted by data link via Oakland and were late in contacting Honolulu Control for entry into their airspace.

Data retrieved from NASA's ASRS site as of April 2012 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.