Document ID: chunk:federal_register_of_legislation:F2018C00889:reg:22:p24
Version: federal_register_of_legislation:F2018C00889
Segment Type: reg
Provision Reference: reg 22 (pt 24/26)
Character Range: 231221–234426

and flown using area navigation system guidance.
       6.2.3For approach procedures, pilots must:
(a) extract the procedure from the on-board navigation database by name; and
(b) comply with the charted procedure. Heading-based legs associated with procedures may be flown using manual technique (based on indicated magnetic heading).
       Procedure validation
       6.3.1Procedures used with suitable GNSS-based area navigation systems, as either a substitute means of navigation or as an alternate means of navigation, must be verified for navigation data and operability using 1 of the following processes before being used:
(a) on-going, system-wide checks of navigation data and operability;
(b) as-needed, procedure specific checks of navigation data and operability.
       6.3.2These processes must ensure navigation data (e.g. waypoint names, waypoint sequence, distance between waypoints, heading/course/track information, and vertical path angles) used in airborne equipment conform to published information. The following methods to check the operability of procedure(s) are acceptable:
(a) suitable desktop analysis;
(b) simulator evaluation; or
(c) flight (in visual meteorological conditions).
       Operating requirements
       6.4.1Pilots may not manually enter published procedure or route waypoints via latitude/longitude, place/bearing, or place/bearing/distance into the aircraft navigation system.
       6.4.2Route centrelines must be maintained as close as practicable, as depicted by lateral deviation indicators or flight guidance systems during all operations described in this Appendix unless authorised to deviate by ATC or under emergency conditions.
Note 1   Brief deviations from the standard mentioned above are acceptable during and immediately after turns, but only to the minimal extent that accurate cross-track information may not be provided during the turn.
Note 2   Piloting standards usually require the aircraft to be flown to maintain lateral deviation not exceeding half the current accuracy requirement (RNP value) or half the lateral deviation scale. While this standard should be observed, pilots must also be aware that Navigation System Error + Flight Technical Error (lateral deviation) may not exceed the specified navigation accuracy. When carrying out approach operations, if the GNSS Horizontal Protection Limit (HPL) exceeds 0.15 NM, the allowable lateral deviation will be limited to less than the half scale value.
       6.4.3Operation on NDB or VOR procedures authorised under this Appendix requires navigation system accuracies of less than or equal to:
(a) 2 NM for en route operations (RNP 2);
(b) 1 NM for initial, intermediate and Missed Approach Segments (RNP 1); and
(c) 0.3 NM for Final Approach Segments (RNP APCH).
Note   GNSS system as a substitute for VOR may not be approved within 8 NM of the VOR and within 4 NM from the NDB.
       6.4.4RAIM or other approved integrity monitor must be available during these operations.
       Equipment requirements
       6.5.1Operators conducting regular passenger transport, or charter, operations must be equipped with at least 1 other independent navigation system in addition to the