Identifying Non-Directional Beacons (NDBs) in the Navigation Database

People often have questions about identifying non-directional beacons (NDBs) in the navigation database.

NDB selection in the flight management system (FMS) has changed over the years. For example, in earlier versions of APEX and EPIC, to select the NDB (MTH), the pilot would need to enter MTHNB as the identifier. In the later versions of FMS software, the pilot would only need to enter MTH as the identifier.

An “NDB Navaid” may be any NDB or locator available in the enroute terminal NDB files in the database. NDBs are included in all databases. In some, they are converted to waypoints with the suffix NB.

Waypoints located at any NDB type of facility take on the official 1-, 2-, 3-, or 4-character identifier of the facility in question.

Examples:

Facility                                                  Fix Field Entry

Ft. Nelson NDB becomes                       YE

For systems employing the “NDB as waypoint” concept, waypoints located at NDBs are identified using the station identifier followed by the alpha characters “NB.”

Examples:

Facility                                                  Fix Field Entry

Fort Nelson Can become                       YENB

Newark, NJ becomes                            EWRNB