Detailed working notes on ICAO requirements for the Non-Directional Beacon (NDB) — a legacy LF/MF radio navigation aid still standardised in Annex 10. This folder expands the summary in topics/ndb_requirements.md into per-aspect files so each can be read on its own.

Files in this folder#

• overview.md — what an NDB is, its role in conventional navigation, and the global decommissioning trend driven by PBN.
• components.md — the physical building blocks of an NDB station: transmitter, antenna and counterpoise, monitor, identification keying, and the LF/MF (190–1750 kHz) frequency band.
• blocks.md — usage roles. The classical operational categories: en-route NDB, terminal/holding NDB, locator at the outer or middle marker, and emergency / contingency uses.
• threads.md — the requirement domains that any NDB installation must satisfy: signal quality, coverage, integrity, identification.
• modules.md — anatomy of a single NDB requirement bucket: signal-in-space, ground monitor, identification, and propagation considerations including night effect.
• enablers.md — the supporting activities and infrastructure: flight inspection, frequency planning and coordination, monitor systems, and regulatory / certification framework.
• performance_objectives.md — KPAs (availability, integrity, continuity) and KPIs that apply to a station-level conventional aid.
• timeline.md — Annex 10 history of NDB SARPs and the phase-out trajectory under Performance-Based Navigation (PBN).
• references.md — consolidated ICAO and external references for everything in this folder.

Reading order#

Start with overview.md, then components.md and blocks.md for the "what" and the "where". Move to threads.md and modules.md for the detailed requirement structure. Use enablers.md and performance_objectives.md for the operating regime, and timeline.md plus references.md for historical and citation context.

Source basis#

Content is grounded in:

• ICAO Annex 10 (Aeronautical Telecommunications), Volume I — Radio Navigation Aids; Chapter 3, §3.4 (NDB SARPs), §3.9 (ADF airborne receiver), Attachment C, §6 (NDB guidance material).
• ICAO Doc 8071 — Manual on Testing of Radio Navigation Aids, Volume I (testing of ground-based radio navigation systems including the NDB). Authoritative source for flight inspection tolerances; not held in the local library.
• ICAO Doc 9613 — Performance-Based Navigation (PBN) Manual. Frames the rationalisation context for conventional aids.
• ICAO Doc 8168 — PANS-OPS, Volumes I and II, for NDB fix tolerances, splay angles, and approach procedure design criteria.
• Regional rationalisation strategies (EUROCONTROL European Plan for Conventional Navigation Aids; FAA VOR Minimum Operational Network; national AIC actions). Web-fallback where flagged.

What an NDB is#

An NDB (Non-Directional Beacon) is a ground-based radio transmitter operating in the LF/MF band that radiates an omnidirectional continuous-wave carrier, identified by a Morse-code call sign. It carries no bearing information itself; bearing is derived on board by an ADF (Automatic Direction Finder) receiver that uses a loop and sense antenna to measure the direction of arrival of the ground-wave signal relative to the aircraft's longitudinal axis.

Because the signal is non-directional and unkeyed in azimuth, an NDB is the simplest possible radio navigation aid: a transmitter, an antenna, a monitor, and a Morse keyer. That simplicity is also its weakness — the aid offers no integrity coding, no precision, and no protection against propagation anomalies.

Role in conventional navigation#

In the conventional (pre-PBN) navigation environment, the NDB filled several distinct operational roles, each with its own coverage and performance expectation:

• En-route NDB — defining airway centrelines or reporting points in remote, oceanic, or low-density continental airspace where VOR/DME coverage was not justified.
• Terminal / holding NDB — defining holding fixes, initial approach fixes, and missed-approach holds at aerodromes.
• Locator (LOM / LMM) — a short-range NDB co-located with the outer or middle marker of an ILS, used as an aid to ILS interception and final approach.
• Aerodrome homer — a single beacon at or near the aerodrome supporting a non-precision NDB approach.

The NDB has historically been valued for its low cost, simple antennas, graceful degradation, and its ability to provide service over the radio horizon via ground-wave propagation in regions where line-of-sight aids (VOR, DME) were impractical.

Why the requirements exist#

The ICAO requirements for NDBs are consolidated in Annex 10 (Aeronautical Telecommunications), Volume I, Chapter 3, §3.4 (the SARPs proper) with supporting guidance material in Attachment C, §6. ADF airborne receiver requirements are in §3.9. PANS-OPS (Doc 8168) provides the procedure-design rules: NDB system-use bearing tolerances, fix construction, and approach criteria.

The requirements answer four questions:

1. What signal must the station radiate? Frequency band, frequency tolerance, modulation type, modulation depth, identification format, keying speed, radiated power.
2. What coverage must the signal achieve? Minimum field strength, wanted-to-unwanted signal ratio, day-versus-night effective coverage.
3. How is the station kept honest? Continuous monitoring of carrier power, identification, and modulation, with defined detection and removal-from-service criteria.
4. How is the aid used in procedures? PANS-OPS bearing tolerances, splay angles, and obstacle-clearance criteria.

The decommissioning trend#

The NDB is now formally a legacy aid. The PBN Manual (Doc 9613) and the Annex 10 amendment cycle treat the NDB as having no PBN role beyond position cross-checking. Globally, the trend is one of progressive withdrawal:

• The FAA has been removing NDBs as part of broader navaid right-sizing alongside the VOR Minimum Operational Network (MON).
• EUROCONTROL's European Plan for Conventional Navigation Aids rationalises VOR/DME/NDB infrastructure across ECAC States as PBN matures (web-fallback reference).
• Airservices Australia has decommissioned NDBs, VORs and DMEs since 2016 in line with Australia's PBN policy.
• Thailand's CAAT issued AIC 10/24 retiring NDBs at several aerodromes.
• Many APAC and MID States now retain NDBs only where a documented safety case (GNSS contingency, non-equipped traffic, transition routes) justifies retention.

