Advisory Circular (AC) No. 700-025

From: Transport Canada

From Transport Canada

Required Navigation Performance 1 (RNP 1)

Issuing Office: Standards Document No.: AC 700-025
File Classification No.: Z 5000-34 Issue No.: 01
RDIMS No.: 6410963-V29 Effective Date: 2013-05-01

Table of Contents

1.0 Introduction

  1. This Advisory Circular (AC) is provided for information and guidance purposes. It describes an example of an acceptable means, but not the only means, of demonstrating compliance with regulations and standards. This AC on its own does not change, create, amend or permit deviations from regulatory requirements, nor does it establish minimum standards.

1.1 Purpose

  1. The purpose of this AC is to inform the aviation industry that air operators and private operators may now obtain a Canadian authorization by Operations Specification (Ops Spec) 618 for Required Navigation Performance 1 (RNP 1). This authorization will enable Canadian air operators or private operators to operate within airspace designated as RNP 1, subject to the applicable requirements of the Ops Spec. The final step in the operational approval is the issuance of the Ops Spec to the air operator or private operator. This Ops Spec will also form the basis upon which a foreign National Aviation Authority (NAA) may authorize, within their jurisdiction, a Canadian air operator or private operator to operate in RNP 1 airspace.

    Note: Ops Spec 618 does not grant the authority to conduct the Radius to Fix (RF) segments which may be part of some RNP 1 procedures. The authority to conduct RF segments is granted by Ops Spec 623 and the guidance associated with such procedures can be found in AC 700-027.

1.2 Applicability

  1. This AC applies to Canadian air operators holding an Air Operator Certificate issued under Part VII of the Canadian Aviation Regulations (CARs) and to private operators holding a Private Operator Certificate issued under Subpart 604 of the CARs, who wish to operate in airspace requiring RNP 1 navigation performance. These will be commonly referred to as “operator” in this AC.
  2. RNP 1 operational authorization is required for operations within some airspace.
  3. This document is also applicable to all Transport Canada Civil Aviation (TCCA) employees, to individuals and organizations when they are exercising privileges granted to them under an External Ministerial Delegation of Authority. This information is also available to the aviation industry at large for information purposes.

1.3 Description of Changes

  1. Not applicable.

2.0 References and Requirements

2.1 Reference Documents

  1. The following reference material may be consulted for information purposes:
    1. Part V of the Canadian Aviation Regulations (CARs)—Transport Category Aeroplanes;
    2. Subpart 604 of the CARs—Private Operator Passenger Transportation;
    3. Subpart 702 of the CARs—Aerial Work;
    4. Subpart 703 of the CARs – Air Taxi;
    5. Subpart 704 of the CARs—Commuter Operations;
    6. Subpart 705 of the CARs—Airline Operations;
    7. Standard 624 of the CARs — Private Operator Passenger Transportation;
    8. Standard 722 of the Commercial Air Services Standards (CASS)—Aerial Work;
    9. Standard 723 of the CASS – Air Taxi;
    10. Standard 724 of the CASS—Commuter Operations;
    11. Standard 725 of the CASS—Airline Operations;
    12. Operations Specification 618, Required Navigation Performance 1 (RNP 1) Airspace;
    13. Transport Canada Publication (TP) 308, Criteria for the Development of Instrument Procedures;
    14. Advisory Circular 700-027, Radius to Fix (RF) Path Terminator;
    15. Federal Aviation Administration Advisory Circular (FAA AC) 90-105, Approval Guidance for RNP Operations and Barometric Vertical Navigation in the U.S. National Airspace System;
    16. International Civil Aviation Organization (ICAO) Doc 4444,Procedures for Air Navigation Services – Air traffic management (PANSATM);
    17. ICAO Doc. 9613, Performance Based Navigation (PBN) Manual, Volume II Part C Implementing RNP 1; and
    18. ICAO Doc. 7030, Regional Supplementary Procedures.

2.2 Cancelled Documents

  1. Not applicable.
  2. By default, it is understood that the publication of a new issue of a document automatically renders any earlier issues of the same document null and void.

