Detailed working notes on the requirements for the VHF Omnidirectional Radio Range (VOR), the workhorse VHF azimuth navigation aid standardised in ICAO Annex 10. This folder expands the summary in topics/vor_requirements.md into per-aspect files so each can be read on its own.

Files in this folder#

• overview.md — what VOR is (CVOR vs DVOR), its role in conventional navigation, and the Minimum Operational Network (MON) concept.
• components.md — the physical and signal components of a VOR ground installation: transmitter, monitor, antenna, identification, DME co-location, frequency band.
• blocks.md — usage roles into which VORs are placed (en-route VOR, terminal VOR, T-VOR, MON-supporting VOR).
• threads.md — the requirement domains that any VOR must satisfy (signal-in-space, monitor, identification, coverage, integrity).
• modules.md — anatomy of a single VOR requirement bucket (signal accuracy, ground monitor, identification, course alignment, flight inspection / FFM).
• enablers.md — supporting elements: flight inspection, frequency planning, monitor and alert system, regulatory framework.
• performance_objectives.md — Key Performance Areas applied to VOR (availability, integrity, continuity, accuracy).
• timeline.md — Annex 10 SARP evolution for VOR, the MON concept (EUROCONTROL and FAA), and the CVOR-to-DVOR conversion arc.
• references.md — consolidated ICAO and external references for everything in this folder.

Reading order#

Start with overview.md, then components.md, then blocks.md and threads.md, then drill into modules.md, enablers.md, and performance_objectives.md. Use timeline.md for date context and references.md for citations.

Source basis#

Content is grounded in:

• ICAO Annex 10 (Aeronautical Telecommunications), Volume I — Radio Navigation Aids, Chapter 3, §3.3 "Specification for VHF omnidirectional radio range (VOR)" and Attachments C and E.
• ICAO Annex 10, Volume I, Chapter 3, §3.5 — DME, including VOR/DME co-location provisions.
• ICAO Doc 8168 (PANS-OPS), Volume I and Volume II — flight procedures and procedure design rules using VOR.
• ICAO Doc 8071 (Manual on Testing of Radio Navigation Aids), Volume I — flight inspection of VOR (authoritative source — not in local library).
• ICAO Doc 9613 (Performance-Based Navigation Manual) — context for VOR/DME within PBN and the rationalisation strategy.
• ICAO Doc 9718 (Handbook on Radio Frequency Spectrum Requirements for Civil Aviation), Volume II — VOR frequency planning (authoritative source — not in local library).
• FAA VOR MON programme and EUROCONTROL conventional-navigation strategy publications.

Out of scope for this folder#

DME-only requirements (covered elsewhere in this workspace), ILS localiser requirements, and PBN-specific navigation specifications. References to those documents appear only where they bear directly on the role or rationalisation of VOR.

What VOR is#

VOR — VHF Omnidirectional Radio Range — is a ground-based radio navigation aid that radiates a signal from which a suitably equipped aircraft can derive its magnetic bearing from the station. Together with a co-located DME (which adds slant range), VOR underpins almost the entire pre-PBN structure of conventional airways, terminal procedures, and non-precision approaches that is still in use worldwide.

A VOR transmits two signals on the same VHF carrier:

• A reference phase signal that is the same in every direction.
• A variable phase signal whose phase depends on the bearing from the station to the receiver.

The receiver compares the two phases. A 0 degree phase difference is defined as magnetic north at the station; the difference in degrees, measured clockwise, is the aircraft's bearing from the VOR.

Two implementations: CVOR and DVOR#

Annex 10, Volume I, §3.3 standardises two physical implementations that deliver the same azimuth information to the aircraft.

• Conventional VOR (CVOR). The variable phase is produced by a rotating cardioid pattern at 30 Hz (originally mechanically rotated; in modern installations electronically commutated on a four-loop Alford array). The 30 Hz amplitude modulation on the carrier is the variable phase; a 9 960 Hz subcarrier, frequency-modulated at 30 Hz, carries the reference phase.
• Doppler VOR (DVOR). The roles of reference and variable phase are reversed. A central antenna radiates a 30 Hz amplitude-modulated reference signal; sideband signals are commutated around a ring of ~50 antennas (typically on a 13.4 m diameter counterpoise) to synthesise a circulating source whose Doppler shift, observed by the receiver, produces a 30 Hz frequency modulation on the 9 960 Hz subcarrier — the variable phase.

DVOR is electrically equivalent at the receiver: a standard airborne VOR receiver cannot tell the two apart. DVOR is preferred at sites with significant scattering (terrain, buildings, vegetation) because its wide counterpoise and commutated sideband geometry are far more tolerant of multipath than a CVOR.

Role in conventional navigation#

Even in heavily PBN-equipped airspace, VOR remains operationally relevant:

• En-route VOR/NDB routes. PANS-OPS Volume II, Section 3 still publishes airway construction criteria based on VOR bearings.
• Terminal procedures. VOR or VOR/NDB SIDs, STARs, and approaches (with or without FAF) under PANS-OPS Volume II, Part II.
• Non-precision approach sensor. A 2D approach down to LNAV minima flown using VOR bearing (and DME range, if co-located).
• Holding. VOR/DME holding entry sectors and teardrop entries are defined in PANS-OPS Volume I.
• Position fix. A radial intersection from two VORs, or VOR plus DME range, is a published fix on charts.

For PBN, Doc 9613 records that VOR/DME supports RNAV 5 only when DME is co-located with the VOR, and discourages new VOR/DME-based PBN implementations except for limited en-route cases where DME/DME infrastructure is not feasible.

The MON (Minimum Operational Network) concept#

GNSS is now the primary means of navigation in most regions. VOR is therefore being rationalised, not abolished. The doctrine in both the FAA and EUROCONTROL is:

• Decommission redundant VORs that no longer carry traffic load.
• Keep a Minimum Operational Network as a GNSS-outage fallback, so that an aircraft losing GNSS in en-route or terminal phase can still navigate to a safe airport using conventional aids.
• For each MON-served airport, guarantee at least one non-GNSS, non-DME/DME approach (ILS, LOC, or VOR) within a defined radius.

