RNP SPECIFICATIONS
L1 RNP 4


O1 Basic RNP 1 all permitted sensors

O2 Basic RNP 1 GNSS
O3 Basic RNP 1 DME/DME

O4 Basic RNP 1 DME/DME/IRU


S1 RNP APCH

S2 RNP APCH with BARO-VNAV


T1 RNP AR APCH with RF
(special authorization required)

T2 RNP AR APCH without RF
(special authorization required)

NOTE-
Combinations of alphanumeric characters not indicated
above are reserved.

(d) NAV/ Significant data related to naviga-
tion equipment, other than as specified in PBN/.
(1) When Performance Based Navigation
Capability has been filed in PBN/, if PBN routing is
desired for only some segment(s) of the flight then
that information can be conveyed by inserting the
character "Z" in Item 10 and "NAV/RNV" in field 18
followed by the appropriate RNAV accuracy value(s)
per the following:
[a] To be assigned an RNAV 1 SID,
insert the characters "D1".

[b] To be assigned an RNAV 1 STAR,

insert the characters "A1".

[c] To be assigned en route extensions
and/or RNAV PTP, insert the characters "E2".
[d] To prevent assignment of an RNAV
route or procedure, insert a numeric value of "0" for
the segment of the flight. Alternatively, you may
simply remove the segment of the flight indicator and
numeric value from the character string.

EXAMPLE-
1. NAV/RNVD1 or NAV/RNVD1E0A0 (Same meaning)

2. NAV/RNVA1 or NAV/RNVD0E0A1 (Same meaning)
3. NAV/RNVE2 or NAV/RNVD0E2A0 (Same meaning)
4. NAV/RNVD1A1 or NAV/RNVD1E0A1 (Same meaning)

5. NAV/RNVD1E2A1
NOTE-
1. Route assignments are predicated on NAV/ data over
PBN/ data in ERAS.

2. Aircraft certification requirements for RNAV opera-
tions within U.S. airspace are defined in AC 90-45A,
Approval of Area Navigation Systems for Use in the U.S.
National Airspace System, and AC 90-100A, U.S.

Terminal and En Route Area Navigation (RNAV)
Operations, as amended.

(2) Operators should file their maximum

capabilities in order to qualify for the most advanced
procedures.

(e) COM/ Indicate communications capabil-
ities not specified in Item 10a, when requested by an

air navigation service provider.
(f) DAT/ Indicate data applications or capab-
ilities not specified in Item 10a, when requested by an
Air Navigation Service Provider.

(g) SUR/ Indicate surveillance capabilities
not specified in Item 10b, when requested by an Air
Navigation Service Provider. If ADS-B capability
filed in Item 10 is compliant with RTCA DO-260B,
include the item "260B" in SUR/. If ADS-B
capability filed in Item 10 is compliant with RTCA
DO-282B, include the item "282B" in SUR/.
EXAMPLE-
1. SUR/260B
2. SUR/260B 282B
(h) DEP/ Insert the non-ICAO identifier, or
fix/radial/distance from navaid, or latitude/longitude,
if ZZZZ is inserted in Item 13. Optionally, append the

name of the departure point.

EXAMPLE-
1. DEP/T23 ALBANY MUNI
2. DEP/T23
3. DEP/UKW197011 TICK HOLLR RANCH
4. DEP/4620N07805W

(i) DEST/ Insert the non-ICAO identifier, or
fix/radial/distance from navaid, or latitude/longitude,
if ZZZZ is inserted in Item 16. Optionally, append the
name of the destination point.

EXAMPLE-
1. DEST/T23 ALBANY MUNI
2. DEST/PIE335033 LEXI DUNES
3. DEST/4620N07805W