2.3 Definitions and Abbreviations

  1. The following definitions are used in this document:
    1. Advisory Circular: A document providing an example of an acceptable means, but not the only means, of demonstrating compliance with regulations and standards.
    2. Aircraft-based Augmentation System: A system which augments and/or integrates the information obtained from other Global Navigation Satellite System (GNSS) elements with information available on board the aircraft. The most common form of Aircraft based Augmentation System (ABAS) is the receiver autonomous integrity monitoring (RAIM).
    3. Air navigation services: This term includes air traffic management (ATM), communications, navigation and surveillance systems (CNS); meteorological services for air navigation (MET); search and rescue (SAR); and aeronautical information services (AIS). These services are provided to air traffic during all phases of operations (approach, aerodrome and en route).
    4. Air navigation services provider: An independent entity established for the purpose of operating and managing air navigation services, and empowered to manage and use the revenues it generates to cover its costs. In Canada, this function is normally performed by NAV CANADA.
    5. Area Navigation: A navigation system that allows aircraft to operate on any desired flight track within the coverage of ground- or space-based navigation aids, or within the limits of the capability of self-contained aids, or a combination of both methods. Area navigation includes performance-based navigation as well as other operations that are not contemplated in the definition of performance-based navigation.
      1. Required Navigation Performance (RNP): Area navigation system that includes the requirement for on-board performance monitoring and alerting, designated by the prefix RNP, e.g. RNP 4, RNP APCH.
      2. Area Navigation (RNAV): Area navigation system that does not include the requirement for on-board performance monitoring and alerting, designated by the prefix RNAV, e.g. RNAV 5, RNAV 1.
    6. Global Navigation Satellite System: A generic term used by the International Civil Aviation Organization (ICAO) to define any global position, speed, and time determination system that includes one or more main satellite constellations, such as GPS and the global navigation satellite system (GLONASS), aircraft receivers and several integrity monitoring systems, including ABAS, satellite-based augmentation systems (SBAS), such as the wide area augmentation systems (WAAS), and ground-based augmentation systems (GBAS), such as the local area augmentation system (LAAS).
    7. Global Positioning System: The global navigation satellite system of the United States is a satellite-based radio navigation system that uses precise distance measurements to determine position, speed, and time in any part of the world. The GPS is made up of three elements: the spatial, the control, and the user elements. The GPS spatial segment nominally consists of at least 24 satellites in 6 orbital planes. The control element consists of 5 monitoring stations, 3 ground antennas, and one main control station. The user element consists of antennas and receivers that provide the user with position, speed, and precise time.
    8. Navigation specification: A set of requirements needed to implement and support performance based navigation within a defined airspace.

    9. Performance Based Navigation: Area navigation based on performance requirements for aircraft operating along an Air Traffic Service (ATS) route, on an instrument approach procedure or in a designated airspace.

      Note. The performance requirements of a navigation specification (RNAV specification or RNP specification) are expressed in terms of accuracy, integrity, continuity, availability and functionality needed for the proposed operation in the context of a particular airspace concept.

    10. RNP operations: Aircraft operations that use an RNP system for RNP applications.
    11. RNP system: An area navigation system which includes on-board performance monitoring and alerting.
    12. Radius to Fix Path Terminator: A specific fixed-radius curved path in a terminal and approach procedure intended to be applied where an accurate repeatable and predictable ground path is required. The portion of the procedure which contains the radius to fix path terminator may be referred to as an RF leg.
    13. Receiver Autonomous Integrity Monitoring: A form of ABAS whereby a GNSS receiver processor determines the integrity of the GNSS navigation signals using only GPS signals or GPS signals augmented with altitude (baro-aiding). This determination is achieved by a consistency check among redundant pseudo-range measurements. At least one additional satellite with the correct geometry needs to be available, over and above that needed for the position estimation, for the receiver to perform the RAIM function.
    14. Satellite-based augmentation system: A wide coverage augmentation system in which the user receives augmentation information from a satellite-based transmitter. The WAAS is a form of SBAS.
    15. Standard instrument arrival: A designated instrument flight rule (IFR) arrival route linking a significant point, normally on an ATS route, with a point from which a published instrument approach procedure can be commenced.
    16. Standard instrument departure: A designated IFR departure route linking the aerodrome or a specified runway of the aerodrome with a specified significant point, normally on a designated ATS route, at which the en-route phase of a flight commences.
    17. Technical Standard Order: A minimum performance standard for specified materials, parts, and appliances used on civil aircraft.
    18. Total System Error: The difference between the true position and the desired position. This error is equal to the sum of the vectors of the path definition error (PDE), the flight technical error (FTE), and the navigation system error (NSE).
      1. Flight Technical Error (FTE): The FTE is the accuracy with which an aircraft is controlled as measured by the indicated aircraft position with respect to the indicated command or desired position. It does not include blunder errors.
      2. Navigation System Error (NSE): The difference between the true position and the estimated position.
      3. Path Definition Error (PDE): The difference between the defined path and the desired path at a given place and time.
    19. World Geodetic System 1984 (WGS 84): The most recent geocentric reference system definition developed by the United States Department of Defence (World Geodetic System Committee).
  2. The following abbreviations are used in this document:
    1. AC: Advisory Circular;
    2. ABAS: Aircraft-Based Augmentation System;
    3. ANSP: Air Navigation Service Provider;
    4. FTE: Flight Technical Error;
    5. GNSS: Global Navigation Satellite System;
    6. GPS: Global Positioning System;
    7. NSE: Navigation System Error;  
    8. PBN: Performance Based Navigation;  
    9. PDE: Path Definition Error;
    10. RNAV: Area Navigation;
    11. RAIM: Receiver Autonomous Integrity Monitoring;
    12. RF: Radius to Fix;
    13. RNP: Required Navigation Performance;
    14. SBAS: Satellite-Based Augmentation System;
    15. SID: Standard Instrument Departure;
    16. STAR: Standard Instrument Arrival;
    17. TSE: Total System Error;
    18. TSO: Technical Standard Order; and
    19. TCCA: Transport Canada Civil Aviation.  

