Par 10 Page 11
(3) The onboard navigation data must be current and appropriate for the region of intended operation and must include the navigation aids, waypoints, and relevant coded terminal airspace procedures for the departure, arrival, and alternate airfields. RNAV STAR procedures may be designed using multiple runway transitions. Operators not having this functionality shall provide an acceptable alternative means (for example, a tailored navigation data base). If no equivalent means are available to fly the charted RNAV procedure containing multiple runway transitions, operators will not file or accept clearance for these procedures.
NOTE: Navigation databases are expected to be current for the duration of the flight. If the AIRAC cycle will 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. Traditionally, this has been accomplished by verifying electronic data against paper products. One acceptable means is to compare aeronautical charts (new and old) to verify navigation fixes prior to dispatch. If an amended chart affecting navigation data is published for the procedure, the database must not be used to conduct the procedure.
(4) If not equipped with GPS/GNSS, aircraft must be capable of navigation system updating using DME/DME/IRU for RNAV 2 or RNAV 1 routes, as well as RNAV 1 departure procedures (DPs) and Standard Terminal Arrivals (STAR). As stated in paragraph 8.b.(1), if the navigation system does not automatically alert the flightcrew of a loss of GPS/GNSS, the operator must develop procedures to verify correct GPS/GNSS operation.
(5) If TSO-C129 equipment is used to solely satisfy the RNAV requirement, GPS RAIM availability must be confirmed for the intended route of flight (route and time) using current GPS satellite information. The availability of SBAS or ABAS fault detection can be determined through NOTAMs (if available) or through prediction for the intended RNAV 1 or RNAV 2 operation. Operators may choose to monitor the status of each satellite in its plane/slot position, account for the latest GPS constellation NOTAMs, and compute RAIM availability using model-specific RAIM prediction software, or by using the Service Availability Prediction Tool (SAPT) on the FAA en route and terminal RAIM prediction Web site, or by contacting a Flight Service Station (FSS). Receiver RAIM prediction capability can also be used. In the event of a predicted, continuous loss of RAIM of more than five (5) minutes for any part of the intended flight, the flight should be delayed, canceled, or re-routed where RAIM requirements can be met.
Pilots should assess their capability to navigate (potentially to an alternate destination) in case of failure of GPS navigation.
(6) If TSO-C145/C146 equipment is used to satisfy the RNAV requirement, the pilot/ operator need not perform the prediction if WAAS coverage is confirmed to be available along the entire route of flight.
NOTE: Outside the U.S. or in areas where WAAS coverage is not available, operators using TSO-C145/C146 receivers are required to check GPS RAIM availability.
Page 12 Par 10
(7) Proper Interpretation of Pre-Departure Clearance (PDC) and printed routings.
Pilots of operators using PDC and printed routings must be able to properly interpret their assigned clearance. Specifically, pilots must be able to recognize direct routings, assigned altitudes, revised clearances, SIDs, and en route transitions. Pilots must understand their operator’s PDC notation and must request clarification from ATC if any doubt exists with regard to their clearance.
b. General Operating Procedures. Operators and pilots should not request or file U.S. RNAV routes or procedures unless satisfying the criteria in this AC. If an aircraft not meeting these criteria receives a clearance from ATC to conduct an RNAV procedure, the pilot must advise ATC that he/she is unable to accept the clearance and request alternate instructions.
(1) The pilot should comply with any instructions or procedures identified by the manufacturer as necessary to comply with the equipment requirements of this AC.
(2) At system initialization, pilots must confirm the navigation database is current and verify the aircraft’s present position.
(3) RNAV DPs and STAR procedures must be retrieved by procedure name from the onboard navigation database and conform to the charted procedure.
(4) Whenever possible, RNAV routes should be extracted from the database in their entirety, rather than loading RNAV route waypoints from the database into the flight plan individually. Selecting and inserting individual, named fixes from the database is permitted, provided all fixes along the published route to be flown are inserted.
NOTE: This does not preclude the use of panel-mount GPS/GNSS avionics to meet the requirements of this AC to fly RNAV routes.
(5) Manual entry of waypoints using latitude/longitude or place/bearing is not permitted.
Additionally, pilots must not change any RNAV DP or STAR database waypoint type from a fly-by to a fly-over or vice versa.
(6) Flightcrews should crosscheck the cleared flight plan against charts or other applicable resources, as well as the navigation system textual display and the aircraft map display, if applicable. If required, confirm exclusion of a specific navigation aid. A procedure should not be used if doubt exists as to the validity of the procedure in the navigation database.
NOTE: Pilots may notice a slight difference between the navigation information portrayed on the chart and their primary navigation display. Differences of 3° or less may result from equipment manufacturer's application of magnetic variation and are operationally acceptable.
(7) Verification of assigned route and correct entry of transitions into RNAV System/Flight Management System (FMS).
(a) DPs. Prior to flight, pilots must verify their aircraft navigation system is operating correctly and the correct runway and departure procedure (including any applicable en route
Par 10 Page 13 transition) are entered and properly depicted. Pilots who are assigned an RNAV 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 takeoff. A final check of proper runway entry and correct route depiction, shortly before takeoff, is recommended.
(b) R outes. Pilots must verify proper entry of their ATC assigned route upon initial clearance and any subsequent change of route. Pilots must ensure the waypoints sequence depicted by their navigation system matches the route depicted on the appropriate chart(s) and their assigned route.
(c) S TARs. Pilots must verify their aircraft navigation system is operating correctly and the correct arrival procedure and runway (including any applicable transition) are entered and properly depicted.
(8) Use of navigation map displays. Prior to takeoff, pilots of aircraft with a navigation map display should verify the relationship of the aircraft position symbol to their assigned runway (if available) and route on their display matches external visual cues, as well as charts.
Specifically, once on or near their assigned runway, pilots should ensure their navigation display reflects the same relative position to the runway and the route depiction reflects that of the respective chart. During flight, these displays should be used in concert with textual displays for route verification.
(9) Pilots must use a lateral deviation indicator (or equivalent navigation map display), flight director and/or autopilot in lateral navigation mode on RNAV 1 routes. Pilots are encouraged to use a lateral deviation indicator (or equivalent navigation map display), flight director and/or autopilot in lateral navigation mode on RNAV 2 routes. Pilots of aircraft with a lateral deviation indicator (e.g., a standalone GNSS receiver) must ensure that lateral deviation indicator scaling (full-scale deflection) is suitable for the navigation accuracy associated with the route/procedure (i.e., ±1 nm for RNAV 1, ± 2.0 nm for RNAV 2).
NOTE: Some TSO-C129() equipment automatically goes to ±5.0 NM beyond 30 NM from the airport reference point. This is acceptable provided the pilot maintains the required minimum performance standard associated with the procedure.
All pilots are expected to maintain route centerlines, as depicted by onboard lateral deviation indicators and/or flight guidance during all RNAV operations described in this AC unless authorized to deviate by ATC or under emergency conditions. For normal operations, cross-track error/deviation (the difference between the RNAV system computed path and the aircraft position relative to the path) should be limited to ± ½ the navigation accuracy associated with the procedure or route (i.e., 0.5 nm for RNAV 1, 1.0 nm for RNAV 2). Brief deviations from this standard (e.g., overshoots or undershoots) during and immediately after procedure/route turns, up to a maximum of 1 times the navigation accuracy (i.e., 1.0 nm for RNAV 1, 2.0 nm for RNAV
2), are allowable.
NOTE: Some aircraft do not display or compute a path during turns. As such, pilots of these aircraft may not be able to adhere to the ± ½ lateral navigation
Page 14 Par 10 accuracy during procedural/route turns but are still expected to satisfy the standard during intercepts following turns and on straight segments.
(10) If ATC issues a heading assignment taking the aircraft off a procedure, the pilot should not modify the route in the RNAV system until a clearance is received to rejoin the procedure or the controller confirms a new route clearance. When the aircraft is not on the published procedure, the specified accuracy requirement (paragraph 8.a.) does not apply.
(11) Manually selecting aircraft bank limiting functions may reduce the aircraft’s ability to maintain its desired track and are not recommended. Pilots should recognize manually selectable aircraft bank-limiting functions might reduce their ability to satisfy ATC path expectations, especially when executing large angle turns. This should not be construed as a requirement to deviate from AFM procedures; rather, pilots should be encouraged to limit the selection of such functions within accepted procedures.
(12) DPs and STARs are flown as RNAV 1 procedures. RNAV routes are flown as RNAV 2 unless otherwise specified.
(13) Pilots operating RNP-approved aircraft under the provisions of this AC are not required to modify manufacturer's RNP default values established in the Flight Management Computers.
c. RNAV DP and STAR Specific Requirements.
(1) RNAV DP Engagement Altitudes. For DPs, the pilot must be able to engage RNAV equipment to follow flight guidance for lateral RNAV no later than 500 feet above airport elevation.
(2) Pilots must use a lateral deviation indicator (or equivalent navigation map display), flight director and/or autopilot in lateral navigation mode on RNAV 1 routes. The full-scale CDI deflection value of ±1 NM is acceptable.
(3) DME/DME/IRU (D/D/I) Aircraft. Pilots of aircraft without GPS/GNSS, using DME/DME/IRU, must ensure the aircraft navigation system position is confirmed, within 1,000 feet, at the start point of take-off roll. The use of an automatic or manual runway update is an acceptable means of compliance with this requirement. A navigation map may also be used to confirm aircraft position, if pilot procedures and display resolution allow for compliance with the 1,000-foot tolerance requirement.
(4) GNSS Aircraft. When using GNSS, the signal must be acquired before the take-off roll commences.
NOTE: For aircraft using TSO-C129/C129a, the departure airport must be loaded into the flight plan in order to achieve the appropriate navigation system monitoring and sensitivity. For aircraft using TSO-C145a/C146a 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.
Par 10 Page 15
d. Contingency Procedures. The pilot must notify ATC of any loss of the RNAV capability, together with the proposed course of action. If unable to comply with the requirements of an RNAV procedure, pilots must advise ATC as soon as possible. For example, ". . .N1234, failure of GPS/GNSS system, unable RNAV, request amended clearance." The loss of RNAV capability includes any failure or event causing the aircraft to no longer satisfy the criteria of this AC. Example failures include, but are not limited to, loss of autopilot/flight director (if required), or reversion to navigation other than GNSS or DME/DME/IRU (even though no pilot monitoring of navigation updating source is required). In the event of communications failure, established lost communication procedures should be followed.
11. PILOT KNOWLEDGE REQUIREMENTS AND TRAINING. The pilot is expected to be knowledgeable in the following areas. Also, for Parts 121, 125, 129, 135, and 91 Subpart K operators, the approved training program should address the elements listed below. This training program should provide sufficient training (for example, simulator, training device, or aircraft) on the aircraft’s RNAV system to the extent that the pilots are not just task oriented. Training need not be repeated if it addresses specific items listed below.
a. The information in this AC.
b. The meaning and proper use of Aircraft Equipment/Navigation Suffixes.
c. Procedure characteristics as determined from chart depiction and textual description.
(1) Depiction of waypoint types (fly-over and fly-by) and path terminators (provided in Appendix 3 and any other types used by the operator) as well as associated aircraft flight paths.
(2) Required navigation equipment for operation on RNAV routes, DPs, and STARs (for example, DME/DME/IRU and GPS/GNSS).
(3) Phraseology. Some RNAV procedures may incorporate the use of “Descend via” clearances. Pilots should be familiar with the correct use of the terminology and procedures as mentioned in AIM (refer to Air Traffic Procedures, Arrival Procedures).
d. RNAV 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 flightcrew procedures.
(4) Monitoring procedures for each phase of flight (for example, monitor PROG or LEGS page).
(5) Types of navigation sensors (for example, DME, IRU, GPS/GNSS) utilized by the RNAV system and associated system prioritization/weighting/logic.
Page 16 Par 11
(6) Turn anticipation with consideration to speed and altitude effects.
(7) Interpretation of electronic displays and symbols.
e. RNAV equipment operating procedures, as applicable, including how to perform the following actions:
(1) Verify currency of aircraft navigation data.
(2) Verify successful completion of RNAV system self-tests.
(3) Initialize RNAV system position.
(4) Retrieve and fly a DP or STAR with appropriate transition.
(5) Adhere to speed and/or altitude constraints associated with a DP or STAR.
(6) Make a runway change associated with a DP or STAR.
(7) Verify waypoints and flight plan programming.
(8) Perform a manual or automatic runway update (with takeoff point shift, if applicable).
(9) Fly direct to a waypoint.
(10) Fly a course/track to a waypoint.
(11) Intercept a course/track.
(12) Be vectored off and rejoin a procedure.
(13) Determine cross-track error/deviation.
(14) Insert and delete/clear route discontinuity.
(15) Remove and reselect navigation sensor input(s).
(16) When required, confirm exclusion of a specific navigation aid or navigation aid type.
(17) Insert and delete a lateral offset.
(18) Change the arrival airport and alternate airport.
(19) Insert and delete a holding pattern.
Par 11 Page 17 (and 18)
f. Operator-recommended levels of automation for phase of flight and workload, including methods to minimize cross-track error to maintain procedure centerline.
g. Contingency procedures for RNAV failures.
Appendix 1 APPENDIX 1. CRITERIA FOR APPROVAL OF BASELINE AREA NAVIGATION (RNAV) SYSTEMS USING DISTANCE MEASURING EQUIPMENT (DME)
1. PURPOSE. The FAA is responsible for evaluating DME/DME coverage and availability against a minimum standard DME/DME RNAV system for each route and procedure. Detailed criteria defining DME/DME RNAV system performance as it relates to the DME infrastructure is needed. This appendix defines the minimum performance and functions (baseline) for DME/DME RNAV systems intended to support the implementation of RNAV 1 and RNAV 2 routes, as well as RNAV 1 departure procedures (DPs) and Standard Terminal Arrivals (STAR).
These criteria may be applied under an airworthiness approval for new equipment or used by the manufacturer for self-certification of existing equipment.
2. MINIMUM REQUIREMENTS FOR DME/DME RNAV SYSTEM.
a. Tuning and Updating Position of DME Facilities. The DME/DME RNAV system must:
(1) Position update within 30 seconds of tuning DME navigation facilities.
(2) Auto-tune multiple DME facilities.
(3) Provide continuous DME/DME position updating. (Given a third DME facility or a second pair has been available for at least the previous 30 seconds, there must be no interruption in DME/DME positioning when the RNAV system switches between DME stations/pairs.)
b. Using Facilities in the Airport/Facility Directory. The FAA cannot ensure all DME signals within reception distance of U.S. airspace meet International Civil Aviation Organization (ICAO) standards. These could include non-U.S. DME facilities, or Department of Defense (DOD) maintained DME facilities excluded from the National Airspace System (NAS) database.
DME/DME RNAV procedure design will only use DME facilities listed in the Airport/Facility Directory (A/FD). Although a procedure design issue, applicants may mitigate this restriction by:
(1) Having the DME/DME RNAV system only use DME facilities listed in the A/FD.
(2) Requiring exclusion of non-NAS DME facilities from the aircraft’s navigation database when the RNAV routes or procedures are within reception range of these non-NAS DME facilities.
(3) Demonstrating to the FAA that their RNAV system performs reasonableness checks to detect errors from the non-NAS DME facilities and excludes these facilities from the navigation position solution when appropriate (e.g., using the ARINC 424 coding to preclude tuning co-channel DME facilities when the DME facilities signals-in-space overlap).
See Appendix 1, paragraph 3 for guidance on testing of reasonableness checks.
c. DME Facility Relative Angles. When needed to generate a DME/DME position, the DME/DME RNAV system (referred to as FMS hereafter) must use, as a minimum, DMEs with a relative include angle between 30° and 150°. The FMS may use DME pairs outside these angles (for example, 20° to 160°).
Appendix 1
d. RNAV System Use of DMEs. The RNAV system may use any receivable DME facility (listed in the A/FD) regardless of its location. When needed to generate a DME/DME position, as a minimum, the RNAV system must use an available and valid low-altitude and/or high-altitude DME anywhere within the following region around the DME facility:
(1) Greater than or equal to 3 NM from the facility;
(2) Less than 40 degrees above the horizon when viewed from the DME facility; and
(3) For facilities with an ARINC 424 figure of merit (FOM), the RNAV system may use the FOM value as the acceptable, usable region:
If the ARINC 424 FOM is:
The aircraft’s DME/DME RNAV system must be:
Less than or equal to: And less than:
0 40 NM from the facility 12,000 ft above facility elevation 1 70 NM from the facility 18,000 ft above facility elevation 2 130 NM from the facility -- 3 160 from the facility -- NOTE 1: RNAV systems may use additional DME facilities (for example, a LOC DME facility may be used but is not required to be used for positioning). RNAV systems are not required to use the FOM value.
NOTE 2: RNAV routes and procedures may include new FOMs with Expanded Service Volumes.
(4) A valid DME facility:
(a) Broadcasts an accurate facility identifier signal,
(b) Satisfies the minimum field strength requirements, and
(c) Is protected from other interfering DME signals according to the co-channel and adjacent channel requirements.
e. No Requirement to Use VOR, NDB, LOC, IRU or AHRS. There is no requirement to use VOR (VHF omni-range), LOC (localizer), NDB (non-directional beacon), IRU (inertial reference unit) or AHRS (attitude heading reference system) during normal operation of the DME/DME RNAV system.
f. Position Estimation Error (PEE). A minimum of two DME facilities satisfying the criteria in paragraph 2, and any other valid DME facilities not meeting that criteria, the 95 percent PEE must be better than or equal to 1.75 NM. A flight technical error contribution not exceeding 1.0 NM (95 percent) may be assumed for RNAV 2 operations.
NOTE 1: This performance requirement is met for any navigation system that uses two DME stations simultaneously, limits the DME inclusion angle to between 30 and 150° and uses DME sensors that meet the accuracy requirements of
Appendix 1 TSO-C66c. If the RNAV system uses DME facilities outside the range identified above, the DME signal-in-space error can be assumed to be 0.1 NM 95 percent.
NOTE 2: When using a minimum of two DME facilities satisfying the criteria in appendix 3, paragraph 2.d., the 95 percent PEE must be better than or equal to the following equation:
)sin( )2 2( )2 2(22 , 2, 2, 1, 1/ α σ σ σ σσ sisairsisairDMEDME + + +≤
Single facility reference, where: σsis = 0.05 NM σair is MAX {(0.085 NM, (0.125% of distance)} α = inclusion angle (30o to 150o)
g. Preventing Erroneous Guidance from Co-Channel Facilities. The RNAV system must ensure co-channel DME facilities do not cause erroneous guidance. This could be accomplished by including VOR reasonableness checking when initially tuning a DME facility or excluding a DME facility when there is a co-channel DME within line-of-sight. See appendix 3, paragraph 3 for guidance on testing of reasonableness checks.
NOTE: The DME assessment cannot use a DME facility when there is a co-channel DME facility within line-of-sight.
h. Preventing Erroneous VOR Signals-in-Space. The RNAV system must ensure an erroneous VOR signal-in-space does not cause the position accuracy to exceed 1.75 NM for RNAV 2 and 0.87 NM for RNAV 1. This could be accomplished by not using VOR signals when DME/DME will be available or weighting and/or monitoring the VOR signal with DME/DME to ensure it does not mislead position results (for example, through reasonableness checks). See paragraph 3 for guidance on testing of reasonableness checks.
i. Ensuring RNAV Systems Use Operational Facilities. The RNAV system must use operational DME facilities. DME facilities listed by NOTAM as unavailable (for example, under test or other maintenance) could still reply to an airborne interrogation. (Therefore, non-operational facilities must not be used.) An RNAV system may exclude non-operational facilities by checking the identification or inhibiting the use of facilities identified as not operational.
j. Operational Mitigations. Operational mitigations defined to qualify equipment with this AC will not require pilot action during critical phases of flight, pilot monitoring of the RNAV system’s navigation updating source(s), or time intensive programming/ blackballing of multiple DME stations prior to executing a procedure.
NOTE 1: Blackballing single facilities listed by NOTAM as out-of-service and/or programming route/procedure-defined “critical” DME is acceptable when this mitigation requires no pilot action during a critical phase of flight. A programming requirement also does not imply the pilot should complete manual
Appendix 1 entry of DME facilities not in the navigation database. Instead, this allows RNAV systems to tune a critical DME, as appropriate to a specific route or procedure.
NOTE 2: The critical phase of flight is normally from the final approach fix on an approach procedure through missed approach, or from field elevation to 2,500 ft above airport elevation on a departure.
3. REASONABLENESS CHECKS. Many FMSs perform a reasonableness check to verify valid DME measurements. Reasonableness checks are very effective against database errors or erroneous system acquisition (such as co-channel facilities), and typically fall into two classes:
• Those the FMS uses after it acquires a new DME. The FMS compares the aircraft’s position before using the DME to the aircraft’s range to the DME, and
• Those the FMS continuously uses, based on redundant information (for example, extra DME signals or IRU data).
a. General Requirements. The reasonableness checks are intended to prevent navigation aids from being used for navigation update in areas where the data can lead to radio position fixing errors due to co-channel interference, multipath, and direct signal screening. In lieu of using radio navigation aid published service volume, the navigation system should provide checks, which preclude use of duplicate frequency NAVAIDs within range, over-the-horizon NAVAIDs, and use of NAVAIDs with poor geometry.
b. Assumptions. Under certain conditions, reasonableness checks can be invalid.
(1) Do not assume a DME signal remains valid just because it was valid when acquired.
(2) Do not assume extra DME signals are available. The intent of this baseline is to support operations where the infrastructure is minimal (for example, when only two DMEs are available for parts of the procedure).
c. Use Stressing Conditions to Test Effectiveness. When an applicant uses a reasonableness check to satisfy any requirement in this AC, they must test the effectiveness of the check under stressing conditions. An example of this condition is a DME signal that is valid at acquisition and ramps off during the test (similar to what a facility under test might do), when there is only one other supporting DME or two signals of equal strength.
4. PERFORMANCE CONFIRMATION PROCESS. New systems may demonstrate compliance with these criteria as part of the airworthiness approval. For existing systems, the manufacturer should determine compliance with the equipment and aircraft criteria in this appendix. Manufacturers who have achieved their compliance should provide this information by letter to their customers. Operators/pilots may use this approval as a basis for their operations.
Manufacturers are also requested to provide a copy of this letter to Flight Technologies and Procedures Division, AFS-400, (202) 267-8790, to facilitate making this information available to all operators. Guidance is provided below for both an airplane manufacturer and FMS and DME manufacturers.