Jeppesen Approach Charts, the Primary NAVAID, and the Pre-Approach Brief That Has to Be Done Before You Enter the Clouds

The primary NAVAID on a Jeppesen instrument approach chart is the first item to confirm before any descent into instrument conditions. It appears in the plan view - the top-down diagram of the approach environment - boxed with its identifier, frequency, and Morse code sequence. Confirming it tuned and positively identified before the final approach course is a regulatory requirement, not a best practice, and the National Transportation Safety Board has identified inadequate approach briefing as a contributing factor in a significant portion of approach-related accidents.

How Jeppesen Charts Differ from Government Approach Plates

Most U.S. pilots first encountered instrument approach plates through charts produced by the National Aeronautical Charting Office under the FAA. These plates appear as the default in ForeFlight and similar applications, are updated on a 28-day cycle, and are available at no cost.

Jeppesen charts use different organization, different symbology, and place the minimums table in a different location. For pilots trained on government plates, a first encounter with a Jeppesen chart is disorienting - things are not where you expect them.

Jeppesen is the professional standard. Most Part 121 airline operations use it. Most Part 135 charter operators use it. Flight training programs oriented toward airline careers train on it. Fluency with Jeppesen charts is a required skill for anyone moving into professional aviation.

What Is the Primary NAVAID and Where Does It Appear on a Jeppesen Chart?

Every instrument approach is built around a navigation aid. For an ILS, that’s the localizer. For a VOR approach, it’s the VHF Omnidirectional Range station. For an NDB approach, it’s the non-directional beacon. The primary NAVAID is the navigation system the entire procedure is constructed around.

On a Jeppesen chart, primary NAVAID information appears in the plan view within a clearly defined box containing the identifier, frequency, and Morse code sequence. These three elements are grouped together because you need all three to complete a proper identification check.

Why NAVAID Identification Is a Regulatory Requirement

The Morse code printed on the chart is a procedural checkpoint. Before using a ground-based NAVAID for an instrument approach, you are required to identify it - tune the frequency, listen for the Morse code signal, and confirm it matches what’s on the plate. Modern avionics often decode and display the identifier automatically, which speeds the cross-check, but the confirmation still must happen.

A NAVAID that’s not available for instrument use doesn’t necessarily go silent. The station continues transmitting, but modifies its identification signal to indicate the station should not be used for approaches. Tuning the frequency and receiving a valid signal without actually identifying it can create a false sense of confidence.

The identification step verifies three things: you’re receiving the right station, it’s currently authorized for instrument procedures, and your avionics have captured it correctly. On an ILS approach with minimums of 200 feet above the runway and a quarter-mile visibility, the certainty that step provides is not optional.

ILS Approaches: Localizer, Glide Slope, and Automatic Pairing

The instrument landing system delivers two components. The localizer provides lateral guidance - a transmitter beyond the departure end of the runway broadcasts a course aligned with the runway centerline. A centered CDI means you’re on the extended centerline.

The glide slope provides vertical guidance - a separate transmitter broadcasts an angled signal, typically 3 degrees above horizontal, defining the standard descent path to the runway threshold.

Localizer frequencies fall in the range of 108.1 to 111.95 MHz on odd-tenth frequencies. Tuning that frequency automatically pairs your receiver with the glide slope transmitter - you do not tune them separately. That pairing is part of the international ILS standard.

The localizer identifier is typically the letter I followed by two or three letters identifying the airport or runway. That’s the Morse code sequence you cross-check against the printed identifier in the Jeppesen plan view.

VOR and NDB Approaches on Jeppesen Charts

VOR approaches are non-precision procedures - they provide lateral guidance but no vertical glidepath. VOR frequencies fall between 108 and 117.95 MHz. The omni bearing selector lets you set a specific radial; the CDI shows your deviation from that course. On a VOR approach, you fly step-down altitudes as defined in the profile view, descending at specified fixes, until reaching the minimum descent altitude.

You hold the MDA until you see the runway environment or reach the missed approach point. That point - whether a crossing radial, a DME reading, or a timing fix - must be briefed before the approach begins.

NDB approaches use the non-directional beacon and an automatic direction finder. The ADF needle points toward the station. These approaches are declining in the United States but remain certificated at many airports, particularly in Alaska and at smaller fields. A working ADF, a tuned beacon, and a confirmed Morse code identifier are all required.

RNAV and LPV Approaches: When GPS Replaces the Ground Station

Area navigation (RNAV) approaches - including GPS procedures and LPV (Localizer Performance with Vertical guidance) approaches - are built around the GPS receiver rather than a ground-based NAVAID. What you confirm before descent shifts accordingly.

You’re not listening for a Morse code identifier. You’re confirming GPS integrity, database currency, and the correct procedure loaded in your flight management system. Receiver autonomous integrity monitoring (RAIM) alerts or WAAS fault detection provide the equivalent assurance that ground-station identification provides on a traditional approach.

