To apply for IOMAR PBCS approval operators should complete and submit a new Form 4 selecting the new FANS 1/A+ (PBCS) option and specifying the RCP and RSP values. The supporting documentary evidence must clearly identify:
- ADS-C – aircraft-allocated performance of RSP 180 under relevant sub networks; and
- CPDLC – aircraft-allocated performance of RCP 240 under relevant sub networks (or RCP 400 for use on US Domestic Routes).
Several aircraft manufacturers have included a RCP 240 and RSP 180 statement of compliance in the AFM for some aircraft types; however not all of these aircraft types are compliant with the required specification due to an Uplink Message Latency Timer issue.
Therefore, where the aircraft AFM states compliance with RCP 240 and RSP 180, and the aircraft type is not listed below, applications for FANS 1A+PBCS (RCP 240 and RSP 180) must be accompanied by a written confirmation from the aircraft TC holder that the aircraft type/avionics meet both the RCP and RSP certification standards.
| Manufacturer | Model | Additional Required Equipment/Modification for PBCS Compliance (RCP 240/RSP 180) |
| Airbus | A318/319/320/321 | nil |
| A330 | nil | |
| A340 | nil | |
| A350 | nil | |
| A380 | nil | |
| Boeing | 757 | with Pegasus 2009 FANS 1 FMC (requires SB-757-34-0488 embodied) |
| 767 | with Pegasus 2009 FANS 1 FMC (requires SB-757-34-0488 embodied) | |
| Bombardier | Global 6000 | nil |
| Global 5000 GVFD | nil | |
| Challenger 300 | with SB 100-23-22 | |
| Challenger 350 | with SB 350-23-011 | |
| Challenger 605 | with SB 605-23-008 | |
| Challenger 650 | with SB 650-23-008 | |
| Gulfstream | G650 | nil |
| G650ER | nil | |
| G280 | with FANS 1/A+ CPDLC and Rockwell Collins Proline Fusion PlaneView | |
| Dassault | Falcon 8X (EASy III) | nil |
| Falcon 2000 | STC Proline 21 | |
| Falcon 2000EX | STC Proline 21 | |
| Falcon 50EX | STC Proline 21 | |
| Falcon 2000LXS S/N ≥ 293 (NG I/O) | FSN-238-R02-A | |
| Falcon 2000S S/N ≥ 731 (NG I/O) | FSN-238-R02-A | |
| Falcon 2000LXS S/N ≤ 292 | FSN-238-R02-A | |
| Falcon 2000S S/N ≤ 730 | FSN-238-R02-A | |
| Falcon 2000EX EASy, DX and LX | FSN-238-R02-A | |
| Falcon 900LX S/N ≥ 291 (NG I/O) | FSN-238-R02-A | |
| Falcon 900LX S/N ≤ 290 | FSN-238-R02-A | |
| Falcon 900EX EASy and DX | FSN-238-R02-A | |
| Falcon 7X S/N ≤ 261 | FSN-238-R02-A | |
| Falcon 7X S/N ≥ 262 (NG I/O) | FSN-238-R02-A |
The aircraft operator shall (in accordance with ICAO Annex 6 Part 2):
- ensure that:
- the aircraft is provided with communication and surveillance equipment which will enable it to operate in accordance with the prescribed RCP and RSP specification(s);
- information relevant to the aircraft RCP and RSP specification capabilities is listed in the flight manual or other aircraft documentation;
- where the aeroplane is operated in accordance with a Minimum Equipment List (MEL), information relevant to the RCP/RSP specification capabilities is included in the MEL.
- establish and document:
- normal and abnormal procedures, including contingency procedures;
- flight crew qualification and proficiency requirements, in accordance with appropriate RCP/RSP specifications;
- a training programme for relevant personnel consistent with the intended operations;
- Appropriate maintenance procedures to ensure continued airworthiness, in accordance with the appropriate RCP/RSP specifications.
The aircraft operator should (in accordance with the ICAO PBCS Manual):
- participate in local and regional PBCS monitoring programmes which are applicable to the aircraft operator’s route system and should provide the following information to the appropriate PBCS monitoring entities specified in AIPs (or equivalent publications):
- operator name;
- operator contact details; and
- other coordination information
- establish procedures to report problems, identified either by the flight crew or other personnel, to the appropriate PBCS monitoring entities associated with the route of flight on which the problem occurred.
- ensure procedures are established for the timely disclosure and delivery of operational data, including data from its CSPs/SSPs, to the appropriate PBCS monitoring entity when requested for the purposes of investigating a reported problem.
- PBCS monitoring data demonstrating non-conformity for the NAT HLA will be communicated initially by the NAT Air Navigation Service Providers. The NAT Region is coordinating with the Regional Monitoring Agencies to implement a centralised mechanism for communicating non-conformity information. ICAO NAT OPS Bulletin 2018_001 will be updated when the centralised system is updated.
- PBCS monitoring for PBCS in the Singapore FIR is not detailed in Singapore AIP Supplement 007/2018.
- ensure that contracted services such as Communications Service Provider (CSP) or Satellite Service Provider (SSP) are bound by contractual arrangements stipulating the RCP/RSP allocations, including any monitoring or recording requirements and also include a provision for the CSP or SSP to notify the appropriate ATS units of failure conditions impacting PBCS operations. An “alternate means of compliance” is for operators to sign up to the PBCS Global Charter using http://www.fans-cra.com/ where stakeholders can obtain proof of respective CSP signature, as required by approval process.
- Note: details of the PBCS monitoring procedures are still under discussion and will be made available in due course by the relevant authorities.
When filing RCP/RSP capabilities, the aircraft operator should ensure that the planned use of associated communication and surveillance capabilities for the flight will be in accordance with regulations, policies and procedures in the specific areas for the flight, as published by the applicable States in their AIPs (or equivalent publications).
The aircraft operator should ensure that the proper denotation of PBCS capabilities are included in the ICAO flight plan:
- In Item 10, the aircraft operator shall insert “P2” to identify an aircraft’s RCP 240 capability; and
- In Item 18, the aircraft operator shall file the RSP 180 capability by inserting the indicator “SUR/RSP 180”.
The implementation list and map below is only intended as guidance.
As of 22nd October 2018, PBCS is in effect in one form or another in the following FIR’s:
- NZZC/Auckland Oceanic
- NFFF/Nadi
- KZAK/Oakland Oceanic
- PAZN/Anchorage Oceanic
- WSJC/Singapore
- VCCF/Sri Lanka
- NTTT/Tahiti
- RJJJ/ Fukuoka
- KZNY/New York Oceanic
- CZQX/Gander
- EGGX/Shanwick
- BIRD/ Reykjavik
- LPPO/Santa Maria Oceanic
What is an RCP specification?
It includes communication performance requirements that are allocated to system components in terms of the communication to be provided and the associated transaction time, continuity, availability, integrity and safety and functionality need for the proposed operation in the context of a particular airspace concept.
What is an RSP specification?
It includes surveillance performance requirements that are allocated to system components in terms of the surveillance to be provided and the associated data delivery time, continuity, availability, integrity, accuracy of the surveillance data and safety and functionality need for the proposed operation in the context of a particular airspace concept.
What is the PBCS Charter?
The PBCS charter is an alternative means to ensure that each data link stakeholder meets its allocated responsibilities according to the RCP/RSP specifications and was developed by ICAO PBCS project team.
What is a CSP and a SSP?
A CSP is any public or private entity providing communications services for general air traffic. This would include services provided by a satellite service provider through a contract or agreement.
A SSP is an entity or group of entities that provide, via satellite, aeronautical fixed services and/or aeronautical mobile services at least from the signal in space to /from aircraft, to the attachment point of the ground earth station (GES) to the ground communication services network.
Who/What must comply with an RCP/RSP specification?
Air Traffic Services (ATS) system, the CSP, the SSP, the operator and the aircraft system.
Are there any additional PBCS requirements concerning the production and airworthiness certificates?
The IOMAR do not mandate any additional PBCS requirements concerning the production and airworthiness certificates for ‘M’ registered aircraft.
Should the system provide flight crew with alerts associated with the RCP 240 and RSP 180?
Yes.
What are the Sub networks designators for FANS 1/A+ (PBCS) for CPDLC at RCP 240 & ADS-C at RSP 180?
VDL M0/A
VDL M2
Satellite Communication (SAT COM) (Inmarsat)
Satellite Communication (SAT COM) (Iridium)
Further information on PBCS can be found in the following documents which are available from ICAO:
- Performance Based Communication and Surveillance (PBCS Manual) (ICAO Doc 9869);
- Global Operation Data Link Document (GOLD) (ICAO Doc 10037);
- ICAO Annex 11 – Air Traffic Services;
- ICAO document 4444 – Pans ATM Manual;
- ICAO Annex 6 Part II- Operation of Aircraft;
- ICAO Annex 15 Aeronautical Information Services; and
ICAO document 7030 Regional Supplementary Procedures Manual.