Volume 86 | Wednesday, January 24, 2024

Jump Seat Logo _New_.png

NOPAC Route System PBCS Requirements

Welcome back to Jump Seat. Big changes are happening very soon (25 January 2024) in the North Pacific (NOPAC) Route System between Alaska and Japan. Keep reading to learn about the changes and the reasoning behind this route system redesign. 

The NOPAC Route System was implemented in 1974 as a combined effort between the FAA and JCAB (Japan Civil Aviation Bureau) creating five parallel ATS Routes between Anchorage Oceanic and Fukuoka FIRs. These airways used 50nm separation with an RNAV 10 equipment requirement. 

 

The purpose of the NOPAC Redesign Project is to replace some of the original airways and relocate additional airways closer together to utilize less airspace than before. This will also provide more airspace south of this area for User Preferred Routes (UPRs). UPRs are customized flight routes created by an operator that don’t align with established airways. 

 

In order to reduce lateral separation between the new airways, PBCS approval (i.e. RCP 240 / RSP 180) and RNP4 equipment will be required for aircraft operating from FL340 through FL400. PBCS approval and RNP4 equipment allow for up to 23nm lateral separation. 

 

Purpose of PBCS  

 

Performance Based Communication and Surveillance (PBCS) ensures that CPDLC and ADS-C meet minimum temporal standards for Air Traffic Control. The transaction time frame is key for Required Communication Performance (RCP) and Required Surveillance Performance (RSP). The number following RCP is the CPDLC message transaction time threshold. It is the time (in seconds) for a message to be initiated, uplinked, received, responded to and downlinked (i.e. RCP240 = 240 seconds threshold time). RSP is similarly a threshold for surveillance data transit time for ADS-C reports (i.e. RSP180 = 180 seconds threshold time). Essentially this PBCS approval allows ATC to fit more aircraft into the same airspace (reduced lateral spacing) due to having a lower message transaction / data transit time. This reduced time frame allows ATC to control more aircraft safely and efficiently. 

 

Where is PBCS Approval Applied?  



PBCS is currently only required on airway L888 over the Himalayas in China, the NOPAC Route System, and the PBCS Tracks in the North Atlantic. However, PBCS Approval can still provide advantages with reduced separation and more preferential routing/altitudes in several areas of the world. 

  

FIRs publishing guidance related to PBCS in select airspace: 

Note: A number of FIRs restrict PBCS Approval to be utilized on specific airways 


  • New York Oceanic FIR (USA)
  • Gander Oceanic FIR (Canada)
  • Reykjavik FIR (Iceland)
  • Shanwick FIR (UK)
  • Santa Maria FIR (Portugal)
  • Canaries FIR (Spain)
  • Sal Oceanic FIR (Cape Verde)
  • Oakland Oceanic FIR (USA)
  • Tahiti FIR (France)
  • Auckland Oceanic FIR (New Zealand)
  • Nadi FIR (Fiji)
  • Fukuoka FIR (Japan)
  • Manila FIR (Philippines)
  • Ujung Pandang FIR (Indonesia)
  • Singapore FIR (Singapore)
  • Kuala Lumpur (Malaysia)
  • Colombo FIR (Sri Lanka)
  • Urumqi FIR (China)
  • Lanzhou FIR (China)

 

NOPAC: A Redesign in Three Phases 

 

This has not been an easy implementation; it’s been underway for over three years. What follows is an overview of the process that will come to completion in mid-2024. It’s important to note that there are strict compliance requirements going into effect on 25 January. 

 

Phase 1a: December 2, 2021 

 

Phase 1a kicked off the NOPAC Redesign in 2021. The airway structure was shifted south, and two new airways were added. Airway R220 also added a requirement for PBCS from FL340 to FL400. This requirement was not strictly enforced in Phase 1a and was primarily focused on information gathering, operator education, and outreach post flight to aircraft not in compliance. 

 

Phase 1b: February 23, 2023 

Phase 1b transitioned to a stricter enforcement of the new PBCS requirement on airway R220 from FL340 to FL400. The other big change was the elimination of the two southernmost airways of R591 and G344.  

 

Phase 2: January 25, 2024  

In Phase 2, airway M523 (in green above) will be added, between airways R220 and R580. Airway R580 will also became an eastbound only route. Strict enforcement will commence for operators using airways R220, M523, and R580 (from FL340 to FL400). Operators must be authorized for RCP 240, RSP 180, and equipment with RNP4.  


Operators not meeting these requirements may fly on R220 or R580, limited to below FL340 and above FL400. Aircraft without the required authorizations or equipage may also operate on or south of airway A590. 

 

Phase 3: Mid-2024

Later this year, Phase 3 will conclude the NOPAC Redesign. This will create an airway N507 (in green above) south of airway R580. Airway A590 will be removed while it's waypoints will remain. Operators must be PBCS approved / RNP4 Equipped if they plan to use Airways R220, M523, R580, N507 or over the waypoints on the former Airway A590 (between FL340 and FL400). Operators not meeting these requirements can still fly below FL340 and above FL400 on Airways R220, R580 and the waypoints over the former airway A590. Airways M523 and N507 will only be available from FL340 to FL400. Operators can still fly a routing at least 75nm south of airway N507 as an alternative. 

 

Final Thoughts 

 

PBCS approval and RNP4 requirements are expanding further with the latest phase of the NOPAC Redesign. Once this NOPAC Redesign is completed, four airways will occupy less airspace than the three airways in Phase 1b. Previously only required when utilizing the PBCS Tracks in the North Atlantic and L888 Airway over the Himalayas in China, operators will likely see further expansion in the years to come as it allows reduced separation, preferential routing/altitude options and more efficient Air Traffic Management. This combination of datalink / surveillance technology via CPDLC and ADS-C is what makes that future possible.  

Did you know?

  • Operators can contact the manufacturer of their data link equipment and request a Statement of Compliance (SOC) which will outline the PBCS Capabilities for your aircraft.
  • ARINCDirect is a signatory to the Global PBCS Charter. Operators can satisfy the requirement of complying with PBCS by becoming a signatory to on the https://www.fans-cra.com/ website, which is approved by the FAA. A Service Information Letter stating ARINCDirect's PBCS Compliance Statement can be found here. Please note, you must be logged into your ARINCDirect Account to access.

Useful Links

Thank you for reading!

Sign up for Izon today!

Izon offers a free, secure, single sign-on experience

that combines the best of ARINCDirect into

one connected platform

Izon Setup Guide
More Jump Seat
ARINCDirect Support