Civil Aviation Order 20.91 (Instructions and directions for performance-based navigation) Instrument 2014
14Operating standards – flight planning – GNSS integrity availability
Start here
Get a plain-English read of 14
Turn the raw legal text into a practical explanation grounded in Civil Aviation Order 20.91 (Instructions and directions for performance-based navigation) Instrument 2014.
14 Operating standards – flight planning – GNSS integrity availability
14.1 When an RNP APCH is planned at the intended destination or designated alternate as part of flight planning, a prediction for GNSS integrity availability must be obtained from a ground-based source.
14.2 If a continuous loss of the GNSS integrity function for more than 5 minutes is predicted for any part of the RNP APCH operation, the flight plan must be revised, for example, by delaying the departure time or planning a different route.
14.3 When an aircraft is operating in oceanic airspace and navigation is based on GNSS, as part of flight planning a prediction for GNSS Fault Detection and Exclusion (FDE) availability for the intended route must be obtained.
14.4 For oceanic/remote operations, the maximum FDE outage duration cannot exceed 25 minutes for RNP-4 operation, 34 minutes for RNP-10 operation and 51 minutes for minimum navigation performance standards (MNPS) operation.
14.5 For continental en route operations a prediction for GNSS integrity availability is not required. If a continuous loss of the GNSS integrity function for more than 5 minutes occurs during PBN operations, Air Traffic Control must be advised.
14.6 For a PBN operation navigating with SBAS receivers, a check must be made for GNSS integrity availability in areas where SBAS is unavailable.
14.7 Paragraphs 14.1, 14.2, 14.3 and 14.4 do not apply to an aircraft whose RNP system can achieve LNAV accuracy less than 0.3 NM using requisite GNSS satellites.
Note Requisite GNSS satellites is defined in subsection 4 of this Order.