Page 1-26 GIA 63 Installation ManualRevision T 190-00303-05confirmed for the intended flight (route and time). In the event of a predicted continuous loss of RAIM ofmore than five minutes for any part of the intended flight, the flight should be delayed, canceled, or re-routed on a track where RAIM requirements can be met.For flight planning purposes, operations where the route requires Class II navigation the aircraft’soperator or pilot-in-command must use the Garmin WFDE Prediction program to demonstrate that thereare no outages on the specified route that would prevent the Garmin GNSS navigation system to provideprimary means of Class II navigation in oceanic and remote areas of operation that requires (RNP-10 orRNP-4) capability. If the Garmin WFDE Prediction program indicates fault exclusion (FDE) availabilitywill exceed 34 minutes in accordance with FAA Order 8400.12A for RNP-10 requirements, or 25 minutesin accordance with FAA Order 8400.33 for RNP-4 requirements, then the operation must be rescheduledwhen FDE is available.Both Garmin GPS navigation receivers must be operating and providing GPS navigation guidance to theirrespective PFD for operations requiring RNP-4 performance.North Atlantic (NAT) Minimum Navigational Performance Specifications (MNPS) Airspace operationsper AC 91-49 and AC 120-33 require both GPS/SBAS receivers to be operating and receiving usablesignals except for routes requiring only one Long Range Navigation sensor. Each display computes anindependent navigation solution based on the on-side GPS sensor. However, either display willautomatically revert to the cross-side sensor if the on-side sensor fails or if the cross-side sensor isdetermined to be more accurate. [On G1000 installations a “BOTH ON GPS1” or “BOTH ON GPS2”message does not necessarily mean that one GPS has failed. Refer to the MFD AUX-GPS STATUS pageto determine the state of the unused GPS].Whenever possible, RNP and RNAV routes including Standard Instrument Departures (SIDs) andObstacle Departure Procedures (ODPs), Standard Terminal Arrival (STAR), and enroute RNAV “Q” andRNAV “T” routes should be loaded into the flight plan from the database in their entirety, rather thanloading route waypoints from the database into the flight plan individually. Selecting and insertingindividual named fixes from the database is permitted, provided all fixes along the published route to beflown are inserted. Manual entry of waypoints using latitude/longitude or place/bearing is prohibited.“GPS”, “or GPS”, and “RNAV (GPS)” instrument approaches using the Garmin navigation systems areprohibited unless the pilot verifies and uses the current Navigation database. GPS based instrumentapproaches must be flown in accordance with an approved instrument approach procedure that is loadedfrom the Navigation database.Not all published Instrument Approach Procedures (IAP) are in the Navigation database. Pilots planningon flying an RNAV instrument approach must ensure that the Navigation database contains the plannedRNAV Instrument Approach Procedure and that approach procedure must be loaded from the Navigationdatabase into the FMS flight plan by its name.IFR non-precision approach approval using the GPS/SBAS sensor is limited to published approacheswithin the U.S. National Airspace System. Approaches to airports in other airspace are not approvedunless authorized by the appropriate governing authority.The navigation equipment required to join and fly an instrument approach procedure is indicated by thetitle of the procedure and notes on the IAP chart. Use of the Garmin GPS/SBAS receivers to providenavigation guidance during the final approach segment of an ILS, LOC, LOC-BC, LDA, SDF, MLS orany other type of approach not approved for “or GPS” navigation is prohibited. When using the GarminVOR/LOC/GS receivers to fly the final approach segment, VOR/LOC/GS navigation data must beselected and presented on the CDI of the pilot flying.DRAFT Rev T 11/12/2010