3.0 Background

  1. The material described in this Advisory Circular (AC) has been developed based on International Civil Aviation Organization (ICAO) Doc 9613 Performance Based Navigation (PBN) Manual, Vol. II Part C Implementing Required Navigation Performance 1 (RNP 1).
  2. This AC does not establish all the requirements that may be specified for a given Standard Instrument Departure (SID) or Standard Instrument Arrival (STAR). These requirements are established in other documents, such as the Transport Canada Publication (TP) 308 Criteria for the Development of Instrument Procedures and ICAO Doc 7030 – Regional Supplementary Procedures. Although operational approval is normally related to airspace requirements, operators must consider the operational documents required by Transport Canada Civil Aviation (TCCA) before conducting flights in RNP 1 airspace.
  3. The final step in the operational approval is the issuance of the Ops Spec 618 to the operator.

3.1 Required Navigation Performance 1 Operations

  1. RNP 1 Operations:
    1. are based on the Global Navigation Satellite System (GNSS);
    2. rely on conventional compliance with descent profiles and altitude requirements;
    3. must use the world geodetic system (WGS) 84 coordinates in the creation of routes and procedures;
    4. must meet the requirements of Annex 15 to the Convention on International Civil Aviation in the navigation data published for the routes and procedures;
    5. are intended in environments where Air Traffic Services (ATS) surveillance is limited or not available, but with direct controller-pilot communication;
    6. will clearly indicate the required navigation standard (e.g. RNP 1) on all the appropriate charts.  

4.0 Aircraft Eligibility Requirements

  1. The purpose of this section is to assist an operator in determining if its aircraft is eligible to be considered for approval to conduct RNP 1 operations in Canada. Aircraft eligibility alone does not authorize RNP 1 operations.

4.1 System Eligibility

  1. The aircraft eligibility has to be determined through demonstration of compliance against the relevant airworthiness criteria and the criteria contained in this AC.
  2. Operators may demonstrate the qualification of their aircraft navigation system by satisfying one of the following criteria:
    1. The aircraft manufacturer has included a statement in the Aircraft Flight Manual indicating that the aircraft is approved to conduct RNP 1 operations, and that this approval is based on GNSS (GPS) navigation. Approval based exclusively on other navigation aids, such as DME, is not acceptable;
    2. The aircraft manufacturer has included a statement in the Aircraft Flight Manual that the aircraft meets the requirements of Federal Aviation Administration Advisory Circular (FAA AC) 90-105 Appendix 2, and that this approval is based on GNSS (GPS) navigation. Approval based exclusively on other navigation aids, such as Distance Measuring Equipment (DME), is not acceptable;
    3. Stand-alone systems: Stand-alone E/TSO-C129 Class A1 or A2 systems (without deviation from the functional requirements established in this AC) or E/TSO-C146 Class 1, 2 or 3 systems (without deviation from the functional requirements established in this AC) meet aircraft qualification requirements for RNP 1 operations. This equipment must be installed and certified as per Part V of the Canadian Aviation Regulations (CARs);
    4. Multi-sensor systems: Multi-sensor systems using E/TSO-C129() Class B or C sensors or E/TSO-C145 Class 1, 2 and 3 sensors, meet aircraft qualification requirements for RNP 1 operations, provided that the installations comply with the criteria of this AC. The associated FMS must comply with E/TSO-C115b and all equipment must be installed and certified as per Part V of the CARs; or
    5. In the event that the aircraft does not meet any of the above criteria but the operator is able to demonstrate that the navigation system meets all of the functional requirements listed below, aircraft eligibility may be determined by TCCA Aircraft Certification.

4.2 Functional Requirements

Note: The design approval holder will demonstrate compliance, and the approval will be documented in manufacturer documentation. Such documentation indicates that the aircraft and equipment meet the technical requirements of this section.

  1. Accuracy
    1. During operations in airspace or on routes designated as RNP 1, the lateral total system error must be within +/- 1 NM for at least 95% of total flight time. The along-track error must also be within +/- 1 NM for at least 95% of total flight time. To satisfy the accuracy requirement, the 95% flight technical error (FTE) should not exceed 0.5 NM.

       

      Note: The use of a course deviation indicator (CDI) with 1 NM full-scale deflection has been found to be an acceptable means of compliance. The use of an autopilot (AP) or flight director (FD) has been found to be an acceptable means of compliance (roll stabilization systems do not meet the requirements).

  2. Integrity
    1. Malfunctioning of the aircraft navigation equipment is classified as a major failure condition under airworthiness regulations (i.e. probability of failure not greater than 1 X 10-5 per hour).
  3. Continuity
    1. Loss of function is classified as a minor failure condition if the operator can revert to a different navigation system and proceed to a suitable aerodrome.
  4. Performance monitoring and alerting
    1. The RNP system must provide an alert if the accuracy requirement is not met, or if the probability that the lateral total system error (TSE) exceeding 1 NM is greater than 1 X 10-5 per hour.
  5. Signal-in-space

    1. If GNSS is used, the aircraft navigation equipment will provide an alert if the probability of signal-in-space errors causing a lateral position error greater than 1 NM exceeds 1 X 10-7 per hour (ICAO Annex 10, Volume I, Table 3.7.2.4.1).

      Note: Compliance with the on-board performance monitoring and alerting requirements does not imply automatic monitoring of flight technical errors. The on-board monitoring and alerting function should consist at least of a navigation system error (NSE) 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.

  6. RNP 1 is based on GNSS positioning
    1. Positioning data from other types of navigation sensors may be integrated with the GNSS data provided the other positioning data do not cause position errors exceeding the TSE budget. Otherwise, means should be provided to deselect the other navigation sensor types. This requirement does not imply an equipment capability must exist providing a direct means of inhibiting DME updating.  A procedural means for the flight crew to inhibit DME updating or executing a missed approach if reverting to DME updating may meet this requirement.
  7. For TSO-C129a equipment, the navigation system must be able to maintain 1NM CDI scaling sensitivity, either automatically or by manual selection, during terminal procedures which extend beyond 30NM from the airport. Operators wishing to conduct RNP 1 operations with aircraft unable to demonstrate this capability may be issued Ops Spec 618 with a restriction to conduct such operations within 30 NM of an airport. Such operators would have to include this restriction in the flight crew member training.
  8. The navigation system must meet the functional requirements contained in Appendix A of this AC.
  9. If the operator wishes to conduct the RF leg segments associated with some RNP 1 procedures, the navigation system must meet the requirements of Ops Spec 623.
  10. The navigation system should not permit the flight crew to select a procedure that is not supported by the equipment, either manually or automatically (e.g., a procedure is not supported if it incorporates an RF leg and the equipment does not provide RF leg capability).

  11. The navigation system should also prohibit flight crew access to procedures requiring RF leg capability 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 autopilot or flight director installed).

    Note: One acceptable means to meet these requirements is to screen the aircraft’s onboard navigation database and remove any routes or procedures the aircraft is not eligible to execute.  For example, if the aircraft is not eligible to complete RF leg segments, then the database screening could remove all procedures containing RF leg segments from the navigation database.
    Another acceptable means of compliance may be flight crew training to identify and prohibit the use of procedures containing RF legs.