The FAA VOR MON programme (FY2016 onward) targets reducing approximately 900 CONUS VORs to about 590, while keeping every VOR in Alaska, the Western US Mountainous Area, and US territories. EUROCONTROL pursues an analogous "Conventional Routes Backup" / reversionary VOR strategy. ICAO Annex 10 Volume I, Attachment H (Strategy for rationalization of conventional radio navigation aids) is the SARP-level reference for this direction of travel.

Where requirements come from#

• What the signal must look like in space — Annex 10 Vol I, §3.3.2 (frequency), §3.3.3 (polarisation, accuracy), §3.3.4 (coverage), §3.3.5 (modulation), §3.3.6 (identification and voice).
• How the station must police itself — Annex 10 Vol I, §3.3.7 (monitoring) and §3.3.8 (FM-broadcast immunity for receivers).
• How the station is sited and how often it is checked — Annex 10 Attachment C §3 (guidance) and Doc 8071 Volume I (flight inspection).
• How VOR is used operationally and how procedures are built around it — Doc 8168 Volumes I and II.
• How VOR fits into the future — Doc 9613 (PBN context) and Annex 10 Attachment H (rationalisation strategy).

The remaining files in this folder break each of these requirement domains down on its own terms.

A VOR ground installation is a small set of well-defined components, each of which carries its own SARP requirements in Annex 10 Volume I, §3.3 and supporting Attachments. This file walks the components from RF in to RF out, then to monitoring and identification.

1. Frequency band and channel plan#

VOR operates in the protected aeronautical VHF navigation band:

• Primary band. 111.975 - 117.975 MHz.
• Lower band. 108 - 111.975 MHz, shared with ILS localizers under the conditions of Annex 10 Vol V Chapter 4 (only specific channels in 108 - 111.975 MHz are usable by VOR; the remainder are reserved for ILS localizers).
• Highest assignable frequency. 117.950 MHz.
• Channel spacing. 50 kHz.
• Carrier frequency tolerance. Plus or minus 0.005 per cent generally; tightened to plus or minus 0.002 per cent at installations in 50 kHz spacing environments and at any installation commissioned after 23 May 1974 in such areas.
• Polarization. Horizontal. The vertically polarised component of the radiated field must be minimised so that aircraft in bank do not pick up appreciable vertical-component error.

Frequency planning between VORs and between VOR and ILS localizers is covered in Doc 9718 Volume II. Co-channel and adjacent-channel geographic separation, especially in dense regions, is the dominant constraint.

2. Transmitter — CVOR vs DVOR#

The transmitter is the largest component by both rack space and primary power. Its job is to radiate the carrier with the correct combination of 30 Hz reference phase and 30 Hz variable phase modulation such that the receiver-derived bearing matches the true magnetic radial.

• CVOR transmitter. Single transmitter feeding a four-loop Alford antenna or equivalent rotating-pattern radiator. The variable phase is the 30 Hz AM envelope of the rotating cardioid; the reference is a 9 960 Hz FM subcarrier, modulated +/-480 Hz at 30 Hz.
• DVOR transmitter. Carrier transmitter feeding a central antenna (reference) plus sideband transmitters feeding a commutator that switches sideband energy around a ring of antennas on a counterpoise. The deviation ratio of the FM-encoded variable phase on the 9 960 Hz sub-carrier is 16 +/-1 (Annex 10 Vol I, §3.3.5).

Modern DVOR installations are typically dual-equipment hot-standby with automatic changeover on monitor alarm.

3. Antenna and counterpoise#

• CVOR. Four-loop Alford array on a small counterpoise; the small footprint is one of CVOR's few remaining advantages.
• DVOR. A 13.4 m diameter elevated counterpoise carrying the central carrier antenna and the ring of (typically 48 or 50) sideband antennas. The counterpoise is engineered to control near-field reflections.

In both cases siting must control multipath: terrain rises within the first Fresnel zone, large reflective structures (hangars, buildings, fences, vehicles), and dense vegetation can all produce site-error "scallops" that bend a published radial. DVOR is the preferred choice where the site cannot be cleared.

4. Identification#

Annex 10 Vol I, §3.3.6 requires:

• A two- or three-letter International Morse Code identification transmitted at 1 020 Hz, simultaneously with the navigation signal.
• An identification rate of at least once every 30 seconds; the speed is approximately seven words per minute.
• For VOR/DME pairs, the identification provisions of §3.5.3.6.4 apply (the VOR and DME identifications interlock so a user can confirm both components are operating).
• An optional voice channel, modulating the carrier to a depth of about 5 +/-1 per cent without disturbing the navigation function.

A VOR whose identification component fails must remove the navigation component too, or shut the station down, under §3.3.7.

5. Monitor#

A separate ground monitor located in the radiation field samples the signal and continuously checks it. Annex 10 Vol I, §3.3.7 requires the monitor to warn the control point and either remove the navigation and identification components from the carrier or shut the station down on:

• Bearing error exceeding 1 degree at the monitor site.
• A reduction of monitored modulation components by 15 per cent or more.
• Failure of the monitor itself (fall back to safe state).

The monitor is the single most important integrity element of a VOR installation. Modern systems use dual monitors with voting.

6. DME co-location#

A VOR is typically paired with a DME (Annex 10 Vol I, §3.5). Co-location limits in §3.5.2.6.1 require:

• Antenna separation not greater than 80 m for terminal and approach use.
• Antenna separation not greater than 600 m for en-route use.

The pairing produces a frequency-paired channel: the airborne VOR receiver tunes a VHF VOR frequency, and the airborne DME interrogator auto-tunes the matching UHF DME channel. From the pilot's perspective this is "VOR/DME tuning by VHF frequency". Channel pairing is in Annex 10 Vol I, §3.5.3.4.

7. Power, control, and remote status#

• Primary power, UPS, and an engine-generator for continuous operation.
• A remote control and status interface to the responsible ATS unit (or to a centralised technical centre) so the controller-in-charge knows the navaid is up, identifying, and within tolerance.
• A NOTAM origination capability whenever the navaid is unserviceable or operating with restrictions.

A VOR is not a single product. The same physical installation may be deployed in any of several usage roles, and each role drives a different set of coverage, accuracy, and procedural expectations. This file groups VORs by the operational job they do.

The four roles below are not exclusive: a VOR commissioned for en-route service may also publish terminal procedures, and a VOR retained on a MON list still keeps its en-route or terminal role.

