**FIGURE 1.5.5. Operational Approval To Operators To Conduct Operations
In Oceanic Airspace Where Required Navigation Performance 10 (RNP‑10) Is
Required.**

**INTRODUCTION**

This paragraph contains guidance for Aviation Safety Inspectors (ASI) on
the steps to be taken to issue operational approval to operators to
conduct operations in oceanic airspace where Required Navigation
Performance 10 (RNP‑10) is required.

**1. BACKGROUND.**

A.        States and operators are implementing RNP as part of a
worldwide ICAO effort to implement the Future Air Navigation Systems
(FANS), Communication/Navigation/ Surveillance (CNS), and Air Traffic
Management (ATM) concepts. To support this effort, in 1998, the Pacific
oceanic planning groups began a phased implementation of 50 nautical
mile (NM) lateral separation in Pacific oceanic airspace. In addition,
50NM longitudinal separation has also been introduced for aircraft that
are equipped with the required communications, navigation and
surveillance equipment. In accordance with (IAW) ICAO Document 7030,
aircraft/operators that operate on routes where these separation
standards are applied must be approved by the State of Operator or
Registry, as appropriate, as capable of navigating to RNP‑10 for the
entire route on which RNP‑10 is required.

> **NOTE: This navigation performance requirement is similar to Minimum
> Navigation Performance Specification (MNPS) over the Atlantic which is
> equivalent to RNP‑12.**

B.         The first oceanic airspace where RNP‑10 and 50 NM lateral
separation were implemented was the NOPAC Route System. Implementation
in additional Pacific oceanic areas proceeded over the next two years.

C.         Other separation standards require different RNP types (e.g.,
30 NM lateral separation requires RNP‑4). The implementation of more
stringent RNP and other CNS capabilities is part of an ICAO coordinated
effort to introduce separation standards that will enable more efficient
air traffic management while maintaining acceptable levels of safety.
Benefits to users are increased availability of fuel/time efficient
altitudes, routes and enhanced airspace capacity, and controller
flexibility.

**2. POLICY.**

A.        RNP Documentation. Federal Aviation Administration (FAA) FAA
Order 8400.12, Required Navigational Performance 10 (RNP‑10) Operational
Approval, is a guide to RNP‑10 aircraft and operator approval in any
airspace where RNP‑10 navigation criteria is required. The FAA has
determined that FAA Order 8400.12, as amended, provides acceptable
criteria and processes for an operator to obtain authority to operate
specific aircraft/navigation systems in areas or on routes where RNP‑10
is required.

B.         Internet Access. Communications, Navigation and Surveillance
requirements, policy and guidance for operation in oceanic airspace can
be found on the Oceanic Operations Standards Group website
(www/ats/ato/130.htm). AFS‑400 is coordinating with their air traffic
counterparts to expand this website as new CNS requirements are
introduced in oceanic areas such as the Pacific.

C.         General Requirements. Operator applications for RNP‑10
approval must be evaluated IAW FAA Order 8400.12, as amended and any
additional criteria specified in this appendix. If an operator requests
to deviate from the practices and procedures provided in FAA Order
8400.12, the inspector should forward a request for assistance through
the regional Flight Standards division to AFS‑400.

D.        Standard Operations Specifications. Title 14 of the Code of
Federal Regulations (14 CFR) part 121, 125, and 135 certificate holders
areapproved for RNP‑10 by the issuance of standard OpSpec paragraphs:

(1)        OpSpec paragraph A002, Definitions and Abbreviations.

(2)        B036, Class II Navigation Using Multiple Long‑Range
Navigation Systems (LRNS) and

(3)        If applicable, B037, Operations in Central East Pacific (CEP)
Airspace.

(4)        If applicable, B038, Operations in North Pacific (NOPAC)
Airspace

E.         Title 14 CFR part 91, Operator Letter of Authorization (LOA).
Part 91 operators will be approved through the issuance of automated LOA
B036, Operations in RNP Airspace or, for short‑term operations, LOA
D098, Flight in Special Areas of Operation For Short‑Term Operations.
LOA's should be issued using the guidance in this handbook and FAA Order
8400.12, as amended.