Annex 10 SARPs for NDBs nonetheless remain in force, because where the aid is operated, it must still meet the published signal-in-space and coverage standards. The requirements continue to matter for two populations of users:

• States retaining NDBs as a backup to GNSS-based PBN, particularly in remote regions or to support ILS interception (locators).
• States in earlier stages of PBN transition where NDB approaches and routes are still in operational use.

Where this folder fits#

This detailed reference unpacks each requirement bucket: signal-in-space, coverage, identification, monitoring, propagation considerations, and the supporting flight-inspection and frequency- planning regime that keeps the SARPs achievable in service.

An NDB station is one of the simplest radio installations in civil aviation. Five physical and functional components together must satisfy the Annex 10 Volume I, §3.4 SARPs.

1. Transmitter#

The transmitter generates a continuous-wave carrier in the LF/MF band and applies the identification keying. Annex 10 Vol I, §3.4.4 sets the band and tolerance:

• Frequency band: 190 kHz to 1 750 kHz (Annex 10 Vol I, §3.4.4.1). The aviation NDB band overlaps the lower end of the AM broadcast band, which has historical implications for interference protection.
• Frequency tolerance: 0.01 percent in general; tightened to 0.005 percent for NDBs above 200 W transmitter power and operating on 1 606.5 kHz or above (§3.4.4.2).
• Radiated power: not more than 2 dB above the level needed to achieve the agreed rated coverage, except where the excess is regionally coordinated (§3.4.3). The intent is to prevent over-radiation that would pollute adjacent channel assignments.

Modern NDB transmitters are typically solid-state, with redundant power amplifiers and automatic changeover. Power levels in service range from a few watts (a locator at an outer marker) to several kilowatts (a long-range coastal en-route beacon).

2. Antenna and counterpoise#

NDB antennas are vertically polarised radiators sized for a small fraction of the wavelength at LF/MF. Common configurations:

• T-antenna or top-loaded vertical wire — historic standard for high-power en-route stations.
• Mast radiator with a top hat or top capacitive loading — common for medium-power terminal stations.
• Short whip with extensive ground radials or counterpoise — used for low-power locators where space is constrained.

Because the antenna is electrically very short, a good RF ground system (buried radials, counterpoise mat) is critical to radiation efficiency. Poor counterpoise condition is a frequent cause of field-strength shortfalls discovered during flight inspection.

3. Monitor#

Annex 10 Vol I, §3.4.8 requires automatic monitoring detecting:

• A reduction of carrier power of more than 50 percent below that required for the rated coverage (§3.4.8.1 a)).
• Failure to transmit the identification signal (§3.4.8.1 b)).
• Malfunctioning or failure of the means of monitoring itself (§3.4.8.1 c)).

For non-locator NDBs the monitor must operate continuously during hours of service, and an alarm at a control point must be raised when any of the above conditions is detected (§3.4.8.4). The monitor itself is typically a far-field or near-field RF detector connected to the keyer logic, with pre-set thresholds for power, identification, and modulation.

4. Identification keying#

Identification is a defining feature of every aviation NDB. Annex 10 Vol I, §3.4.5 sets the rules:

• Each NDB transmits a two-letter or three-letter Morse code group as its identification (§3.4.5.1).
• Keying speed is approximately 7 words per minute (§3.4.5.2).
• The identification is transmitted at least once every 30 seconds for a standard NDB; for locator-class NDBs (rated coverage at or below 92.7 km / 50 NM) it is transmitted at least three times every 30 seconds (§3.4.5.3).
• For NON/A2A emissions the identification keying takes the form of an on/off keyed audio modulating tone of approximately 1020 Hz (§3.4.6.2); for NON/A1A emissions the carrier itself is interrupted.

Identification is the only integrity check available to the pilot — the absence of, or change in, the Morse identification is the cue that the station is unserviceable.

5. Emission and modulation#

Annex 10 Vol I, §3.4.6 distinguishes two emission classes:

• NON/A2A — uninterrupted carrier with on/off keyed amplitude- modulating tone for identification. Modulation depth is set as near to 95 percent as practicable (§3.4.6.2). Required for holding, approach and landing aids and any NDB with rated coverage of 92.7 km (50 NM) or more (§3.4.6.1).
• NON/A1A — unmodulated carrier interrupted to form Morse identification. Permitted where high beacon density or coverage limitations make NON/A2A impractical (§3.4.6.1.1). NON/A1A imposes a higher demand on the airborne receiver, which must include a beat frequency oscillator (BFO) to render the keying audible.

6. Frequency band character#

Operating at LF/MF (190 kHz to 1 750 kHz) gives the NDB its defining propagation behaviour:

• Ground-wave propagation dominates over land and sea, providing predictable daytime coverage that follows the curvature of the Earth.
• Sky-wave propagation appears at dusk and at night as the D-layer weakens, producing fading, bearing errors, and the well-known night effect (Annex 10 Vol I, Attachment C, §6.2.3).
• Atmospheric noise rises sharply below about 500 kHz, especially in tropical latitudes; this is why Annex 10 recognises higher field-strength minima for low-latitude regions.
• Industrial and man-made noise and the spectrally rich AM broadcast band above 525 kHz make frequency planning more demanding than the simple SARP frequency tolerance suggests.

These propagation and noise characteristics are why coverage rather than azimuth accuracy is the dominant design constraint of an NDB installation.

Why role matters for requirements#

Annex 10 Vol I, §3.4 sets a common signal-in-space SARP that every NDB must meet, but the operational role of the station drives the practical interpretation: rated coverage radius, emission class, monitoring discipline, and identification cadence all change with role. Attachment C, §6.2 and §6.3 group the roles below by rated-coverage band and discuss the planning consequences.

