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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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

8.5.5.1.5. Airport sketch. The airport sketch and all the information associated<br />

with it.<br />

8.5.5.2. Operating hours. The IAP books contain complete radar minimums. The<br />

IFR Supplement contains time periods when the aerodrome and its NAVAIDs are<br />

operational. It also indicates when NAVAIDs will be off the air for NO-NOTAM<br />

preventive maintenance, as well as other items unique to the particular operation of<br />

the airfield.<br />

8.5.6. Reviewing RNAV (GPS) IAPs. The following section highlights elements of<br />

RNAV (GPS) IAPs that differ from IAPs based on conventional NAVAIDs.<br />

8.5.6.1. Equipment requirements. The “TERMS/LANDING MINIMUMS DATA”<br />

(Section A) of the U.S. Government Terminal Procedures books provide a description<br />

of the aircraft equipment requirements for RNAV (GPS) IAPs. More detailed<br />

information can be obtained via the AFFSA web page. Pilots are responsible for<br />

ensuring that the aircraft is suitably equipped for the level of minimums used. Be<br />

aware that very few RNAV (GPS) IAPs may be flown using DME/DME RNAV<br />

systems. Note that the “(GPS)” in the approach title does not indicate the approach<br />

may be flown in aircraft with any GPS equipment. GPS equipped aircraft must meet<br />

the equipment requirements described above.<br />

8.5.6.1.1. Use of LNAV/VNAV DA requires certified VNAV functionality or<br />

WAAS on the aircraft. Use of GLS minimums requires WAAS equipment on<br />

the aircraft.<br />

8.5.6.2. Procedure name. Where multiple RNAV procedures exist to the same<br />

runway, subsequent RNAV procedure titles will be followed by the suffix X, Y, or Z<br />

(e.g., “RNAV (GPS) Z RWY 22”). ATC clearance for the RNAV procedure will<br />

authorize the pilot to use any landing minimums for which the pilot and/or aircraft is<br />

capable and authorized.<br />

8.5.6.3. Chart Terminology.<br />

8.5.6.3.1. Decision Altitude (DA). DA replaces the term Decision Height (DH)<br />

as a step towards harmonization with ICAO terminology. The published descent<br />

profile is flown to the DA, where a missed approach will be initiated if visual<br />

references for landing are not established. Obstacle clearance criteria accounts for<br />

a momentary descent below DA while transitioning to the missed approach.<br />

8.5.6.3.2. Minimum Descent Altitude (MDA). MDA carries the same meaning<br />

as in conventional IAPs, and is associated with LNAV minimums. Obstacle<br />

clearance is based on no descent below MDA. Thus, if vertical guidance is used<br />

down to LNAV minimums, pilots must ensure that the descent is broken in time<br />

to level off at MDA if visual references for landing are not established.<br />

8.5.6.3.3. LPV. LPV minimums are based on augmented GPS systems (WAAS)<br />

providing near ILS accuracy. "LPV" is not an acronym, but the title of a set of<br />

approach minima associated with specific performance criteria. LPV can also be<br />

referred to as GNSS Landing System (GLS). LPV minima can be as low as a<br />

DA(H) of 250 feet above the ground, with visibility as low as 1/2 mile.

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

Saved successfully!

Ooh no, something went wrong!