Objective

The performance-based communication and surveillance (PBCS) concept provides objective operational criteria to evaluate different and emerging communication and surveillance technologies, intended for evolving air traffic management (ATM) operations. The PBCS also provides a framework in which all stakeholders (regulators, air traffic service providers, operators, communication service providers (CSP), and manufacturers) continue to collaborate in optimizing the use of available airspace while identifying and mitigating safety risks.

PBCS Vs PBN

The PBCS concept is aligned with that of performance-based navigation (PBN). While the PBN concept applies required navigation performance (RNP) and area navigation (RNAV) specifications to the navigation element, the PBCS concept applies required communication performance (RCP) and required surveillance performance (RSP) specifications to communication and surveillance elements, respectively. However, there are some differences between the PBCS and PBN concepts:

a) the PBCS concept applies RCP and RSP specifications, which allocate criteria to ATS provision, including communication services, aircraft capability, and the aircraft operator; whereas the PBN concept applies RNP/RNAV specifications, which allocate criteria only to the aircraft capability and the aircraft operator; and

b) the PBCS concept includes post-implementation monitoring programs, on a local and regional basis, with global exchange of information; whereas the PBN concept includes real time monitoring and alerting functionality in the aircraft capability.

 WHY WAS SEPTEMBER 30, 2018 CHOSEN FOR A PBCS DEADLINE?

The ICAO Provisions for Performance Based Communication and Surveillance, PBCS including new Standards and Recommended Practices (SARPS) and related guidance material have been applicable since 10NOV16. It became apparent to the NAT Systems and Planning Group and Asia/Pacific Air Navigation Planning and Implementation Regional Group that worldwide PBCS would not be fully implemented by that date. A new date was agreed upon, 30SEPT18.

NOTE –  Even with the relaxed deadline for Part 91, you should begin addressing the requirements as soon as possible.

WHY DO I HAVE TO DO THIS PBCS MONITORING STUFF?

Some States may require the filing of PBCS designators in flight plans for the provision of 50 NM and 30 NM longitudinal and 23 NM (formerly 30 NM) lateral separation minima after the applicability date of the PBCS provisions.

FOR CURRENT OPSSPEC/LOA A056 HOLDERS, AFTER 30SEPT18 AND W/O PBCS MONITORING DATA, DOES THE OPSPEC/LOA BECOME INVALID?

Yes, is the short answer. Current A056 holders will have to comply with a mandatory change to the new A056 template.  With the new template, the operator will have to determine if their aircraft is eligible for RCP/RSP (PBCS) operations.  This is done by following Chapter 3 of AC 90-117 (Published in late October 2017). An FAA operator’s guide to compliance is also in the works, (to be published after the AC).  ICAO has already published new guidance in Annex 11 and Documents #4444, #9869, and #10037.

WHERE IS IT THAT I CAN GET THIS “PBCS MONITORING DATA” ?

Since 2009 the FAA has tracked the rates of equipage, connection and continuity for CPDLC and ADS-C. The North American Approvals Registry and Monitoring Organization (NAARMO), hosted by the FAA Separation Standards Analysis Branch at the Technical Center has produced a monitoring webpage (similar to RVSM monitoring results) to publish this data and provide important information related to PBCS. Here is a link: https://www.faa.gov/air_traffic/separation_standards/pbcs_monitoring/ During initial implementation, monitoring results will be posted every 6 months.  As the program matures, that interval may change. The most recent data covers JUL thru DEC 2017. The data on this spreadsheet comes from CPDLC and ADS-C connections pilots made in Oakland, Anchorage, New York OCAs. Operators are encouraged to sign up to the www.FANS-CRA.com website to obtain more comprehensive monitoring data including results from FAA as well as Gander, Fukuoka, CPDLC/ADS-C connection and continuity data is being shared with the FAA from Reykjavik, Shanwick, Santa Maria, and Auckland OCAs. Magadan and the others are an unknown at this point. It is not a requirement for OpsSpec/LOA A056 holders to keep PBCS monitoring data onboard while operating.

WHAT IS ALL THIS DATA TRYING TO TELL ME?

Required Communication Performance, RCP the designator (i.e. RCP 240, 400) represents the value for the maximum communication transaction time after which the initiator should revert to an alternative communication procedure. Usually HF radio is the backup in oceanic/remote regions. Besides a time threshold, an RCP specification represents operational values for communication transaction continuity, availability, and integrity applicable to the communication transaction supporting an ATM function. This elapsed time includes technical communication performance, average human-machine interface and average cockpit response times. This is commonly referred to as “Cockpit thinking times”. “STBY” is not the response that triggers this timing threshold. Only the “ROGER” or “WILCO” count toward an RCP-240 qualification. An RSP specification label (i.e. RSP 180, 400) represents the values assigned to RSP parameters for surveillance transaction time (in seconds), continuity, availability, and integrity. Traditionally, surveillance over oceanic and remote areas was limited to pilot position reports via High Frequency, HF radio. Once the aircraft entered a radar environment, pilot reports were eliminated. Surveillance in oceanic and remote airspace is accomplished much more accurately through the use of ADS-C. As with CPDLC, ADS-C requires certain performance requirements for operational surveillance in support of specific ATM functions. This includes the transmission of aircraft position, velocity and intent with a specified precision, accuracy and update rates.