4.3 Continued Airworthiness

  1. The operators of aircraft approved to perform RNP 1 operations must ensure that the navigation system is maintained according to the design approval holder’s instructions for continuing airworthiness (ICAs), including any software updates.

  2. Each operator who applies for RNP 1 operational approval is required to incorporate the RNP 1 equipment inspection requirements, specified by the design approval holder, and amend the aircraft maintenance schedule as required. This requirement is designed to ensure that navigation systems continue to meet the RNP 1 approval criteria.

    Note: If the aircraft was delivered by the aircraft manufacturer with RNP 1 capability the maintenance requirements may already exist in the maintenance schedule.

  3. Maintenance for the affected aircraft is required to include the maintenance practices listed in the maintenance manuals of the aircraft manufacturer and its components, and must consider:
    1. that the equipment involved in the RNP 1 operation is required to be maintained according to the ICA from the component design approval holder;
    2. that any amendment or change of navigation system affecting in any way RNP 1 initial approval, must be submitted to the principal maintenance inspector (PMI) and reviewed for acceptance or approval of such changes prior to its implementation; and
    3. that any repair that is not included in the approved/accepted maintenance documentation, and that could affect the integrity of navigation performance, is required to be forwarded to the PMI or regional airworthiness office for acceptance or approval thereof.  

5.0 Required Navigation Performance 1 procedures

  1. Operational approval is required to confirm the adequacy of the operator’s normal and contingency procedures for the particular equipment installation. Information that indicates the potential for repeated errors may require modification of an operator’s training program. Information that attributes multiple errors to a particular flight crew member may necessitate remedial training.
  2. The operator and its flight crew members will be familiar with the following operating and contingency procedures associated with RNP 1 operations.

5.1 Pre-Flight Planning

  1. The appropriate flight plan suffixes must be included on the flight plan.
  2. The on-board navigation data must be current and include appropriate procedures.

     

    Note: Navigation databases are expected to be current for the duration of the flight or series of flight segments. If the AIRAC cycle is due to change during flight, procedures should be established to ensure the accuracy of the navigation data, including the suitability of navigation facilities used to define the routes and procedures for flight.

  3. The availability of the Navigation Aid (NAVAID) infrastructure required for the intended routes, including any non-RNAV contingencies, must be confirmed for the period of intended operations, using all available information. Since ICAO Annex 10 Volume I requires GNSS integrity (RAIM or SBAS signal) the availability of these should also be determined as appropriate. For aircraft that navigate with SBAS receivers (all TSO-C145() / C146() receivers), availability of the GNSS RAIM must be confirmed in areas where the SBAS signal is not available.
  4. Receiver Autonomous Integrity Monitoring (RAIM) (ABAS) Availability:
    1. RAIM levels required for RNP 1 can be verified either through Notices to Airmen (NOTAMs) (where available) or through prediction services. Operators must be familiar with the prediction information available for the intended route.
    2. The prediction of RAIM availability must take into account the latest GPS constellation NOTAMs. The RAIM prediction service can be provided through the Air Navigation Service Providers (ANSPs), the avionics manufacturers, other entities, or through the RAIM prediction capability of the aircraft on-board receiver. RAIM availability can be confirmed using model-specific RAIM prediction software.
    3. The predictive capability must account for known and predicted outages of GPS satellites or other effects on the navigation system sensors. The prediction program should not use a mask angle below 5 degrees, since operational experience indicates that satellite signals on low elevations are not reliable. The use of a higher mask angle should be considered when conducting RAIM availability predictions for airports with known topographical obstructions. RAIM availability prediction should take into account the latest GPS constellation NOTAMs, and use an identical algorithm to that used in the airborne equipment or an algorithm based on assumptions for RAIM prediction that provides a more conservative result.   
    4. In the event of a predicted continuous loss of the appropriate level of fault detection of more than five (5) minutes for any part of the RNP 1 operation, the flight planning must be revised (e.g. delaying the departure or planning a different departure procedure).
    5. The RAIM availability prediction software does not guarantee the service. This software is a tool for assessing the expected capability to meet the required navigation performance. Due to unplanned failures of some GNSS elements, both RAIM and GNSS navigation may be lost while airborne, which may require reversion to an alternate means of navigation. Therefore, flight crew members should assess their capability to navigate (potentially to an alternate destination) in the case of the failure of GPS navigation.

