Pilot's Operating Handbook
Supplement 69
Baro-VNAV approaches
Edition 0 - September 30, 2018
Rev. 0
Page 9.69.7
GNSS (GPS/SBAS) navigation system limitations
Navigation database limitations
The pilot must confirm at system initialization that the Navigation database is current.
If the AIRAC cycle will change during flight, the pilot must ensure the accuracy of
navigation data, including suitability of navigation facilities used to define the routes
and procedures for flight. If an amended chart affecting navigation data is published
for the procedure
,
the database must not be used to conduct the procedure
.
GPS/SBAS based IFR enroute
,
oceanic
,
and terminal navigation is prohibited unless
the pilot verifies and uses a valid
,
compatible, and current Navigation database or
verifies each waypoint for accuracy by reference to current approved data
.
Discrepancies that invalidate a procedure must be reported to Garmin International.
The affected procedure is prohibited from being flown using data from the Navigation
database until a new Navigation database is installed in the airplane and verified that
the discrepancy has been corrected
.
Contact information to report Navigation database discrepancies can be found at
www
.
Garmin
.
com>Support>Contact Garmin Support>Aviation
.
Pilots and operators
can view navigation data base alerts at www
.
Garmin
.
com>In the Air>NavData Alerts
.
RNP APCH including “GPS”
,
“or GPS”
,
“RNAV (GPS)” and “RNAV (GNSS)”
instrument approaches using the Garmin integrated flight deck are prohibited unless
the pilot verifies and uses the current Navigation database. GPS based instrument
approaches must be flown in accordance with an approved instrument approach
procedure that is loaded from the Navigation database into the flight plan by its name
.
Not all published Instrument Approach Procedures (IAP) are in the Navigation
database
.
Manual entry of waypoints using latitude/longitude or place/bearing is prohibited for
published RNP and RNAV routes.
Whenever possible
,
RNP and RNAV routes including Standard Instrument
Departures (SIDs) and Obstacle Departure Procedures (ODPs), Standard Terminal
Arrival (STAR), and enroute RNAV Q and RNAV T routes should be loaded into the
flight plan from the database in their entirety
,
rather than loading 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
.
PIM - DO NOT USE FOR FLIGHT OPERATIONS