Learn why navigation beacons transmit Morse code identifiers, how pilots verify them, and what a missing or incorrect ident means.
Navigation beacons transmit Morse code identifiers so pilots can confirm that the received signal belongs to the intended facility, rather than another station using the same frequency. In aviation, hearing and matching that identifier is the positive identification check made before relying on VOR, NDB, ILS or associated DME guidance.
What does the Morse identifier actually prove?
The identifier confirms which navigation facility the receiver is hearing; it does not provide the bearing, radial or distance itself. Frequencies are reused between suitably separated stations, and unusual propagation, incorrect tuning or selecting the wrong radio can produce guidance from somewhere other than the expected beacon.
Each facility has a published identifier, normally shown as letters and their corresponding dots and dashes on charts or approach procedures. The transmitted sequence repeats regularly so the pilot can compare the complete code with that publication.
A correct identifier does not guarantee that every indication is being interpreted correctly. It will not prevent an incorrectly set OBS, localiser back-course confusion, ADF tracking error or use of the wrong DME source. Instrument flags, published service information and sensible cross-checks still matter.
Why is Morse code used instead of ordinary speech?
Morse provides a short, standardised and language-independent way to identify a station repeatedly without occupying much audio time. Its keyed tone can be carried alongside the navigation signal, recognised through noise and generated automatically without a continuous voice broadcast.
Some facilities also transmit voice information, and certain equipment can decode and display the identifier automatically. A cockpit display may instead be showing a database label associated with the tuned frequency, however, so pilots must understand whether the displayed name came from the received radio signal or merely from stored data.
Which navigation aids transmit an identifier?
Most conventional radio navigation aids provide an audible or automatically decoded identification signal, although the format and method differ.
| Navigation aid | Typical identification |
|---|---|
| VOR | Usually a three-character Morse identifier heard through the selected NAV receiver; some stations also carry voice. |
| NDB | Usually a two- or three-character identifier modulated onto the beacon carrier and monitored through the ADF audio. |
| ILS localiser | A published Morse identifier, commonly presented with an I prefix. The glideslope does not normally have a separate pilot-audible identifier. |
| DME | An identification associated or co-ordinated with the paired VOR or ILS, or an independent identifier for a stand-alone facility. |
How do pilots check a beacon identifier?
Pilots tune the facility, route its identification audio to the headset or speaker, and compare the complete received code with the published identifier before using its guidance.
- Tune the published frequency. Check that it has been placed in the active receiver rather than left in standby.
- Select the correct audio source. Choose NAV1, NAV2 or ADF as appropriate and set enough identification volume to hear it. Our explanation of how NAV, ADF and audio-panel controls interact covers the controls that commonly cause silence.
- Listen to a complete sequence. Compare every letter with the dots and dashes printed on the chart or procedure. A fragment that sounds close is not a positive identification.
- Cross-check the instrument. Confirm that warning flags are clear and that the indicated bearing, radial or distance is plausible for the aircraft’s position.
For the complete radio-navigation workflow, see our practical VOR and NDB tuning procedure.
What should you do if the identifier is missing or wrong?
A missing or incorrect identifier means the facility has not been positively identified and its guidance should not be relied upon until the cause is resolved. A station fault may cause the identifier or navigation signal to be removed, but cockpit audio routing and reception limits are frequent causes too.
- Recheck the frequency, active radio and selected audio-panel source.
- Increase identification volume and confirm that the headset or speaker output is not muted.
- Check range, altitude and terrain. VOR reception is largely line-of-sight, while NDB reception is vulnerable to interference and propagation effects; our guide to why NDB reception becomes unreliable at range explains those limits.
- Compare the received code carefully. A wrong identifier is stronger evidence of the wrong station or frequency than no audio at all.
- Use another suitable navigation source and check published facility status information where available.
Why does Morse code keep beeping in a flight simulator?
Repeated Morse beeping in a flight simulator usually means the NAV or ADF identification audio has been selected on the audio panel. Muting that monitor source normally stops the sound without untuning the receiver or disabling the needle indication.
A mistake we see often is switching off the audio before identifying the beacon. Match the code first, then mute it if desired. FSX users can follow the specific steps to mute FSX Morse identification audio without untuning the radio.
Default aircraft and add-ons vary in how completely they model identification audio. If the published identifier and simulated transmission disagree, check that the aircraft’s navigation data, scenery and chart information represent the same facility configuration rather than assuming the received code is close enough.