WHAT HAPPENS IF I DON’T PASS THE PBCS TEST ?

The operator will have to provide proof of aircraft eligibility to either receive their initial authorization or add PBCS to their current A056 and monitoring data will be used to determine demonstrated performance. All new A-056 approvals are to be initially approved with a provision to get monitoring and provide adequate sampling to remain qualified. 100 data points are the desired level of sampling. For “N”-registered aircraft, if it is found an operator/airframe does not have enough data, the initial authorization will be based on an OEM statement of compliance in the AFM, AFM supplement or similar documentation. One-off installations via STC’s will be handled individually. Operators need to be diligent in getting problem reports to regional monitoring authorities. The next best option is to make your POI and the ATC agency involved aware of data link problems encountered. If demonstrated performance monitoring is available and it is “pass”, provide that information with their application.  If that monitoring data is “fail” that aircraft/fleet is not eligible for RCP/RSP (PBCS) ops pending satisfactory performance.  If no monitoring data is available or “insufficient data” is shown, the operator should include proof in their application and only the Statement of Compliance will be used.  Performance monitoring sight is listed in AC 90-117 Chapter 6. Meanwhile, for further information on your specific airframe monitoring results, please contact NAARMO@faa.gov

JUST WHAT DOES ALL THIS MONITORING GET ME OPERATIONALLY ?

RCP-240 is coupled with RSP-180 is the desired designation for ATC. These two designations are what allow ATC to separate your aircraft from other equally equipped and performing aircraft by minimum distances while preserving the Target Level of Safety (READ: no mid-air). Current reduced separation standards are 30NM lateral/longitudinal and 23NM lateral/5-min longitudinal. The monitoring data for granting initial authorization will give an operator their OpsSpec/LOA A056 stating operational approval to use RCP/RSP at the performance level shown.  Subsequent monitoring data may “fail”; the operator should follow the guidance on the monitoring site.  They should not file the corresponding P-code/Block 18 code until they follow the given directions.  If performance doesn’t improve, it may result in losing their A056 RCP/RSP authorization.  If this happens, the operator may still be able to participate in basic CPDLC/ADS-C ops. Domestic USA enroute services are expected to begin in 2019 using existing FANS 1/A aircraft to deliver CPDLC services in the U.S. NAS en route airspace. ?Full enroute services are expected to begin in 2025 and will provide advanced services, such as four-dimensional (4D) trajectories, dynamic required navigation performance, advanced flight interval management with ATC wind information.

MORE FLIGHT PLAN EQUIPMENT CODES

These documents will reference the use of “P-Codes” on the flight plan forms. P-1, 2, 3 or 4 when inserted into block#10 will indicate what level of RCP your CPDLC connections are operating at (400sec or 240sec).  Here is an example: Item 10: Equipment, 10A Communication and Navigation (Before the diagonal mark) P1, CPDLC RCP 400 P2, CPDLC RCP 240 P3, SATVOICE RCP 400 P4-P9, Reserved These are to be further explained in block#18 behind the DAT/ and SUR/ entries. D-1 and G-1 entries will have a similar description for the ADS-C connection. MMEL and MEL’s will need to be updated with this RCP/RSP information. Operators are cautioned that an MEL downgrade to RCP or RSP needs to be indicated on the current flight plan. Without a J-5 or J-7 code on the flight plan, expect to be denied routing thru FANS1/a required airspace due to ATOP computer programming. ATC expects this programming to be complete by summer of 2017. RCP400 and RSP400 are not tied to any reduced separation standards. Basically “P3” won’t do anything for you. Bottomline 1. Flight plan equipment codes are dependent on installation, functionality and performance, not just an STC/TC installation 2. Pilots need to understand that “STBY” is a quick and legitimate response to ATC but, will NOT help improve response time performance monitoring 3. In most cases, prior datalink performance monitoring is required for operating approval 4. Problem reporting to POI’s and regional monitoring agencies will be key to troubleshooting FANS communication and surveillance problems

SourceOne Aviation Compliance programs:

Please see our “Purchase” page to submit a purchase order for the Data Link Operations Manual & FAA LOA A056 LOA/OpSpec Application

ICAO and FAA compliant Data Link Operations Manuals

FAA LOA/OpSpec A056 New Issue & Re-Issue Applications

for the following: