Of the current RNP designations, RNP-4 is the specification designed for oceanic and remote continental navigation applications. While RNP-10 and North Atlantic High Level Airspace (the old MNPS) are also used, they are not true Performance Based Navigation standards. (We can expect them to go away in the future.)
As of summer 2016, only a handful of places in the world say RNP-4 is required but they all have work arounds in place if you are RNP-10 authorized. If you plan on oceanic or remote operations, you will need an LOA when operating under 14 CFR 91. If you are operating under 14 CFR 135, you will need OpSpec B036.
What follows comes from the references shown below. Where I think it helpful, I've added my own comments in blue.
[ICAO Doc 7030, §MID/ASIA, ¶22.214.171.124.2] For flights on designated controlled oceanic routes or areas within the Auckland Oceanic, Brisbane, Fukuoka, Honiara, Melbourne, Nauru, New Zealand and Port Moresby FIRs, a longitudinal separation minimum of 55.5 km (30 NM) derived by RNAV may be applied between RNAV-equipped aircraft approved to RNP 4 or better, in accordance with the provisions of the PANS-ATM, 126.96.36.199.
[ICAO Doc 7030, §PAC, ¶188.8.131.52.2] For flights on designated controlled oceanic routes or areas within the Anchorage Arctic, Anchorage Continental, Anchorage Oceanic, Auckland Oceanic, Nadi, Oakland Oceanic and Tahiti FIRs, a longitudinal separation minimum of 55.5 km (30 NM) derived by RNAV may be applied between RNAV-equipped aircraft approved to RNP 4 or better, in accordance with the provisions of the PANS-ATM, 184.108.40.206.
In both the Asia and Pacific instances, the 30 NM longitudinal separation "may be applied." If you do not have RNP-4 authorization the following PANS-ATM provisions are cited:
[ICAO Doc 4444, ¶220.127.116.11] LONGITUDINAL SEPARATION MINIMA BASED ON DISTANCE USING RNAV WHERE RNP IS SPECIFIED
18.104.22.168.2.2 Direct controller-pilot communications shall be maintained while applying a distance-based separation minima. Direct controller-pilot communications shall be voice or CPDLC. The communication criteria necessary for CPDLC to satisfy the requirement for direct controller-pilot communications shall be established by an appropriate safety assessment.
22.214.171.124.3 Longitudinal distance-based separation minima in an RNP RNAV environment not using ADS
126.96.36.199.3.1 For aircraft cruising, climbing or descending on the same track, the following separation minimum may be used:
|Separation minimum||RNP type||Communication requirement||Surveillance requirement||Distance verification requirements|
|93 km (50NM)||10||Direct controller-pilot communications||Procedure position reports||At least every 24 minutes|
188.8.131.52.4 Longitudinal distance-based separation minima in 184.108.40.206.4 an RNP RNAV environment using ADS
220.127.116.11.4.3 For aircraft cruising, climbing or descending on the same track, the following separation minima may be used:
|Separation minimum||RNP type||Maximum ADS periodic reporting interval|
|93 km (50NM)||10||27 minutes|
|93 km (50NM)||4||32 minutes|
|55.5 km (30NM)||4||14 minutes|
If you do not have ADS and are not RNP-4 authorized, the controllers have the option of accepting you but using increased separation standards provided: you are RNP-10 qualified, you are in direct communications with the controller, and you make position reports at least every 24 minutes.
[ICAO Doc 9613, Volume II, Part C,¶18.104.22.168]
Note.— Compliance with the performance monitoring and alerting requirement does not imply an automatic monitor of flight technical error. The on-board monitoring and alerting function should consist at least of a navigation system error (NSE) monitoring and alerting algorithm and a lateral deviation display enabling the crew to monitor the flight technical error (FTE). To the extent operational procedures are used to monitor FTE, the crew procedure, equipment characteristics, and installation are evaluated for their effectiveness and equivalence as described in the functional requirements and operating procedures. Path definition error (PDE) is considered negligible due to the quality assurance process (1.3.6) and crew procedures (1.3.4).
These requirements are duplicated in Advisory Circular (AC) 20-138( ), Airworthiness Approval of Positioning and Navigation Systems.
[ICAO Doc 9613, Volume II, Part C,¶22.214.171.124] It is important to understand that additional requirements will have to be met for operational authorization in RNP 4 airspace or on RNP 4 routes. Controller-pilot data link communications (CPDLC) and automatic dependent surveillance — contract (ADS-C) systems will also be required when the separation standard is 30 NM lateral and/or longitudinal. The on-board navigation data must be current and include appropriate procedures.
This is a potential "gotcha" in the works. You can have an OpSpec/MSpec/LOA for RNP-4 authorization without CPDLC and ADS. (Some POIs will not permit this, but some will.) There are locations in the world where the requirement for RNP-4 authorization assumes CPDLC and ADS.
[AC 90-105A, App. F, ¶F.2]
Note: RNP 4 operations are based on Global Positioning System (GPS) positioning. Positioning data from other types of navigation sensors may be integrated with the GPS data provided it does not cause position errors exceeding the Total System Error (TSE) budget. Otherwise, means should be provided to deselect the other navigation sensor types.
Note: Previous approvals under FAA Order 8400.12C, Required Navigation Performance 10 (RNP 10) Operational Authorization, and FAA Order 8400.33, Procedures for Obtaining Authorization for Required Navigation Performance 4 (RNP-4) Oceanic and Remote Area Operations, are still valid for these operations. Operators must ensure their operations remain consistent with the performance and functional requirements of this AC.
[AC 90-105A] Parts 91K, 121, 125, 129, and 135 Operators. Title 14 CFR parts 91K, 121, 125, 129, and 135 operators receive approval to fly RNP operations as described in this AC via operations specifications (OpSpecs), management specifications (MSpecs), or LOAs as follows:
[FAA Order 8900.10 Vol 3, Chapter 18, Part B, §B036, ¶k)] OpSpec/MSpec Entries.
"Easter Russia" is probably a typo, most likely means eastern Russia.
Figure: Limitations Extract, from G450 Airplane Flight Manual, §1-03-10, ¶13.]
Portions of this page can be found in the book International Flight Operations, Part III, Chapter 9.
Advisory Circular 20-138D, Positioning and Navigation Systems, 5/8/12, U.S. Department of Transportation
Advisory Circular 90-105A, Approval Guidance for RNP Operations and Barometric Vertical Navigation in the U.S. National Airspace System and in Oceanic and Remote Continental Airspace, 3/7/2016, U.S. Department of Transportation
FAA Order 8400.33, Procedures for Obtaining Authorization for Required Navigation Performance 4 (RNP-4) Oceanic and Remote Area Operations, U.S. Department of Transportation, 9/15/05
ICAO Doc 4444 - Air Traffic Management, Fourteenth Edition, Procedures for Air Navigation Services, International Civil Aviation Organization, 2001 *
ICAO Doc 4444 - Air Traffic Management, Fifteenth Edition, Procedures for Air Navigation Services, International Civil Aviation Organization, 2007 *
* Not all of Doc 4444 seems to have been reproduced in the 15th edition, so you might need to look at the 15th edition and then then 14th edition for some sections.
ICAO Doc 4444 - Amendment No. 1, Procedures for Air Navigation Services, International Civil Aviation Organization, Amendment No. 1, 2007
ICAO Doc 4444 - Amendment No. 2, Procedures for Air Navigation Services, International Civil Aviation Organization, Amendment No. 2, 19/11/09
ICAO Doc 7030 - Regional Supplementary Procedures, International Civil Aviation Organization, 2008
ICAO Doc 9613 - Performance Based Navigation (PBN) Manual, International Civil Aviation Organization, 2008