The four traditional usage roles are:

Role 1 — Locator at outer or middle marker (LOM / LMM)#

A Locator is an LF/MF NDB used as an aid to final approach, typically sited on or near the ILS localizer course at the position of the outer marker (LOM) or middle marker (LMM) (Annex 10 Vol I, §3.4.7).

Requirement profile.

• Rated coverage typically 10–25 NM around the airfield.
• Emission NON/A2A (continuous carrier with keyed audio tone), so pilots can hear identification on a normal AM-receiving ADF.
• Identification transmitted at least three times every 30 seconds (§3.4.5.3). The rapid identification cadence is what marks a locator in the airwaves.
• Continuous monitoring not mandatorily required by §3.4.8.4 (which applies to NDBs "other than a locator"); but States routinely apply continuous monitoring anyway because the locator is on a procedure used in low visibility.

The locator role has been steadily eliminated as ILS marker beacons are withdrawn and DME and GNSS waypoints take over the role of marking distances on the localizer.

Role 2 — Terminal / holding NDB#

A holding or aerodrome-approach NDB defines an initial approach fix (IAF), an intermediate fix, a final approach fix (FAF), or a holding fix on a non-precision instrument approach.

Requirement profile.

• Rated coverage to the boundary of the terminal area, generally up to 50 NM (Attachment C, §6.2.2 guidance).
• NON/A2A required when rated coverage equals or exceeds 92.7 km (50 NM) (§3.4.6.1).
• Identification at least once every 30 seconds (§3.4.5.3).
• Continuous monitoring during published hours of service (§3.4.8.4).

PANS-OPS Vol I, Chapter 2 gives the design constraints: an NDB system-use bearing tolerance of ±6.2° (95 percent) and an NDB fix constructed from the cone-of-confusion radius around the station plus a ±15° splay (Figure I-2-2-4). These tolerances drive obstacle- clearance areas, missed-approach geometry, and minimum-segment lengths for the procedure designer.

Role 3 — En-route NDB#

The en-route NDB defines an airway centreline, a route reporting point, or an off-airway position fix in low-density continental, oceanic, or remote airspace.

Requirement profile.

• Rated coverage typically 50–150 NM, larger in remote regions (Attachment C, §6.2 and §6.3).
• NON/A2A required when coverage is at or above 50 NM, otherwise NON/A1A is permitted in dense beacon environments (§3.4.6.1.1).
• Frequency planning must achieve a wanted-to-unwanted ratio of at least 15 dB by day at the rated coverage boundary (Att C, §6.2.1.3.1).
• Continuous monitoring during hours of service.

PANS-OPS uses an NDB en-route splay of 10.3° (versus 7.8° for VOR); the wider splay is the procedural recognition of the larger NDB bearing error budget. This in turn drives wider route protection areas and earlier obstacle-clearance penalties — a major reason why en-route NDBs are the first to be removed in PBN transitions.

Role 4 — Emergency / contingency#

A residual but doctrinally important role. A small number of NDBs are retained explicitly as a contingency aid:

• GNSS-outage backup. A documented contingency procedure that reverts to NDB tracking when GNSS is unavailable, particularly in remote and oceanic regions.
• Non-equipped traffic. State or military aircraft, general aviation, and humanitarian operators that may not carry GNSS or PBN capability.
• Air defence identification / transition routes. Some States use NDBs to mark hand-off points on transition routes between civil and military airspace.

The signal-in-space requirements remain the Annex 10 §3.4 baseline, but the operational case is constructed around the contingency role — typically with reduced hours of service, lower power, and explicit mention in AIP GEN 1 and the relevant approach charts.

Cumulative principle#

The role categories are not exclusive: a single physical station may serve, for example, as a locator for one ILS and a holding fix for a parallel runway approach. When that happens, the most demanding of the role-specific requirements applies — typically the higher identification cadence and the continuous-monitoring discipline.

The rule is the same as in any safety-of-life navigation context: the declared service determines the engineering envelope, not the cheapest applicable role.

Why split the requirements into domains#

Annex 10 Vol I, §3.4 reads as a flat list of paragraphs, but in operational and engineering terms the SARPs sort naturally into four requirement domains. Each domain answers a different question, has its own measurement methodology, and is verified by a different oversight activity (commissioning flight inspection, periodic flight inspection, ground monitor, and frequency-coordination review).

The remainder of this file expands each domain.

Domain 1 — Signal quality#

What the transmitter and antenna deliver into space, independent of where it goes.

Frequency. Band 190–1750 kHz (§3.4.4.1). Tolerance 0.01 percent in general; 0.005 percent for stations above 200 W using 1 606.5 kHz or above (§3.4.4.2).

Emission class.

• NON/A2A — continuous carrier with keyed audio tone modulation, modulation depth as near 95 percent as practicable (§3.4.6.2).
• NON/A1A — keyed carrier (no audio modulation), permitted only where density or coverage limitations rule out NON/A2A (§3.4.6.1.1).

Spectral cleanliness. Although not a numbered SARP, Att C, §6.2 expects spurious and harmonic emissions to be controlled at a level that does not degrade other navigation or broadcast services. Local spectrum regulators (and ITU-R) supplement the Annex 10 wording.

Power. Radiated power not more than 2 dB above that needed for the agreed rated coverage, except where the excess is regionally coordinated (§3.4.3). The limit prevents over-radiating stations from spoiling the regional frequency-reuse plan.

Domain 2 — Coverage#

Where the signal is operationally usable, as distinct from where it can simply be detected.

Definitions. Annex 10 Vol I, §3.4.1 defines:

• Average radius of rated coverage — the radius of a circle of area equivalent to that of the rated coverage area.
• Rated coverage — the area surrounding the NDB within which the vertical ground-wave field strength exceeds the regional minimum.
• Effective coverage — the area within which bearings can be obtained with operationally acceptable accuracy at a given time.