5.2 General Operating Procedures

  1. Any instructions or procedures identified by the manufacturer as necessary to comply with RNP 1 performance requirements must be followed.
  2. Operators and flight crew members should not request, accept or file RNP 1 procedures unless all the criteria in this AC are satisfied.
  3. At system initialization, the aircraft position must be confirmed as having been entered correctly. The proper entry of the ATC assigned route upon initial clearance and any subsequent change of route must be verified. The waypoint sequence depicted by the navigation system must match the route depicted on the appropriate chart(s) and the assigned route.
  4. An RNP 1 SID or STAR must be retrievable by procedure name from the on-board navigation database and conform to the charted procedure. However, the procedure may subsequently be modified through the insertion or deletion of specific waypoints in response to ATC clearances. The entry or creation of new waypoints by manual entry of latitude and longitude, or rho/theta values, is not permitted. Additionally, a SID or STAR database waypoint may not be changed from a fly-by type to a fly-over type or vice versa.

  5. The cleared flight plan should be cross-checked by comparison to charts or other applicable resources with the navigation system textual display and the aircraft map display, if applicable. If required, the exclusion of specific NAVAIDs should be confirmed.

    Note: There may be a slight difference between the navigation information portrayed on the chart and the primary navigation display. Differences of 3 degrees or less may result from the equipment manufacturer’s application of magnetic variation and are operationally acceptable.

  6. Cross-checking with conventional NAVAIDs is not required, as the absence of an integrity alert is considered sufficient to meet the integrity requirements. However, monitoring of navigation reasonableness is suggested, and any loss of RNP capability must be reported to ATC.
  7. For RNP 1 routes, a lateral deviation indicator, flight director, or autopilot in lateral navigation mode must be used. Lateral deviation scaling must be suitable for the navigation accuracy associated with the route/procedure (e.g. full-scale deflection: ±1 nm for RNP 1), when using a lateral deviation display.

  8. As depicted by on-board lateral deviation indicators and/or flight guidance during all RNP 1 operations described in this manual, the centrelines must be maintained unless authorized to deviate by ATC or under emergency conditions. For normal operations, FTE should be limited to 0.5 nm. Brief deviations from this standard (e.g. overshoots or undershoots) during and immediately after turns, up to a maximum 1.0 nm are allowable.

    Note: Some aircraft do not display or compute a path during turns, but are still expected to satisfy the above standard during intercepts following turns and on straight segments.

  9. If ATC issues a heading assignment that takes an aircraft off a route, the flight plan in the RNP system should not be modified until a clearance is received to rejoin the route or ATC confirms a new route clearance. When the aircraft is not on the published RNP 1 route, the specified accuracy requirement does not apply.
  10. Manually selecting aircraft bank limiting functions may reduce the aircraft’s ability to maintain its desired track and are not recommended. Manually selectable aircraft bank-limiting functions might reduce the ability to satisfy ATC path expectations, especially when executing large angle turns. This should not be construed as a requirement to deviate from aeroplane flight manual procedures. The selection of such functions should be limited within accepted procedures.
  11. Before starting a RNP 1 procedure, flight crew members must:
    1. confirm that the correct procedure has been selected. This process includes verifying waypoint sequence, the reasonableness of track angles, distances, and of any other parameter that can be modified by the flight crew member, such as altitude or speed constraints; and
    2. for multi-sensor systems, verify that the correct sensor is being used for position computation.    
  12. Flight crew members operating aircraft with RNP accuracy value input selection capability should confirm, and correct as required, an RNP accuracy value of 1 or lower for RNP 1 SIDs and STARs.
  13. Operators are only permitted to conduct the RF leg portion of RNP 1 procedures if they have received the authority to do so by the issuance of Ops Spec 623.