LPV approaches can have decision altitudes as low as 200 feet with visibility requirements equivalent to a Category I ILS. The precision is real, and the dependence on GPS integrity is equally real. The distinction between an LPV and a full ILS matters when planning alternates or evaluating options if GPS degrades en route.

The habits built around traditional NAVAID identification transfer directly to RNAV flying. The specific action changes; the discipline of verification does not.

The Glass Cockpit Complacency Risk

Moving maps and integrated flight management systems make approaches feel more automated than they are. When the display is drawing the approach path on screen and the CDI is coupled to GPS, there’s a temptation to reduce the depth of the approach brief - to assume that because the system has the approach loaded, the pilot has it briefed.

Those are not the same thing. A system with the right approach loaded can still guide a crew to the wrong minimums if the specific procedure wasn’t verified. Incorrect data can appear if the database is not current. The approach brief is the human layer on top of the avionics, not a redundant step below them.

The History Behind Jeppesen’s Chart Design

Elrey Borge Jeppesen was an airmail and early airline pilot in the late 1920s and early 1930s, flying at a time when instrument procedures were being developed in real time. Weather minimums were poorly defined. Obstruction data was scattered or absent. Pilots relied on local knowledge and personal experience.

Jeppesen kept a black notebook - every useful piece of information gathered at every airport he flew into. Smokestack heights near the field. Road patterns that led to the runway. Personal minimums for specific approaches. By 1930, other pilots were borrowing it. By 1934, he was selling charts commercially. By mid-century, Jeppesen and Company had become the global standard for instrument approach documentation. Boeing acquired the company in the 1990s, and Jeppesen charts are used by professional crews worldwide.

The Jeppesen format was built from operational experience, not administrative process. The layout reflects what a pilot in the cockpit actually needs, in the sequence they need it. The primary NAVAID box in the plan view - identifier, frequency, and Morse code together - is a direct expression of that philosophy.

The Six-Step Pre-Approach Brief

This framework applies regardless of chart format:

1. Confirm the approach name and runway. What procedure are you flying and which runway does it serve?

2. Find the primary NAVAID. Frequency, identifier, Morse code - or GPS integrity confirmation for RNAV procedures. Tune and identify it before you’re on the final approach course.

3. Trace the routing. Where does the approach start? What is the initial approach fix and its altitude? Are you being vectored to final or flying the full procedure?

4. Review the profile. Step-down fixes and altitudes for non-precision approaches. Glide slope intercept altitude for precision. Know what terrain is below you at each point.

5. Brief the minimums. Decision altitude and required visibility for precision approaches. Minimum descent altitude and required visibility for non-precision. These must be in memory before descent begins - not something to read off the plate at 400 feet while managing descent rate and airspeed simultaneously.

6. Brief the missed approach. Every brief ends here. If the runway environment isn’t visible at minimums, you need to know what to do in the next two or three seconds. Visualize the turn, the altitude, the fix. Flying crew, brief it aloud.

Six items. Two minutes if you know the chart. Longer if you don’t. Every additional minute spent orienting to the plate is workload added at exactly the wrong point in the flight.

Why the NTSB Takes Approach Briefing Seriously

The NTSB has examined approach accidents where pilots descended below minimums or became confused during the procedure. Inadequate approach briefing is a documented contributing factor in a significant portion of those cases - not always the sole cause, but present often enough to be a recurring focus in accident analysis and instrument proficiency check standards.

The brief is not bureaucratic overhead. It’s the cognitive preparation that creates capacity for the actual flying. When the minimums are already in memory, the missed approach is already visualized, and the primary NAVAID is already confirmed - you’re flying the approach with information you already have, not searching for it in actual instrument conditions.

Building Approach Chart Literacy as a Practiced Skill

Chart literacy improves with deliberate practice. Pull a Jeppesen plate for your home airport - even if you never intend to use Jeppesen operationally. Find the primary NAVAID box in the plan view. Trace the procedure inbound. Brief the minimums and missed approach aloud. Time yourself. Repeat until the sequence is automatic and the scan is fast.

The goal is to reach the initial approach fix with the chart already in your head, not in your hands.

Key Takeaways

The primary NAVAID on a Jeppesen chart appears in the plan view with its identifier, frequency, and Morse code - tune and positively identify it before beginning any instrument descent
A NAVAID unavailable for instrument use continues transmitting with a modified identifier signal; skipping the identification check can mask a station that shouldn’t be used
ILS localizer frequencies (108.1–111.95 MHz, odd-tenth) automatically pair with the glide slope transmitter when tuned - no separate frequency required
RNAV and LPV approaches shift identification from a Morse code check to GPS integrity, database currency, and correct procedure loading - the verification discipline is identical
The NTSB has documented inadequate approach briefing as a contributing factor in a significant portion of approach-related accidents
A complete pre-approach brief covers six items in sequence: approach name and runway, primary NAVAID, routing, profile, minimums, and missed approach procedure