AIM 

4/20/23 

the navigational system providing final approach guidance and a letter (e.g., VOR A). More than one 

navigational system separated by a slash indicates that more than one type of equipment must be used to execute 

the final approach (e.g., VOR/DME RWY 31). More than one navigational system separated by the word “or” 

indicates either type of equipment may be used to execute the final approach (e.g., VOR or GPS RWY 15). 

(b) 

In some cases, other types of navigation systems including radar may be required to execute other 

portions of the approach or to navigate to the IAF (e.g., an NDB procedure turn to an ILS, an NDB in the missed 

approach, or radar required to join the procedure or identify a fix). When radar or other equipment is required 

for procedure entry from the en route environment, a note will be charted in the planview of the approach 

procedure chart (e.g., RADAR REQUIRED or ADF REQUIRED). When radar or other equipment is required 

on portions of the procedure outside the final approach segment, including the missed approach, a note will be 

charted in the notes box of the pilot briefing portion of the approach chart (e.g., RADAR REQUIRED or DME 

REQUIRED). Notes are not charted when VOR is required outside the final approach segment. Pilots should 

ensure that the aircraft is equipped with the required NAVAID(s) in order to execute the approach, including the 

missed approach. 

NOTE

−

 

Some military (i.e., U.S. Air Force and U.S. Navy) IAPs have these “additional equipment required” notes 

charted only in the planview of the approach procedure and do not conform to the same application standards 

used by the FAA. 

(c) 

The FAA has initiated a program to provide a new notation for LOC approaches when charted on an 

ILS approach requiring other navigational aids to fly the final approach course. The LOC minimums will be 

annotated with the NAVAID required (e.g., “DME Required” or “RADAR Required”). During the transition 

period, ILS approaches will still exist without the annotation. 

(d) 

Many ILS approaches having minima based on RVR are eligible for a landing minimum of RVR 1800. 

Some of these approaches are to runways that have touchdown zone and centerline lights. For many runways 

that do not have touchdown and centerline lights, it is still possible to allow a landing minimum of RVR 1800. 

For these runways, the normal ILS minimum of RVR 2400 can be annotated with a single or double asterisk or 

the dagger symbol “

†

”;

 for example “** 696/24 200 (200/1/2).” A note is included on the chart stating “**RVR 

1800 authorized with use of FD or AP or HUD to DA.” The pilot must use the flight director, or autopilot with 

an approved approach coupler, or head up display to decision altitude or to the initiation of a missed approach. 

In the interest of safety, single pilot operators should not fly approaches to 1800 RVR minimums on runways 

without touchdown and centerline lights using only a flight director, unless accompanied by the use of an 

autopilot with an approach coupler. 

(e) 

The naming of multiple approaches of the same type to the same runway is also changing. Multiple 

approaches with the same guidance will be annotated with an alphabetical suffix beginning at the end of the 

alphabet and working backwards for subsequent procedures (e.g., ILS Z RWY 28, ILS Y RWY 28, etc.). The 

existing annotations such as ILS 2 RWY 28 or Silver ILS RWY 28 will be phased out and replaced with the new 

designation. The Cat II and Cat III designations are used to differentiate between multiple ILSs to the same 

runway unless there are multiples of the same type. 

(f) 

RNAV (GPS) approaches to LNAV, LP, LNAV/VNAV and LPV lines of minima using WAAS and 

RNAV (GPS) approaches to LNAV and LNAV/VNAV lines of minima using GPS are charted as RNAV (GPS) 

RWY (Number) (e.g., RNAV (GPS) RWY 21). 

(g) 

Performance

−

Based Navigation (PBN) Box. As charts are updated, a procedure’s PBN requirements 

and conventional equipment requirements will be prominently displayed in separate, standardized notes boxes. 

For procedures with PBN elements, the PBN box will contain the procedure’s navigation specification(s); and, 

if required: specific sensors or infrastructure needed for the navigation solution, any additional or advanced 

functional requirements, the minimum Required Navigation Performance (RNP) value, and any amplifying 

remarks. Items listed in this PBN box are REQUIRED for the procedure’s PBN elements. For example, an ILS 

with an RNAV missed approach would require a specific capability to fly the missed approach portion of the 

procedure. That required capability will be listed in the PBN box. The separate Equipment Requirements box 

Arrival Procedures

5

−

4

−

6