Field-strength minimum. §3.4.2.1 (Recommendation): minimum 70 microvolts/m in the rated coverage area. Att C, §6.1 raises this threshold for low-latitude regions where atmospheric noise is higher.

Wanted-to-unwanted ratio. Att C, §6.2.1.3.1: at least 15 dB by day at the boundary of the rated coverage. This is the practical target driving frequency planning, not the SARP frequency tolerance itself.

Night effect. Att C, §6.2.3 documents that effective coverage shrinks at night because of sky-wave interference with the ground wave. Procedure designers and AIP authors should express NDB usability with the night limitation in mind.

Domain 3 — Integrity (monitoring)#

When the station must remove itself from service so that ADF receivers do not act on a corrupted signal.

Detected conditions (§3.4.8.1):

• Carrier power reduced more than 50 percent below the level required for rated coverage.
• Failure to transmit the identification signal.
• Malfunction or failure of the means of monitoring itself.

Action. §3.4.8.4: for NDBs other than locators, the monitor must operate continuously during hours of service, and an alarm must be provided at a control point. Unserviceability must be NOTAMed and the identification must cease.

Why integrity is a hard problem for NDBs. The aid carries no in-band integrity coding (no data block, no parity, no CRC). The only "integrity bit" the user receives is the identification itself. If the identification persists while the carrier or radiation is degraded, the user can be misled — which is why the §3.4.8.1 c) clause about monitor self-failure exists.

Domain 4 — Identification#

How the user confirms the station is the one expected.

Format. Two-letter or three-letter Morse identification group (§3.4.5.1). Speed approximately 7 wpm (§3.4.5.2).

Cadence.

• Standard NDB: at least once every 30 seconds (§3.4.5.3 a)).
• Locator (rated coverage at or below 92.7 km / 50 NM): at least three times every 30 seconds (§3.4.5.3 b)). The triple-rate identification is the airwave signature of the locator role.

Practical implication. The Morse group is the only piece of the NDB signal that is information-bearing. Any operational or maintenance change that affects identification — even a 1-second keyer-glitch routinely — must be treated as an integrity event.

Cross-domain interactions#

The four domains are not independent:

• Signal quality x Coverage. The 2 dB power limit (signal quality) caps the over-radiation that would otherwise extend rated coverage. This is a frequency-planning constraint, not a coverage constraint.
• Integrity x Identification. The Morse keying both supplies identification and creates the only user-visible integrity check. Monitoring §3.4.8.1 b) on identification is therefore the most load-bearing single integrity rule of the SARP.
• Coverage x Propagation. Rated coverage is a daytime ground-wave concept; the night effect (§6.2.3) is what makes "rated coverage" and "useful coverage at 0200Z" diverge.

Treating the four domains together, rather than as a checklist, is what distinguishes a properly engineered NDB station from one that ticks the SARPs but fails in service.

What a "requirement bucket" is#

For a complex aid such as ASBU we can talk about modules at the intersection of Blocks and Threads. For a simple navigation aid such as the NDB, the closest analogue is a requirement bucket: a coherent sub-set of the §3.4 SARPs and Att C, §6 guidance that can be specified, tested, and accepted as a unit.

Four buckets capture every SARP in Annex 10 Vol I, Chapter 3 that applies to an NDB station. Each bucket has the same internal anatomy described below.

Common anatomy of a requirement bucket#

For each bucket the following structured information should be carried in the State or operator design document and in the commissioning record.

1. Title and identifier#

E.g. Bucket SiS — Signal-in-Space. The identifier is internal but must be stable so that flight-inspection records and AIP entries can cite it.

2. Operational outcome#

A plain-language statement of the operational benefit. For SiS this is "an aircraft within rated coverage receives a usable NDB signal during published hours of service".

3. Performance requirement#

The numerical SARPs from Annex 10 Vol I, §3.4 that bound the bucket. Restated as design parameters with margin.

4. Verification method#

How the requirement is shown to be met:

• Ground measurement (transmitter logs, antenna feed-point measurements, modulation analyser, frequency counter referenced to a traceable standard).
• Flight inspection (Doc 8071 Vol I procedures — radial field-strength runs, bearing-error survey, coverage volume).
• Continuous monitor (real-time during hours of service).

5. Tolerances and margin#

Operating tolerances tighter than the SARP, so that drift between inspections does not cause SARP non-compliance.

6. Failure behaviour#

What the station does when the bucket is breached: removal from service, alarm, NOTAM, ID off.

7. Records#

What is kept and for how long: maintenance log, monitor alarm log, flight inspection report, frequency assignment record.

Worked example 1 — Signal-in-Space (SiS) bucket#

• Operational outcome. Antenna radiates a stable carrier within the permitted band, modulated and identified per Annex 10.
• Performance requirement.
  • Carrier in 190–1750 kHz, frequency tolerance 0.01 percent (0.005 percent above 200 W and 1 606.5 kHz).
  • NON/A2A or NON/A1A per role.
  • Modulation depth near 95 percent (§3.4.6.2) for NON/A2A.
  • Radiated power not more than 2 dB above that needed for rated coverage (§3.4.3).
• Verification. Ground measurement at commissioning and at periodic intervals (modulation analyser, calibrated field-strength meter near field, oscilloscope on the keyer line). Periodic flight inspection per Doc 8071 Vol I.
• Tolerances and margin. Operating tolerance for frequency typically 10 percent of SARP (i.e. 0.001 percent operating versus 0.01 percent SARP).
• Failure behaviour. Carrier off, ID off, alarm to control point.

Worked example 2 — Ground Monitor bucket#

