Radar Vectors
Advisory Circular Current Issued Mar 7, 2016 AFS-400 129 pages Copy saved Nov 18, 2026

AC 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

This advisory circular (AC) provides guidance for operators to conduct Required Navigation Performance (RNP) operations in the United States, in oceanic and remote continental airspace, and in foreign countries which adopt International Civil Aviation Organization (ICAO) standards for RNP operations. Guidance is provided for the following: • Required Navigation Performance Approach (RNP APCH) procedures; • Barometric vertical navigation (baro-VNAV); • RNP 1 (terminal) operations; • RNP 0.3 (rotorcraft) operations; • RNP 2 domestic, offshore, oceanic, and remote continental operations; • RNP 4 oceanic and remote continental operations; • RNP 10 (Area Navigation (RNAV) 10) oceanic and remote continental operations; • Advanced Required Navigation Performance (A-RNP), and • Additional Capabilities. This AC does not apply to those approaches which require unique authorization (Required Navigation Performance Authorization Required (RNP AR), as described in AC 90 101( ), Approval Guidance for RNP Procedures with AR, nor does it address instrument approach procedures (IAP) using localizer performance with vertical guidance (LPV) or localizer performance without vertical guidance (LP), which are addressed in AC 90-107( ), Guidance for Localizer Performance with Vertical Guidance and Localizer Performance without Vertical Guidance Approach Operations in the U.S. National Airspace System.

Official source ↗ Open PDF

AC_90-105A_FAA_Web

U.S. Department of Transportation Federal Aviation Administration

Advisory Circular

Subject: Approval Guidance for RNP

Operations and Barometric Vertical Navigation in the U.S. National Airspace System and in Oceanic and Remote Continental Airspace

Date: 3/7/16 AC No: 90-105A Initiated by: AFS-400 Change:

This advisory circular (AC) provides guidance for operators to conduct Required Navigation Performance (RNP) operations in the United States, in oceanic and remote continental airspace, and in foreign countries which adopt International Civil Aviation Organization (ICAO) standards for RNP operations. Guidance is provided for the following:

• Required Navigation Performance Approach (RNP APCH) procedures;

• Barometric vertical navigation (baro-VNAV);

• RNP 1 (terminal) operations;

• RNP 0.3 (rotorcraft) operations;

• RNP 2 domestic, offshore, oceanic, and remote continental operations;

• RNP 4 oceanic and remote continental operations;

• RNP 10 (Area Navigation (RNAV) 10) oceanic and remote continental operations;

• Advanced Required Navigation Performance (A-RNP); and

• Additional Capabilities.

This AC does not apply to those approaches which require unique authorization (Required Navigation Performance Authorization Required (RNP AR), as described in AC 90-101( ), Approval Guidance for RNP Procedures with AR, nor does it address instrument approach procedures (IAP) using localizer performance with vertical guidance (LPV) or localizer performance without vertical guidance (LP), which are addressed in AC 90-107( ), Guidance for Localizer Performance with Vertical Guidance and Localizer Performance without Vertical Guidance Approach Operations in the U.S. National Airspace System.

John Barbagallo Deputy Director, Flight Standards Service

ii

CONTENTS Paragraph Page

Chapter 1. General Information … 1-1

1.1 Purpose … 1-1

1.2 Alternative Method … 1-2

1.3 AC Feedback Form … 1-2

Chapter 2. Applicability … 2-1

2.1 Audience … 2-1

2.2 Approach Guidance Not Applicable to This AC … 2-1

2.3 Terms … 2-1

2.3.1 Major and Minor Failures … 2-1

2.4 References … 2-1

2.5 Aircraft Eligibility and Aircraft Modification … 2-2

Chapter 3. Documentation … 3-1

3.1 Cancellation … 3-1

3.2 FAA ACs and Orders … 3-1

3.3 Related Regulations Title 14 of the Code of Federal Regulations (14 CFR) … 3-2

3.4 FAA Technical Standard Orders (TSO) … 3-2

3.5 RTCA Documents … 3-2

3.6 Other Documents … 3-3

Chapter 4. General Information … 4-1

4.1 Performance-Based Navigation (PBN) Concept … 4-1

4.1.1 Components … 4-1

4.1.2 Lateral Performance … 4-2

4.1.3 Vertical Performance … 4-2

4.1.4 Onboard Performance Monitoring and Alerting … 4-2

4.2 Procedures and Routes … 4-2

4.3 Navigation Error Components/Definitions … 4-3

4.3.1 Flight Technical Error (FTE) or Path Steering Error (PSE) … 4-3

4.3.2 Path Definition Error (PDE) … 4-4

4.3.3 Navigation System Error (NSE) or Position Estimation Error (PEE) … 4-4

iii

4.3.4 Total System Error (TSE) … 4-4

4.3.5 Position Estimation Error (PEE) or Navigation System Error (NSE) … 4-4

Chapter 5. Applications of Required Navigation Performance (RNP) Operations … 5-1

5.1 Overview … 5-1

Chapter 6. Operational Guidance for Required Navigation Performance (RNP) Operations … 6-1

6.1 General … 6-1

6.2 Centerline … 6-1

6.3 RNP En Route, RNP Terminal, and RNP APCH Operations … 6-1

6.4 RNP Operational Transitions … 6-1

6.4.1 Transitions to Instrument Landing System (ILS), Ground Based Augmentation System (GBAS) Landing System (GLS), Localizer Performance with Vertical Guidance (LPV) or Conventional Approach Procedures … 6-1

6.5 Oceanic/Remote Continental Airspace and Offshore Airspace … 6-2

6.5.1 Airspace Distinction … 6-2

Chapter 7. Operational Approval Process … 7-1

7.1 Part 91 Operators … 7-1

7.2 Operational Authorization … 7-1

7.3 Parts 91K, 121, 125, 129, and 135 Operators … 7-1

7.4 Preapplication Meeting … 7-2

7.5 Multiple OpSpecs/MSpecs/LOAs … 7-2

7.5.1 Application … 7-2

7.5.2 Amendments … 7-2

Chapter 8. Operator Responsibilities … 8-1

8.1 Operational Manuals and Checklists … 8-1

8.2 Training Documentation … 8-1

8.2.1 Part 91 Operator Training … 8-1

8.2.2 Parts 91K, 121, 125, and 135 Operator Training … 8-1

8.3 Minimum Equipment List (MEL) Considerations … 8-1

8.4 Pilot Knowledge/Training … 8-1

8.4.1 Flightcrew Training … 8-1

8.4.2 RNP Authorization Requests … 8-1

iv

8.4.3 Pilot Knowledge … 8-2

8.4.4 Pilot Knowledge and Actions … 8-3

8.5 Operation, Procedure, or Route Selection … 8-4

Chapter 9. Flight Planning … 9-1

9.1 Required Navigation Performance (RNP) Flight Planning Requirements … 9-1

9.1.1 RNP 2, RNP 4, and RNP 10 … 9-1

9.2 Notices to Airmen (NOTAM) … 9-1

9.3 GPS Performance Prediction … 9-1

9.3.1 Equipment in Accordance with TSO-C129 or TSO-C196 … 9-1

9.3.2 Prediction Methods … 9-2

9.3.3 Prediction Model Parameters … 9-2

9.3.4 Flight Planning Guidance … 9-2

9.3.5 Resolving Predicted Outages in Performance … 9-3

9.4 Distance Measuring Equipment (DME) Flight Planning Requirements … 9-3

9.5 Contingency Planning for Alternate Airport … 9-3

9.5.1 Alternate Airport Considerations … 9-3

Chapter 10. Database Integrity … 10-1

10.1 Database Suppliers … 10-1

10.2 Navigation Data Requirements … 10-1

10.3 Terminal and En Route Requirements … 10-1

10.4 Database Validity … 10-1

10.5 Navigation Data Validation Program … 10-1

10.6 Data Process for Part 91 Operators … 10-1

10.7 Data Process for Parts 91K, 121, 125, 129, and 135 … 10-2

Chapter 11. Aircraft and System Requirements … 11-1

11.1 References … 11-1

Chapter 12. Bundling Concept … 12-1

12.1 Performance-based Navigation (PBN) Authorization … 12-1

12.2 Visual of Bundling Options … 12-1

12.3 Approach Phase Composition … 12-1

12.4 Credit for Existing RNP AR Approvals … 12-1

v

12.5 RNP 2 Areas of Operation … 12-1

12.6 Terminal and En Route Phases of Flight … 12-1

12.7 Oceanic/Remote Continental RNP 2 Authorization … 12-2

12.8 Advanced Required Navigation Performance (A-RNP) … 12-2

Appendix A. Qualification Criteria for Required Navigation Performance Approach

(RNP APCH) Operations … A-1

Appendix B. Use of Barometric Vertical Navigation (baro-VNAV) for Required

Navigation Performance Approach (RNP APCH) Operations … B-1

Appendix C. Qualification Criteria for Required Navigation Performance (RNP) 1

(Terminal) Operations … C-1

Appendix D. Qualification Criteria for Required Navigation Performance (RNP) 0.3

(Rotorcraft) Operations … D-1

Appendix E. Qualification Criteria for Required Navigation Performance (RNP) 2

Domestic, Offshore, Oceanic, and Remote Continental Operations … E-1

Appendix F. Qualification Criteria for Required Navigation Performance (RNP) 4

Oceanic and Remote Continental Operations … F-1

Appendix G. Qualification Criteria for Required Navigation Performance (RNP) 10

Oceanic and Remote Continental Operations … G-1

Appendix H. Advanced Required Navigation Performance (A-RNP) … H-1

Appendix I. Additional Capabilities … I-1

Appendix J. Administrative Information … J-1

List of Figures

Figure 4-1. Performance-Based Navigation Concept … 4-1

Figure 4-2. Total System Error (TSE) … 4-3

Figure 12-1. Bundling Options … 12-3

List of Tables

Table 5-1. Applications of RNP Operations … 5-1

Table H-1. RNP Functions … H-2

Table J-1. Acronyms … J-6

CHAPTER 1. GENERAL INFORMATION › 1.1 Purpose.

CHAPTER 1. GENERAL INFORMATION

1.1 Purpose. This advisory circular (AC) provides aircraft eligibility and operational guidance for operators to conduct Required Navigation Performance (RNP) operations in the United States, in oceanic and remote continental airspace, and in foreign countries which adopt International Civil Aviation Organization (ICAO) standards for RNP operations. The contents of this document do not have the force and effect of law and are not meant to bind the public in any way. This document is intended only to provide clarity to the public regarding existing requirements under the law or agency policies. Guidance is provided for the following:

• Required Navigation Performance Approach (RNP APCH) Procedures: Appendix A, Qualification Criteria for Required Navigation Performance Approach (RNP APCH) Operations.

• RNP APCH Procedures to LNAV/VNAV Approach Minimums: Appendix B, Use of Barometric Vertical Navigation (baro-VNAV) for Required Navigation Performance Approach (RNP APCH) Operations.

• RNP 1 Arrival and Departure Procedures: Appendix C, Qualification Criteria for Required Navigation Performance (RNP) 1 (Terminal) Operations.

• RNP 0.3 En Route and Terminal Operations for Rotorcraft: Appendix D, Qualification Criteria for Required Navigation Performance (RNP) 0.3 (Rotorcraft) Operations.

• RNP 2 En Route Operations: Appendix E, Qualification Criteria for Required Navigation Performance (RNP) 2 Domestic, Offshore, Oceanic, and Remote Continental Operations.

• RNP 4 Operations in Oceanic and Remote Continental Airspace: Appendix F, Qualification Criteria for Required Navigation Performance (RNP) 4 Oceanic and Remote Continental Operations.

• RNP 10 Operations in Oceanic and Remote Continental Airspace: Appendix G, Qualification Criteria for Required Navigation Performance (RNP) 10 Oceanic and Remote Continental Operations.

Note: Area Navigation (RNAV) 10 is designated and authorized as RNP 10. This document uses the designation of RNP 10.

• Advanced RNP En Route, Terminal, or Approach Operations: Appendix H, Advanced Required Navigation Performance (A-RNP).

• Additional Capabilities: Appendix I.

Note: The contents of this AC reflect and harmonize with ICAO Doc 9613, fourth edition, Performance-Based Navigation (PBN) Manual (see Table 5-1).

1.2 Alternative Method. In lieu of following the guidance in this AC without deviation, operators may elect to follow an alternative method, provided the alternative method is found to be acceptable by the Federal Aviation Administration (FAA).

CHAPTER 1. GENERAL INFORMATION › 1.3 AC Feedback Form.

1.3 AC Feedback Form. For your convenience, the AC Feedback Form is the last page of this AC. Note any deficiencies found, clarifications needed, or suggested improvements regarding the contents of this AC on the Feedback Form.

CHAPTER 2. APPLICABILITY

2.1 Audience. The guidance contained in this advisory circular (AC) applies to all operators conducting Required Navigation Performance (RNP) operations under Title 14 of the Code of Federal Regulations (14 CFR) parts 91, 91 subpart K (part 91K), 121, 125, 129, and 135 within the U.S. National Airspace System (NAS). It also applies to all U.S. operators conducting RNP operations offshore as defined by the Federal Aviation Administration (FAA) Order JO 7400.11( ), Airspace Designations and Reporting Points; and oceanic and remote continental airspace. This AC also applies to all U.S. operators conducting RNP operations in foreign airspace, where the foreign authority has implemented RNP in accordance with International Civil Aviation Organization (ICAO) Doc 9613.

CHAPTER 2. APPLICABILITY › 2.4 References.

2.2 Approach Guidance Not Applicable to This AC. This AC does not apply to Required Navigation Performance Authorization Required (RNP AR) covered by AC 90-101( ), Approval Guidance for RNP Procedures with AR. Guidance for operators to conduct 14 CFR part 97 instrument flight rules (IFR), Area Navigation (RNAV) Global Positioning System (GPS), instrument approach procedures (IAP) with localizer performance with vertical guidance (LPV), and localizer performance without vertical guidance (LP) lines of minima using the wide area augmentation system (WAAS) is covered in AC 90-107( ), Guidance for Localizer Performance with Vertical Guidance and Localizer Performance without Vertical Guidance Approach Operations in the U.S. National Airspace System.

2.3 Terms. Mandatory terms used in this AC such as “must” are used only in the sense of ensuring applicability of these particular methods of compliance when the acceptable means of compliance (AMC) described herein are used. This AC does not change, add, or delete regulatory requirements or authorize deviations from regulatory requirements.

2.3.1 Major and Minor Failures. The terms of major and minor failure conditions are referenced from ICAO Doc 9613. Refer to AC 20-138( ), Airworthiness Approval of Positioning and Navigation Systems, for specific failure conditions and system performance requirements.

2.4 References. Most of the document references in this AC are the most current version as designated by parentheses ( ) placed at the end of the document title. In some cases, the actual version will be indicated by a letter. Documents without ( ) or a letter after the end of the document title designates all versions apply. As a convenience, most references are hyperlinked to the appropriate website containing the most current document. To navigate to the most current AC, Order, or Technical Standard Order (TSO), use the following links:

• Advisory Circulars,

• FAA Order, and

• Technical Standard Orders.

CHAPTER 2. APPLICABILITY › 2.5 Aircraft Eligibility and Aircraft Modification.

2.5 Aircraft Eligibility and Aircraft Modification. Aircraft eligibility provided in this AC provides guidance for an operator to determine if their aircraft is capable of conducting these operations. This guidance is not appropriate for conducting any modifications to aircraft type design. Detailed and complete airworthiness guidance is available in AC 20-138( ) and should be used by all airworthiness applicants.

CHAPTER 3. DOCUMENTATION › 3.2 FAA ACs and Orders.

CHAPTER 3. DOCUMENTATION

3.1 Cancellation. Advisory Circular (AC) 90-105, Approval Guidance for RNP Operations and Barometric Vertical Navigation in the U.S. National Airspace System is cancelled. AC 90-94, Guidelines for Using Global Positioning System Equipment for IFR En Route and Terminal Operations and for Nonprecision Instrument Approaches in the U.S. National Airspace System (dated 12/14/1994) and AC 90-97, Use of Barometric Vertical Navigation (VNAV) for Instrument Approach Operations Using Decision Altitude (dated 10/19/2000) were cancelled with the publication of AC 90-105 (dated 1/23/2009).

Note: Guidance from Federal Aviation Administration (FAA) Order 8400.33, Procedures for Obtaining Authorization for Required Navigation Performance 4 (RNP-4) Oceanic and Remote Area Operations, and FAA Order 8400.12C, Required Navigation Performance 10 (RNP 10) Operational Authorization, are included in this AC.

3.2 FAA ACs and Orders. Please refer to the links provided in the bullets of paragraph 2.4 to obtain the latest ACs and/or orders.

• AC 20-138( ), Airworthiness Approval of Positioning and Navigation Systems.

• AC 20-153( ), Acceptance of Aeronautical Data Processes and Associated Databases.

• AC 23.1309-1( ), System Safety Analysis and Assessment for Part 23 Airplanes.

• AC 25.1309-1( ), System Design and Analysis.

• AC 25-15( ), Approval of Flight Management Systems in Transport Category Airplanes.

• AC 90-100( ), U.S. Terminal and En Route Area Navigation (RNAV) Operations.

• AC 90-101( ), Approval Guidance for RNP Procedures with AR.

• AC 90-107( ), Guidance for Localizer Performance with Vertical Guidance and Localizer Performance without Vertical Guidance Approach Operations in the U.S. National Airspace System.

• AC 91-70( ), Oceanic and International Operations.

• AC 120-29( ), Criteria for Approval of Category I and Category II Weather Minima for Approach.

• Order 7110.82, Reporting Oceanic Errors.

• Order 7400.11( ), Airspace Designations and Reporting Points.

• Order 8260.3( ), United States Standard for Terminal Instrument Procedures (TERPS).

• Order 8260.19( ), Flight Procedures and Airspace.

• Order 8260.42( ), United States Standard for Helicopter Area Navigation (RNAV).

• Order 8260.46( ), Departure Procedure (DP) Program.

• Order 8260.58( ), United States Standard for Performance Based Navigation (PBN) Instrument Procedure Design.

3.3 Related Regulations Title 14 of the Code of Federal Regulations (14 CFR).

CHAPTER 3. DOCUMENTATION › 3.5 RTCA Documents.

• Part 71, §§ 71.31 and 71.71.

• Part 91, § 91.123, 91.175, 91.205, and Subpart H.

• Part 95.

• Part 97, § 97.20.

• Part 121, §§ 121.349, 121.351, and 121.567, Appendix G.

• Part 125, §§ 125.203, 125.287, and 125.325.

• Part 129, § 129.17.

• Part 135, § 135.165.

3.4 FAA Technical Standard Orders (TSO).

• TSO-C106, Air Data Computer.

• TSO-C115b, Airborne Area Navigation Equipment Using Multisensor Inputs.

• TSO-C115c or later, Airborne Area Navigation Equipment Using Multisensor Inputs.

• TSO-C129a, Airborne Supplemental Navigation Equipment Using the Global Positioning System (GPS).

• TSO-C145, Airborne Navigation Sensors Using the Global Positioning System (GPS) Augmented by the Wide Area Augmentation System (WAAS).

• TSO-C146, Stand-Alone Airborne Navigation Equipment Using the Global Positioning System (GPS) Augmented by the Wide Area Augmentation System (WAAS).

• TSO-C196, Airborne Supplemental Navigation Sensors for Global Positioning System Equipment using Aircraft-Based Augmentation.

3.5 RTCA Documents. Copies of the following RTCA, Inc. documents may be obtained from RTCA, Inc., 1150 18th Street NW, Suite 910, Washington, DC 20036, or purchased online at https://my.rtca.org/nc__store.

• RTCA/DO-178( ), Software Considerations in Airborne Systems and Equipment Certification.

• RTCA/DO-187( ), Minimum Operational Performance Standards for Airborne Area Navigation Equipment Using Multi-Sensor Inputs.

• RTCA/DO-201( ), Standards for Aeronautical Information.

CHAPTER 3. DOCUMENTATION › 3.6 Other Documents.

• RTCA/DO-208( ), Minimum Operational Performance Standards for Airborne Supplemental Navigation Equipment Using Global Positioning System (GPS).

• RTCA/DO-229( ), Minimum Operational Performance Standards for Global Positioning System/Wide Area Augmentation System Airborne Equipment.

• RTCA/DO-236( ), Minimum Aviation System Performance Standards: Required Navigation Performance for Area Navigation.

• RTCA/DO-283( ), Minimum Operational Performance Standards for Required Navigation Performance for Area Navigation.

• RTCA/DO-316( ), Minimum Operational Performance Standards for Global Positioning System/Aircraft -based Augmentation System Airborne Equipment.

3.6 Other Documents. Copies of the International Civil Aviation Organization (ICAO) documents may be obtained from Document Sales Unit, ICAO, 999 Robert-Bourassa Boulevard, Montreal, Quebec, H3C 5H7, Canada:

• ICAO Doc 9613, Performance Based Navigation (PBN) Manual.

• ICAO Doc 4444 PANS ATM, Procedures for Air Navigation Services, Air Traffic Management.

• ICAO Doc 7030, Regional Supplementary Procedures (SUPPS).

• Aeronautical Information Publications (AIP), United States, 2020.

CHAPTER 4. GENERAL INFORMATION

4.1 Performance-Based Navigation (PBN) Concept. The PBN concept represents a shift from ground-based navigation to Area Navigation (RNAV). Performance requirements are identified in navigation specifications (Nav Spec) (e.g., the requirements in this advisory circular (AC)), which also identify the choices of navigation sensors, navigation equipment, operational procedures, and training needed to meet the performance requirements.

4.1.1 Components. › 4.1.1.3 Nav Spec.

4.1.1 Components. The PBN concept specifies aircraft Required Navigation Performance (RNP) system performance requirements in terms of accuracy, integrity, availability, continuity, and functionality needed for particular operations or airspace. The Navigation Application is achieved by the use of a Navigational Aid (NAVAID) infrastructure and associated Nav Spec (See Figure 4-1, Performance-Based Navigation Concept).

Figure 4-1. Performance-Based Navigation Concept

4.1.1.1 Navigation Application. This is defined as the application of a Nav Spec and the supporting NAVAID infrastructure, to routes, procedures, and/or defined airspace volume, in accordance with the intended airspace concept. For example, in the terminal area, the Nav Spec is RNP 1 with an accuracy of 1 nautical mile (NM). The NAVAID infrastructure would be Global Navigation Satellite System (GNSS) or distance measuring equipment (DME)/DME.

4.1.1.2 NAVAID Infrastructure. NAVAID infrastructure refers to space-based and/or ground-based NAVAIDs available to meet the requirements in the Nav Spec.

4.1.1.3 Nav Spec. A set of aircraft and aircrew requirements needed to support PBN operations within a defined airspace. There are two kinds of Nav Spec:

1. RNAV specification. A Nav Spec based on area navigation that does not include the requirement for onboard performance monitoring and alerting, designated by the prefix RNAV (e.g., RNAV 5, RNAV 1).

CHAPTER 4. GENERAL INFORMATION › 4.2 Procedures and Routes.

2. RNP specification. A Nav Spec based on area navigation that includes the requirement for onboard performance monitoring and alerting, designated by the prefix RNP (e.g., RNP 4, Required Navigation Performance Approach (RNP APCH).

Note: The Performance-based Navigation Manual (Doc 9613), Volume II, contains additional information on Nav Specs.

4.1.2 Lateral Performance. For oceanic/remote, en route and terminal phases of flight, PBN is limited to operations with linear lateral performance requirements and time constraints due to legacy reasons associated with the previous RNP concept. In the approach phases of flight, PBN accommodates both linear and angular laterally guided operations.

4.1.2.1 RNP Values. The RNP value (also known as lateral navigation accuracy) designates the 95 percent lateral navigation (LNAV) performance (in NM) and the related monitoring and alerting requirements associated with an RNP instrument flight operation or a particular segment of that instrument flight. RNP values are specified in NM (e.g., RNP 0.3).

4.1.3 Vertical Performance. Some Nav Specs include requirements for vertical guidance using augmented GNSS or barometric vertical navigation (baro-VNAV) (see Appendix B). However, these requirements do not constitute vertical RNP which is neither defined nor included in the PBN Concept.

4.1.4 Onboard Performance Monitoring and Alerting. Onboard performance monitoring and alerting is the main element that determines if the navigation system complies with the necessary safety level associated to an RNP application. It relates to both lateral and longitudinal navigation performance; and it allows the aircrew to detect that the navigation system is not achieving, or cannot guarantee with 10-5 integrity, the navigation performance required for the operation. RNP systems provide improvements on the integrity of operations; this may permit closer route spacing and can provide sufficient integrity to allow only RNP systems to be used for navigation in a specific airspace. The use of RNP systems may therefore offer significant safety, operational and efficiency benefits.

4.2 Procedures and Routes. RNP procedures and routes require the use of RNAV systems with onboard performance monitoring and alerting. A critical component of RNP is the ability of the aircraft navigation system in combination with the pilot to monitor its achieved navigation performance and to identify for the pilot whether the operational requirement is or is not being met during an operation.

Note: Compliance with the performance monitoring and alerting requirement does not imply an automatic monitor of Flight Technical Error (FTE). The

4.3.1 Flight Technical Error (FTE) or Path Steering Error (PSE). › 4.3.1.1 Display Error.

onboard monitoring and alerting function should consist at least of a Navigation System Error (NSE) or Position Estimation Error (PEE) monitoring and alerting algorithm and a lateral deviation display enabling the crew to monitor the 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 database integrity process (see Chapter 10, Database Integrity) and crew procedures.

Figure 4-2. Total System Error (TSE)

Note 1: When evaluating RNP compliance, consideration must be given to possible error sources. Figure 4-2 displays possible cross-track (XTK) errors that can occur with definitions provided in paragraph 4.3.

Note 2: PDE is negligible and assumed to be zero. NSE is used instead of PEE and FTE is used instead of Path Steering Error (PSE) because they are considered equivalent and are the industry preferred terms.

4.3 Navigation Error Components/Definitions. Also in Appendix J, Administrative Information.

4.3.1 Flight Technical Error (FTE) or Path Steering Error (PSE). The accuracy with which the aircraft is controlled as measured by the indicated aircraft position, with respect to the indicated command or desired position is the FTE. It does not include blunder errors.

4.3.1.1 Display Error. As a component of FTE, these errors may include error components contributed by any input, output, or signal conversion equipment used by the display as it presents either aircraft position or guidance commands (e.g., course deviation or command heading) and by any course definition entry device employed.

4.3 Navigation Error Components/Definitions. › 4.3.5 Position Estimation Error (PEE) or Navigation System Error (NSE).

4.3.2 Path Definition Error (PDE). This is the difference between the defined path and the desired path at a specific point.

4.3.3 Navigation System Error (NSE) or Position Estimation Error (PEE). The difference between true position and estimated position.

4.3.4 Total System Error (TSE). The difference between the true position and the desired position and is equal to the vector sum of the FTE, PDE, and NSE.

4.3.5 Position Estimation Error (PEE) or Navigation System Error (NSE). PEE or NSE is the difference between true position and estimated position.

CHAPTER 5. › 5.1 Overview.

CHAPTER 5. APPLICATIONS OF REQUIRED NAVIGATION PERFORMANCE

(RNP) OPERATIONS

5.1 Overview. RNP operations as defined in this advisory circular (AC) are the application of navigation specification (Nav Spec) to a particular phase of flight. The columns of Table 5-1 contain RNP values (if applicable) for RNP operations in each phase of flight. RNP 1 requires an RNP value of 1 for arrival and departures in the terminal area and is also used in the initial, intermediate, and missed approach phase. RNP 2 is for both domestic and oceanic/remote continental operations with an RNP value of 2. RNP 4 and 10 are for oceanic and remote continental operations only with RNP values of 4 and 10 respectively. Advanced Required Navigation Performance (A-RNP) includes an RNP value of 2 for oceanic and remote continental operations and may have a 2 or 1 value for domestic en route segments. Except for the Final Approach Segment (FAS), advanced RNP allows scalability with a range from 1 to 0.3 as routing boundaries will gradually expand from 0.3 to greater values on departures/missed approaches and narrow on arrivals/approaches. Required Navigation Performance Approach (RNP APCH) operations have RNP values of 1 until the FAS where the boundaries narrow to RNP 0.3; the RNP value expands back to RNP 1 in the missed approach segment. Lastly, rotorcraft RNP 0.3 requires an RNP value of 0.3 for all phases of flight except for oceanic and remote continental and the FAS.

Table 5-1. Applications of RNP Operations

Flight Phase

Navigation Specifications

Terminal Approach Terminal En route Oceanic/Remote

Continental

En route Domestic Arrival Initial Intermediate Final Missed Departure

RNP 1 N/A N/A 1 1 1 N/A 1 1 RNP 2 2 2 N/A N/A N/A N/A N/A N/A RNP 4 4 N/A N/A N/A N/A N/A N/A N/A RNP 10 10 N/A N/A N/A N/A N/A N/A N/A A-RNP 2 2 or 1 1 – 0.3 1 – 0.3 1 – 0.3 N/A 0.3 - 1 0.3 - 1 RNP APCH N/A N/A N/A 1 1 0.3 1 N/A RNP 0.3 N/A 0.3 0.3 0.3 0.3 N/A 0.3 0.3

Note 1: N/A: Not Applicable

Note 2: Except for RNP APCH, all the final blocks are intentionally labeled N/A.

Note 3: RNP 1 and A-RNP may be used in combination with any type of approach (RNP, instrument landing system (ILS), Ground Based Augmentation System (GBAS) Landing System (GLS)).

Note 4: RNP 0.3 applies to Domestic (Rotorcraft) Operations.

6.4 RNP Operational Transitions. › 6.4.1 Transitions to Instrument Landing System (ILS), Ground Based…

CHAPTER 6. OPERATIONAL GUIDANCE FOR REQUIRED NAVIGATION

PERFORMANCE (RNP) OPERATIONS

6.1 General. This section provides guidance on the operational aspects that must be considered for conduct of all RNP operations. Additional guidance that is specific to each RNP navigation specification (Nav Spec) is provided in the appendices to this advisory circular (AC), including how to determine if your aircraft is eligible for the operation. In addition to this guidance, the operator must continue to ensure they comply with the general operating requirements, including checking Notices to Airmen (NOTAM), availability of Navigational Aids (NAVAID), airworthiness of aircraft systems, and aircrew qualification.

6.2 Centerline. All pilots are expected to maintain centerline, as depicted by onboard lateral deviation indicators and/or flight guidance during all RNP operations described in this AC unless authorized to deviate by air traffic control (ATC) or under emergency conditions. For normal operations, the cross-track (XTK) error/deviation (the difference between the RNP system computed path and the aircraft position relative to the path) should be limited to ±½ the RNP value. Brief deviations from this standard (e.g., overshoots or undershoots) during track changes (flyby and flyover turns), up to a maximum of one times the RNP value are allowable.

6.3 RNP En Route, RNP Terminal, and RNP APCH Operations:

1. The pilot is not required to monitor ground-based NAVAIDs used in position updating unless specified by the Airplane Flight Manual (AFM).

2. The pilot must comply with published and assigned altitudes, and airspeeds.

Note: Pilots operating aircraft with a barometric vertical navigation (baro-VNAV) system must ensure compliance with all altitude constraints as published in the procedure by reference to the barometric altimeter.

6.4 RNP Operational Transitions.

6.4.1 Transitions to Instrument Landing System (ILS), Ground Based Augmentation System (GBAS) Landing System (GLS), Localizer Performance with Vertical Guidance (LPV) or Conventional Approach Procedures. In order to fly RNP transitions to an ILS or GLS final approach course, or from an ILS or GLS approach with an RNP missed approach, pilots must comply with the operating requirements of this AC (see Appendices A (Required Navigation Performance Approach (RNP APCH)), C (RNP 1), and/or H (Advanced Required Navigation Performance (A-RNP)). RNP systems used for this type of operation must allow for a means to become established prior to the final approach fix (FAF) on an ILS or GLS or LPV final with minimal overshoot or undershoot. The pilot must ensure the appropriate navigation mode is selected/armed and that the Final Approach Segment (FAS) course and glideslope are correctly captured. Pilots must verify lateral and vertical capture on ILS procedures.

6.5.1 Airspace Distinction. › 6.5.1.3 Offshore.

Note 1: Charts for ILS and GLS procedures with RNP transitions will contain notes specifying the requirement for suitable RNP capability. These RNP transitions are also identified by the use of waypoint symbols on the procedure.

Note 2: Pilots must pay close attention to the navigation source of both lateral and vertical axis. When transitioning from an RNP segment to a precision approach segment, it is possible for the lateral precision navigation source to acquire prior to capture of the vertical precision navigation source.

Note 3: Additional criteria for operation on ILS, LPV final and GLS approaches with Radius to Fix (RF) transitions are covered in Appendix I, Additional Capabilities.

6.5 Oceanic/Remote Continental Airspace and Offshore Airspace.

6.5.1 Airspace Distinction. For continuity purposes, there is a distinction between oceanic, remote continental, and offshore operations. The paragraphs below define these Areas of Operation.

6.5.1.1 Oceanic. Oceanic airspace is defined as international airspace over oceans where separation and procedures are in accordance with the International Civil Aviation Organization (ICAO), and outside the area defined as offshore. Responsibility for the provision of ATC service in this airspace is delegated to various countries. Controllers provide Air Traffic Services (ATS) utilizing procedural control and procedural separation.

6.5.1.2 Remote Continental. Remote continental airspace is defined as airspace above terrain where line-of-sight communications, independent surveillance and reliable ground-based NAVAIDs are not available. Controllers provide ATS utilizing procedural control and procedural separation.

6.5.1.3 Offshore. Offshore airspace is defined by Title 14 of the Code of Federal Regulations (14 CFR) part 71, §§ 71.31 and 71.71, and part 91, § 91.511. It is designated in international airspace within areas of domestic radio navigational signal or ATC radar coverage, and within which domestic ATC procedures are applied. For more details, refer to Federal Aviation Administration (FAA) Order 7400.11( ), Airspace Designations and Reporting Points. All certificated operators, and all large and turbine-powered multiengine aircraft, must have two independent RNP navigation systems appropriate for the route to be flown, or a single RNP navigation system and a second navigation system capable of proceeding to a safe landing from anywhere on the route.

CHAPTER 7. OPERATIONAL APPROVAL PROCESS › 7.3 Parts 91K, 121, 125, 129, and 135 Operators.

CHAPTER 7. OPERATIONAL APPROVAL PROCESS

7.1 Part 91 Operators. A Letter of Authorization (LOA) is not required for Title 14 of the Code of Federal Regulations (14 CFR) part 91 operators (other than part 91 subpart K (part 91K)) except for oceanic operations (see Appendices E, F, and G) or if required in foreign airspace. Part 91 operators (other than part 91K) should comply with the aircraft eligibility and operational guidance in this advisory circular (AC).

7.2 Operational Authorization. To obtain operational authorization, aircraft eligibility must be determined in accordance with the applicable appendix of this AC. Operational authorizations issued under a previous version of this AC or other canceled ACs does not need to be reissued or reevaluated.

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.

7.3 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:

• OpSpec/MSpec/optional LOA, paragraph C063, Area Navigation (RNAV) and Required Navigation Performance (RNP) Terminal Operations;

• OpSpec/MSpec, paragraph B035, Class 1 Navigation in U.S. Class A Airspace Using Area or Long-Range Navigation Systems;

• OpSpec/MSpec/LOA (to include Part 91 operators), paragraph B036, Oceanic and Remote Continental Navigation Using Multiple Long-Range Navigation Systems (M-LRNS); or

• Helicopter Specification (HSpec)/LOA, paragraph H123, Class I Navigation Using Area or Long-Range Navigation Systems with Wide Area Augmentation System (WAAS) for Rotorcraft Required Navigation Performance (RNP) 0.3 En Route and Terminal Operations.

Note: This AC only addresses the navigation equipment and operating requirements for these operations. The pilot and operator, as applicable, must comply with all requirements for the operation. Those requirements are specified in 14 CFR for all U.S. operators, and may be augmented by additional requirements for operations outside of the United States as specified in other documents, such as the Aeronautical Information Publications (AIP) and the International Civil Aviation Organization (ICAO) Doc 7030, Regional Supplementary Procedures (SUPPS).

7.5 Multiple OpSpecs/MSpecs/LOAs. › 7.5.2 Amendments.

7.4 Preapplication Meeting. Certificate holders, operators, and program managers should schedule a preapplication meeting with the responsible Flight Standards office. This meeting allows the operator an opportunity to discuss the requirements for operational approval.

7.5 Multiple OpSpecs/MSpecs/LOAs. The operator should consolidate all applications for relevant RNP OpSpecs, MSpecs, or LOAs as appropriate per the operator’s present/future operational plans and capabilities (see Chapter 12, Bundling Concept).

7.5.1 Application. All operators seeking an initial approval should provide relevant documentation in support of the following areas/topics:

1. Evidence of aircraft eligibility,

Note: This may be documented in manufacturer documentation (e.g., Service Letters (SL), etc.). Airplane Flight Manual (AFM) entries are not required provided the Federal Aviation Administration (FAA) accepts the manufacturer’s documentation.

2. Establishment of operating procedures for the RNP system,

3. Control of those procedures through the operations manual (as required),

4. Identification of flightcrew training requirements, and

5. Control of process for updating the navigation database.

7.5.2 Amendments. Operators who hold an approval and propose to amend due to a change in equipment or operating procedures should provide appropriate evidence that the change does not affect compliance.

8.4 Pilot Knowledge/Training. › 8.4.2 RNP Authorization Requests.

CHAPTER 8. OPERATOR RESPONSIBILITIES

8.1 Operational Manuals and Checklists. Title 14 of the Code of Federal Regulations (14 CFR) part 91 operators should use relevant Airplane Flight Manuals (AFM) and checklists. Operations manuals and checklists for 14 CFR parts 91 subpart K (part 91K), 121, 125, 129, and 135 operators must address information/guidance on the standard operating procedures (SOP) detailed in Appendices A through I (as appropriate). The appropriate manuals should also contain navigation operating instructions and contingency procedures.

8.2 Training Documentation.

8.2.1 Part 91 Operator Training. Part 91 operators should be knowledgeable with the procedures and operations associated with the use of Required Navigation Performance (RNP) systems.

8.2.2 Parts 91K, 121, 125, and 135 Operator Training. Parts 91K, 121, 125, and 135 operators should have a training program addressing the operational practices, procedures and training items related to RNP operations (e.g., initial, upgrade, or recurrent training for flightcrew, operational control personnel, and maintenance personnel).

Note: A separate training program is not required if RNP training is integrated in the current training program. However, the applicant must identify the training elements from this advisory circular (AC) within the existing training program.

8.3 Minimum Equipment List (MEL) Considerations. If an MEL is required, it must include any revisions necessary to address RNP flight operations. These provisions must be approved. Operators must adjust the MEL, or equivalent, and specify the required dispatch conditions.

8.4 Pilot Knowledge/Training. Parts 91K, 121, 125, and 135 operators should maintain training syllabi (e.g., initial, upgrade, recurrent) and other appropriate materials that include operational practices and procedures. Training for other personnel must be included where appropriate (e.g., operational control personnel, maintenance).

8.4.1 Flightcrew Training. Parts 91K, 121, 125, and 135 operators should ensure their programs contain training for flightcrews on equipment requirements, normal and non-normal operations and flight procedures, and limits of their RNP navigation capability.

8.4.2 RNP Authorization Requests. Parts 91K, 121, 125, 129, and 135 operators requesting an RNP authorization must ensure that crewmembers are knowledgeable on the material contained in this AC. Training “acceptable” to the Federal Aviation Administration (FAA) is not a prerequisite for issuing an RNP authorization.

8.4 Pilot Knowledge/Training. › 8.4.3 Pilot Knowledge. Pilots must be familiar with the following:

8.4.3 Pilot Knowledge. Pilots must be familiar with the following:

1. The information in this AC, as applicable;

2. The meaning and proper use of aircraft equipment/navigation capability codes used on the flight plan;

3. Procedure characteristics as determined from chart depiction and textual description;

4. Depiction of waypoint types (flyover and flyby) as well as associated aircraft flightpaths;

5. A waypoint may be a flyover in one procedure and the same waypoint may also be a flyby in another procedure;

6. Required equipment for RNP operations;

7. Aircraft automation, mode annunciations, changes, alerts, interactions, reversions, and degradations;

8. Functional integration with other aircraft systems;

9. Meaning of route discontinuities and appropriate flightcrew procedures;

10. Types of navigation sensors used by the RNP system and their annunciations;

11. Turn anticipation with consideration to speed and altitude effects;

12. Interpretation of electronic displays and symbols;

13. Understanding the operational conditions used to support RNP operations (e.g., appropriate selection of course deviation indicator (CDI) scaling (lateral deviation display scaling));

14. If applicable, the importance of maintaining the published path and maximum airspeeds while performing RNP operations with Radius to Fix (RF) legs;

15. Depiction of path terminators, associated aircraft flightpaths, altitude, and speed restrictions;

16. Monitoring procedures for each phase of flight (e.g., monitor PROG or LEGS page);

17. Automatic and/or manual setting of the required RNP value;

18. Understanding of the navigation equipment regarding lateral and vertical capture from an RNP routing to an instrument landing system (ILS) or Ground Based Augmentation System (GBAS) Landing System (GLS);

19. Awareness of possible false vertical and lateral captures during a transition on an ILS capture;

20. Know how offsets are applied, the functionality of their particular navigation system and the need to advise air traffic control (ATC) if this functionality is not available;

8.4 Pilot Knowledge/Training. › 8.4.4 Pilot Knowledge and Actions.

21. Operator-recommended automation use for phase of flight and workload, including methods to minimize cross-track (XTK) error to maintain route centerline;

22. Receiver/transmitter (R/T) phraseology for RNP applications;

23. Flightcrew contingency procedures for a loss of RNP capability; and

24. Understanding the performance requirement to couple the autopilot (AP)/flight director (FD) to the navigation system’s lateral guidance on RNP procedures, if required.

Note: Operators are encouraged to use manufacturer recommended training and operating procedures.

8.4.4 Pilot Knowledge and Actions. Pilots must have adequate knowledge to perform the following actions if required by navigation specification(s) (Nav Spec(s)):

1. Verify currency and integrity of aircraft navigation data;

2. If applicable, obtain a receiver autonomous integrity monitoring (RAIM) prediction for the planned RNP operation;

3. Verify successful completion of RNP system self-tests;

4. Initialize navigation system position;

5. Retrieve and fly an RNP procedure (e.g., Standard Instrument Departure (SID) or a Standard Terminal Arrival (STAR) with appropriate transition);

6. Adhere to speed and/or altitude constraints associated with RNP operations;

7. Select the appropriate STAR or SID for the active runway in use and be familiar with procedures to deal with a runway change;

8. Verify waypoints and flight plan programming;

9. Perform a manual or automatic runway update (with takeoff point shift for Inertial Reference Units (IRU) only);

10. Fly direct to a waypoint;

11. Fly a course/track to a waypoint;

12. Intercept a course/track;

13. Fly vectors, and rejoin an RNP route/procedure from the ‘heading’ mode;

14. Selecting/arming the navigation system for an ILS or GLS transition;

15. Insert and delete route discontinuity;

16. Remove and reselect navigation sensor input;

17. When required, confirm exclusion of a specific navigation aid or navigation aid type (distance measuring equipment (DME) and very high frequency omni-directional range (VOR) only);

CHAPTER 8. OPERATOR RESPONSIBILITIES › 8.5 Operation, Procedure, or Route Selection.

18. Change arrival airport and alternate airport;

19. Verify the RNP value set in the flight management system (FMS) matches the equipment capability and authorizations as annotated in the flight plan; and

20. Perform parallel offset function if capability exists.

8.5 Operation, Procedure, or Route Selection. The equipment should not permit the flightcrew to select an operation, procedure (instrument approach procedure (IAP), SID, or STAR) or route that is not supported by the equipment, either manually or automatically (e.g., a procedure is not supported if it incorporates a RF leg or a fixed radius transition (FRT) and the equipment does not provide RF leg or FRT capability). The system should also restrict pilot access to procedures requiring RF leg capability or FRT if the system can select the procedure, but the aircraft is not otherwise equipped (e.g., the aircraft does not have the required roll steering AP or FD installed).

Note: Equipment manufacturers and airworthiness applicants should refer to AC 20-138( ), Chapter 6, Equipment Performance - RNAV Multi-Sensor Equipment.

9.3 GPS Performance Prediction. › 9.3.1 Equipment in Accordance with TSO-C129 or TSO-C196.

CHAPTER 9. FLIGHT PLANNING

9.1 Required Navigation Performance (RNP) Flight Planning Requirements. Pilots and operators must use all available information in planning their flight, to ensure suitable navigation performance.

Note: Oceanic and remote continental RNP operations have unique flight planning requirements to ensure reliable navigation if a Global Positioning System (GPS) satellite fails.

9.1.1 RNP 2, RNP 4, and RNP 10. The specific requirements for RNP 2, RNP 4, and RNP 10 can be found in:

• Appendix E, Qualification Criteria for Required Navigation Performance (RNP) 2 Domestic, Offshore, Oceanic, and Remote Continental Operations,

• Appendix F, Qualification Criteria for Required Navigation Performance (RNP) 4 Oceanic and Remote Continental Operations, and

• Appendix G, Qualification Criteria for Required Navigation Performance (RNP) 10 Oceanic and Remote Continental Operations, respectively.

9.2 Notices to Airmen (NOTAM). All operators should review NOTAMs, as the Federal Aviation Administration (FAA) may indicate that GPS is unreliable in certain airspace and at certain times. For example, the FAA may do this in the event of interference to GPS. The FAA also provides a NOTAM service for Satellite-based Augmentation System (SBAS) (e.g., wide area augmentation system (WAAS)) receivers for all domestic RNP operations covered by this advisory circular (AC), which will identify any performance outages affecting Technical Standard Order (TSO)-C145 or TSO-C146 equipment. Operators flying aircraft equipped with SBAS do not need to conduct a preflight availability prediction for domestic RNP operations if WAAS coverage is confirmed to be available along the entire route of flight. For operations outside of the United States and using SBAS equipment, the operator should determine if the Air Navigation Service Provider (ANSP) monitors the performance of SBAS equipment or if it is appropriate to use a receiver autonomous integrity monitoring (RAIM) prediction program for the flight.

9.3 GPS Performance Prediction.

9.3.1 Equipment in Accordance with TSO-C129 or TSO-C196. If TSO-C129( ) or TSO-C196 equipment is used to solely satisfy the RNP monitoring and alerting requirement, GPS RAIM availability must be confirmed for the intended route of flight (route and time) using available GPS satellite information. Therefore, pilots should prepare to assess their capability to navigate (potentially to an alternate destination) in case of failure of Global Navigation Satellite System (GNSS) navigation.

9.3 GPS Performance Prediction. › 9.3.4 Flight Planning Guidance.

9.3.2 Prediction Methods. Operators may satisfy the predictive RAIM requirement through any one of the following methods:

1. Operators of large fleets of aircraft or users of flight planning programs may wish to use their own preflight availability verification tool. The operator is responsible for selecting a tool that accurately predicts the performance for their aircraft. The tool must consider the GPS satellites that are in service at the time of the prediction, and may take into account unique characteristics of the GPS receiver, aircraft integration or installation; including performance better than required in FAA standards or use of inertial information integrated into the navigation position solution. The FAA does not evaluate or approve a particular tool, but may evaluate the basis of the operator’s determination that the tool is appropriate to their aircraft, particularly if its use results in unexpected loss of RNP navigation.

2. Operators may use the FAA en route and terminal RAIM prediction: Service Availability Prediction Tool (SAPT) (http://sapt.faa.gov). Refer to the SAPT User Guide (current edition) for specific instructions on its use;

3. Operators may use a third party interface, incorporating FAA RAIM prediction data without altering performance values, to predict RAIM outages for the aircraft’s predicted flightpath and times;

4. Operators may use the receiver’s installed RAIM prediction capability (for TSO-C129a/Class A1/B1/C1 or TSO-C196( ) equipment) to provide Nonprecision Approach (NPA) RAIM, accounting for the latest GPS constellation status (e.g., NOTAMs or Notice Advisories to Navstar Users (NANU)). Receiver NPA RAIM should be checked at airports spaced at intervals not to exceed 60 nautical miles (NM) along the Area Navigation (RNAV) 1 procedures flight track. Terminal or approach RAIM must be available at the estimated time of arrival (ETA) over each airport checked.

9.3.3 Prediction Model Parameters. The operator should use a model appropriate to their equipment, including the type of GPS receiver and the demonstrated capability to track satellites at a given mask angle. When selecting a mask angle, the operator should consider the equipment qualification, installation in the aircraft, and the effects of normal maneuvering. Aircraft are typically qualified with a five-degree mask angle, and operational experience has indicated that a two-degree mask angle can be achieved by some equipment installations. If using the SAPT, each prediction is valid for the operation within 5 minutes of the plan time and 7.5 NM of the route. The operator may wish to submit additional requests for predictions for varying times around the proposed departure time to ensure compliance at the actual departure time.

9.3.4 Flight Planning Guidance. Predictions can be used for initial flight planning as early as 72 hours prior to the planned departure. However, the operator should conduct a performance prediction as close to departure time as feasible, but with sufficient time to re-plan the flight or obtain air traffic control (ATC) prior approval in the event a segment of the flight will not be compliant. The prediction should be reevaluated if a new NOTAM identifies an unscheduled GPS satellite outage.

9.5.1 Alternate Airport Considerations. › 9.5.1.1 For flight planning purposes, TSO-C129( ) and TSO-C196( )…

9.3.5 Resolving Predicted Outages in Performance. In the event of a predicted, continuous loss of RAIM of more than 5 minutes for any part of the intended flight, the flight must be delayed, canceled, or re-routed where RAIM requirements can be met. Alternatively, the flight may be re-planned based on a different form of navigation.

9.4 Distance Measuring Equipment (DME) Flight Planning Requirements. For multisensor aircraft with operating GPS and DME/DME/Inertial Reference Unit (IRU) positioning, a RAIM check for continental operations is not required as long as DME is identified as an available navigation service for the route and critical DME’s are functioning normally. However, when planning for a Required Navigation Performance Approach (RNP APCH) (Appendix A, Qualification Criteria for Required Navigation Performance Approach (RNP APCH) Operations), a RAIM check is still required as this exception does not apply to RNP APCH operations.

9.5 Contingency Planning for Alternate Airport.

9.5.1 Alternate Airport Considerations. For the purposes of flight planning, any required alternate airport must have an available instrument approach procedure (IAP) that does not require the use of GPS. This restriction includes conducting a conventional approach at the alternate airport using a substitute means of navigation that is based upon the use of GPS. For example, these restrictions would apply when planning to use GPS equipment as a substitute means of navigation for an out-of-service very high frequency omni-directional range (VOR) that supports an instrument landing system (ILS) Missed Approach Procedure (MAP) at an alternate airport. In this case, some other approach not reliant upon the use of GPS must be available. This restriction does not apply to pilots with navigation systems meeting the requirements below.

9.5.1.1 For flight planning purposes, TSO-C129( ) and TSO-C196( ) equipped users (GPS users) whose navigation systems have fault detection and exclusion (FDE) capability, who perform a preflight RAIM prediction at the airport where the RNAV (GPS) approach will be flown, and have proper knowledge and any required training and/or approval to conduct a GPS-based IAP, may file based on a GPS-based IAP at either the destination or the alternate airport, but not at both locations. At the alternate airport, pilots may plan for applicable alternate airport weather minimums using:

1. Lateral navigation (LNAV) or circling minimum descent altitude (MDA);

2. LNAV/vertical navigation (VNAV) decision altitude (DA), if equipped with and using approved barometric vertical navigation (baro-VNAV) equipment;

3. RNP 0.3 DA on an RNAV (RNP) IAP, if they are specifically authorized users using approved baro-VNAV equipment and the pilot has verified RNP availability through an approved prediction program.

9.5.1 Alternate Airport Considerations. › 9.5.1.2 Pilots with WAAS receivers, TSO-C145( ) or TSO-C146( ), may…

Note: If the above conditions cannot be met, any required alternate airport must have an approved IAP other than GPS that is anticipated to be operational and available at the ETA, and which the aircraft is equipped to fly.

9.5.1.2 Pilots with WAAS receivers, TSO-C145( ) or TSO-C146( ), may flight plan to use any IAP authorized for use with their WAAS avionics as the planned approach at a required alternate, with the following restrictions. When using WAAS at an alternate airport, flight planning must be based on flying the RNAV (GPS) LNAV or circling minima line, or minima on a GPS approach procedure, or conventional approach procedure with “or GPS” in the title. Properly trained and approved, as required, TSO-C145( ) and TSO-C146( ) equipped users (WAAS users) with and using approved baro-VNAV equipment may plan for LNAV/VNAV DA at an alternate airport. Specifically authorized WAAS users with and using approved baro-VNAV equipment may also plan for RNP 0.3 DA at the alternate airport as long as the pilot has verified RNP availability through an approved prediction program. Title 14 of the Code of Federal Regulations (14 CFR) part 91 nonprecision weather requirements must be used for planning. Upon arrival at an alternate, when the WAAS navigation system indicates that LNAV/VNAV or localizer performance with vertical guidance (LPV) service is available, then vertical guidance may be used to complete the approach using the displayed level of service.

CHAPTER 10. DATABASE INTEGRITY › 10.6 Data Process for Part 91 Operators.

CHAPTER 10. DATABASE INTEGRITY

10.1 Database Suppliers. Navigation databases must be obtained from a database supplier holding an Federal Aviation Administration (FAA) Letter of Acceptance (LOA) in accordance with Advisory Circular (AC) 20-153( ), Acceptance of Aeronautical Data Processes and Associated Databases. This LOA provides recognition of a data supplier’s compliance with the data quality, integrity, and quality management practices of RTCA, Inc.’s document, RTCA DO-200( ), Standards for Processing Aeronautical Data. The operator’s supplier (e.g., flight management system (FMS) manufacturer) must have a Type 2 LOA. AC 20-153( ) contains procedures for database LOAs.

10.2 Navigation Data Requirements. The onboard navigation data must be current and appropriate for the region of intended operation and should include the navigation aids, waypoints, and relevant coded terminal airspace procedures for the departure, arrival, and alternate airfields.

10.3 Terminal and En Route Requirements. Further database guidance for terminal and en route requirements may be found in AC 90-100( ), U.S. Terminal and En Route Area Navigation (RNAV) Operations.

10.4 Database Validity. Prior to using a procedure or waypoint retrieved from the airborne navigation database, the pilot should verify the validity of the database.

Note: Navigation databases are also expected to be current for the duration of the flight. If the Aeronautical Information Regulation and Control (AIRAC) cycle will change during flight, operators and pilots must establish procedures to ensure the accuracy of navigation data, including suitability of navigation facilities used to define the routes and procedures for flight. Traditionally, this has been accomplished by verifying electronic data against paper or Electronic Flight Bag (EFB) products. One acceptable means is to compare aeronautical charts (new and old) to verify navigation fixes prior to departure. If an amended chart (hard copy amendment not in the database) is published for the procedure, the database must not be used to conduct the operation.

10.5 Navigation Data Validation Program. Navigation databases should be obtained from a supplier complying with AC 20-153( ) or equivalent, and should be compatible with the equipment.

10.6 Data Process for Part 91 Operators. For Title 14 of the Code of Federal Regulations (14 CFR) part 91 (except part 91 subpart K (part 91K)) operators, pilots must confirm at system initialization that the navigation database is current. Part 91 (except part 91K) operators may consider navigation database validation complete when checking the navigation database currency and applicable Notice to Airmen (NOTAM).

CHAPTER 10. DATABASE INTEGRITY › 10.7 Data Process for Parts 91K, 121, 125, 129, and 135.

10.7 Data Process for Parts 91K, 121, 125, 129, and 135. For Title 14 CFR parts 91K, 121, 125, 129, and 135, operators should establish a database program that meets the following requirements:

1. The operator must identify within their procedures the responsible manager for the data updating process,

2. The operator must document a process for accepting and verifying applicability,

3. The operator must place their documented data process under configuration control, and

4. The pilots must confirm at system initialization that the navigation database is current.

5. Discrepancies that invalidate a procedure (e.g., database errors) must be reported to the navigation database supplier and the use of affected procedures must be prohibited by an operator’s notice to its flightcrew. The affected procedure can be reinstated for flightcrew use only after the operator has verified that the database error has been corrected.

CHAPTER 11. AIRCRAFT AND SYSTEM REQUIREMENTS › 11.1 References.

CHAPTER 11. AIRCRAFT AND SYSTEM REQUIREMENTS

11.1 References. Refer to the appendices below for aircraft and system requirements:

1. Appendix A, Qualification Criteria for Required Navigation Performance Approach (RNP APCH) Operations.

2. Appendix B, Use of Barometric Vertical Navigation (baro-VNAV) for Required Navigation Performance Approach (RNP APCH) Operations.

3. Appendix C, Qualification Criteria for Required Navigation Performance (RNP) 1 (Terminal) Operations.

4. Appendix D, Qualification Criteria for Required Navigation Performance (RNP) 0.3 (Rotorcraft) Operations.

5. Appendix E, Qualification Criteria for Required Navigation Performance (RNP) 2 Domestic, Offshore, Oceanic, and Remote Continental Operations.

6. Appendix F, Qualification Criteria for Required Navigation Performance (RNP) 4 Oceanic and Remote Continental Operations.

7. Appendix G, Qualification Criteria for Required Navigation Performance (RNP) 10 Oceanic and Remote Continental Operations.

8. Appendix H, Advanced Required Navigation Performance (A-RNP).

9. Appendix I, Additional Capabilities.

CHAPTER 12. BUNDLING CONCEPT › 12.6 Terminal and En Route Phases of Flight.

CHAPTER 12. BUNDLING CONCEPT

12.1 Performance-based Navigation (PBN) Authorization. The Federal Aviation Administration (FAA) allows PBN authorizations to be bundled. This concept provides the FAA more latitude in granting a wider range of authorizations on a single operator application. Each flight phase contains a hierarchy of PBN authorizations where bundling can be accomplished. PBN authorizations within an operation specification (OpSpec), management specification (MSpec) or Letter of Authorization (LOA) are combined with less restrictive PBN authorization(s) within each phase of flight, if applicable. This reduces cost and workload for both the operator and the FAA.

12.2 Visual of Bundling Options. Figure 12-1, Bundling Options, illustrates this concept of bundling by flight phase into approach, terminal, en route, and oceanic/remote continental. Each phase contains a hierarchy of PBN operations within the applicable OpSpec, MSpec, or LOA.

12.3 Approach Phase Composition. The approach phase has two distinct divisions of Required Navigation Performance Authorization Required Approach (RNP AR APCH) and Required Navigation Performance Approach (RNP APCH). For the purpose of bundling, Required Navigation Performance Authorization Required (RNP AR) is excluded from bundling because of unique requirements for authorization.

Note: Localizer performance with vertical guidance (LPV) and localizer performance without vertical guidance (LP) minimums are authorized through OpSpec/MSpec/LOA C052, but are excluded as a bundling option.

12.4 Credit for Existing RNP AR Approvals. Operators with a current and approved RNP AR approval meet the requirements the Required Navigation Performance (RNP) operations as described in this advisory circular (AC).

12.5 RNP 2 Areas of Operation. The Areas of Operation for RNP 2 are within the U.S. National Airspace System (NAS) or offshore airspace where domestic air traffic control (ATC) procedures are applied and also in oceanic and remote continental airspace.

Note: Oceanic and remote continental airspace often have additional surveillance, communication, and higher navigation continuity requirements.

12.6 Terminal and En Route Phases of Flight. The terminal and en route phases of flight contains RNP 1, RNP 2, Area Navigation (RNAV) 1, RNAV 2, and RNAV 5 for terminal and en route operations (see Figure 12-1). An operator with an RNP 1 authorization as described in Appendix C, Qualification Criteria for Required Navigation Performance (RNP) 1 (Terminal) Operations, would also be granted authorization for RNAV 1. Additionally, an RNP 2 (domestic) authorization as described in Appendix E, Qualification Criteria for Required Navigation Performance (RNP) 2 Domestic, Offshore, Oceanic, and Remote Continental Operations, would also be granted RNAV 2 and RNAV 5 authorizations.

CHAPTER 12. BUNDLING CONCEPT › 12.8 Advanced Required Navigation Performance (A-RNP).

12.7 Oceanic/Remote Continental RNP 2 Authorization. An operator with an oceanic/remote continental RNP 2 authorization (Figure 12-1) will also be granted RNP 4 and RNP 10 navigation authorizations. Authorizations in oceanic and remote continental airspace also depend upon the operator’s qualification to meet international surveillance and communication requirements. Those requirements are specified in other documents, such as the Aeronautical Information Publications (AIP) and the International Civil Aviation Organization (ICAO) Doc 7030, Regional Supplementary Procedures (SUPPS) and AC 91-70( ), Oceanic and International Operations.

12.8 Advanced Required Navigation Performance (A-RNP). In order to be A-RNP qualified (see Appendix H, Advanced Required Navigation Performance (A-RNP)), operators must be operationally and functionally qualified to perform the following three required functions:

1. Scalability,

2. Radius to Fix (RF), and

3. Parallel offset.

Note: Higher continuity may be required for oceanic and remote continental airspace. Currently, fixed radius transition (FRT) and Time of Arrival Control (TOAC) are optional. For each applicable OpSpec, MSpec, or LOA, A-RNP functions are added to the bundled hierarchy of PBN authorizations (see Figure 12-1).

Figure 12-1. Bundling Options

A.2 Aircraft and System Requirements. › A.2.4 Qualified Avionics Equipment and Airworthiness Approval. Aircraft…

3/7/16 AC 90-105A Appendix A

APPENDIX A. QUALIFICATION CRITERIA FOR REQUIRED NAVIGATION

PERFORMANCE APPROACH (RNP APCH) OPERATIONS

A.1 Introduction. This appendix provides guidance on the performance and functional

requirements for systems used to conduct RNP APCH operations, which are designated under Title 14 of the Code of Federal Regulations (14 CFR) part 97 as Area Navigation (RNAV) Global Positioning System (GPS) or GPS and categorized as RNP APCH by the International Civil Aviation Organization (ICAO). Localizer performance without vertical guidance (LP) and localizer performance with vertical guidance (LPV) operations can be found in Advisory Circular (AC) 90-107( ), Guidance for Localizer Performance with Vertical Guidance and Localizer Performance without Vertical Guidance Approach Operations in the U.S. National Airspace System. The barometric vertical navigation (baro-VNAV) aspects of RNP APCHs are specified in Appendix B, Use of Barometric Vertical Navigation (baro-VNAV) for Required Navigation Performance Approach (RNP APCH) Operations. Baro-VNAV systems are optional capabilities that are not a minimum requirement to fly RNAV (GPS) or GPS approaches using the lateral navigation (LNAV) line of minima. The requirements for Radius to Fix (RF) legs are specified in Appendix I, Additional Capabilities.

A.2 Aircraft and System Requirements.

A.2.1 Approval for RNAV (GPS) or GPS Approaches. Aircraft with approval to conduct

RNAV (GPS) or GPS approaches meet the performance and functional requirements in this AC for RNP APCH instrument approaches without RF legs.

A.2.2 Statement of Compliance (SOC). Aircraft with a SOC with the criteria in this AC in their

Airplane Flight Manual (AFM), Airplane Flight Manual Supplement (AFMS), pilot’s operating handbook (POH), or the operating manual for their avionics meet the performance and functional requirements of this AC.

A.2.3 Statement from the Manufacturer. Aircraft with a statement from the manufacturer

documenting compliance with the criteria in AC 20-138( ), Airworthiness Approval of Positioning and Navigation Systems, meet the performance and functional requirements of this AC. Manufacturer documentation can include Service Bulletins (SB) or Service Letters (SL). These statements should include the airworthiness basis for compliance. AFM/Rotorcraft Flight Manual (RFM) entries are not required provided the Federal Aviation Administration (FAA) accepts the manufacturer’s documentation.

A.2.4 Qualified Avionics Equipment and Airworthiness Approval. Aircraft with the following

avionics equipment and an appropriate airworthiness approval automatically qualify for RNP APCH to LNAV minima capability without further documentation by virtue of the avionics Technical Standard Order (TSO) and airworthiness approval:

1. GPS stand-alone systems approved in accordance with TSO-C129( ), Class A1, or TSO-C146 operational Class 1, 2, or 3 and installed in accordance with AC 20-138( ).

A.3.1 Accuracy. The aircraft must comply with Section 2.1.1 of… › A.3.1.2 To satisfy the accuracy requirement, the 95 percent Flight…

3/7/16 AC 90-105A Appendix A

2. Aircraft with a TSO-C115c or later flight management system (FMS) with a TSO-C129( ) (Class B1, C1, B3, C3), TSO-C145( ), or TSO-C196( ) sensors installed in accordance with AC 20-138( ).

3. Aircraft with a TSO-C115b FMS using a TSO-C129( ) Class B1/C1, TSO-C145( ), or TSO-C196( ) sensor with documented compliance to the RNP requirements in RTCA, Inc.’s document, RTCA/DO-236 (revision ‘B’ or later) or RTCA/DO-283 (revision ‘A’ or later) as part of the approval basis.

A.2.5 GPS-Equipped Multisensor Systems. Multisensor systems using GPS should be approved

in accordance with AC 20-138( ) or TSO-C115b or later and meet the functionality requirements of this appendix. Multisensor systems that use distance measuring equipment (DME)/DME or DME/DME/Inertial Reference Unit (IRU) as the only means of Required Navigation Performance (RNP) compliance are not authorized to conduct RNP APCHs. However, operators still retain the option to develop special RNP APCHs using these systems.

A.2.6 Other Equipment. For equipment other than what is listed in paragraph A.2, the Original

Equipment Manufacturer (OEM) or the holder of installation approval for the aircraft (e.g., Supplemental Type Certificate (STC) holder) must demonstrate compliance with the criteria in this AC.

A.3 Performance and Functionality Requirements for RNP APCH Systems.

A.3.1 Accuracy. The aircraft must comply with Section 2.1.1 of RTCA/DO-236C. During

operations on the initial and intermediate segments and for the missed approach of an RNP APCH procedure, the lateral Total System Error (TSE) must be within ±1 nautical mile (NM) for at least 95 percent of the total flight time. The along-track (ATRK) error must also be within ±1 NM for at least 95 percent of the total flight time.

Note: There are no RNP requirements for the missed approach if it is based on conventional means (very high frequency omni-directional range (VOR), DME, and Non-Directional Beacon (NDB)) or on dead reckoning.

A.3.1.1 During operations on the Final Approach Segment (FAS), the lateral TSE must be within ±0.3 NM for at least 95 percent of the total flight time. The ATRK must also be within ±0.3 NM for at least 95 percent of the total flight time.

A.3.1.2 To satisfy the accuracy requirement, the 95 percent Flight Technical Error (FTE) should not exceed 0.5 NM on the initial and intermediate segments, and for the RNAV missed approach, of an RNP APCH. The 95 percent FTE should not exceed 0.25 NM on the FAS of an RNP APCH.

Note: The use of a deviation indicator with 1 NM full-scale deflection on the initial and intermediate segments, and for the RNAV missed approach and 0.3 NM full-scale deflection on the FAS, has been found to be an acceptable means of compliance (AMC). The use of an

A.3.7 Functional Requirements of Navigation Displays. The following… › A.3.7.1 RNP systems using TO/TO navigation algorithms do not require a…

3/7/16 AC 90-105A Appendix A

autopilot (AP) or flight director (FD) has been found to be an AMC (roll stabilization systems do not qualify).

A.3.2 Integrity. Malfunction of the aircraft navigation equipment that causes the TSE to exceed

2 times the RNP APCH value is classified as a major failure condition under airworthiness regulations (i.e., 10-5 per hour).

A.3.3 Continuity. Loss of function is classified as a minor failure condition if the operator can

revert to a different navigation system and safely proceed to a suitable airport.

A.3.4 Performance Monitoring and Alerting. During operations on the initial, intermediate, and

the missed approach segment, the RNP system or the RNP system and pilot in combination must provide an alert if the accuracy requirement is not met or if the probability that the lateral TSE exceeds 2 NM is greater than 10-5. During operations on the FAS, the RNP system or the RNP system and pilot in combination must provide an alert if the accuracy requirement is not met or if the probability that the lateral TSE exceeds 0.6 NM is greater than 10-5.

A.3.5 Signal in Space (SIS). During Global Navigation Satellite System (GNSS) operations on

the initial, intermediate, and missed approach segments, the aircraft navigation equipment must provide an alert if the probability of SIS errors causing a lateral position error greater than 2 NM exceeds 10-7 per hour. During GNSS operations on the FAS, the aircraft navigation equipment must provide an alert if the probability of SIS errors causing a Navigation System Error (NSE) greater than 0.6 NM exceeds 10-7 per hour.

Note 1: There are no RNP requirements for the missed approach if it is based on conventional means (VOR, DME, and NDB) or on dead reckoning.

Note 2: Aircraft with an approved multisensor RNP system where GNSS integrity is incorporated into an RNP integrity alert consistent with DO-236( ) do not require a separate GNSS integrity alert when performance cannot be met.

A.3.6 Path Definition. Aircraft performance is evaluated around the path defined by the

published procedure and RTCA/DO-236C.

A.3.7 Functional Requirements of Navigation Displays. The following navigation displays and

functions are required, as installed in accordance with AC 20-138( ) or equivalent system installation advisory material. Navigation data, including a TO/FROM indication and a failure indicator, must be displayed on a lateral deviation display, course deviation indicator (CDI), electronic horizontal-situation indicator (EHSI), and/or a navigation map display. These must be used as primary flight instruments for aircraft navigation, for maneuver anticipation, and for failure/status/integrity indication.

A.3.7.1 RNP systems using TO/TO navigation algorithms do not require a navigation display with a TO/FROM indication during RNP instrument procedures. Displays supporting TO/TO navigation computers can fully comply with all RNP-related criteria in this AC without a TO/FROM indication. At a minimum, the navigation display supporting a TO/TO RNP system should

A.3.7 Functional Requirements of Navigation Displays. The following… › A.3.7.2 A non-numeric lateral deviation display (e.g., CDI, EHSI), with…

3/7/16 AC 90-105A Appendix A

display the active waypoint and active waypoint name. However, TO/TO RNP systems must have the ability accommodate route discontinuities and continue providing navigation information.

A.3.7.2 A non-numeric lateral deviation display (e.g., CDI, EHSI), with TO/FROM indication and a failure annunciation, used as primary flight instruments for aircraft navigation, for maneuver anticipation, and for failure/status/integrity indication, should have the following attributes:

1. The displays must be visible to the pilot and located in the primary field of view (FOV) when looking forward along the flightpath.

2. The lateral deviation display must have a full-scale deflection suitable for the current phase of flight and must be based on the TSE requirement. Scaling of ± 1 NM for the initial, intermediate, and missed approach segments and ±0.3 NM for the final segment is acceptable. It is also acceptable for the scaling to be more conservative than the TSE (e.g., ±0.3 NM for the initial, intermediate, and missed approach segments).

3. The display scaling may be set automatically by default logic or set to a value obtained from a navigation database. The full-scale deflection value must be known or must be available for display to the pilot commensurate with approach values.

4. The lateral deviation display must be automatically slaved to the RNP-computed path. It is recommended that the course selector of the deviation display be automatically slewed to the RNP-computed path.

Note: This does not apply for installations where an electronic map display contains a graphical display of the flightpath and path deviation.

5. As an alternate means, a navigation map display must provide equivalent functionality to a lateral deviation display with appropriate map scales (scaling may be set manually by the pilot). To be approved as an alternative means, the navigation map display must be shown to meet the TSE requirements and be located in the primary FOV.

6. It is not necessary for navigation displays, particularly primary flight displays (PFD), to include an Actual Navigation Performance (ANP) or Estimate of Position Error (EPE) value. The displays only need to provide an alert if the RNP for the operation cannot be met.

3/7/16 AC 90-105A Appendix A

A.3 Performance and Functionality Requirements for RNP APCH Systems. › A.3.8 System Capabilities. The following system capabilities are…

A.3.8 System Capabilities. The following system capabilities are required as a minimum:

1. The capability to continuously display to the pilot flying (PF), on the primary flight instruments for navigation of the aircraft (primary navigation display), the RNP APCH-computed desired path, and aircraft position relative to the path. For operations where the required minimum flightcrew is two pilots, a means for the pilot monitoring (PM) to verify the desired path; and the aircraft position relative to the path must also be provided.

2. A navigation database, containing current navigation data officially promulgated for civil aviation, which can be updated in accordance with the Aeronautical Information Regulation and Control (AIRAC) cycle. The stored resolution of the data must be sufficient to achieve the required track-keeping accuracy. The database must be protected against pilot modification of the stored data.

3. The means to display the validity period of the navigation data to the pilot.

4. The means to retrieve and display data stored in the navigation database relating to individual waypoints and navigation aids, to enable the pilot to verify the route to be flown.

5. Capability to load from the database into the RNP system the whole approach to be flown. The approach must be loaded from the database, into the RNP system, by its name.

Note: Numeric values for database defined procedures must be automatically loaded from the RNP system database.

6. The means to display the following items, either in the pilot’s primary FOV, or on a readily accessible display page:

• Distance between flight plan waypoints,

• Distance to go to the waypoint selected by the pilot,

• Active navigation sensor type,

• The identification of the active (To) waypoint,

• The ground speed or time to the active (To) waypoint, and

• The distance and bearing to the active (To) waypoint.

7. The capability to execute a “Direct to” function.

8. The capability for automatic leg sequencing with display to the pilots.

9. The capability to execute an RNP APCH instrument approach procedure (IAP) extracted from the onboard database, including the capability to execute flyover and flyby turns.

3/7/16 AC 90-105A Appendix A

10. The capability to automatically execute leg transitions and maintain tracks consistent with the following Aeronautical Radio, Inc. (ARINC) 424 path terminators, or their equivalent:

A.5 Special Characteristics of RNP APCH Instrument Approaches. › A.5.2 Lines of Minima. RNP APCH may have multiple lines of minima. This…

• Initial Fix (IF),

• Track to Fix (TF), and

• Direct to Fix (DF).

Note: Path terminators are defined in ARINC Specification 424, and their application is described in more detail in RTCA, Inc. documents, DO-236( ) and DO-201( ).

11. The capability to display an indication of the RNP system failure, in the pilot’s primary FOV.

12. The capability to indicate to the crew when the NSE or Position Estimation Error (PEE) alert limit is exceeded (alert provided by the onboard performance monitoring and alerting function).

13. The system must allow for a means to become established prior to the final approach fix (FAF) on an instrument landing system (ILS) or Ground Based Augmentation System (GBAS) Landing System (GLS) with minimal overshoot or undershoot.

A.3.9 FD/AP. For aircraft equipped with FD and/or AP, it is recommended the FD is engaged

and/or AP remain coupled for RNP APCH. If the lateral TSE cannot be demonstrated without these systems, then coupling becomes mandatory. In this instance, operating guidance must indicate FD engagement and/or automatic pilot coupling from the RNP system is mandatory for approaches.

A.4 Database.

A.4.1 Database Integrity. The operator must ensure their navigation database supplier possesses

a Type 2 Letter of Acceptance (LOA) in accordance with AC 20-153( ), Acceptance of Aeronautical Data Processes and Associated Databases.

A.4.2 Path Terminators. The database supplier should not substitute path terminators in lieu of

those specified in the original State Aeronautical Information Publication (AIP) data.

A.5 Special Characteristics of RNP APCH Instrument Approaches.

A.5.1 Navigational Aid (NAVAID) Infrastructure. GPS is the primary navigation system to

support RNP APCH procedures. DME/DME-based systems are not acceptable for RNP APCH. The missed approach segment may be based upon a conventional NAVAID (e.g., VOR, DME, and NDB).

A.5.2 Lines of Minima. RNP APCH may have multiple lines of minima. This appendix

addresses the LNAV and LNAV/vertical navigation (VNAV) lines of minima. In

3/7/16 AC 90-105A Appendix A

addition, the use of baro-VNAV for an RNP APCH to the LNAV/VNAV minima is addressed in Appendix B. Reference AC 90-107( ) for an RNP APCH to the LP and LPV lines of minima.

A.6.4 LNAV/VNAV Line of Minima Qualification. › A.6.4.2 Multisensor Systems. Multisensor systems using TSO-C129a Class…

Note: AC 20-138( ) addresses aircraft integration that includes baro-VNAV and GPS/Satellite-based Augmentation System (SBAS) and/or GPS/Ground Based Augmentation System (GBAS) for vertical guidance.

A.6 Aircraft Eligibility for RNP APCH Operations.

A.6.1 Introduction. The OEM or the holder of installation approval for the aircraft

(e.g., STC holder) must demonstrate compliance with the appropriate provisions of this AC to the Federal Aviation Administration (FAA), and the approval can be documented in manufacturer documentation (e.g., SLs, etc.). AFM/RFM entries are not required.

A.6.2 System Eligibility for RNP APCH LNAV and LNAV/VNAV Minima. Systems meeting

the requirements in AC 20-138( ) are eligible for RNP APCH operations. Aircraft qualified by AC 90-101( ), Approval Guidance for RNP Procedures with AR, are considered qualified for RNP APCH operations without further examination.

A.6.3 LNAV Line of Minima Qualification.

A.6.3.1 Stand-Alone Systems. Stand-alone systems meeting TSO-C129a Class A1 or TSO-C146( ) Class 1, 2, or 3 meet the aircraft qualification requirements for RNP APCH operations using the LNAV line of minima provided the instrument flight rules (IFR) installations were performed in accordance with AC 20-138( ).

A.6.3.2 Multisensor Systems. Multisensor systems using TSO-C196, TSO-C129a Class B1, B3, C1, or C3, or TSO-C145 Class 1, 2, or 3 sensors meet the aircraft qualification requirements for RNP APCH operations using the LNAV line of minima, provided the installations meet the criteria of this AC and Appendix A, the associated FMS complies with TSO-C115b or later and are installed in accordance with AC 20-138( ).

A.6.4 LNAV/VNAV Line of Minima Qualification.

A.6.4.1 Stand-Alone Systems. Stand-alone TSO-C146 Class 2 or 3 systems meet the aircraft qualification requirements for RNP APCH operations using the LNAV/VNAV line of minima provided that the installations meet at least the performance and functional requirements of this AC.

A.6.4.2 Multisensor Systems. Multisensor systems using TSO-C129a Class B1, B3, C1, or C3 sensors, TSO-C145 Class 1 sensors, or TSO-C196( ) with baro-VNAV meet the aircraft qualification requirements for RNP APCH operations using the LNAV/VNAV line of minima provided the installations meet the requirements of this AC (including Appendix A and Appendix B). Multisensor systems using TSO-C145 Class 2 or 3 meet the requirements for

A.7.1 Preflight Planning. › A.7.1.4 The flightcrew may notice a slight difference between the…

3/7/16 AC 90-105A Appendix A

RNP APCH operations to LNAV/VNAV minima without baro-VNAV when using SBAS-based vertical guidance. The RNP systems including the FMS must be installed in accordance with AC 20-138( ) and the associated FMS must comply with TSO-C115b or later.

A.6.4.3 Demonstrations. Demonstration of aircraft performance in accordance with AC 20-138( ) does not constitute operations approval to conduct RNP operations.

A.7 Operational Considerations.

A.7.1 Preflight Planning.

A.7.1.1 Operators and pilots intending to conduct operations on RNP APCH IAPs must file the appropriate flight plan suffixes.

A.7.1.2 At system initialization, pilots must confirm the navigation database is current and includes appropriate procedures. Pilots must also verify that the aircraft position is correct.

Note 1: Navigation databases are expected to be current for the duration of the flight. If the AIRAC cycle is due to change during flight, operators and pilots should establish procedures to ensure the accuracy of navigation data, including suitability of navigation facilities used to define the routes and procedures for flight. This may be accomplished by verifying electronic data against paper or Electronic Flight Bag (EFB) products. One acceptable means is to compare aeronautical charts (new and old) to verify navigation fixes prior to dispatch. If an amended chart (hard copy amendment not in the database) is published for the procedure, the database must not be used to conduct the operation.

Note 2: On U.S. IAPs only, the “Procedure Amendment Effective Date” may be used to ensure the accuracy of the navigation data contained in an expired database. If the Procedure Amendment Effective Date falls on or after the navigation database expiry date, the procedure should not be flown using the out-of-date database.

A.7.1.3 Pilots must verify proper entry of their air traffic control (ATC)-assigned route upon initial clearance and any subsequent change of route. Pilots must ensure the waypoint sequence depicted by their navigation system matches their assigned route and the route depicted on the appropriate chart(s).

A.7.1.4 The flightcrew may notice a slight difference between the navigation information portrayed on the chart and their primary navigation display. Differences of 3 degrees or less may result from equipment manufacturer’s application of magnetic variation and are operationally acceptable.

A.7.2 During the Procedure. Pilots must comply with any instructions or… › A.7.2.3 All pilots are expected to maintain procedure centerline, as…

3/7/16 AC 90-105A Appendix A

A.7.1.5 Manually selecting aircraft bank limiting functions can reduce the aircraft’s ability to maintain the desired track (DTK) and is not recommended.

A.7.1.6 The aircraft RNP APCH capability is dependent on operational aircraft equipment. The flightcrew must be able to assess the impact of equipment failure on the anticipated RNP APCH operation and take appropriate action. When the dispatch of a flight is predicated on flying an RNP APCH requiring the use of the AP or FD at the destination and/or alternate, the operator must determine that the AP and/or FD is installed and operational.

A.7.1.7 The availability of the navigation infrastructure, required for the intended routes, procedures, or instrument approaches (including any non-RNP contingencies) must be confirmed for the period of intended operations using all available information. Since GPS integrity (e.g., receiver autonomous integrity monitoring (RAIM) or SBAS signal) is required, the availability of these should also be determined, as appropriate (see Chapter 9, Flight Planning, of this AC).

A.7.1.8 The pilot must notify ATC of any loss of the RNP APCH capability, together with the proposed course of action. If unable to comply with the requirements of an RNP APCH procedure, pilots must advise the Air Traffic Service (ATS) as soon as possible. The loss of RNP APCH capability includes any failure or event causing the aircraft to no longer satisfy the RNP APCH requirements of the procedure. The operator should develop contingency procedures in order to react safely following the loss of the RNP APCH capability during the approach.

A.7.2 During the Procedure. Pilots must comply with any instructions or procedures

identified by the manufacturer as necessary to comply with the performance requirements in this AC.

A.7.2.1 Pilots must confirm the system has initiated transition from terminal mode to approach mode by 2 NM prior to the FAF.

A.7.2.2 The appropriate displays must be selected so that the following information can be monitored:

1. The RNP APCH computed DTK and

2. Aircraft position relative to the path cross-track (XTK) deviation for FTE monitoring.

A.7.2.3 All pilots are expected to maintain procedure centerline, as depicted by onboard lateral deviation indicators and/or flight guidance during the approach procedure unless authorized to deviate by ATC or under emergency conditions.

3/7/16 AC 90-105A Appendix A

A.7.2.4 While operating on RNP APCH segments, pilots are encouraged to use FD and/or AP in LNAV mode and VNAV mode, if available.

A.7.2 During the Procedure. Pilots must comply with any instructions or… › A.7.2.10 Flightcrew accomplishing RNP APCH IAPs (RNAV (GPS) or RNAV…

A.7.2.5 For aircraft requiring two pilots, crews must verify that each pilot’s altimeter has the current setting before beginning the final approach of an RNP APCH procedure. The crew must also observe any operational limitations associated with the source(s) for the altimeter setting and the latency of checking and setting the altimeters approaching the FAF.

A.7.2.6 Although scaling should change automatically, pilots of aircraft with a lateral deviation indicator (e.g., CDI) must ensure that lateral deviation indicator scaling (full-scale deflection) is suitable for the various segments of the procedure (i.e., ±1.0 NM for the initial and intermediate segments, ±0.3 NM for the FAS, and ±1.0 NM for the missed approach segment).

A.7.2.7 RNP APCH procedures require flightcrew monitoring of lateral and, if installed, vertical track deviations on the pilot’s PFDs to ensure the aircraft remains within the bounds defined by the procedure.

A.7.2.8 The flightcrew must initiate a go-around if either a lateral or vertical deviation is too large unless the visual conditions required to continue the approach exist between the aircraft and the runway of intended landing.

A.7.2.9 For normal operations, XTK/deviation (the difference between the displayed computed path and the displayed aircraft position relative to the path) should be limited to the values specified for the segment of the procedure (i.e., 0.5 NM for the initial and intermediate segments, 0.25 NM for the FAS, and 0.5 NM for the missed approach segment). Brief deviations from this standard (e.g., overshoots or undershoots) during and immediately after turns, up to a maximum of one times the RNP value (i.e., 1.0 NM for the initial and intermediate segments) are allowable.

A.7.2.10 Flightcrew accomplishing RNP APCH IAPs (RNAV (GPS) or RNAV

(GNSS) are required to monitor lateral and, if approved for operational credit, vertical guidance deviations. For baro-VNAV approach operations on an RNP APCH using the LNAV/VNAV minimums, aircraft qualified using AC 20-138( ) must allow the pilot to readily distinguish if the XTK deviation exceeds the RNP value (or a smaller value) or if the vertical deviation exceeds 75 feet (or a smaller value). This information must be published in the AFM, a STC, or verified by the Aircraft Evaluation Division (AED).

Note: Aircraft approved under previous AC guidance using baro-VNAV with LNAV/VNAV minimums, the legacy vertical deviation limits of +100/-50 feet remains valid.

A.8 Go-Around or Missed Approach. › A.8.1 Visual References. Unless the pilot has in sight the visual…

3/7/16 AC 90-105A Appendix A

A.8 Go-Around or Missed Approach.

A.8.1 Visual References. Unless the pilot has in sight the visual references required to continue

the approach, the procedure must be discontinued if any of the following conditions occur:

1. The navigation display is flagged invalid,

2. Loss of integrity alerting function,

3. The integrity alerting function is activated before passing the FAF, or

4. Lateral or vertical deviation exceeds the limits in paragraphs A.7.2.6, A.7.2.9, and A.7.2.10.

B.3 Aircraft Eligibility. › B.3.2 Baro-VNAV Capability. Eligible aircraft are those with an…

3/7/16 AC 90-105A Appendix B

APPENDIX B. USE OF BAROMETRIC VERTICAL NAVIGATION (BARO-VNAV)

FOR REQUIRED NAVIGATION PERFORMANCE APPROACH (RNP APCH)

OPERATIONS

B.1 Introduction. This appendix addresses those systems using barometric altitude and

navigation system information in the definition of vertical flightpaths and vertical tracking to a path. Baro-VNAV provides vertical path information defined by vertical angles or altitudes at fixes in the RNP APCH procedure. This specification provides system and operational criteria for the approval of a vertical navigation (VNAV) system using barometric altimetry as a basis for its vertical navigation capability.

B.2 Applicability. This appendix applies to all operators conducting baro-VNAV operations

under Title 14 of the Code of Federal Regulations (14 CFR) parts 91, 91 subpart K (part 91K), 121, 125, 129, and 135 within the U.S. National Airspace System (NAS). This appendix also provides guidance for approval to use baro-VNAV equipment to perform 14 CFR part 97 Area Navigation (RNAV) (Global Positioning System (GPS)) or GPS instrument approach procedures (IAP) published with a lateral navigation (LNAV)/VNAV line of minima with a decision altitude (DA).

B.3 Aircraft Eligibility.

B.3.1 Required Navigation Performance (RNP) System Capability. Eligible aircraft are those

which meet the performance and functional requirements outlined in Appendix A, Qualification Criteria for Required Navigation Performance Approach (RNP APCH) Operations, and Appendix C, Qualification Criteria for Required Navigation Performance (RNP) 1 (Terminal) Operations, as appropriate for the RNP operation.

B.3.2 Baro-VNAV Capability. Eligible aircraft are those with an Airplane Flight Manual

(AFM)/Rotorcraft Flight Manual (RFM) or Airplane Flight Manual Supplement (AFMS)/Rotorcraft Flight Manual Supplement (RFMS) which explicitly states that the VNAV system is approved for approach operations in accordance with Advisory Circular (AC) 20-138( ), Airworthiness Approval of Positioning and Navigation Systems. Aircraft accomplishing RNP APCH operations (RNAV (GPS) or RNAV (Global Navigation Satellite System (GNSS)) are required to monitor lateral and, if approved for operational credit, vertical guidance deviations. Aircraft qualified using AC 20-138( ) must allow the pilot to readily distinguish if the cross-track (XTK) deviation exceeds the RNP value (or a smaller value) or if the vertical deviation exceeds 75 feet (or a smaller value). Aircraft with an authorization for Required Navigation Performance Authorization Required (RNP AR) operations are considered eligible for baro-VNAV operations conducted in accordance with this AC.

Note: Aircraft approved under previous AC guidance using baro-VNAV with LNAV/VNAV minimums, the legacy vertical deviation limits of +100/-50 feet remains valid.

3/7/16 AC 90-105A Appendix B

B.3.2.1 Part 91 operators should review their AFM or AFMS to establish navigation system eligibility as detailed in paragraph B.3. Once the operator establishes system eligibility, the operator should take steps to ensure that baro-VNAV approach operations are conducted in accordance with the guidance in paragraphs B.4 and B.5. After these actions have been completed, the operator may begin to conduct baro-VNAV approach operations to the published LNAV/VNAV line of minima. A Letter of Authorization (LOA) is not required when eligibility is based on the AFM and provisions of this AC.

B.3.5 Eligibility Not Based on the AFM or AFMS (Special Approval). The… › B.3.5.2 For parts 91K, 121, 125, 129, and 135 operators, the FAA will…

B.3.3 Documentation. Parts 91K, 121, 125, 129, and 135 operators should present the following

documentation to the responsible Flight Standards office:

1. Sections of the AFM or AFMS which document RNAV/RNP airworthiness approval for approach operations in accordance with B.3; and

2. Sections of the training and operations manuals which reflect the operating policies of B.4 and B.5.

B.3.4 Satisfaction. Once the operator has addressed the guidance in these paragraphs to the

satisfaction of the responsible Flight Standards office, the operator may begin to conduct baro-VNAV approach operations to the published LNAV/VNAV line of minima.

B.3.5 Eligibility Not Based on the AFM or AFMS (Special Approval). The operator may not be

able to determine baro-VNAV approach eligibility from the AFM or AFMS. In this case, a part 91 operator should request that the assess the equipment for baro-VNAV approach eligibility while parts 91K, 121, 125, 129, and 135 operators should request that the responsible Flight Standards office make the eligibility assessment. The operator should provide the responsible Flight Standards office with the baro-VNAV system make, model, and part number, any evidence of instrument flight rules (IFR) navigation system approval, and pertinent information from crew operating procedures. If the responsible Flight Standards office is unable to determine equipment eligibility, it should forward the request and supporting data to the Aircraft Evaluation Division (AED). The AED will verify that the aircraft and RNP system meet the criteria for baro-VNAV, and that the system can safely fly specified VNAV paths associated with IAPs applying a DA rather than a minimum descent altitude (MDA). The AED will provide written documentation (i.e., amend Flight Standards Bulletin Report or other official documentation) to verify the eligibility of that equipment. Additionally, the Aircraft Certification Service (AIR) may be consulted.

B.3.5.1 For part 91 operators, if the FAA determines that the navigation equipment is eligible for baro-VNAV instrument approach operations to a published DA, the Flight Standards District Office (FSDO) will provide documentation that the aircraft equipment is approved for these baro-VNAV operations.

B.3.5.2 For parts 91K, 121, 125, 129, and 135 operators, the FAA will attempt to establish system eligibility and ensure that the operator’s training and operations manuals reflect the operating policies of paragraphs B.4 and B.5. Once these steps are successfully completed, the operator may begin using

B.4.5 Altimetry Cross-Check. › B.4.5.2 Where two pilots are required, the flightcrew must complete an…

3/7/16 AC 90-105A Appendix B

this baro-VNAV equipment to fly to the LNAV/VNAV DA as published on the procedure.

B.4 Operating Procedures (General). For baro-VNAV approach operations, the flightcrew

should be familiar with the following operating procedures.

B.4.1 Actions at DA. The pilot/crew is expected to fly the aircraft along the published vertical

path and execute a Missed Approach Procedure (MAP) upon reaching DA, unless the visual references specified in part 91, § 91.175 for continuing the approach are present.

B.4.2 Temperature Limitation. Because of the pronounced effect of nonstandard temperature on

baro-VNAV systems, RNAV (GPS) approaches with an LNAV/VNAV line of minima should contain a low and high temperature limitation. Uncompensated baro-VNAV systems may not operate to the LNAV/VNAV DA when the actual temperature is below or above the temperature limitations. The temperature limitation will be shown as a note on the procedure. If the aircraft contains a temperature compensation capability, manufacturer instructions should be followed for use of the baro-VNAV function.

B.4.3 VNAV Path Mode Selection. Crews should be knowledgeable on selection of the

appropriate vertical mode(s) that command VNAV via the published vertical path. Other vertical modes such as Vertical Speed (VS) are not applicable to baro-VNAV approach operations.

B.4.4 Remote Altimeter Setting Restriction. Use of baro-VNAV to a DA is not authorized with

a remote altimeter setting. A current altimeter setting for the landing airport is required. Where remote altimeter minima are shown, the VNAV function may be used but only to the published LNAV MDA.

B.4.5 Altimetry Cross-Check.

B.4.5.1 Pilots must verify the current local altimeter at the airport of intended landing is set not later than the final approach fix (FAF). Remote altimeter settings are not allowed.

B.4.5.2 Where two pilots are required, the flightcrew must complete an altimetry cross-check ensuring both pilots’ altimeters agree within ±100 feet prior to the FAF after receiving the current local altimeter setting at the airport of intended landing. If the altimetry cross-check fails then the procedure should not be conducted or, if in progress, it must not be continued. The flightcrew procedures should also address actions to take if a comparator warning for the pilots’ altimeters occurs while conducting a RNP APCH procedure.

Note: This operational cross-check is not necessary if the aircraft automatically compares the altitudes to within 100 feet.

Appendix B. › B.5 Pilot Knowledge. Pilot knowledge should include the following:

3/7/16 AC 90-105A Appendix B

B.4.6 VNAV System Cross-Check. For baro-VNAV operations to the LNAV/VNAV line of

minima, pilots must cross-check the vertical guidance displayed by the navigation system against other available data at the FAF. If the difference between the displayed glidepath and the published altitude at FAF exceeds 75 feet, the LNAV/VNAV line of minima may not be used. Pilots should revert to the LNAV line of minima and comply with any published stepdown fix altitude.

Note 1: This cross-check is not required when GPS/Satellite-based Augmentation System (SBAS) vertical guidance is used with the LNAV/VNAV line of minima.

Note 2: For systems that provide temperature compensation capability, the displayed temperature compensated glidepath should be compared to the temperature compensated altitude computed by system when crossing the FAF.

Note 3: This cross-check may be accomplished by ensuring that the glidepath displacement from center does not exceed 75 feet when crossing the FAF at the published crossing altitude, or if descending on a centered glidepath, ensuring that the aircraft’s altitude crossing the FAF is within 75 feet of the altitude published at the FAF.

Note 4: Aircraft approved under previous AC guidance using baro-VNAV with LNAV/VNAV minimums, the legacy vertical deviation limits of +100/-50 feet remains valid.

B.5 Pilot Knowledge. Pilot knowledge should include the following:

1. The aeronautical instrument approach chart that will promulgate LNAV/VNAV procedures including, but not limited to, temperature and altimeter source limitations for baro-VNAV operations.

2. Barometric altimeters are calibrated to indicate true altitude under International Standard Atmosphere (ISA) conditions.

3. The effect of temperature on true altitude vs. indicated altitude (i.e., warmer than ISA, the true altitude will be higher than indicated altitude and colder than ISA, the true altitude will be lower than indicated altitude).

4. Understanding the VNAV system capabilities relating to geometric or performance-based VNAV paths.

5. Understanding the use of VNAV angles and altitude restrictions during arrival.

6. Interpretation of electronic displays and symbols.

7. Levels of automation, mode annunciations, changes, alerts, interactions, reversions, degradation.

8. Turn anticipation with consideration to speed and altitude effects.

9. Functional integration with other aircraft systems.

3/7/16 AC 90-105A Appendix B

10. The meaning of vertical path discontinuities as well as related flightcrew procedures.

11. VNAV equipment operating procedures, including how to determine vertical-track error/deviation.

12. Procedures for change in arrival/runway assignment.

13. Understanding of possible conflicts between aircraft performance and flight management system (FMS) functions (e.g., airspeed and descent angles).

14. Failures and mode reversions, which adversely impact the aircraft’s ability to conduct baro-VNAV approach operations.

15. Contingency downgrade actions (i.e., reverting to LNAV MDA following VNAV failures).

16. Contingency abort actions (i.e., understand which failures and performance parameters require discontinuing the approach and executing an early missed approach).

17. Altimeter cross-check procedures.

18. VNAV system-specific information, including VNAV vertical deviation scaling provided in the Final Approach Segment (FAS). Pilot and flightcrews should be knowledgeable in applying this scaling to the baro-VNAV display cross-check required at the FAF when conducting an approach to the LNAV/VNAV line of minima.

C.2 Aircraft and System Requirements for RNP Terminal Operations. › C.2.3 Qualified Avionics Equipment and Airworthiness Approval. Aircraft…

3/7/16 AC 90-105A Appendix C

APPENDIX C. QUALIFICATION CRITERIA FOR REQUIRED NAVIGATION

PERFORMANCE (RNP) 1 (TERMINAL) OPERATIONS

C.1 Introduction. This appendix provides guidance on the performance and functional

requirements for systems used to conduct RNP in terminal operations. This appendix includes:

1. Instrument departure procedures (DP) RNP Obstacle Departure Procedures (ODP),

2. RNP Standard Instrument Departures (SID), and

3. RNP Standard Terminal Arrival Routes (STAR).

C.2 Aircraft and System Requirements for RNP Terminal Operations.

C.2.1 Performance and Airworthiness Guidance. Refer to Advisory Circular (AC) 20-138( ),

Airworthiness Approval of Positioning and Navigation Systems, for performance and airworthiness guidance on aircraft and system criteria.

C.2.2 Statement of Compliance (SOC). Aircraft with an SOC with the criteria in this AC or

AC 20-138( ) in their Airplane Flight Manual (AFM), Airplane Flight Manual Supplement (AFMS), pilot’s operating handbook (POH), or the operating manual for their avionics meet the performance and functional requirements of this AC.

C.2.3 Qualified Avionics Equipment and Airworthiness Approval. Aircraft with the following

avionics equipment and an appropriate airworthiness approval automatically qualify for RNP 1 capability without further documentation by virtue of the avionics Technical Standard Order (TSO) and airworthiness approval:

1. Global Positioning System (GPS) stand-alone systems approved in accordance with TSO-C146( ) operational Class 1, 2, or 3.

2. A TSO-C115c light management system (FMS) (or later revision) with a TSO-C129( ) Class B1 or C1, TSO-C145( ), or TSO-C196( ) sensor.

Note: TSO-C129a has been cancelled, but equipment with an existing TSO-C129a Technical Standard Order Authorization (TSOA) may still be installed.

3. A TSO-C115b FMS using a TSO-C129( ) Class B1 or C1, TSO-C145( ), or TSO-C196( ) sensor with documented compliance to the RNP requirements in RTCA, Inc.’s document, RTCA/DO-236 (revision ‘B’ or later) or RTCA/DO-283A.

4. Aircraft with a Required Navigation Performance Authorization Required (RNP AR) approval per AC 90-101( ), Approval Guidance for RNP Procedures with AR, or AC 20-138( ).

3/7/16 AC 90-105A Appendix C

C.2.3.1 Aircraft/equipment with approval under AC 90-100( ), U.S. Terminal and En Route Area Navigation (RNAV) Operations, for use of GPS are approved under this AC for RNP 1 operations.

Continue reading ↓ 120 of 329 passages shown