Document ID: chunk:federal_register_of_legislation:F2018C00889:reg:5:p15
Version: federal_register_of_legislation:F2018C00889
Segment Type: reg
Provision Reference: reg 5 (pt 15/51)
Character Range: 65020–67944

or
(b) making manual entry of latitude, longitude or rho/theta values; or
(c) changing an RNAV SID or STAR database waypoint type from a fly-by to a flyover or vice versa.
Note   Wherever possible, the pilot in command should extract RNAV 1 and RNAV 2 routes in the en route domain from the database in their entirety rather than load individual waypoints from the database into the navigation system flight plan. The pilot in command may, however, select and insert individual, named fixes and waypoints from the navigation database, provided all fixes along the published route to be flown are inserted.
       7.5 The following checks and cross-checks must be made:
(a) a cross-check of the flight plan by comparing charts or other applicable resources with the navigation system flight plan and the aircraft map display (if applicable);
(b) if required, confirm the exclusion of specific navaids.
Note   Small differences between charted navigation information and displayed navigation data may be noted. Differences of 3 degrees or less due to the equipment manufacturer's application of magnetic variation or leg track averaging are operationally acceptable.
       7.6 Flight progress must be monitored for navigational reasonableness by periodic cross‑checks with available data from ground-based aids, if available.
       7.7 For RNAV 1 routes, a lateral deviation indicator, flight director or autopilot in LNAV mode must be used.
Note   For RNAV 2 routes, a lateral deviation indicator, flight director or autopilot in the LNAV mode is recommended. In lieu of a lateral deviation indicator, a navigation map display with equivalent functionality to a lateral deviation indicator is recommended.
       7.8 Where a lateral deviation indicator is used, scaling must be selected suitable for the navigation accuracy associated with the route or procedure, for example, full scale deflection ±1 NM for RNAV 1, ±2 NM for RNAV 2, or ±5 NM for (E)TSO-C129 ( ) equipment on RNAV 2 routes.
       7.9 Route centrelines must be maintained as close as practicable, as depicted by lateral deviation indicators or flight guidance, unless authorised to deviate by ATC or under emergency conditions. Navigation System Error + Flight Technical Error (lateral deviation) must not exceed the specified navigation accuracy.
       7.10 Brief deviations from the standard mentioned in subclause 7.9 of this Appendix 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.
       7.11 If ATC issues a heading assignment taking the aircraft off a route, the navigation system flight plan may only be modified when:
(a) ATC clearance is received to rejoin the route; or
(b) ATC confirms a new clearance.

8 Operating standards – flight procedures – RNAV SID requirements
       8.1 Before an eligible aircraft takes-off, the following