• Operational outcome. A station with a degraded signal removes itself from service before users are misled.
• Performance requirement.
  • Detect carrier power reduction of more than 50 percent below rated-coverage requirement (§3.4.8.1 a)).
  • Detect failure to transmit identification (§3.4.8.1 b)).
  • Detect malfunction of the monitor itself (§3.4.8.1 c)).
  • Continuous operation during hours of service for non-locator NDBs (§3.4.8.4).
• Verification. Periodic on-site test routines that simulate each detected condition; record of monitor alarm history.
• Tolerances and margin. Detection thresholds set inside the SARP bound (e.g. 30 percent power-drop trigger, not 50 percent).
• Failure behaviour. Identification ceases; alarm at control point; NOTAM raised.

Worked example 3 — Identification bucket#

• Operational outcome. The user receives a stable, correct Morse identification at the cadence appropriate to the role.
• Performance requirement.
  • 2- or 3-letter Morse group (§3.4.5.1).
  • Approximately 7 wpm (§3.4.5.2).
  • Once per 30 seconds (standard) or three times per 30 seconds (locator) (§3.4.5.3).
• Verification. Aural check at commissioning, at periodic flight inspection, and at every routine maintenance visit.
• Tolerances and margin. Keyer timing held inside vendor tolerance, typically a few percent of the keying interval.
• Failure behaviour. Loss of ID is itself a §3.4.8.1 b) condition; the monitor must remove the carrier.

Worked example 4 — Propagation considerations bucket#

• Operational outcome. Coverage and bearing accuracy declared in the AIP are realisable at the times the aid is published as available.
• Performance requirement.
  • Field strength at least 70 microvolts/m within the rated coverage (§3.4.2.1 recommendation), raised in low-latitude regions (Att C, §6.1).
  • Wanted-to-unwanted ratio at least 15 dB by day at rated-coverage boundary (Att C, §6.2.1.3.1).
  • Effective coverage stated separately for day and night where night effect is significant (Att C, §6.2.3).
• Verification. Flight inspection field-strength runs along representative radials; periodic measurement at the rated-coverage boundary; review of frequency-plan compatibility.
• Tolerances and margin. AIP-published coverage usually sized inside the engineering rated coverage so that seasonal or solar-cycle variation does not breach the published service.
• Failure behaviour. Coverage shortfall below the AIP-published area is an integrity event treated like any other unserviceability.

Why this anatomy matters#

A simple aid invites a casual SARP read-through. Splitting the SARPs into the four buckets above makes the engineering acceptance, flight-inspection schedule, maintenance log, and configuration-change control all line up — and it makes the relationship to Doc 8071 Vol I testing procedures explicit.

What an enabler is for an NDB station#

An enabler is a supporting activity, system, or institutional arrangement without which the SARPs in Annex 10 Vol I, §3.4 cannot be sustained in service. The Annex sets the technical bar; enablers are what keep the bar in the air after commissioning.

For a single-purpose aid such as the NDB, four enablers carry the operational case.

1. Flight inspection#

Flight inspection is the airborne acceptance and periodic verification activity that confirms the station meets Annex 10 Vol I, §3.4 in space as well as on paper. The authoritative reference is Doc 8071 — Manual on Testing of Radio Navigation Aids, Volume I (Testing of Ground-Based Radio Navigation Systems).

Activities.

• Commissioning flight inspection. Initial radial field-strength runs, coverage volume verification, bearing-error survey using a reference position source, identification audibility check, monitor trip verification.
• Periodic flight inspection. Repeated at intervals defined by the State (typically every 12 to 24 months for an NDB, with shorter intervals after maintenance affecting radiation).
• Special flight inspection. Triggered by maintenance affecting the antenna or counterpoise, by a complaint of bearing error, after a significant change in the local RF environment, or after a sustained monitor outage.

Tolerances applied. Doc 8071 Vol I provides the inspection tolerance set (field strength, ID audibility, modulation depth, monitor trip points). Inspection is not a re-measurement of the SARP itself but a check that the station is inside its operating envelope, which is set tighter than the SARP.

2. Frequency planning and coordination#

NDBs operate in a busy and noisy LF/MF band shared with broadcast and maritime services. Even a SARP-compliant station can be unusable if its frequency assignment is not protected.

Activities.

• Spectrum allocation. ITU-R Radio Regulations allocate parts of the 190–1750 kHz band for aeronautical radionavigation. National spectrum regulators issue the operating licence.
• Regional aeronautical frequency planning. ICAO regional offices (APAC, MID, EUR, AFI, NAT, CAR/SAM) coordinate NDB frequency assignments to keep the wanted-to-unwanted ratio at the rated- coverage boundary at or above 15 dB by day (Annex 10 Vol I, Att C, §6.2.1.3.1).
• Compatibility studies. Bilateral / regional studies when a new station is proposed near a State boundary, particularly at higher power levels or in the upper part of the NDB band where AM broadcast intermodulation appears.
• Periodic review. As stations are decommissioned, freed channels are reassigned; reviews ensure new assignments do not erode the protection of remaining stations.

Reference. Although Doc 9718 (Handbook on Radio Frequency Spectrum Requirements for Civil Aviation) primarily covers VHF/UHF aviation spectrum, its general planning approach applies; the LF/MF NDB- specific guidance is in Annex 10 Vol I, Att C, §6 itself.

3. Monitor systems and maintenance#

The §3.4.8 monitor is one component; the surrounding monitoring system is the enabler that makes the SARP achievable in service.

Components and activities.

