Narrative:

Flying through manila airspace is often colloquially known as being in the 'wild west' - HF and VHF communications are often spotty and irregular. Flight X and subsequent flight Y were no different; but it was much worse than usual. On initial check-in with mnl after handoff from ZZZZ; we were told 'cell call unable.' cpdlc (controller-pilot data link communications) didn't automatically transfer; and it took quite a while to get it to connect. Meanwhile; we queried if we should maintain a listening watch and were not clearly instructed to do so; this begs the question; if we *hadn't* done so; and with cpdlc disconnected; how would the controlling facility (mnl ATC) have been able to get in touch with us if necessary? No backup frequency was given. We were instructed to report a further fix; but by the time we arrived at that fix; no contact via HF was possible. Since neither I nor the captain had flown mnl recently; we couldn't remember the usual VHF frequency; this was not available on the ipad jeppesen chart over any of the nearby fir (flight information region) boundary comms boxes; so a mad scramble ensued that was finally solved when cpdlc connected and we were able get a frequency via the free text feature. Meanwhile; we were plowing into mnl airspace at night at 600mph. Let us say; this was not a comfortable situation. On the way from mnl to ZZZ; they didn't bother giving us an HF frequency at all - we were cut loose several hundred miles before the fir; told there was no HF available; given no alternate communications procedures; and told to please contact ZZZZ over the fir. It was a relief to exit their airspace; but it was an unsettling and; to my mind; unsafe situation. Of course; we could have texted dispatch or asked sfo [commercial radio] to pass messages along; but this kind of comms loss happens too often in mnl airspace. It's unsafe.

Related reports:

Google
 

Original NASA ASRS Text

Title: Air carrier First Officer reported poor ATC communication when flying in Manila airspace.

Narrative: Flying through Manila airspace is often colloquially known as being in the 'wild west' - HF and VHF communications are often spotty and irregular. Flight X and subsequent Flight Y were no different; but it was much worse than usual. On initial check-in with MNL after handoff from ZZZZ; we were told 'cell call unable.' CPDLC (Controller-Pilot Data Link Communications) didn't automatically transfer; and it took quite a while to get it to connect. Meanwhile; we queried if we should maintain a listening watch and were not clearly instructed to do so; this begs the question; if we *hadn't* done so; and with CPDLC disconnected; how would the controlling facility (MNL ATC) have been able to get in touch with us if necessary? No backup frequency was given. We were instructed to report a further fix; but by the time we arrived at that fix; no contact via HF was possible. Since neither I nor the Captain had flown MNL recently; we couldn't remember the usual VHF frequency; this was not available on the iPad Jeppesen chart over any of the nearby FIR (Flight Information region) Boundary comms boxes; so a mad scramble ensued that was finally solved when CPDLC connected and we were able get a frequency via the free text feature. Meanwhile; we were plowing into MNL airspace at night at 600mph. Let us say; this was not a comfortable situation. On the way from MNL to ZZZ; they didn't bother giving us an HF frequency at all - we were cut loose several hundred miles before the FIR; told there was no HF available; given no alternate communications procedures; and told to please contact ZZZZ over the FIR. It was a relief to exit their airspace; but it was an unsettling and; to my mind; unsafe situation. Of course; we could have texted Dispatch or asked SFO [Commercial Radio] to pass messages along; but this kind of comms loss happens too often in MNL airspace. It's unsafe.

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.