APANPIRG/29

Appendix B to the Report on Agenda Item 3.4

PBN NavSpecs and Route Spacing (Ref. PBN Manual Doc 9613 Volume II, Attachment B & PANS-OPS Doc 8168 Volume II, Part III, PANS-ATM Doc 4444, and Annex 15)
Flight Phase Additional Functionality
Operational Requirements
Nav Specs En-route En-route Approach Supporting Nav. (Repuired or Optional)
Arrival Departure Route Spacing (NM)
Remote Continental Initial Intermediate Final Missed1) Infrastructure RF FRT TOAC2) Baro VNAV Nav DB Communication Navigation Surveillance AIM Others
Not require ground- Lateral Voice com through RNAV 10 (RNP 10) Longitudinal WGS-84; QMS for System safety and
based Naviad 50 between RNAV10, RNP4, or RNP2 3rd party, DCPC in Approval, lateral deviation Procedureal pilot AIS; AIRAC datalink performance
Dual LRNS (INS, IRS some areas. less than 7NM (same position report (max Compliance for (PBCS) must be
FMS, GNSS) Longitudinal direction)/6NM (opposite 24min) publication (42 days, -9
monitored, TLS 5X10
50 with DCPC, procedureal position report Longitudinal direction) 50 with RSP 180 recommended 56 accident per flight hour
- Distance verification : at least every 50 with RCP240 (CPDLC) days ); ICARD for
24min (ADS-C) new waypoint Max ADS-C periodic
50 with reporting interval 27min names; Air reporting interval
5min with reporing interval 14min Navigation Plan - 27min for 50NM
RNAV 10
10 TBD2) O Amendment for - 14min for 5min
(RNP 10)
Regional ATS Routes;
Regional
Supplementary
Procedures (Doc
7030) for application
in airspace over the
high seas; PBCS

VOR/DME Lateral DCPC- VHF RNAV 5 OPS Approval Procedureal pilot WGS-84; QMS for
DME/DME 16.5 - straight unidirectional racks (same (BRNAV) position report AIS; AIRAC
INS or IRS direction route-ECAC) Surveillance (RNAV Compliance for
GNSS 18 - straight bidirectional tracks (opposite 5) publication (42 days,
direction route- ECAC) recommended 56
10 - ATC intervention capability (ECAC) days; ICARD for new
RNAV 5 5 53) 30 - No ATS Surveillance in high traffic TBD O waypoint names; Air
density (ECAC) Navigation Plan
Amendment for
Regional ATS Routes

GNSS Lateral DCPC- VHF RNAV 2 OPS Approval surveillance Same as RNAV 5
RNAV 2 2 2 2 DME/DME 8 to 9 - straight tracks in high traffic TBD R (PRNAV, US RNAV AC 90-
DME/DME/IRU density (en-route) (FAA) 100)

