8-1 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-2
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-3
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);
8-4
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-1 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-2
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-3
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-4 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.
10-1 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).
10-2
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.
11-1 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.
12-1 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.