5.3 Required Navigation Performance 1 Standard Instrument Departure Specific Requirements

  1. Prior to flight, the flight crew members must verify their aircraft navigation system is operating correctly and the correct runway and departure procedure (including any applicable en-route transition) are entered and properly depicted. Flight crew members who are assigned a RNP 1 departure procedure and subsequently receive a change of runway, procedure or transition must verify the appropriate changes are entered and available for navigation prior to take-off. A final check of proper runway entry and correct route depiction, shortly before take-off, is recommended.
  2. The use of RNP 1 equipment to follow flight guidance for lateral navigation (e.g. LNAV) must begin no later than 153 m (500 ft) above the aerodrome elevation.
  3. Flight crew members must use an authorized method (lateral deviation indicator/navigation map display/flight director/autopilot) to achieve an appropriate level of performance for RNP 1.
  4. The GNSS signal must be acquired before the take-off roll commences.
  5. For aircraft using TSO-C129a avionics, the departure airport must be loaded into the flight plan in order to achieve the appropriate navigation system monitoring and sensitivity. For aircraft using a lateral deviation display (i.e. navigation map display), the scale must be adjusted for the RNP 1 SID and flight director or autopilot should be used. If the RNP 1 SID extends beyond 30 nm from the aerodrome and a lateral deviation indicator is used, its full-scale sensitivity must be selected to not greater than 1 NM between 30 nm from the aerodrome and the termination of the RNP 1 SID.
  6. For aircraft using TSO-C145()/C146() avionics, if the departure begins at a runway waypoint, then the departure airport does not need to be in the flight plan to obtain appropriate monitoring and sensitivity.

5.4 Required Navigation Performance 1 Standard Instrument Arrival Specific Requirements

  1. Prior to the arrival phase, the correct terminal route must be verified as having been loaded. The active flight plan should be checked by comparing the charts with the route depicted and entered. This includes confirmation of the waypoint sequence, reasonableness of track angles and distances, any altitude or speed constraints, and, where possible, which waypoints are fly-by and which are flyover. A route must not be used if doubt exists as to the validity of the route in the navigation database.

    Note: As a minimum, the arrival checks could be a simple inspection of a suitable map display that achieves the objectives of this paragraph.

  2. The creation of new waypoints by manual entry into the RNP 1 system would invalidate the route and is not permitted.
  3. Where the contingency procedure requires reversion to a conventional arrival route, necessary preparations must be completed before commencing the RNP 1 procedure.
  4. Procedure modifications in the terminal area may take the form of radar headings or “direct to” clearances, and the flight crew members must be capable of reacting in a timely fashion. This may include the insertion of tactical waypoints loaded from the database. Manual entry or modification of the loaded route, using temporary waypoints or fixes not provided in the database, is not permitted.
  5. The flight crew members must verify that the aircraft navigation system is operating correctly and that the correct arrival procedure and runway (including any applicable transition) are entered and properly depicted.
  6. Although a particular method is not mandated, any published altitude and speed constraints must be observed.
  7. For aircraft using TSO-C129a avionics, when using a lateral deviation display (i.e. navigation map display), the scale must be set for the RNP 1 STAR, and the flight director or autopilot should be used. If the RNP 1 STAR begins beyond 30 NM from the aerodrome and a lateral deviation indicator is used, then full scale sensitivity should be manually selected to not greater than 1 NM prior to commencing the STAR.

5.5 Contingency Procedures

  1. If, for any reason, it is not possible to meet the requirements of a RNP 1 SID or STAR, the flight crew members must notify ATC as soon as possible together with the proposed course of action. The loss of RNP capability includes any failure or event causing the aircraft to no longer satisfy the RNP 1 requirements of the route.
  2. In the event of communication failure, the flight crew members should continue with the published procedure.

5.6 Navigation Errors

  1. The operator will establish a procedure to receive, analyze, and follow up on navigation error reports in order to determine appropriate corrective action.
  2. Information indicating a potential for repetitive errors may require the modification of the training program of the operator.
  3. Information attributing multiple errors to a flight crew member may call for additional training.
  4. Repetitive navigation errors attributed to the equipment or a specific part of the navigation equipment or to operating procedures can be the cause of cancellation of an operational approval (withdrawal/suspension of RNP 1 operation specification authorization).

5.7 Navigation Database

  1. The operator must obtain the navigation database from a supplier that complies with Radio Technical Commission for Aeronautics (RTCA) document DO 200A/EUROCAE ED 76 – Standards for Processing Aeronautical Data. A Letter of Acceptance (LOA) issued by the appropriate regulatory authority to each participant in the data chain demonstrates compliance with this requirement (e.g., FAA LOA issued in accordance with FAA AC 20-153 or European Aviation Safety Agency (EASA) LOA issued in accordance with EASA OPINION Nr. 01/2005).
  2. Discrepancies that invalidate a SID or STAR must be reported to the navigation database supplier and the affected SID or STAR must be prohibited by an operator’s notice to its flight crew members.