GNSS Lateral DCPC- VHF RNAV 1 OPS Approval surveillance WGS-84; QMS for
DME/DME For SIDs/STARs (PANS-ATM) (PRNAV, US RNAV AC 90- AIS; AIRAC
DME/DME/IRU 7 between RNAV1 and RNAV1, RNP1. RNP 100) Compliance for
RNAV 1 1 1 1 1 1 1 APCH, or RNP AR APCH TBD O R publication (42 days,
recommended 56
days

3.4B - 1
 APANPIRG/29
Appendix B to the Report on Agenda Item 3.4

Not require ground- Lateral DCPC or CPDLC. RNP 4 OPS Approval ADS with a lateral WGS-84; QMS for Conformance
based Naviad 50 between RNAV10, RNP4 or RNP2 Requires PBCS deviation contract AIS; AIRAC monitoring shall be
GNSS 23 between RNP4 or RNP2 (SLOP up to (RCP240) having 5NM. Compliance for ensured by establishing
2NM) Requires PBCS publication (42 days, an ADS-C event
- 12 for climbs/descends through aircraft (RSP180) recommended 56 contract specifying a
in level days; ICARD for new lateral deviation change
20 between RNP4 or RNP2 (No SLOP or waypoint names; Air event with a maximum
SLOP up to 0.5NM) Navigation Plan of 5 NM threshold and
- 9 for climbs/descends through aircraft Amendment for a waypoint change
RNP 4 4 in level O TBD R Regional ATS Routes; event
Regional
Longitudinal Supplementary Max ADS-C periodic
50 with reporting interval 32min Procedures (Doc reporting interval
30 with reporitn interval 12min 7030) for application - 32min for 50NM
5 min with reporting intercal 14min in airspace over the - 12min for 30NM
high seas; PBCS - 14min for 5min

GNSS Lateral Requires PBCS RNP 2 OPS Approval Requires PBCS Same as RNP 4 Conformance
Apply minima in RNP4 if RNP2 is related (RCP240) for (Oceanic/Remote/contine (RSP180) for monitoring shall be
Between RNP2 or GNSS equipage Oceanic/Remote; ntal) Oceanic/Remote ensured by establishing
- 23 for SLOP up to 2NM, climbs/descends For other areas, an ADS-C event
through aircraft in level depends on contract specifying a
- 20 for No SLOP or SLOP up to 0.5NM, operational lateral deviation change
climbs/descends through aircraft in level considerations event with a maximum
- 18 for SLOP up to 2 NM with VHF DCPC (route spacing, of 5 NM threshold and
- 15 for No SLOP or SLOP up to 0.5NM traffic density, a waypoint change
with VHF DCPC complexity, event
- 10 for SLOP up to 2 NM with VHF DCPC, contingency
RNP 2 2 2 O TBD R
climbs/descends through aircraft in level procedures) Max ADS-C periodic
- 7 for No SLOP or SLOP up to 0.5NM with reporting interval
VHF DCPC, climbs/descends through - 12min for 30NM
aircraft in level - 14min for 5min
Longitudinal
30 with reporitn interval 12min
5 min with reporting intercal 14min

GNSS Lateral DCPC (RNP 1 RNP 1 OPS Approval Not required except WGS-84; QMS for
For SIDs/STARs (PANS-ATM) SIDs/STARs) reduced route AIS; AIRAC
5 between RNP1 and RNP1, RNP APCH, or spacing Compliance for
RNP 1 1 1 1 1 1 RNP AR APCH O TBD O R publication (42 days,
recommended 56
days

GNSS Lateral DCPC- VHF A-RNP OPS Approval surveillance (may WGS-84; QMS for
Multi-DME may be 7 - straight and turning tracks (<90˚) in (Navigation accuracy at not be required to AIS; AIRAC
provided high traffic density (en-route, Terminal, least ±1NM, 95% of the certain navigation Compliance for
A RNP4) 2 2 or 1 1 - 0.3 1 - 0.3 1 - 0.3 0.3 1 - 0.3 1 - 0.3 Eurocontrol) R O TBD O R flght time) application) publication (42 days,
6 to 7 NM with an RNP 0.5 (terminal, recommended 56
Eurocontrol) days

3.4B - 2
 APANPIRG/29
Appendix B to the Report on Agenda Item 3.4

GNSS Lateral Not required RNP APCH OPS Approval Not required WGS-84, QMS for
(Missed App - For SIDs/STARs (PANS-ATM) AIS, AIRAC,
RNAV or Conv.) 7 between RNAV1 and RNP APCH Compliance for
RNP APCH
5) 1 1 0.3 1 5 between RNP1 and RNP APCH O TBD O R publication (42 days,
(Part A)
recommended 56
days )

1 or 0.3 GNSS Lateral Not required RNP APCH OPS Approval Not required WGS-84, QMS for
RNP APCH (Initial For SIDs/STARs (PANS-ATM) AIS, AIRAC,
1 1 Angular O TBD R
(Part B)5) Straight 7 between RNAV1 and RNP APCH Compliance as
MISAP) 5 between RNP1 and RNP APCH above.
GNSS Lateral Not required RNP AR APCH OPS Not required WGS-84; QMS for
(DME/DME may be For SIDs/STARs (PANS-ATM) Approval AIS; AIRAC
authorized 7 between RNAV1 and RNP AR APCH Compliance for
6) 6)
RNP AR APCH 1 - 0.1 1 - 0.1 0.3 - 0.1 1 - 0.1 5 between RNP1 and RNP AR APCH R TBD R R publication (42 days,
recommended 56
days

GNSS Lateral (no clear reference) Not required RNP 0.3 OPS Approval Not required WGS-84; QMS for
For SIDs/STARs (PANS-ATM) AIS; AIRAC
7 between RNAV1 and RNP0.3 Compliance for
RNP 0.3 0.3 0.3 0.3 0.3 0.3 0.3 5 between RNP1, RNP APCH and RNP AR O TBD O R publication (42 days,
APCH recommended 56
days

1) RNP requirements do not apply to initial and intermediate missed approach segments.
2) TOAC (Time of Arrival Control), TBD (To Be Determined)
3) RNAV 5 may be used for initial parts of STARs outside 30 NM from the ARP.
4) Advanced RNP core requirements are limited to RNP 1 in all flight phases except final approach (RNP 0.3) and RNP 2 in oceanic/remote and en-route continental. A scaleability option will allow accuracy values between 0.3 and 1.0, in 0.1 NM
increments, in all flight phases except oceanic/remote/en-route continental (RNP 1 and RNP 2) and final approach (RNP 0.3).
5) Part A and B refer to the Performance-based Navigation (PBN) Manual (Doc 9613), Volume II, Part C, Chapter 5, Part A — RNP APCH operations down to LNAV and LNAV/VNAV minima and Part B — RNP APCH operations down to LP and LPV minima,
respectively.
6) Specific requirement for RF and VNAV

3.4B - 3