To apply for IOMAR PBCS approval operators should complete and submit a new Form 4 selecting 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)|
|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||Challenger 300||with SB 100-23-22|
|Challenger 350||with SB 350-23-011|
|Challenger 604||with SB 604-23-014|
|Challenger 605||with SB 605-23-008|
|Challenger 650||with SB-650-23-008|
|Global Express/XRS||with SB 700-31-039|
|Global 5000||with SB 700-1A11-31-021|
|Global 5000 GVFD||nil|
|Gulfstream||G280||with FANS 1/A+ CPDLC and Rockwell Collins Proline Fusion PlaneView|
|G550||with ASC 912A or later|
|Dassault||Falcon 50EX||STC Proline 21|
|Falcon 900LX S/N ≤ 290||with SB F900EX-560|
|Falcon 900LX S/N ≥ 291||with SB F900EX-561|
|Falcon 2000||STC Proline 21|
|Falcon 2000EX||STC Proline 21|
|Falcon 2000EX EASy and DX||with SB F900EX-560|
|Falcon 2000S S/N ≤ 730||with SB F2000EX-450|
|Falcon 2000S S/N ≥ 731||with SB F2000EX-451|
|Falcon 2000LXS S/N ≤ 292||with SB F2000EX-450|
|Falcon 2000LXS S/N ≥ 293||with SB F2000EX-451|
|Falcon 2000EX EASy, DX and LX||with SB F2000EX-450|
|Falcon 7X S/N ≤ 261||with SB F7X-520|
|Falcon 7X S/N ≥ 262||with SB F7X-521|
|Falcon 8X (EASy III)||nil|
The aircraft operator shall ensure that:
1) Normal and abnormal procedures, including contingency procedures are documented that meet the specific operational criteria for airspace where FANS 1/A+ (PBCS) is mandatory and flight crews are suitably trained and competent to operate the data link communication equipment;
NOTE: flight crew procedures and training should include normal operations, as well as those associated with alerts provided by the aircraft system to indicate failures when the aircraft is no longer capable of meeting the RCP/RSP specification prescribed for the associated ATM operations;
2) Contracted services, such as those with communication service providers (CSPs), are bound by contractual arrangements stipulating the RCP/RSP allocations, including any monitoring or recording requirements;
3) Contractual arrangements include a provision for the CSP to notify the appropriate ATS units for the route system of the aircraft operator in case failure conditions impact PBCS operations;
NOTE: 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.
4) The aircraft system is properly maintained, including configuring user-modifiable software, such as those used to manage communication media and routing policies, to meet the appropriate RCP/RSP specification(s); and
5) Procedures have been established for the reporting of problems, identified either by the flight crew or other personnel, to the IOMAR.
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 Field 10a, the aircraft operator shall insert “P2” to identify an aircraft’s RCP 240 capability; and
- In Field 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 designated airspace and FIR’s:
- NAT HLA Special PBCS tracks;
- NZZC/Auckland Oceanic;
- KZAK/Oakland Oceanic;
- PAZN/Anchorage Oceanic;
- VCCF/Sri Lanka;
- RJJJ/ Fukuoka;
- KZNY/New York Oceanic;
- BIRD/ Reykjavik;
- LPPO/Santa Maria Oceanic.
What is an RCP specification?
Required Communication Performance (RCP). The RCP Transaction Time defines the maximum time required for the completion of the transaction after which the initiator should revert to an alternative procedure.
What is an RSP specification?
Required Surveillance Performance (RSP). The RSP Surveillance Data Transit Time describes the time required for delivery of surveillance data in seconds.
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 Communication Service Provider (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 Satellite Service Provider (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?
What are the Sub networks designators for FANS 1/A+ (PBCS) for CPDLC at RCP 240 & ADS-C at RSP 180?
Satellite Communication (SAT COM) (Inmarsat)
Satellite Communication (SAT COM) (Iridium)
What happens if a PBCS non-compliance report is received by the IOMAR from from EUR RMA about my aircraft?
Depending on the categorisation of data transmitted to the IOMAR (State Oversight Authority) by the RMA, the IOMAR may engage in a choice of actions:
- To monitor the data provided and retain the data for trend analysis; or
- Contact the Flight Operations Representative (FOR) and Operator contacts directly to understand the actions being taken to improve performance. The email will cc the appropriate reporting ANSP or ATSP who filed the report attaching a copy of the report. (Exceptionally, the IOMAR may choose to take formal enforcement action for the operator. Although this remains a tool within its toolbox, it should be fully justified.)
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);
- ICAO NAT Ops bulletins;
- 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.
ICAO have published NAT OPS Bulletin 2019_003 Rev 3 effective 30 June 2021, with the purpose to provide guidance to North Atlantic (NAT) operators regarding options that are available to improve data link performance.
The attachment 'List of data link performance improvement options' gives nine problems/issues and appropriate solutions/actions to remedy them.
The Registry would like to draw attention to page 8 of the bulletin that gives the full information regarding the recommended software versions for NAT data link operations.
A sample of some aircraft types have been copied into the table below:
|Aircraft Type||FANS software||ACARS software||Notes|
|A318/A319/A320/A321||CSB7.5 or CSB9.4||CSB7.5 or CSB9.4||Aircraft with Thales FMS: S8
|A330/A340||CLR7.5 or CLR9.4||CLR7.5 or CLR9.4||Aircraft with Thales FMS: T6
|A4 hardware: FMS U12*
C1 hardware: FMS U13* or U14
|Refer to applicable Service Bulletins and/or STCs||* There are planned ADs against the currently listed software. Updated software with AD related fixes are
currently in the certification process or are already available for installation.
|Bombardier Learjet 35, 36, 35A, 36A, 40, 40XR,
45, 45XR, 60, 60XR
|Universal Avionics FMS SCN 1002.1||Universal Avionics UniLink UL-80X SCN 31.3||nil|
|Bombardier Challenger 300, 350||Collins Proline 21 Advanced||Collins RIU-4000||nil|
|Bombardier Challenger 600, 601, 601-1A, 601-3A, 601-3R, 604||Universal Avionics FMS SCN 1002.1||Universal Avionics UniLink UL-80X SCN 31.3||nil|
|Bombardier Challenger 600, 601, 601-1A, 601-3A, 601-3R||Honeywell NZ6.1.1||Honeywell CMU MK II+||nil|
|Bombardier Challenger 605, 650||Collins Proline 21 Advanced||Collins CMU-4000||nil|
|Bombardier Global Express,
Global Express XRS, Global 5000
|Honeywell NZ6.1.1||Refer to applicable Service Bulletins/STCs||nil|
|Bombardier Global 5000 GVFD||Collins Proline Fusion||Collins DLCA-6000||nil|
|Bombardier Global 5500||Collins Proline Fusion||Collins DLCA-6000||nil|
|Bombardier Global 6000||Collins Proline Fusion||Collins DLCA-6000||nil|
|Bombardier Global 6500||Collins Proline Fusion||Collins DLCA-6000||nil|
|Bombardier Global 7500||Collins Proline Fusion||Collins DLCA-6500||nil|
|Dassault F50, F50EX||Universal Avionics UNS-1||Universal Avionics UniLink UL-80X SCN 30.4||3rd party STCs|
|Dassault F50, F50EX||Honeywell NZ6.1.1||Honeywell CMU MK II+||3rd party STCs|
|Dassault F2000||Universal Avionics UNS-1||Universal Avionics UniLink UL-80X SCN 30.4 3||3rd party STCs|
|Dassault F2000 DX/EX/LX/S||Honeywell EPIC NZ7.1.2||Honeywell EPIC CMF 2.51||EASy II 4th Cert|
|Dassault F900, F900B, F900C, F900EX||Honeywell NZ6.1.1||Honeywell CMU MK II+||nil|
|Dassault F900 DX/EX/LX||Honeywell EPIC NZ7.1.2||Honeywell EPIC CMF 2.51||EASy II 4th Cert|
|Dassault F900B||Universal Avionics UNS-1||Universal Avionics UniLink UL-80X SCN 30.4||3rd party STCs|
|Dassault F7X||Honeywell EPIC NZ7.1.2||Honeywell EPIC CMF 2.51||EASy II 4th Cert|
|Dassault F7X||Honeywell NGFMS||Honeywell EPIC CMF 3.4||New EASy IV late 2021|
|Dassault F8X||Honeywell NGFMS||Honeywell EPIC CMF 3.0||EASy III 2nd Cert|
|Dassault F8X||Honeywell NGFMS||Honeywell EPIC CMF 3.4||New EASy IV late 2021|
"Legacy 600/650" business jet version
|Honeywell NZ6.1.1||Honeywell CMU MK III Bld 1.29||nil|
"Lineage 1000" business jet version
|Honeywell NGFMS||Honeywell EPIC CMF 3.0||nil|
|Embraer E170/175/190/195||Honeywell NGFMS||Honeywell EPIC CMF 3.0||nil|
|Embraer E170/175/190/195||Honeywell NGFMS||Honeywell EPIC CMF 3.4||nil|
|Embraer E2-190/195||Honeywell NGFMS||Honeywell EPIC CMF 3.3||nil|
|Embraer E2-190/195||Honeywell NGFMS||Honeywell EPIC CMF 3.4||New Load 9 mid 2022|
|Gulfstream G200||Collins Proline 4 (FMC SW 4.0)||Collins CMU-1000||Gulfstream STC|
|Gulfstream G200||Universal Avionics UNS-1||Universal Avionics UniLink UL-80X SCN 30.4||Gulfstream STC|
|Gulfstream G200||Universal Avionics UNS-1||Universal Avionics UniLink UL-80X SCN 30.4||3rd party STCs|
|Gulfstream G280||Collins Proline Fusion||DLCA-6000||Production standard|
|Gulfstream G450||Honeywell EPIC NZ7.1.2||Honeywell EPIC CMF 2.6||(ASC 912C)|
|Gulfstream G550||Honeywell EPIC NZ7.1.2||Honeywell EPIC CMF 2.6||(ASC 912C)|
|Gulfstream GIV, GIV-SP||Honeywell NZ6.1.1||Honeywell CMU MK III Bld 1.29||nil|
|Gulfstream GV, GV-SP||Honeywell NZ6.1.1||Honeywell CMU MK III Bld 1.29||nil|
|Gulfstream G500||Honeywell NGFMS||Honeywell EPIC CMF 3.1||(Type Cert)|
|Gulfstream G600||Honeywell NGFMS||Honeywell EPIC CMF 3.1||(Type Cert)|
|Gulfstream G650||Honeywell NGFMS||Honeywell EPIC CMF 3.0||(ASC 902B)|
|Gulfstream G650||Honeywell NGFMS||Honeywell EPIC CMF 3.1||New Block 3 late 2021|
|Gulfstream G700||Honeywell NGFMS||Honeywell EPIC CMF 3.5||New Type Cert 2022|
Information above from NAT Ops bulletin 2019_003 Rev 3, dated 30 June 2021.