Narrative:

The flight was normal up until the point where we transitioned from manila (rphi) to fukuoka (rjjj - japan oceanic area) at mevin intersection on airway L625. We had been in continuous contact with manila control via cpdlc and manila radio on HF (after receiving a good SELCAL check upon entering manila airspace between anoki and aresi). About 5 min before crossing the fir at mevin we received a cpdlc disconnect message indicating the link with manila rphi was terminated. We immediately signed-on to rjjj and sent them a position report after they accepted the cpdlc sign-on. We could not raise tokyo radio on HF and we asked rjjj via cpdlc for an HF frequency for tokyo radio. We received the following cryptic message; 'this is oceanic control. Contact control on VHF'. We touched ball note #8 on the jepp-pro application. The communication block that came-up in FD-pro was worthless information! We touched-on the communication box in the pull-out menu on FD-pro and it showed fukuoka control 118.9 and 119.35(secondary) - we received no response on either. We finally received a SELCAL from the last manila radio frequency and was told to contact naha control on 123.9. We made contact with naha and were chastised twice by the controller and again by the controller supervisor for being in their airspace for 10 min without contacting them! The high IFR chart in jepp-pro indicates the airspace belongs to rjjj fir -this is absolutely not true! It belongs to naha control on okinawa! The jeppesen high chart and the pull-out information box need to be updated to reflect this reality. The whole incident could be avoided with proper charts and/or a cpdlc or HF handoff from manila control to naha control. Manila simply terminated the cpdlc connection without comment and manila radio failed to SELCAL us with the hand-off to naha control until 10 minutes after we had passed the fir boundary.

Related reports:

Google
 

Original NASA ASRS Text

Title: Air carrier flight crew reported being out of contact for ten minutes in Fukuoka airspace due to a late hand off from Manila ATC and an error in ATC frequency information in the Jepp-Pro application.

Narrative: The flight was normal up until the point where we transitioned from Manila (RPHI) to Fukuoka (RJJJ - JAPAN OCEANIC AREA) at MEVIN intersection on airway L625. We had been in continuous contact with Manila control via CPDLC and Manila radio on HF (after receiving a good SELCAL check upon entering Manila airspace between ANOKI and ARESI). About 5 min before crossing the FIR at MEVIN we received a CPDLC disconnect message indicating the link with Manila RPHI was terminated. We immediately signed-on to RJJJ and sent them a position report after they accepted the CPDLC sign-on. We could not raise Tokyo Radio on HF and we asked RJJJ via CPDLC for an HF frequency for Tokyo Radio. We received the following cryptic message; 'This is oceanic control. Contact control on VHF'. We touched Ball note #8 on the Jepp-Pro application. The communication block that came-up in FD-Pro was WORTHLESS INFORMATION! We touched-on the communication box in the pull-out menu on FD-Pro and it showed FUKUOKA CONTROL 118.9 and 119.35(secondary) - we received no response on either. We finally received a SELCAL from the last Manila Radio frequency and was told to contact NAHA control on 123.9. We made contact with NAHA and were chastised twice by the controller and again by the controller supervisor for being in their airspace for 10 min without contacting them! The High IFR chart in JEPP-PRO indicates the airspace belongs to RJJJ FIR -This is absolutely NOT TRUE! It belongs to NAHA Control on Okinawa! The Jeppesen high chart and the pull-out information box need to be updated to reflect this REALITY. The whole incident could be avoided with proper charts and/or a CPDLC or HF handoff from Manila Control to NAHA control. Manila simply terminated the CPDLC connection without comment and Manila radio failed to SELCAL us with the hand-off to NAHA control until 10 minutes after we had passed the FIR boundary.

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.