• Local monitor electronics. Sense carrier power, identification, and self-fault, with thresholds set inside the SARP bounds. Routine test of trip points (typically quarterly).
• Remote alarm transport. Telecommunication link from the NDB site to the responsible ATC unit / ANSP control centre, with its own availability target.
• Watch standing. Defined response procedure when an alarm is raised: NOTAM action, dispatch of maintenance, fall-back navigation procedure for affected traffic.
• Maintenance regime. Preventive maintenance on the antenna, counterpoise, transmitter, keyer, and monitor at vendor-recommended intervals; spare-parts holding sized to the criticality of the role.
• Configuration management. Records of every adjustment that could change radiated power, frequency, or identification.
• Logging and trend analysis. Long-term log of alarm events, field-strength flight-inspection results, and identification audits; used to detect creeping degradation that would otherwise go unnoticed between inspections.

The availability of the monitoring chain becomes the dominant limit on the availability of the navigation service: a station whose local SARP performance is perfect but whose alarm transport fails for a week is not delivering an Annex 10-compliant service for that week.

4. Regulation and certification#

The institutional layer that ties the technical SARPs to a State's oversight regime.

Elements.

• State regulatory framework. Civil Aviation Authority (CAA) rules transposing Annex 10 Vol I into national regulation; explicit references to §3.4 SARPs; designation of the responsible ANSP.
• Service-provider certification. Certification of the ANSP under Annex 6 / Annex 11 with the NDB station as part of the certified CNS infrastructure.
• Type acceptance / equipment approval. National acceptance of the transmitter, monitor, and antenna design against Annex 10 SARPs and the corresponding national equipment standard.
• Licensing of operators. Personnel licensing for engineers and technicians performing maintenance and flight inspection (Annex 1).
• AIP publication. AIP entries (GEN, ENR, AD sections) declaring the NDB call sign, frequency, location, hours of service, and approved use; AIP amendment cycle for any change to those parameters.
• NOTAM regime. Procedure and timeline for issuing NOTAMs on unserviceability and changes.
• Safety management. Annex 19 SMS coverage of the NDB service; risk assessment for any change of role, hours, or decommissioning.
• Data quality and AIM linkage. Coordinates of the NDB site declared per WGS-84 with the data quality required by PANS-AIM (Doc 10066) so that the published procedure built on the NDB is flyable.

Why these enablers are the real workload#

The Annex 10 §3.4 SARPs can be met by a competent transmitter manufacturer in a few rack-mount units. Sustaining the service across years and seasons is the substance of running an NDB. The enabler list above is what distinguishes an NDB that supports a published instrument approach from a transmitter that simply happens to radiate.

For a State considering retention versus decommissioning, the cost of the four enabler workstreams — not the equipment cost — is what typically swings the business case.

The performance lens for a single-aid service#

ASBU performance vocabulary (KPAs from Doc 9854 / Doc 9883) was designed for system-wide ATM performance. For a single ground-based navigation aid such as the NDB, the relevant KPAs collapse into the classical signal-in-space performance triplet familiar from Annex 10 Vol I:

Availability  +  Integrity  +  Continuity
                 |
                 +-> bounded by Accuracy (the bearing-error budget)

All four reduce to Doc 9854 KPAs:

• Availability is read across to Capacity and Predictability (the aid is there when the published procedure says it is there).
• Integrity is read across to Safety (the aid does not mislead).
• Continuity is read across to Predictability (the aid does not drop out within a procedure).
• Accuracy underpins Flight efficiency indirectly via wider or narrower obstacle-clearance areas.

This file collects the requirement-level KPAs and the practical KPIs used to measure them.

Key Performance Areas as applied to an NDB#

1. Availability#

The probability that the station is radiating an Annex 10-compliant signal at a randomly chosen instant during published hours of service.

Engineering target. Conventional aids are not given a single Annex 10 numerical availability target; the State sets one consistent with the role of the aid. Typical practice:

• Locator on an ILS: availability target aligned with the ILS itself (often 0.99 or higher in service).
• Terminal NDB supporting a published approach: 0.99.
• En-route NDB in low-density airspace: 0.95–0.99 depending on redundancy of the route.

2. Integrity#

The probability that the station is not radiating misleading information when declared "in service". For an NDB the in-band integrity check is the Morse identification; integrity is therefore determined by the monitor chain (§3.4.8) and the time to remove a faulty carrier from service.

Engineering target. Time to alarm + time to ID-off + time to NOTAM = the integrity exposure window. Typical operating practice keeps the time from internal failure to ID-off below 15 seconds, and the time to NOTAM below the State's published value (often a few minutes).

3. Continuity#

The probability that the station, having been available at the start of a procedure, remains available for the duration of that procedure. Particularly important for locators and approach NDBs, where a mid-approach loss is operationally significant.

Engineering target. Continuity is largely driven by power-supply robustness, transmitter redundancy, and monitor / alarm chain robustness. Typical practice: dual transmitter changeover; UPS or short-term battery backup sized to the typical procedure length.

4. Accuracy#

The bearing error budget the user can expect, against which PANS-OPS designs the procedure. Annex 10 Vol I, §3.9.1.1 sets the airborne ADF bearing-accuracy SARP at ±5° in a 70 microvolts/m field in the presence of a co-channel unwanted signal at 90°. PANS-OPS Vol I, Chapter 2 raises this to a system-use bearing tolerance of ±6.2° (95 percent) to absorb ground-station and propagation effects.

Performance Objectives expressed at the requirement level#

A small, station-level catalogue, expressed in the same form as the GANP Performance Objectives, is useful when writing a State CNS plan:

• PO — Maintain published NDB service availability. Measured by outage minutes per month, mean time between failures (MTBF), monitor alarm rate.
• PO — Maintain integrity of NDB identification. Measured by time-to-alarm distribution, time-to-ID-off distribution, audited identification correctness.
• PO — Maintain rated-coverage field strength. Measured by flight inspection results against the 70 microvolts/m threshold along each representative radial.
• PO — Maintain bearing accuracy within PANS-OPS tolerance. Measured by flight-inspection bearing-error survey against a reference position source.
• PO — Sustain frequency-plan protection. Measured by complaint rate of co-channel or adjacent-channel interference and by review of the regional frequency-plan database.