6.0 Knowledge and Training requirements

  1. Flight crew members must be trained to the standard as required by:
    1. Subpart 604 of the CARs;
    2. Subsection 722.76(15) of the Commercial Air Service Standards (CASS);
    3. Subsection 723.98(21) of the CASS;
    4. Subsection 724.115(22) of the CASS;
    5. Subsection 725.124(27) of the CASS;
  2. Additionally, flight crew members will be trained on the following:
    1. The information in this AC;
    2. The meaning and proper use of aircraft equipment/navigation suffixes;
    3. RNP 1 procedure characteristics as determined from the charts;
    4. Depiction of waypoint types (fly-over and fly-by) and path terminators as well as associated aircraft flight paths;
    5. Required navigation equipment for operation on RNP 1 SIDs and STARs;
    6. RNP system specific information:
      1. Levels of automation, mode annunciations, changes, alerts, interactions, reversions and degradation;
      2. Functional integration with other aircraft systems;
      3. The meaning and appropriateness of route discontinuities as well as related flight crew procedures;
      4. Flight crew member procedures consistent with the operation;
      5. Types of navigation sensors utilized by the RNP system and associated system prioritization/weighting/logic;
      6. Turn anticipation with consideration to speed and altitude effects;
      7. Interpretation of electronic displays and symbols;
      8. Understanding of the aircraft configuration and operational conditions required to support RNP 1 operations, i.e. appropriate selection of CDI scaling (lateral deviation display scaling);
    7. RNP system operating procedures, as applicable, including how to perform the following actions:
      1. Verify currency and integrity of the aircraft navigation data;
      2. Verify the successful completion of RNP system self-tests;
      3. Initialize navigation system position;
      4. Retrieve and fly a RNP 1 SID or a STAR with appropriate transition;
      5. Adhere to speed and/or altitude constraints associated with a RNP 1 SID or STAR;
      6. Select the appropriate RNP 1 SID or STAR for the active runway in use and be familiar with procedures to deal with a runway change;
      7. Verify waypoints and flight plan programming;
      8. Fly direct to a waypoint;
      9. Fly a course/track to a waypoint;
      10. Intercept a course/track;
      11. Fly radar vectors and rejoining a RNP 1 route from “heading” mode;
      12. Determine cross-track error/deviation. More specifically, the maximum deviations allowed to support RNP 1 must be understood and respected;
      13. Resolve route discontinuities;
      14. Remove and reselect navigation sensor input;
      15. Change arrival airport and alternate airport;
      16. Perform parallel offset function if capability exists. Flight crew members should know how offsets are applied, the functionality of their particular RNP system and the need to advise ATC if this functionality is not available;
      17. Perform RNAV holding function;
      18. Select the required CDI scaling, particularly when conducting terminal procedures beyond the automatic scaling capability of the RNAV system;
      19. Inhibit or de-select RNP 1 procedures containing RF legs (for operators not having Ops Spec 623);
      20. Perform RF leg associated with RNP 1 procedures as per the requirements of Ops Spec 623 (for operators holding that Ops Spec 623);
    8. Operator-recommended levels of automation for phase of flight and workload, including methods to minimize cross-track error to maintain route centerline;
    9. R/T phraseology for RNAV/RNP applications;
    10. Contingency procedures for RNAV/RNP failures; and
    11. Any TCCA-imposed restrictions associated with the Ops Spec 618.
  3. Operational Control Personnel must be trained on the following:
    1. The Performance Based Navigation concept;
    2. Flight planning as it pertains to RNP 1;
    3. WAAS NOTAMs (as applicable);
    4. RAIM prediction;
  4. Maintenance personnel involved in the routine or detailed checks of RNP 1 avionics should be familiar with the Performance Based Navigation concept.
  5. Operators wishing to receive credit for elements of RNP training already conducted as part of an existing training program (e.g. elements of a training curriculum already in place to satisfy a foreign state’s approval requirements) must receive approval from their principal operations inspector or equivalent. In such a case, the operator must include flight crew member training on the differences between RNP 1 procedures and the operation(s) associated with the common training elements.

7.0 Operational Approval

  1. The requirements for authorization to operate in RNP 1 airspace are as follows:
    1. The equipment must meet the certification and installation requirements of Part V of the CARs;
    2. The operator must ensure the quality of the navigation database;
    3. The operator must establish procedures in its Company Operations Manual (COM), or private operator equivalent, for the guidance of its personnel related to the conduct of RNP 1 operations. These procedures must include at least a system description and any limitations; operational aspects, including normal, abnormal and emergency operations; and any effects or dependences on other aircraft systems. Updates to the operator’s COM should be done in accordance with the requirements of Subpart 604 and sections 702.82, 703.105, 704.121, 705.135, of the CARs, as applicable;
    4. If a MEL has been approved by the Minister, in respect of an operator of that type of aircraft, the operator must amend its MEL, where required, and specify the required dispatch conditions. The MEL must indicate clearly to the flight crew members the implications of equipment failures to RNP 1 operations. All MEL amendments must be submitted to, and approved by, TCCA;
    5. The operator must amend its Maintenance Program accordingly; and
    6. The operator must amend its training program to provide training to operational control personnel, each flight crew member and, when applicable, maintenance personnel involved with RNP 1 operations. Updates to the operator’s Training Program should be done in accordance with the requirements of Subpart 604 of the CARs, or the guidance in Sections 722.26, 723.98, 724.115, 725.124, of the CASS, as applicable.
  2. Operators intending to apply for Ops Spec 618 should review the referenced documents and then contact their Principal Operations Inspector (POI), or private operator equivalent, for more information. In order to minimize the workload for the operator (e.g. Training Program development, aircraft eligibility), it is recommended that operators who wish to apply for Ops Spec 623, authorization to conduct radius to fix legs, do so simultaneously with the application for Ops Spec 618.
  3. RNP 1 operational approval may be restricted to operations within 30NM of an airport if the navigation system’s functionality does not include the capability to demonstrate 1NM scaling outside of 30NM of an airport.

8.0 Conclusion

  1. The POI, with the assistance of the PMI or Regional Airworthiness office, should confirm that all of the above requirements are satisfied. Once all of the applicable conditions of this AC have been met, Ops Spec 618 may be issued to the operator. 

