BY ORDER OF THE SECRETARY OF THE AIR FORCE AIR FORCE ...

136
AFMAN 11-217V1 3 JANUARY 2005
on the paper copy of the terminal procedure (to include the missed approach) as
discussed in the section 7.13 of this AFMAN.
7.12.5.1.4. CDI must be set to terminal sensitivity (+- 1 nm) or confirmed the
receiver has automatically set it.
7.12.5.1.5. A predictive RAIM check must be accomplished prior to
commencing the approach. If RAIM outages are predicted or occur, the flight
must rely on other approved equipment; otherwise the flight must be rerouted,
delayed, or canceled.
7.12.5.1.6. Comply with alternate requirements IAW AFI 11-202 Volume 3
General Flight Rules.
7.13. Data Base Issues for RNAV and GPS Navigation. GPS and other RNAV
procedures rely on data extracted from the aircraft navigation database. The potential for
serious navigation errors is created by inherent properties of database creation and its use by
aircrew and aircraft systems. In order to mitigate these potential errors crews must be
familiar with database issues and required procedures.
7.13.1. Aircraft use navigation databases provided by either National Geospatial-
Intelligence Agency (NGA) (i.e. DAFIF) or a commercial vendor (i.e. Jeppesen). These
databases contain a worldwide list of airports, navigation aids, waypoints, and instrument
procedures. Outside the US NAS, this data is provided by host nations, and is not
necessarily quality-checked by database providers during database creation. Navigation
data may be filtered and tailored to meet individual aircraft requirements. Jeppesen
tailors their data to meet customer specifications, while DAFIF data is filtered and
formatted by outside contractors. Updated navigation data is published on a 28-day cycle.
7.13.1.1. Database Requirements. In order to use GPS for the terminal area, all
procedures (DP, Standard Terminal Arrival (STAR), IAP) must be retrieved in
their entirety from a current, approved navigation database. Only those approaches
included in the receiver database are authorized, and must display as full approaches
(not advisory approaches which would not allow pilot to "arm" the approach).
7.13.1.1.1. Manual Data Base Manipulation. Users may not alter terminal
procedures retrieved from the equipment database. However, this requirement
does not prevent the storage of “user-defined” data. This requirement also does
not preclude aircrew from complying with ATC instructions by proceeding direct
to a point on a STAR/DP or by receiving ATC vectors onto course.
7.13.1.1.1.1. NOTE: This “user-defined” data cannot be part of a terminal
procedure, to include IAF or feeder fixes.
7.13.2. Database related errors have occurred at all stages of database development and
use. Host nations have provided inaccurate data; database providers have introduced
errors during database creation and aircraft specific tailoring; aircrew have selected
incorrect waypoint/procedure data; finally, aircraft flight management systems/navigation
computers have flown instrument procedures in a manner that does not match the charted
procedure.
7.13.3. A paper copy of the applicable instrument procedure (IAP, SID, STAR) must