**3. ACTION**. The principal inspectors should inform their certificate
holders that this appendix contains the approval process for RNP‑10
authorization. The steps in this process should be followed when an
operator seeks authority to operate an airplane type/long range
navigation system (LRNS) combination in Class II navigation areas where
RNP‑10 is applied and the operator has not previously received RNP‑10
approval for that specific airplane type/LRNS combination. Normally, if
an operator has received initial Class II navigation/RNP‑10 approval for
a specific airplane type/LRNS combination, that operator should not be
required to re‑apply for approval to conduct Class II navigation/RNP‑10
operations on additional routes or areas.

A.        FAA Order 8400.12 Index, Appendix 8. The POI and the
certificate holders may find it easier to use FAA Order 8400.12 if they
are aware that Appendix 8 is an index to the Order. The certificate
holder should be made aware that references to the appropriate
subparagraphs and sections of FAA Order 8400.12 are indicated in
subparagraphs below:

B.         Application, FAA Order 8400.12, paragraph 9. Paragraph 9
provides guidance on the content of an operator's RNP‑10 application.
The application should contain the items listed in subparagraphs below.
Subparagraphs provide additional detail on application items.

(1)        Aircraft/Navigation System Group. Airworthiness documents
that establish the proposed aircraft/navigation system group, its RNP‑10
approval status, and a list of airframes in that group.

(2)        Time Limit For INS or IRU Only Equipped Aircraft . Approved
or requested RNP‑10 time limit for aircraft for which Inertial
Navigation Systems (INS) or Inertial Reference Units (IRU) are the only
source of Long Range Navigation (LRN).

(3)        RNP‑10 Area of Operations. Documentation establishing the
RNP‑10 area of operations or routes for which the specific
aircraft/navigation system is eligible.

(4)        Operating Practices and Procedures. Documentation that the
operator has adopted operating practices and procedures related to
RNP‑10 operations.

(5)        Pilot and Dispatcher Knowledge. Documentation showing that
the pilot and, if applicable, dispatcher knowledge of RNP‑10 operating
practices and procedures will be adequate.

(6)        Airworthiness Practices. Documentation that appropriate
maintenance practices and procedures have been adopted.

(7)        Minimum Equipment List (MEL) updates, if applicable.

(8)        Operating History. Operating history that identifies past
problems and incidents, if any, and actions taken to correct the
situation.

(9)        Removal of RNP‑10 Operating Authority. Awareness of the
necessity to follow up action after navigation error reports, and the
potential for removal of RNP‑10 operating authority.

C.         Aircraft Groups & Eligibility. Aircraft Groups (Fleets of
Aircraft), paragraph 11 and Determining Aircraft Eligibility, paragraph
12 of FAA Order 8400.12.

(1)        Aircraft Groups (Fleets of Aircraft), paragraph 11, of FAA
Order 8400.12. In accordance with paragraph 11, the operator must show
the aircraft/navigation system groups that will be presented for
approval of RNP‑10 operations and provide a list of airframes that are
determined to be in the specific aircraft/navigation system groups to be
evaluated.

(2)        Determining Aircraft Eligibility, paragraph 12a of FAA Order
8400.12. For aircraft navigation systems which have been approved by an
aircraft certification authority to RNP‑10 or better, the operator must
provide appropriate sections of the Airplane Flight Manual (AFM) that
address RNP, including any associated time limits for INS and IRU
navigation systems.

(3)        Aircraft Equipped with Global Positioning Systems (GPS)
Approved to Primary Means of Navigation Standards, FAA Order 8400.12,
paragraph 12b(4). For aircraft equipped with GPS, where such GPS units
are the only systems for long range navigation, the operator must show
that it is approved IAW paragraph 12b(4). An RNP‑10 time limit is not
applicable.