Key Performance Indicators (KPIs)#

Availability KPIs#

• Outage minutes per month (planned and unplanned, separately).
• MTBF of the transmitter chain.
• Mean time to repair (MTTR) for unplanned outages.
• Monitor alarm rate per month, segmented by cause.

Integrity KPIs#

• Time from internal fault to monitor alarm (95th percentile).
• Time from monitor alarm to identification removal (95th percentile).
• Number of integrity events per year (events where misleading signal may have been radiated).

Continuity KPIs#

• Probability of in-procedure loss for procedures that include the station as a fix (computed from outage statistics).
• Number of in-procedure losses reported in the State safety log per year.

Accuracy KPIs#

• Bearing error standard deviation along each flight-inspected radial.
• Maximum bearing error observed in the most recent inspection cycle.
• Field strength margin above 70 microvolts/m at the rated-coverage boundary on each representative radial.

Cost-effectiveness KPIs (decommissioning case)#

• Annualised cost of station ownership (capital amortisation + maintenance + flight inspection + spectrum coordination).
• Number of published procedures dependent on the station.
• Number of movements per month using a procedure that depends on the station.

How performance is reported#

• Internally to the ANSP. Monthly CNS performance report; quarterly flight-inspection trend; annual safety performance review.
• To the regulator. State Safety Programme reporting where the aid is part of safety-of-life service; AIP amendment cycle for any change in declared service.
• To the regional ICAO office. As part of the ANP Volume II / Volume III actual-versus-planned reporting, where retained NDBs appear.

Why this matters for retention versus decommissioning decisions#

A serious retention-versus-decommissioning case for an NDB is built on the KPI set above. Stations that fail to deliver consistent availability and integrity, that depend on aging counterpoise systems, or that are no longer dependency-critical to any published procedure become weak retention candidates. Conversely, stations that demonstrate strong KPIs, low monitor alarm rates, and remain load-bearing for a contingency or non-equipped use case can be retained on a documented safety case rather than on legacy presence.

Two timelines to keep distinct#

When discussing the NDB, separate two threads:

1. Annex 10 SARP timeline — when ICAO published or amended the NDB provisions in Annex 10 Volume I.
2. Phase-out trajectory — when States began withdrawing NDBs as PBN matured under Doc 9613 and the ASBU framework.

A State's own retention-and-decommissioning plan is a third, national timeline; it must be expressed against both ICAO timelines above.

Annex 10 SARP timeline (NDB)#

The NDB is one of the oldest aids covered by Annex 10. The signal-in- space SARPs predate radar and were inherited from the early post-WWII civil aviation system. Annex 10 Volume I was first published in 1949; the NDB has appeared as Chapter 3, §3.4 throughout the modern editions.

The pattern is clear: NDB SARPs have been in maintenance mode for more than two decades. ICAO is not adding capability to the NDB; it is preserving the SARP set so that retained stations remain interoperable.

Companion document timeline#

• Doc 8071 — Manual on Testing of Radio Navigation Aids, Volume I. The authoritative manual on NDB flight inspection tolerances and test procedures. Periodic editions track Annex 10 amendments.
• Doc 8168 — PANS-OPS, Volumes I and II. NDB system-use bearing tolerance, ±15° splay for fix construction, NDB approach criteria with and without FAF. Stable for decades; current editions retain the historical NDB construction rules even while new PBN-only approaches replace NDB approaches at most aerodromes.
• Doc 9613 — PBN Manual. First published 2008; current 4th edition 2013. Sets the PBN framework that supersedes NDB-based en-route and approach navigation.

Phase-out trajectory under PBN#

Global driver#

ICAO's Performance-Based Navigation strategy, set out in Doc 9613 and supported by the ASBU NAVS thread, sequences States toward GNSS- based RNAV/RNP as the primary navigation infrastructure. Conventional aids (VOR, DME, NDB) move from primary to backup, then to decommissioning where redundancy and traffic justify it. The NDB, having the weakest accuracy and integrity profile of the three, typically goes first.

Indicative national trajectories#

The retention case#

A small population of NDBs is being retained explicitly, not by omission. Retention is justified on:

• GNSS-outage contingency in remote or oceanic regions.
• Non-equipped / non-PBN traffic still in operation.
• ILS locator function where the locator remains useful and the ILS itself is being retained.
• Transition routes between civil and military airspace.

In each case the retention is supported by a documented safety case referencing Annex 10 Vol I, §3.4 and Doc 9613, rather than by legacy presence alone.

How to read a date in an NDB document#

When reading an NDB-related document, identify the date type:

• "Annex 10 Vol I §3.4 amended in 19xx" — SARP timeline.
• "PBN policy in force from 20xx" — Doc 9613 implementation timeline.
• "AIC ##/24 retiring NDB at YYYY" — national decommissioning action.
• "Periodic flight inspection due 2026Q3" — operational maintenance cadence for a single station.

Mixing these up leads to confusing claims about whether the NDB is "still required". The correct answer is that the SARPs remain in force for States that operate NDBs, while the operational role is being progressively retired in line with PBN.

Primary ICAO documents#

