Pilot's Operating Handbook
Section 2
Limitations
EASA Approved
Edition 0 - March 05, 2019
Rev. 0
Page 2.6.8
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
.
GNSS integrity limitations
For flight planning purposes
,
in areas where SBAS coverage is not available, the pilot
must check RAIM availability. The availability of GPS integrity RAIM shall be
confirmed for the intended route of flight.
In the event of a predicted continuous loss of RAIM of more than five minutes for any
part of the intended route of flight, the flight should be delayed
,
cancelled
,
or re-routed
on a track where RAIM requirements can be met
.
For flight planning purposes
,
in Remote Continental and Oceanic areas, the pilot must
check FDE availability. Refer to the Table 2.6.1 - GNSS operational requirements, to
check maximum authorized FDE unavailability and WFDE Prediction program
references.
PIM - DO NOT USE FOR FLIGHT OPERATIONS
