08.01.2015 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

AFMAN 11-217V1 3 JANUARY 2005 137<br />

always be available and crosschecked in the terminal environment.<br />

7.13.3.1. Data Base Procedures.<br />

7.13.3.1.1. Prior to flight, crews must check navigation database validity. If the<br />

database has expired, the crew:<br />

7.13.3.1.1.1. May continue a mission with an expired database if the<br />

database information required for the flight can be verified with current<br />

flip.<br />

7.13.3.1.1.2. Shall get the database updated at the first opportunity.<br />

7.13.3.1.1.3. May not use the database to fly procedures that require<br />

terminal or better accuracy (i.e. terminal or approach).<br />

7.13.4. Defining Airways<br />

7.13.4.1. Conventional (Overlay) Airways. Appropriately certified RNAV<br />

equipment may be used to fly conventional airways (e.g. FAA J /V routes). These<br />

routes may be either retrieved from the aircraft database or constructed by manually<br />

entering waypoints.<br />

7.13.4.1.1. If within aircraft capabilities, conventional airways should be<br />

retrieved from the aircraft database using the airway identifier.<br />

7.13.4.1.2. If airways cannot be retrieved from the database using the airway<br />

identifier, conventional airways may be constructed by manual entry of associated<br />

waypoints/NAVAIDS. These waypoints/NAVAIDS should be retrieved from the<br />

database by waypoint name if possible. Entry of all airway waypoints is not<br />

required. At a minimum, all compulsory waypoints, all NAVAIDS, and any<br />

waypoint associated with a change in course must be entered. If airways are<br />

entered manually, waypoint sequence must be verified by another crewmember<br />

on multi-crew aircraft.<br />

7.13.4.2. RNAV Airways. RNAV airways should be retrieved in their entirety from<br />

the database using the airway identifier. If entered manually, aircrew must ensure<br />

that all waypoints are entered and flyby/flyover attributes are correctly entered.<br />

7.13.5. RNAV Terminal Area Operations.<br />

7.13.5.1. Some databases may not contain all transitions or departures from all<br />

runways. Terminal area and instrument approach procedures must be retrieved in<br />

their entirety from the navigation database. These procedures may not be modified or<br />

entered manually.<br />

7.13.5.2. Prior to commencing a terminal area or instrument approach procedure,<br />

crews must confirm waypoint name, sequence, course, distance, and altitude<br />

information match charted information (to include the missed approach segment).<br />

Waypoint type (flyby vs. flyover) should also be confirmed if this information is<br />

available.<br />

7.13.5.3. In the event of differences between the terminal procedure chart or<br />

approach chart and database, the published approach chart, supplemented by

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!