(4)        Multisensor Systems Integrating GPS (with GPS Integrity
Provided by Receiver Autonomous Integrity Monitoring (RAIM) or Aircraft
Autonomous Integrity Monitoring (AAIM), FAA Order 8400.12, paragraph
12b(5). For multisensor systems incorporating GPS, the operator must
show that systems are approved and operated IAW paragraph 12b(5). An
RNP‑10 time limit is not applicable.

(5)        GPS Equipage In Combination With Another Approved LRNS (e.g.,
INS or IRU); Reference Advisory Circular (AC) 90‑94, Guidelines for
Using GPS Equipment for IFR En Route & Terminal Operations & for
Nonprecision Instrument Approaches, and AC 20‑138, Airworthiness
Approval of Global Positioning System (GPS) Navigation Equipment for Use
as a VFR and IFR Supplemental Navigation System. The operator must show
that aircraft equipped with GPS and one or more approved LRNS are
installed and operated IAW AC 90‑94, and AC 20‑138. An RNP‑10 time limit
is not applicable.

(6)        Equipage Where INS or IRU's Provide the Only Means of Long
Range Navigation, Paragraph 12b(1), (2), and (3) of FAA Order 8400.12.
The operator must show that INS or IRU installation is approved IAW
paragraph 12b(1), (2) or (3). Unless the operator takes action to extend
the approved navigation system time limit and/or plans to update the
system en route, a baseline RNP‑10 time limit of 6.2 hours, starting at
the time the system was placed in navigation mode, is applicable. See
paragraph 4E, extending navigation system time limit and paragraph
4D(1)© (of this appendix), en route updating.

(7)        Aircraft Eligibility Through Data Collection, (Eligibility
Group 3), paragraph 12c of FAA Order 8400.12. For navigation systems not
approved under existing criteria, the operator may demonstrate RNP‑10
eligibility through data collection IAW paragraph 12c using the
processes detailed in FAA Order 8400.12, appendices 1 or 6.

D.        Route Evaluation. Route Evaluation for RNP‑10 Time Limits for
Aircraft Equipped with only INSs or IRUs, FAA Order 8400.12, paragraph
15e. If restrictions (e.g., INS RNP‑10 time limit) apply to navigation
systems, the operator must show the routes or areas where it is eligible
to operate. In accordance with paragraph 15e, the operator can conduct a
one‑time evaluation of eligibility to fly in an RNP‑10 area of
operations or on specific RNP‑10 routes or may elect to evaluate on a
per‑flight basis.

(1)        One‑Time Evaluation. For one‑time evaluation of a specific
RNP‑10 area or track system, ASI's should expect the operator to
accomplish the following:

(a)        Calculate the longest distance from either departure airports
or en route update points (if applicable) to the point at which the
aircraft will begin to navigate by reference to VHF Omnidirectional
Range Station (VOR), Distance Measuring Equipment (DME), Nondirectional
Beacon (NDB),or comes under air traffic control (ATC) radar
surveillance.

(b)        As detailed in paragraph 15e, using 75% probability wind
component, convert this distance to en route time.

(c)        As detailed in paragraph 12e, if navigation systems are to be
updated en route, adjust the base line RNP‑10 time limit approved for
the specific operator navigation system to account for update accuracy.

(i)         Subtract .3 hours from the baseline for DME/DME.

(ii)        Subtract .5 hours from the baseline for VOR/DME.

(iii)       Subtract 1 hour from the baseline for manual update.

(d)        Compare calculated en route time to the navigation system
RNP‑10 time limit (adjusted for en route update, if applicable) to
determine if the airplane is eligible for the operation.

(e)        If the aircraft navigation system is found eligible for
operation on the specific routes evaluated, then the RNP‑10 area of
operations or routes on which RNP‑10 operations can be conducted are
established. If the aircraft navigation system is not found eligible for
operation on all routes evaluated, then the operator will need to
designate routes for which it is eligible or take action to gain
approval for an extended RNP‑10 time limit. See paragraph 4E of this
appendix.

(2)        Calculation of Time Limit for Each Specific Flight, FAA Order
8400.12A, Paragraph 15e(6). For a per‑flight evaluation of eligibility
to fly a specific RNP‑10 route, follow the steps shown in paragraph
4D(1) of this appendix using flight plan winds to determine en route
time. If the RNP‑10 time limit is exceeded, the flight must be re‑routed
or delayed.

E.         Time Limit Extension. Obtaining an RNP‑10 Time Limit
Extension for INS‑ or IRU‑Equipped Aircraft, paragraph 12d of FAA Order
8400.12. Operator can show eligibility for an extended time limit by:

(1)        Obtaining approval from an appropriate Aircraft Certification
Office, or

(2)        Conducting operational data collection using the processes
established in appendices 1 or 6 of FAA Order 8400.12A.

F.         Maintenance Requirements. Continuing Airworthiness
(Maintenance Requirements), paragraph 14 of FAA Order 8400.12. The
certificate holder must provide documentation that appropriate
maintenance practices and procedures have been adopted.

G.         MEL Requirements. MEL Updates (if applicable), paragraph 13
of FAA Order 8400.12. In accordance with paragraph 13, if applicable,
the operator must revise the MEL to address any new operating
requirements.

H.        Operations Programs.

(1)        Operations Manuals and Checklists, FAA Order 8400.12,
paragraphs 9a(5), 12f, 12g, 15, appendices 4 and 7 (if applicable).

(a)        Part 121, 125 and 135 certificate holders must provide
revisions to manuals and checklists to show the adoption of the RNP‑10
operating practices and procedures contained in the reference paragraphs
and sections listed in paragraph 4h(1) of this appendix.

(b)        If applicable, part 91 operators should show appropriate
sections of the AFM relating to RNP‑10 aircraft/navigation system
eligibility.

(2)        Operations Training Programs and Operating Practices and
Procedures, FAA Order 8400.12, paragraphs 9a(4), 12f, 12g, 15, and
appendices 4 and 7 (if applicable).

(a)        Part 121 and 135 certificate holders should show that
training programs have been updated to include the practices in FAA
Order 8400.12, paragraphs 12f and/or 12g (if applicable), paragraph 15,
appendices 4 and 7 (if applicable). Part 125 initial and recurrent pilot
testing programs should be updated with applicable information from
these paragraphs.

(b)        In accordance with FAA Order 8400.12, appendix 4, paragraph
5b, Part 91 operators must show during the application process that
pilot knowledge of paragraphs 12f and 12g (if applicable), paragraph 15,
appendices 4 and 7 (if applicable), will be adequate. Appendix 4,
paragraph 5b contains options for part 91 operators to fulfill this
requirement.

I.          Deviation to RNP‑10 Requirements. The administrator may
authorize a certificate holder to deviate from the RNP‑10 requirements
in subparagraph c of OpSpec B036 for a specific flight in designated
RNP‑10 airspace if the Air Traffic Service provider determines that the
airplane may be provided appropriate separation and the flight will not
interfere with, or impose a burden on other operators. For operations
under such authority, the certificate holder shall not take off for
flight in designated RNP‑10 airspace, unless the following requirements
of subparagraphs b and d of B036 are met:

(1)        If fuel planning is predicated on en route climb to flight
levels where RNP‑10 is normally required, an appropriate request must be
coordinated with the Air Traffic Service provider in advance of the
flight.

(2)        The appropriate information blocks on the ICAO flight plan
filed with the Air Traffic Service provider show that the airplane
and/or certificate holder is not approved for RNP‑10 as specified in the
certificate holders operations specifications paragraph B036, Class II
Navigation Using Long Range Navigation Systems.

(3)        For these flights either of the following conditions must be
met:

(a)        At least one of the navigation system configurations listed
below must be installed and operational:

(b)        At least two independent INS.

(c)        At least two flight management system/navigation sensor
combinations (or equivalent).

(d)        At least two independent approved GPS navigation systems
acceptable for primary means of Class II navigation in oceanic and
remote areas.

(e)        At least two approved independent LRNS from the list below:

(i)         Inertial navigation system.

(ii)        Flight management system/navigation sensor combination (or
equivalent).

(iii)       GPS navigation system approved for Class II navigation in
oceanic and remote areas.

J.          Application Evaluation. Evaluation of Application,
Conditions for Removal of Authorization, and Error Reports, FAA Order
8400.12, paragraph 9b. The operator should indicate awareness of the
provisions of paragraph 9b for operator follow‑up action on reported
navigation errors and of the potential to remove RNP‑10 operating
authority.

K.        Validation. Validation Tests and Validation Flights for part
121 and 135 operators, reference FAA Order 8400.10, volume III, chapter
9.

(1)        General. The following is intended to provide broad guidance
for establishing requirements for validation tests and/or validation
flights. The POI should consider each application on its own merit and
IAW 8400.10, volume III, chapter 9 consult with the regional Flight
Standards division, as necessary.

(2)        Program/Document Evaluation. Validation testing requires that
ASI's evaluate operator programs and documents IAW the guidance in this
figure.

(3)        Establishing the Necessity for Validation Flights. The
following is provided as guidance for ASI's to consider in determining
whether or not validation flights are required.

(a)        Operators with previous Class II navigation experience with
the same navigation equipment as that being proposed for RNP‑10
approval. Evaluation of the applicant's programs and documents should
normally suffice. A validation flight should not normally be required.

(b)        Operators with previous Class II navigation experience
navigating with an LRNS other than that being proposed for RNP‑10
approval. Evaluation of the applicant's programs and documents is
required. A validation flight should normally be required. If conducted
in Class I airspace, the validation flight may be conducted in revenue
service. If conducted in Class II airspace, it must be non‑revenue with
the exception that cargo may be carried.

(c)        Operators with no previous Class II navigation experience
proposing to operate where RNP‑10 is required. Evaluation of the
operator's programs and documents is required. A validation flight
should be required and should be conducted in Class II airspace. It
should be a non‑revenue flight with the exception that cargo may be
carried.

(4)        Conditions for Validation Flights.

(a)        At least one flight should be observed by an FAA ASI.

(b)        A demonstration of any required dispatch procedures must be
conducted for routes or areas where RNP‑10 is required.

(c)        The flight(s) should be of adequate duration for the pilots
to demonstrate knowledge of dispatch requirements, capability to
navigate with the system, and to perform the normal and non‑normal
procedures.

L.         OPERATIONS SPECIFICATIONS ENTRIES. Sample standard OpSpec
paragraphs for A002, B036, B038 are provided.

(1)        OpSpec paragraph A002, Definitions and Abbreviations,

(2)        OpSpec paragraph B038, Operations in North Pacific (NOPAC)
Airspace,

(3)        OpSpec paragraph B036

(a)        Required Navigation Performance Type Block. This is the RNP
type for which the specific navigation system has been approved. Entry
options for this block are:

(i)         RNP‑X. Example: RNP‑4, RNP‑10, etc.

(ii)        Per AFM. Example: For B747‑400 equipped with FANS‑1 package,
AFM establishes RNP Type availability based on GPS satellite
availability at dispatch.

(iii)       NA (not applicable). Example: aircraft not used for RNP
operations.

(b)        RNP Time Limit Block. This is the RNP‑10 time, if applicable,
for which the navigation system has been approved. Entry options are:

(i)         X Hours. Example: 6.3 hours, 10.0 hours.

(ii)        UNL (Unlimited). Example: Primary means GPS, approved
multisensor system that incorporate GPS.

(iii)       NA (not applicable). Example: aircraft/navigation system not
used in RNP operations.

**5.         PROGRAM TRACKING AND REPORTING SYSTEM (PTRS).** PTRS
entries shall be made. The operations activity code number shall be
1442; the avionics activity code shall be 5434, and the "national use"
field entry shall be "RNP‑10" followed by three spaces.