1. En-route VOR (high / low altitude)#

Role. Defines and delineates VOR/DME airways and ATS routes, provides position fixing in cruise, and supports holding patterns at en-route fixes.

Service volume. Traditionally described in three Standard Service Volumes (SSVs):

• High SSV — usable to 60 000 ft AGL within ~130 NM at upper altitudes.
• Low SSV — usable up to 18 000 ft AGL within ~40 NM.
• Terminal SSV — see role 2 below.

Procedural use. PANS-OPS Volume II, Section 3 (en-route) constructs airway protection areas around the published radial using the standard VOR fix tolerance:

• A cone of ambiguity with a 50 degree semi-angle (default) overhead the station, defining where bearing information is unusable.
• Track-keeping accuracy expectations that combine the ground-station bearing tolerance, airborne system tolerance, and flight technical error.

Typical implementation. DVOR at sites with terrain or building clutter; CVOR at clean, flat sites. Co-located with DME for rho-theta fixing.

2. Terminal VOR#

Role. Supports SIDs, STARs, IAFs, IFs, FAFs, and missed-approach holding for an aerodrome or terminal area. Often co-located with DME so that the procedure can be flown using bearing and range from a single tuneable channel.

Service volume. Terminal SSV — usable to 12 000 ft AGL within ~25 NM (FAA SSV definition; equivalent regional definitions apply).

Procedural use. PANS-OPS Volume II, Part II builds approach procedures around the VOR. Specific paragraphs of interest:

• §2.4.3 — fixes for VOR or NDB with DME, including the 23 degree maximum divergence angle if the DME is not co-located.
• §2.5.1 — VOR fix tolerance overhead the station, the cone of ambiguity at 50 degree semi-angle by default.

Typical implementation. Often DVOR for siting reasons (terminal sites are rarely clutter-free). Always co-located with DME under the 80 m terminal/approach separation limit.

3. T-VOR (Terminal-class small-coverage VOR)#

Role. A reduced-power VOR designed to serve only the terminal manoeuvring area of an aerodrome. T-VORs were historically used where a full-power VOR could not be sited or was not justified.

Distinguishing characteristics.

• Lower transmitter power, hence smaller coverage volume — typically designed to a defined service radius rather than an SSV.
• Often associated with a specific aerodrome and not used for en-route airway construction.
• Subject to the same SARP-level accuracy and monitoring requirements in Annex 10 Vol I §3.3 as any other VOR — the SARPs do not have a "T-VOR" sub-category. The "terminal" qualifier is operational, not regulatory.

Status. Many T-VORs have been decommissioned in favour of GNSS approaches; those retained typically migrate into a MON role.

4. MON-supporting VOR#

Role. A VOR retained explicitly to provide a GNSS-outage fallback — the Minimum Operational Network. Identification of MON VORs is a deliberate State-level decision to maintain conventional reversionary capability while decommissioning everything else.

Coverage requirement. Driven by the MON design, not by historical airway structure:

• FAA MON. New "MON SSV" defined from 5 000 ft AGL up to defined upper bound; coverage so that any aircraft in CONUS within MON airspace can navigate to a MON airport (within 100 NM) using VOR alone.
• EUROCONTROL Conventional Routes Backup. Reversionary VOR network underpinning a designated set of contingency routes, sized by expected fallback traffic flows, with retained ILS or VOR approaches at MON aerodromes.

Procedural use. MON aerodromes must offer at least one non-GNSS, non-DME/DME approach (ILS, LOC, or VOR) so an aircraft with a complete GNSS failure has a usable approach available.

Typical implementation. Existing high SSV DVORs converted to MON status, often paired with retained DME and (where the airport has it) ILS. Modernised remote control and status reporting because the MON must be visible to flow management as a system, not just as individual sites.

How a State documents the role of each VOR#

A national air navigation plan typically lists every commissioned VOR with the following metadata, much of which feeds the AIP:

• Identifier, magnetic site declination, frequency channel, paired DME channel.
• Type (CVOR / DVOR), service volume class.
• Operational role (en-route, terminal, T-VOR, MON).
• Hours of service, monitor configuration, NOTAM responsibility.
• Flight inspection schedule and last-flight-inspection result.

In countries operating an MON, the role assignment is the most operationally significant field — it determines whether the VOR can be decommissioned during the rationalisation programme or must be kept.

The SARPs for VOR in Annex 10 Volume I, §3.3 separate cleanly into five requirement domains. Each domain has its own metric, its own test, and its own way of failing. Understanding them as distinct is essential when commissioning, flight inspecting, or troubleshooting a VOR.

The five domains are:

1. Signal-in-space — what the radiated waveform must look like.
2. Coverage — where in space the signal must be usable.
3. Identification — how the user knows which station they hear.
4. Monitor and integrity — how the station polices itself and alerts when it cannot.
5. Receiver / interference immunity — what protection the receiver side enjoys against external interference.

1. Signal-in-space#

The headline domain. It groups the SARPs in Annex 10 Vol I §3.3.2 (frequency), §3.3.3 (polarisation and accuracy), and §3.3.5 (modulation).

Specific normative requirements include:

• Carrier frequency tolerance. +/-0.005 per cent generally; +/-0.002 per cent in 50 kHz spacing areas (§3.3.2.2 - §3.3.2.3).
• Polarisation. Horizontal; the vertically polarised component of the radiation must be minimised (§3.3.3).
• Bearing pattern accuracy. The ground-station contribution to bearing error must be within +/-2 degrees over elevation 0 to 40 degrees, measured from the centre of the antenna system (§3.3.3.2). DVOR sites in practice hold to about +/-1 degree.
• Modulation components. 30 Hz reference and variable phase modulation; 9 960 Hz subcarrier with a deviation ratio of 16 +/-1 (§3.3.5). Identification at 1 020 Hz; voice channel where provided at ~5 +/-1 per cent depth.

Failure modes: course bends from siting multipath; bearing offset from antenna or transmitter drift; subcarrier deviation drift.

2. Coverage#

What service volume the station guarantees. Annex 10 Vol I §3.3.4 and Attachment C §3 provide:

• Elevation coverage. Signals shall permit satisfactory operation of a typical aircraft installation up to 40 degrees elevation measured from the antenna centre.
• Field strength. Recommended minimum field strength at the maximum specified service radius and altitude is 90 microvolts per metre (-107 dBW/m^2).
• Standard Service Volumes. Operationally defined high / low / terminal SSVs (and, in the FAA system, a MON SSV from 5 000 ft AGL).

Failure modes: line-of-sight obstruction at low elevations; pattern distortion from a poor counterpoise or building reflections; reduced field strength from PA or feeder degradation.

3. Identification#

Annex 10 Vol I §3.3.6 sets:

• A two- or three-letter Morse identification at 1 020 Hz, transmitted simultaneously with the navigation signal.
• Identification at least once every 30 seconds.
• For VOR/DME pairs, the identification interlock provisions of §3.5.3.6.4 — VOR Morse and DME Morse coordinated so a user can confirm both elements.
• Optional voice channel at ~5 +/-1 per cent modulation depth.

Failure modes: Morse keyer fault; voice channel modulation depth drift; loss of DME-VOR identification interlock.

A station whose identification fails the SARP must remove the navigation component (or be shut down) under the monitor logic in §3.3.7.

4. Monitor and integrity#

Annex 10 Vol I §3.3.7 — the most operationally critical domain. The ground monitor must, on detection of any of the following, warn the control point and either remove the navigation and identification components or cause radiation to cease:

• A change of bearing exceeding 1 degree at the monitor site (§3.3.7.1 a)).
• A reduction of 15 per cent or more in the modulation components of the radio signal at the monitor (§3.3.7.1 b)).
• Failure of the monitor itself (§3.3.7.2) — failsafe action.

Modern installations add:

• Dual monitor architecture with voting.
• Hot-standby transmitter changeover triggered by monitor alarm.
• Integration into a national NavAid Management System exposing station status, alarms, and flight-inspection due dates.

Failure modes: latent monitor mis-calibration (the station appears to be in tolerance to a drifted monitor while actually transmitting an out-of-tolerance signal); slow degradation that stays within the 1-degree alarm threshold but exceeds the design accuracy.

5. Receiver / interference immunity#

Annex 10 Vol I §3.3.8 places performance requirements on the airborne side of the link:

• Adequate immunity to two-signal third-order intermodulation produced by adjacent VHF FM broadcast carriers (§3.3.8.1) — driven by the expansion of FM broadcasting into the upper FM band adjacent to the 108-118 MHz aeronautical allocation.
• Adequate desensitisation immunity in the presence of strong VHF FM broadcast signals at the receiver input (§3.3.8.2).

Guidance for practical immunity testing is in Doc 9718 Volume II. Frequency planners use Doc 9718 procedures to assess co-existence between aeronautical and FM broadcast services in border regions.

How the domains interact#

The domains are interdependent in operation:

• A signal-in-space deviation will only be flagged if the monitor sees it (Domain 4 catches Domain 1).
• A coverage shortfall is invisible to a fixed monitor but obvious to a flight inspection; this is why flight inspection (Doc 8071) is the guarantor of Domain 2.
• A receiver-immunity shortfall can simulate a Domain 1 / Domain 4 failure without any actual VOR fault, so frequency-coordination analyses precede in-service problem reports.

Each requirement domain therefore has its own primary check method:

The five requirement domains in threads.md are the high-level groupings. Inside each domain there are individual SARP requirement "buckets" — the smallest unit at which a VOR is actually specified, tested, and signed off. This file walks five representative buckets and gives, for each, the same anatomical breakdown that lets an engineer or inspector treat the requirement as a deliverable.

The five buckets covered:

1. Signal accuracy (the bearing-pattern bucket).
2. Ground monitor (the integrity bucket).
3. Identification (the Morse / interlock bucket).
4. Course alignment (the on-radial bias bucket).
5. Flight inspection / FFM (the field-of-flight measurement bucket).

For each bucket, the structured fields are:

• SARP source. The Annex 10 Volume I paragraph or the supporting document.
• Numeric requirement. The actual tolerance.
• Test method. How conformance is demonstrated.
• Failure mode. What goes wrong, what it looks like, and what the required ground action is.
• Ownership. Who in the organisation answers for it.

1. Signal accuracy (bearing-pattern bucket)#

• SARP source. Annex 10 Vol I §3.3.3.2.
• Numeric requirement. Ground-station contribution to bearing error within +/-2 degrees over 0 to 40 degrees elevation. DVOR sites typically held to +/-1 degree by site practice.
• Test method. Periodic flight inspection per Doc 8071 Vol I — orbit and radial flight profiles measured with a flight-inspection reference system; comparison of received VOR bearing against truth.
• Failure mode. Course bends ("scallops") from site multipath; uniform bearing offset from antenna mis-alignment or transmitter phasing drift; high-elevation cone distortion. Out-of-tolerance results trigger an unserviceable NOTAM and corrective maintenance before re-commissioning.
• Ownership. Engineering authority (CNS) jointly with the flight-inspection unit.

2. Ground monitor (integrity bucket)#

• SARP source. Annex 10 Vol I §3.3.7.1 and §3.3.7.2.
• Numeric requirement. Alarm and act on bearing change >1 degree at the monitor site, or 15 per cent reduction in monitored modulation components, or monitor failure.
• Test method. Periodic monitor verification — controlled stimulus to the monitor input simulating a 1-degree bearing change and a 15 per cent modulation reduction; verification that the alarm output reaches the control point and that radiation is removed or identification is suppressed within the specified delay.
• Failure mode. Monitor drift: the station radiates an out-of-tolerance signal but the drifted monitor reports "in tolerance". Mitigated by independent calibrated checks at every flight inspection and by dual / voting monitor architectures.
• Ownership. Engineering authority (CNS) — the monitor is the station's own integrity guarantee and is treated as flight-safety critical.

3. Identification (Morse / interlock bucket)#

• SARP source. Annex 10 Vol I §3.3.6, with §3.5.3.6.4 for VOR/DME pairs.
• Numeric requirement. Two- or three-letter Morse code at 1 020 Hz, transmitted at least once every 30 seconds, simultaneously with the navigation signal. Voice channel (if provided) at approximately 5 +/-1 per cent modulation depth. For VOR/DME, the VOR and DME identifications must interlock per §3.5.3.6.4.
• Test method. Ramp test with a calibrated VOR test set; spectrum and modulation-depth check; aural verification of Morse content. Continuous monitor surveillance for ID-fail conditions.
• Failure mode. Stuck Morse keyer (continuous tone or no tone); wrong identifier after a frequency change; lost VOR/DME interlock so one element identifies and the other does not. Required ground action: remove navigation component or shut down, NOTAM as unserviceable.
• Ownership. Engineering authority (CNS) for the keyer; ATS unit for the published identifier and any AIP correlation.

4. Course alignment (on-radial bias bucket)#

• SARP source. Annex 10 Vol I §3.3.3 (with reference to the +/-2 degree pattern accuracy in §3.3.3.2). For procedure use, PANS-OPS Vol II §2.5.1 (cone of ambiguity) and §2.4.3 (VOR/DME fix divergence).
• Numeric requirement. Each published radial used by an instrument procedure must be aligned to the design intent within the SARP-level pattern accuracy. The procedure designer applies a tolerance budget that combines ground station error, airborne system error, and flight technical error.
• Test method. Commissioning flight inspection on every published radial, plus periodic re-inspection. The 50 degree semi-angle cone of ambiguity is exercised on overhead passes.
• Failure mode. A radial bias just inside the +/-2 degree SARP envelope can still degrade a low-margin instrument procedure (for example a low-minima approach with tight obstacle clearance). This is why procedure designers use the procedure-design tolerance, not the SARP tolerance, as the working margin.
• Ownership. Procedure design (PANS-OPS office) for the published radial; engineering authority for the alignment.

5. Flight inspection / FFM (field-of-flight measurement bucket)#

• SARP source. Annex 10 Vol I, Attachment C §3 (guidance) and Doc 8071 Volume I (Manual on Testing of Radio Navigation Aids — the authoritative reference; not in the local library).
• Numeric requirement. A defined inspection profile (orbit, radial, approach, holding, overhead) at a defined cadence (commissioning; periodic, typically 6 to 12 months; special-purpose after maintenance affecting the radiation pattern; following any complaint from operators).
• Test method. Calibrated flight-inspection aircraft with a reference position system (GNSS plus ground tracking) and a reference VOR receiver; data recorded and reduced into a flight inspection report classifying the aid as Unrestricted / Restricted / Unusable.
• Failure mode. Lapsed flight inspection (the aid is then by policy non-publishable for instrument procedures regardless of monitor state); failed flight inspection (NOTAM unserviceable, follow with corrective action and re-inspect).
• Ownership. Flight-inspection unit; procedure design and AIP drafting consume the report.

How the buckets compose into a serviceable VOR#

A VOR is "fit for use" only when every bucket is in date and within tolerance. Practically this means:

• Signal-in-space requirements pass the latest flight inspection.
• Ground monitor was verified within its calibration period.
• Identification is being heard correctly, including any DME interlock.
• Each published radial has a current commissioning flight check.
• The flight-inspection cycle has not lapsed.

A breach of any one bucket is, on its own, sufficient grounds for a NOTAM unserviceable and for ATS to stop publishing or clearing procedures dependent on the aid.

A serviceable VOR is more than a transmitter on a hilltop. The aid only delivers a usable navigation signal when a set of supporting elements — enablers — are in place and current. Without them, even a perfectly healthy radiating cabinet does not produce a publishable navigation service. This file groups the enablers into four categories.

1. Flight inspection#

The single most important enabler. A VOR cannot be commissioned, and its published radials cannot be used by an instrument procedure, until flight inspection has measured the actual signal-in-space against the SARP envelope and signed it off.

• Authoritative reference. ICAO Doc 8071 (Manual on Testing of Radio Navigation Aids), Volume I, Chapter "VHF Omnidirectional Radio Range (VOR)". Authoritative source — not in the local library.
• Inspection categories.
  • Commissioning — full pattern, every published radial, holding pattern, overhead cone, modulation, identification.
  • Periodic — recurring at the State-defined cadence (commonly 6 to 12 months); reduced profile but covers all published radials.
  • Special-purpose — after maintenance that may have affected the radiation pattern (transmitter swap, antenna work, monitor re-calibration).
  • Complaint-driven — triggered by an operator-reported anomaly.
• Equipment. Calibrated flight-inspection aircraft with reference GNSS positioning, reference VOR receiver, and recording suite.
• Output. A written flight inspection report classifying the aid as Unrestricted / Restricted (with conditions) / Unusable, and driving NOTAM / AIP action.

A lapsed flight inspection is, regardless of how healthy the station looks on remote monitoring, sufficient cause for the procedure office to suspend publication of dependent procedures.

2. Frequency planning and spectrum protection#

A VOR signal is only useful if it is not corrupted by other transmitters on the same or adjacent channels.

• Authoritative reference. ICAO Doc 9718 (Handbook on Radio Frequency Spectrum Requirements for Civil Aviation), Volume II. Authoritative source — not in the local library.
• Domestic planning. Co-channel and adjacent-channel separation between VORs and between VORs and ILS localizers in the 108 - 117.95 MHz band.
• Cross-border coordination. Frequency assignment lists exchanged through the regional air navigation plan and ITU coordination.
• FM-broadcast immunity. Coordination with national broadcasting regulators in the upper FM band (88 - 108 MHz) so that intermodulation products from the strongest FM stations do not exceed the receiver immunity envelope of Annex 10 Vol I §3.3.8.
• Identifier and channel-pair management. Allocation of unique Morse identifiers and, where DME is co-located, of paired VOR/DME channels per Annex 10 Vol I §3.5.3.4.

The frequency planner is therefore upstream of every commissioning: a VOR cannot be put on air on a channel that has not been coordinated.

3. Monitor and alert system#

The Annex 10 Vol I §3.3.7 monitor is itself an enabler — it converts a silent failure into a controlled, alerted, fail-safe event.

Modern installations expand the basic monitor into a full NavAid Management System with the following features:

• Dual ground monitor with voting. Resilience against single-point monitor drift.
• Hot-standby transmitter. Automatic changeover on monitor alarm.
• Remote control and status. Alarm exposure to the control point (ATS unit or technical centre) within the SARP-required delay.
• Logging. Every alarm, transmitter changeover, and operator action recorded for safety review and trend analysis.
• Integration with ATS. When the monitor pulls the navaid down, ATS must already be in receipt of the alarm, must broadcast on the appropriate ATC frequencies, and must originate a NOTAM unserviceable.
• Calibration. The monitor itself is verified against a reference signal source on a defined cadence. Monitor calibration error is the single largest hidden integrity risk.

Without the alert chain working end-to-end, the SARP requirement of §3.3.7 is met only on paper.

4. Regulatory framework#

VOR exists inside a State regulatory framework that determines who is allowed to commission, modify, decommission, and operate the aid.

• Standards adoption. The State adopts ICAO Annex 10 Volumes I and V into national CNS regulation, with any State-filed differences declared to ICAO.
• Type certification. The transmitter, monitor, and antenna model are type-certified or accepted under the State's CNS equipment approval process.
• Site approval. A site survey demonstrates that the proposed location can deliver the SARP coverage and bearing accuracy in the expected operating environment (terrain, buildings, RF noise floor).
• Operational authorisation. The CAA / ANS regulator authorises the aid for instrument flight use after acceptance of the commissioning flight inspection.
• Continuing surveillance. Periodic CAA audits of monitoring records, flight-inspection cycle, NOTAM history, and SMS occurrence reports.
• Decommissioning. Withdrawal of a VOR (especially a non-MON VOR in a rationalising network) follows a formal change process: AIP amendment, NOTAM, withdrawal of dependent published procedures, airspace user consultation, and (in the FAA / EUROCONTROL programmes) alignment with the published MON master list.

How the four enablers combine#

For a State that operates VORs, the enabler chain looks like:

Frequency planning  -->  Site approval  -->  Type-certified equipment
        -->  Commissioning flight inspection  -->  Operational authorisation
        -->  In-service:
                Continuous monitor / alert system
                Periodic flight inspection
                Continuing CAA surveillance
        -->  Decommissioning under MON / rationalisation policy

Each link is a SARP and / or a State-regulation requirement. A VOR can only stay published while every link is currently honoured. This is why VOR-network rationalisation programmes (FAA MON, EUROCONTROL Conventional Routes Backup) have to be governed end-to-end: deciding to keep a VOR also commits the State to keep funding its enabler chain for the foreseeable horizon.

VOR is a CNS infrastructure service. Like any other navigation service, it is judged against four standard Key Performance Areas (KPAs):

1. Accuracy — how close the indicated bearing is to the truth.
2. Integrity — the trust that can be placed in the indicated bearing being correct, and the timeliness of warnings when it is not.
3. Continuity — how reliably the service stays available once it has begun.
4. Availability — the fraction of time the service is usable when required.

These four KPAs are inherited from the wider Required Navigation Performance / RNP framework (Doc 9613) and from Annex 10 Volume I's treatment of GNSS, but they apply in essentially the same form to VOR because VOR is, ultimately, a navigation signal-in-space.

1. Accuracy#

Definition. The conformity between the bearing indicated by an ideal airborne receiver and the true magnetic bearing from the station.

Requirement (SARP). Annex 10 Vol I §3.3.3.2 — the ground-station contribution to bearing error is within +/-2 degrees over 0 to 40 degrees elevation.

Working margins.

• CVOR. Worst case approaches the +/-2 degree SARP envelope at cluttered sites; at clean sites holds to +/-1 degree.
• DVOR. Site practice typically targets +/-1 degree or better.
• Total system error. Procedure designers add airborne system tolerance and flight technical error; the working track-keeping accuracy is therefore wider than the ground SARP figure.

Measured by. Flight inspection (Doc 8071 Vol I) on each published radial, plus orbit and overhead profiles.

2. Integrity#

Definition. The probability that an undetected out-of-tolerance signal is being radiated, combined with the time to alert when one is detected.

Requirement (SARP). Annex 10 Vol I §3.3.7. The ground monitor must cause a warning at the control point and either remove the navigation and identification components or shut radiation off, on:

• Bearing change exceeding 1 degree at the monitor site, or
• 15 per cent or greater reduction in modulation components, or
• Failure of the monitor itself.

Engineering implications.

• The monitor's own calibration is the dominant integrity risk.
• Dual / voting monitors and hot-standby transmitter changeover are the principal mitigations.
• The end-to-end alert chain (monitor -> control point -> ATS broadcast -> NOTAM unserviceable) is part of the integrity case, not just the RF side.

Measured by. Periodic monitor verification with a calibrated stimulus; recording of alarm-to-control-point latency; SMS occurrence review of any monitor-driven shutdowns.

3. Continuity#

Definition. The probability that the service, having been available at the start of an operation (e.g. a published approach), remains available throughout the operation without unscheduled interruption.

Requirement. Annex 10 Vol I does not state a numerical continuity figure for VOR equivalent to GNSS approach SARPs, but Doc 9613 and regional MON design documents apply a continuity expectation of "adequate for the supported operation":

• For a non-precision approach, the relevant figure is the probability that the navaid does not fail during the approach window.
• For en-route MON service, continuity is dominated by mean time between unscheduled outages.

Engineering implications.

• Hot-standby transmitter (changeover within seconds, not minutes).
• UPS and engine-generator on primary power.
• Spare transmitter modules and regional logistics for fast restore.
• Avoidance of single points of failure on the antenna feed and monitor sampling line.

Measured by. MTBF, MTBO (mean time between outages), unscheduled outage rate per year, mean time to restore.

4. Availability#

Definition. The fraction of time the navaid is in service and within tolerance, when required.

Requirement. Set at the State level as a service-level target, informed by the operational role:

• MON and primary terminal VORs. Typically 99.9 per cent or better, recognising that failure forces fallback in a wider area.
• En-route VORs in a dense, redundant network. Lower per-site targets are tolerable because adjacent VORs cover the gap.
• T-VORs supporting a single procedure. Availability target tied directly to the procedure's expected utilisation.

Engineering implications.

• Scheduled maintenance windows that minimise disruption (off-peak, coordinated with neighbouring aids).
• Routine flight inspection scheduling that avoids withdrawing the station unnecessarily.
• Proactive component replacement on lifed parts.

Measured by. Availability percentage over a 12-month rolling window, NOTAM-time as a fraction of clock time, procedure non- publishability events.

Performance under the MON / rationalisation strategy#

The MON concept changes how the four KPAs are weighted:

• A MON VOR is held to higher availability, integrity, and continuity than a routine en-route VOR, because the entire fallback case rests on the surviving network.
• A non-MON VOR earmarked for decommissioning is allowed to deteriorate in a controlled way: maintenance is reduced, the procedure office removes dependent procedures, the AIP is updated, and the aid is finally withdrawn under NOTAM.
• The MON master list is therefore not just a navigation question; it is a performance commitment. A State that designates a VOR as MON is committing to maintain its KPA performance across the rationalisation horizon.

How the KPAs feed reporting#

• CAA / ANSP. Internal KPI dashboards report availability, MTBF, monitor-alarm rate, lapsed flight inspections, and NOTAM hours per aid.
• Regional bodies. Regional air navigation plans (APAC, EUR, MID) consolidate VOR availability into their reversionary-capability reporting.
• Global. ICAO Annex 10 Volume I, Attachment H rationalisation strategy is the global frame; States report progress against it through ANC and the regional planning groups.

The VOR requirement story has three intertwined timelines:

1. Annex 10 SARP evolution — when ICAO standardised, refined, or adjusted VOR provisions.
2. Technology evolution — from CVOR to solid-state DVOR.
3. Network evolution — from a dense conventional network to a rationalised Minimum Operational Network (MON).

Treating them as one timeline is misleading; understanding them as three parallel arcs explains why VOR is simultaneously an "old" technology and an actively maintained, future-relevant one.

1. Annex 10 SARP evolution#

VOR was selected by ICAO as the international short-range navigation aid in the late 1940s and has been carried in Annex 10 Volume I, Chapter 3 ever since. Headline events:

• Late 1940s. ICAO adopts VOR as the international standard short-range VHF navigation aid.
• 1950s - 1960s. Annex 10 Vol I §3.3 SARPs mature: 108 - 118 MHz band allocated; bearing accuracy SARP at +/-2 degrees; horizontal polarisation; identification at 1 020 Hz.
• 23 May 1974. Cut-off date in §3.3.2.2 - §3.3.2.3 — installations in 50 kHz spacing areas commissioned after this date must hold the tighter +/-0.002 per cent carrier-frequency tolerance, and existing VORs in such areas should be tightened to the same.
• 1980s. §3.3.7 monitoring requirements progressively refined; 1 degree alarm threshold and 15 per cent modulation reduction threshold solidified as the global norm.
• 1990s - 2000s. §3.3.8 receiver immunity requirements introduced to handle the spread of high-power VHF FM broadcasting in the upper FM band; the two-signal third-order intermodulation criterion is the headline test.
• 2010s onward. Annex 10 Vol I, Attachment H — Strategy for rationalization of conventional radio navigation aids — formalises the direction of travel: retain VOR as a reversionary network supporting PBN, decommission redundant aids in a controlled way.

Throughout, the core SARP envelope (frequency band, +/-2 degree pattern accuracy, monitor thresholds, identification cadence) has been remarkably stable. Successive amendments have tightened tolerances and added receiver-side immunity rather than re-architecting the aid.

2. Technology evolution: CVOR to DVOR#

The same SARP envelope can be met by either CVOR or DVOR; from the receiver's point of view they are indistinguishable. The migration from CVOR to DVOR is therefore a ground-side engineering choice, not a SARP change.

• 1950s - 1970s. Primarily mechanical / four-loop CVOR installations. Site clearance requirements drive the choice of hilltop or open-airfield locations.
• Late 1970s - 1980s. Doppler VOR developed and progressively deployed at sites where multipath made CVOR marginal. The 13.4 m diameter counterpoise and 48 / 50 antenna ring become standard.
• 1990s - 2000s. Solid-state DVOR transmitters and dual-monitor configurations; remote control and status integrated into national technical centres.
• 2010s onward. Most CVOR sites in modernising regions either decommissioned or replaced with DVOR. Modern DVOR replacements have reduced power consumption, web-based status, and seamless monitor / transmitter changeover.

Many countries today still operate a mixed CVOR / DVOR fleet. The distinction matters operationally only at the site-survey and flight-inspection level: DVOR is the default at sites with reflection issues; CVOR is retained where the site is clean and the lifetime cost of replacement is not justified.

3. Network evolution and the MON concept#

The biggest change of the past two decades has not been in the individual VOR but in the network it forms.

• Pre-2000. Dense national VOR networks define the airway structure. Every airport of any consequence has a co-located VOR/DME.
• 2000s. GNSS becomes the de facto primary means of navigation; PBN approaches (RNP APCH with LNAV / LNAV+VNAV / LPV minima) proliferate. VOR utilisation falls; the cost of maintaining a dense VOR network rises in relative terms.
• 2011 - 2016 (FAA). FAA publishes plans to rationalise the CONUS VOR network. The "VOR MON" programme is formalised: ~900 CONUS VORs reduced to ~590; new MON SSV defined from 5 000 ft AGL. A 100 NM MON airport guarantee is introduced — every aircraft within MON airspace is within 100 NM of a MON airport with a non-GNSS, non-DME approach (ILS, LOC, or VOR). All VORs in Alaska, the Western US Mountainous Area, and US territories are retained.
• 2010s onward (EUROCONTROL). A parallel "Conventional Routes Backup" / reversionary VOR strategy: keep enough VORs to underpin a designated set of fallback routes when GNSS is unavailable. Member States rationalise their national VOR networks accordingly.
• ICAO frame. Annex 10 Vol I, Attachment H — Strategy for rationalization of conventional radio navigation aids — and the PBN Manual (Doc 9613) jointly set the global doctrine: PBN as the primary navigation paradigm, with conventional aids retained selectively for reversion.

4. Where Pakistan / APAC sit#

Indicative regional context (verify current status against the latest APANPIRG and ICAO APAC Implementation Plan documents, which are revised annually):

• VOR / DME networks remain the backbone of conventional procedures across the region.
• PBN approach implementation continues, with VOR/DME retained for reversionary use where alternative ILS or LOC approaches are not available.
• Selective DVOR replacement of older CVOR sites is in progress; decommissioning of redundant T-VORs follows AIP coordination and airspace user consultation.
• A formal regional MON-equivalent designation is under discussion in several APAC States, anchored on the ICAO Annex 10 Attachment H rationalisation strategy.

5. How to read a date in a VOR document#

When a VOR document cites a date, place it on one of the three arcs:

• "Annex 10 §3.3.2 carrier tolerance tightened after 23 May 1974" - Arc 1 (SARP evolution).
• "DVOR replacement programme completed 2018" - Arc 2 (technology).
• "FAA VOR MON target 2030; reduce 900 to 590 VORs" - Arc 3 (network evolution).

Mixing the arcs leads to the false impression that VOR is being phased out. SARP-level VOR is stable, the ground equipment continues to be modernised, and the network is being rationalised — not abolished.

Primary ICAO documents#

• Annex 10 (Aeronautical Telecommunications), Volume I — Radio Navigation Aids, Chapter 3, §3.3 — Specification for VHF omnidirectional radio range (VOR). The headline SARP block.
• Annex 10, Volume I, Chapter 3, §3.3.2 — VOR radio frequency band (111.975 - 117.975 MHz; 108 - 111.975 MHz under Vol V Chapter 4 conditions; highest assignable frequency 117.950 MHz; 50 kHz channel spacing; carrier frequency tolerance +/-0.005 per cent and +/-0.002 per cent in 50 kHz spacing areas).
• Annex 10, Volume I, Chapter 3, §3.3.3 — Polarisation and pattern. §3.3.3.2: ground-station bearing-error contribution within +/-2 degrees over 0 to 40 degrees elevation.
• Annex 10, Volume I, Chapter 3, §3.3.4 — Coverage requirements and field-strength expectations.
• Annex 10, Volume I, Chapter 3, §3.3.5 — Modulation: 30 Hz reference and variable phase modulation; 9 960 Hz subcarrier with 16 +/-1 deviation ratio.
• Annex 10, Volume I, Chapter 3, §3.3.6 — Voice and identification (Morse identification at 1 020 Hz; voice channel modulation depth approximately 5 +/-1 per cent; interaction with §3.5.3.6.4 for VOR/DME identification interlock).
• Annex 10, Volume I, Chapter 3, §3.3.7 — Monitoring. §3.3.7.1 requires alarm and remove-or-shutdown action on bearing change >1 degree at the monitor site or 15 per cent reduction in monitored modulation components; §3.3.7.2 covers monitor self-failure.
• Annex 10, Volume I, Chapter 3, §3.3.8 — Interference immunity performance for VOR receiving systems against VHF FM broadcast signals, including two-signal third-order intermodulation and desensitisation criteria.
• Annex 10, Volume I, Chapter 3, §3.5 — Distance Measuring Equipment, including §3.5.2.6.1 VOR/DME co-location limits (not greater than 80 m for terminal/approach; not greater than 600 m otherwise) and §3.5.3.4 channel pairing.
• Annex 10, Volume I, Attachment C, Section 3 — Material concerning VOR/DVOR. Guidance on accuracy budgets, siting, and pattern effects.
• Annex 10, Volume I, Attachment E — Pre-flight checking provisions, including the VOT (VOR Test) facility.
• Annex 10, Volume I, Attachment H — Strategy for rationalization of conventional radio navigation aids and evolution toward supporting PBN; the SARP-level basis for MON / reversionary-VOR doctrine.
• Doc 8168 (PANS-OPS), Volume I, Part I, Section 4, Chapter 1, §1.5.1.1 — General criteria for VOR and NDB en-route routes apply to PBN en-route procedures except as amended.
• Doc 8168 (PANS-OPS), Volume II, Part I, Section 2, Chapter 2, §2.4.3 — Fixes for VOR or NDB with DME (collocation; 23 degree maximum divergence for non-collocated DME).
• Doc 8168 (PANS-OPS), Volume II, Part I, Section 2, Chapter 2, §2.5.1 — VOR fix tolerance overhead a station: cone of ambiguity with 50 degree semi-angle (default) and construction of position-fix tolerance area.
• Doc 8071 (Manual on Testing of Radio Navigation Aids), Volume I, Chapter on VOR — Authoritative flight inspection guidance for VOR (commissioning, periodic, and special inspections; profiles and tolerances) (authoritative source — not in local library).
• Doc 9613 (Performance-Based Navigation Manual) — Context for VOR/DME within PBN; VOR/DME RNAV 5 only when DME is co-located; rationale for limiting new VOR/DME-based PBN implementations.
• Doc 9718 (Handbook on Radio Frequency Spectrum Requirements for Civil Aviation), Volume II — Frequency planning, geographic separation between co-channel and adjacent-channel VOR / ILS, and immunity coordination with VHF FM broadcasting (authoritative source — not in local library).

ICAO Annexes most touched by VOR requirements#

• Annex 10 Volumes I and V (CNS and spectrum).
• Annex 11 (ATS) — for ATS responsibilities when a VOR alarms or is withdrawn.
• Annex 14 (Aerodromes) — siting on aerodromes.
• Annex 15 (AIS) and PANS-AIM (Doc 10066) — publication of VOR data and dependent procedures in the AIP.
• Annex 19 (SMS) — safety management of VOR-driven occurrences.

Authoritative external sources#

• FAA VOR MON programme. https://www.faa.gov/about/office_org/headquarters_offices/ato/service_units/techops/navservices/gbng/vormon
• FAA Federal Register notice on NextGen navigation services provision (2016). https://www.federalregister.gov/documents/2016/07/26/2016-17579/provision-of-navigation-services-for-the-next-generation-air-transportation-system-nextgen
• ICAO Annex 10 Volume I (store / overview page). https://store.icao.int/en/annex-10-aeronautical-telecommunications-volume-i-radio-navigational-aids
• EUROCONTROL navigation strategy (conventional and PBN). https://www.eurocontrol.int/navigation
• EUROCONTROL Specification for ATM Surveillance Sensor Performance (context for CNS rationalisation). https://www.eurocontrol.int/publication
• General reference (background description). https://en.wikipedia.org/wiki/VHF_omnidirectional_range

Where local search of the ICAO Markdown library is required, the canonical VOR provisions are in Annex 10 Volume I Chapter 3, §3.3 and the supporting Attachments C, E, and H. Doc 9613 (PBN Manual) is the PBN-side reference. Doc 8071 and Doc 9718 are authoritative but, at the time of writing, not held in the local library; primary use is via official ICAO publication channels.