• Annex 10 (Aeronautical Telecommunications), Volume I — Radio Navigation Aids. Chapter 3, §3.4 — Specification for non-directional radio beacon (NDB); definitions of rated and effective coverage, locator, and average radius of rated coverage (§3.4.1); coverage and field-strength minima (§3.4.2); radiated-power limitation (§3.4.3); frequency band and tolerances (§3.4.4); identification (§3.4.5); characteristics of emissions, including NON/A2A and NON/A1A (§3.4.6); siting of locators (§3.4.7); monitoring (§3.4.8). §3.9 — System characteristics of airborne ADF receiving systems; bearing-accuracy requirement of ±5° at 70 microvolts/m with co-channel and adjacent-channel interferers (§3.9.1.1). Attachment C, §6 — Material concerning NDB; field-strength guidance for low-latitude regions (§6.1); rated and effective coverage including the 15 dB day wanted-to-unwanted ratio at the rated-coverage boundary (§6.2.1.3.1) and night-effect considerations (§6.2.3); NDB coverage planning studies (§6.3).
• Doc 8071 — Manual on Testing of Radio Navigation Aids, Volume I (Testing of Ground-Based Radio Navigation Systems). Authoritative source for NDB flight-inspection procedures, tolerances, and acceptance criteria; commissioning and periodic test routines (authoritative source — not in local library).
• Doc 8168 — PANS-OPS, Volume I (Flight Procedures). Part I, Section 2, Chapter 2 — Terminal-area fix tolerances; NDB system-use bearing tolerance and ±15° splay for NDB fix construction (Table I-2-2-1, Figure I-2-2-4). Part I, Section 3 — En-route criteria for VOR and NDB routes; route protection widths and splay angles (NDB 10.3° terminal vs. VOR 7.8°).
• Doc 8168 — PANS-OPS, Volume II (Construction of Visual and Instrument Flight Procedures). Part II, Section 2, Chapter 3 — Non-precision approach: VOR or NDB with no FAF; segment construction and obstacle-clearance criteria. Part II, Section 2, Chapter 4 — Non-precision approach: VOR or NDB with FAF; segment construction and obstacle-clearance criteria.
• Doc 9613 — Performance-Based Navigation (PBN) Manual. Sets the PBN framework that supersedes NDB-based en-route and approach navigation; classifies conventional aids as legacy in the PBN context; provides the strategic rationale for NDB rationalisation.
• Doc 9718 — Handbook on Radio Frequency Spectrum Requirements for Civil Aviation, Volume II. Guidance on spectrum planning relevant to NDB frequency assignment and protection (authoritative source — limited NDB-specific material; main NDB frequency-planning guidance is in Annex 10 Vol I, Att C, §6).
• Doc 4444 — PANS-ATM. Air traffic services procedures, where NDB-defined fixes appear in route, holding, and approach clearances.

ICAO Annex provisions most relevant to the NDB#

• Annex 10 (Aeronautical Telecommunications), Volume I — primary NDB SARPs, as above.
• Annex 11 (Air Traffic Services) — provision and continuity of ATS where the NDB underpins published procedures; coordination of unserviceability and AIP amendment.
• Annex 14 (Aerodromes) — siting considerations for locator NDBs in relation to the runway and other aerodrome equipment.
• Annex 15 (Aeronautical Information Services) — publication of NDB call sign, frequency, location, and hours of service in the AIP; NOTAM regime for unserviceability.
• Annex 19 (Safety Management) — SMS coverage of the NDB service and risk assessment for changes in role, hours, or decommissioning.
• Annex 1 (Personnel Licensing) — licensing of engineers and technicians performing NDB maintenance and flight inspection.

Live / authoritative sources#

• ICAO Annex 10 Volume I product page — https://store.icao.int/en/annex-10-aeronautical-telecommunications-volume-i-radio-navigational-aids
• ICAO PBN portal / Doc 9613 — https://www.icao.int/safety/pbn/Pages/default.aspx
• ICAO GANP Portal (NAVS thread context for conventional-aid rationalisation) — https://ganpportal.icao.int/
• ITU-R Radio Regulations (LF/MF aeronautical radionavigation allocations) — https://www.itu.int/pub/R-REG-RR

Regional rationalisation references (web fallback — flagged)#

These references are not held in the local ICAO Markdown library. They reflect the public regional position on conventional-aid rationalisation under PBN.

• EUROCONTROL — European Plan for Conventional Navigation Aids rationalisation. Public strategy on coordinated reduction of VOR/DME/NDB infrastructure across ECAC States as PBN matures. (Web fallback — see EUROCONTROL public site for the current edition.) https://www.eurocontrol.int/
• FAA — VOR Minimum Operational Network (MON) and NDB decommissioning. Public FAA programme right-sizing the conventional navaid network. (Web fallback.) https://www.faa.gov/air_traffic/flight_info/aeronav/
• Airservices Australia — Navigation Rationalisation Project. Programme decommissioning NDBs, VORs, and DMEs since 2016 in line with the national PBN policy. (Web fallback.) https://www.airservicesaustralia.com/
• Thailand CAAT — AIC 10/24. Retirement of NDBs at several aerodromes. (Web fallback.) http://aip.caat.or.th/
• ICAO APAC Office — Seamless ATM Plan. Regional realisation of the ASBU NAVS thread, including conventional-aid rationalisation trajectory. (Web fallback.) https://www.icao.int/APAC/

General-aviation and educational references#

• Wikipedia — Non-directional beacon. General introduction to the technology and historical context. https://en.wikipedia.org/wiki/Non-directional_beacon
• Southern Avionics — "Why is the FAA decommissioning NDBs?". Industry commentary on the U.S. decommissioning programme. https://www.southernavionics.com/blog/why-is-the-faa-decommissioning-ndbs
• CFI Notebook — Non-Directional Radio Beacon. Pilot-oriented description of NDB and ADF operation. https://www.cfinotebook.net/notebook/avionics-and-instruments/non-directional-radio-beacon

How to use these references#

For SARP-grade citations, always quote Annex 10 Volume I directly with chapter and paragraph (for example, "Annex 10 Vol I, §3.4.5.3" for identification cadence). Use Doc 8071 Vol I for flight-inspection tolerances and procedures. Use Doc 9613 only for the strategic PBN framing — it does not redefine the NDB SARPs. Treat the regional and industry references as policy and trajectory context, not as substitutes for the ICAO primary sources.