9.0 Information Management

  1. Not applicable.

10.0 Document history

  1. Not applicable.  

11.0 Contact office

For more information, please contact:

Commercial Flight Standards Division (AARTF)

E-mail:  AARTinfodoc@tc.gc.ca

Suggestions for amendment to this document are invited, and should be submitted via:

AARTinfodoc@tc.gc.ca 

Original signed by Arlo Speer on September 20, 2013.

Aaron McCrorie

Director, Standards

Civil Aviation

Transport Canada

Transport Canada documents or intranet pages mentioned in this document are available upon request through the Contact Office.

Appendix A — Functional Requirements

Paragraph Functional Requirements Explanation
a) Navigation data, including a failure indicator, must be displayed on a lateral deviation display (e.g. CDI, (E)HSI) and/or a navigation map display. These lateral deviation displays must be used as primary flight instruments for the navigation of the aircraft, for manoeuvre anticipation, and for indication of failure/status/integrity. 
  1. Non-numeric lateral deviation display (e.g. CDI, (E)HSI)), with a to/from indication and a failure annunciation, for use as primary flight instruments for navigation of the aircraft, for manoeuvre anticipation, and for failure/status/integrity indication, with the following five attributes:
    1. The capability to continuously display to the pilot flying, on the primary flight instruments for navigation of the aircraft (primary navigation display), the RNAV computed path and aircraft position relative to the path. For operations where the required minimum flight crew is two pilots, the means for the pilot not flying to verify the desired path and the aircraft position relative to the path must also be provided.
    2. Each display must be visible to the flight crew members and located in the primary field of view (±15 degrees from the flight crew member’s normal line of sight) when looking forward along the flight path.
    3. The lateral deviation display scaling should agree with any alerting and annunciation limits.
    4. The lateral deviation display must also have a full-scale deflection suitable for the current phase of flight and must be based on the required track keeping` accuracy.
    5. The display scaling may be set automatically by default logic; automatically to a value obtained from a navigation database; or manually by flight crew procedures. The full-scale deflection value must be known or must be available for display to the flight crew member commensurate with the required track keeping accuracy.
    6. The lateral deviation display must be automatically slaved to the computed path. The course selector of the deviation display should be automatically slewed to the computed path or the flight crew member must adjust the CDI or HSI selected course to the computed desired track.
  2. As an alternate means of compliance, a navigation map display can provide equivalent functionality to a lateral deviation display as described in Paragraph 1 (a) to (f) above, with appropriate map scales and giving equivalent functionality to a lateral deviation display. The map scale should be set manually to a value appropriate for the RNP 1 operation.

 

b) The following system functions of the RNP 1 system are required as a minimum within any RNP 1 equipment:
  1. 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 and from which ATS routes can be retrieved and loaded into the RNP system. The stored resolution of the data must be sufficient to achieve negligible path definition error (PDE). The database must be protected against flight crew member modification of the stored data.
  2. The means to display the validity period of the navigation data to the flight crew members;
  3. The means to retrieve and display data stored in the navigation database relating to individual waypoints and NAVAIDs, to enable the flight crew members to verify the route to be flown;
  4. The capacity to load from the database into the RNP 1 system the entire segment of the SID or STAR to be flown.

NOTE. Due to variability in systems, this document defines the RNAV segment from the first occurrence of a named waypoint, track or course to the last occurrence of a named waypoint, track or course. Heading legs prior to the first named waypoint or after the last named waypoint do not have to be loaded from the navigation database. The entire SID will be considered an RNP 1 procedure.

c) The means to display the following items, either in the flight crew member’s primary field of view, or on a readily accessible display page
  1. The active navigation sensor type;
  2. The identification of the active (To) waypoint;
  3. The ground speed or time to the active (To) waypoint; and
  4. The distance and bearing to the active (To) waypoint.
d) The capability to execute a “direct to” function.  
e) The capability for automatic leg sequencing with the display of sequencing to the flight crew member.  
f) The capability to load and execute a RNP 1 SID or STAR from the on-board database by procedure name into the RNP system.

  

 
g) The aircraft must have the capability to automatically execute leg transitions and maintain tracks consistent with the following ARINC 424 path terminators or their equivalent:

- Initial fix (IF);

- Course to fix (CF);

- Direct to fix (DF); and

- Track to fix (TF).

NOTE Path terminators are defined in the ARINC Specification 424, and their application is described in more detail in RTCA documents DO-236B/EUROCAE ED-75B and DO-201A/EUROCAE ED-77.

 

NOTE Numeric values for courses and tracks must be automatically loaded from the RNP system database.

h) The aircraft must have the capability to automatically execute leg transitions consistent with VA, VM and VI ARINC 424 path terminators or must be able to be manually flown on a heading to intercept a course or to go direct to another fix after reaching a procedure-specified altitude.  
i) The aircraft must have the capability to automatically execute leg transitions consistent with CA and FM ARINC 424 path terminators, or the RNP system must permit the flight crew member to readily designate a waypoint and select a desired course to or from a designated waypoint.  
k) The capability to display an indication of the RNP 1 system failure in the flight crew member’s primary field of view.  

 

AC 700-025 - Required Navigation Performance 1 (RNP 1)
(PDF, 296 KB)

Report a problem with this page

Date modified: