Reduced Vertical Separation Minimum (RVSM) airspace is one of the most consequential expansions of usable high-altitude airspace in modern aviation. By cutting the vertical separation standard from 2,000 feet to 1,000 feet in the flight levels between FL290 and FL410, RVSM effectively doubled the number of available cruise altitudes in that band. For aircraft dispatchers and pilots alike, this efficiency gain comes with a strict set of equipment, approval, and monitoring requirements that must be satisfied before any flight is released into RVSM airspace.
Understanding RVSM is not simply an academic exercise. The dispatcher's signature on a release document constitutes a legal affirmation that the aircraft, crew, and operation are authorized for the planned route. If that route transits domestic U.S. RVSM airspace — or any of the international RVSM regions — the dispatcher must verify authorization before releasing the flight. This article explains the mechanics of RVSM, what approval entails, and how to correctly apply those requirements at the dispatch desk.
What RVSM Airspace Is and Where It Applies
In the United States, RVSM airspace encompasses the contiguous band of altitudes from Flight Level 290 (29,000 feet MSL) to Flight Level 410 (41,000 feet MSL) inclusive. This airspace is designated as Class A airspace domestically, though RVSM itself is a vertical separation standard, not an airspace class. Outside the U.S., RVSM applies in virtually every major oceanic and continental region worldwide — North Atlantic (NAT), Pacific (PACOTS), Europe (EUR), and others — each governed by its own regional supplementary procedures, though all share the same 1,000-foot separation minima within their designated altitude bands.
Prior to RVSM implementation in the lower portion of high-altitude airspace (which the FAA adopted domestically in January 2005), the minimum vertical separation above FL290 was 2,000 feet. That standard existed because older altimetry technology introduced enough error that two aircraft could deviate significantly from their cleared altitudes without triggering a conflict alert. RVSM requires both the aircraft and the altimetry system to meet far tighter tolerances, making the tighter separation physically safe.
How RVSM Approval Works
RVSM authorization is a two-layer process: the aircraft itself must be approved, and the operator must be approved. Neither alone is sufficient.
Aircraft Airworthiness Approval
An aircraft is approved for RVSM operations when it has been shown to meet the height-keeping performance standards defined in the applicable technical standards. In practical terms, this means the aircraft's altimetry system — including static sources, Air Data Computers (ADCs), and the autopilot altitude-hold function — must maintain assigned altitude within plus or minus 200 feet under normal conditions and within plus or minus 245 feet for the purpose of the Total Vertical Error (TVE) budget. The aircraft must carry at least two independent altitude measurement systems and one altitude alerting system. Most transport-category jets manufactured after the early 1990s were designed with RVSM approval in mind, but the dispatcher should never assume approval; it must be documented.
Aircraft airworthiness approval for RVSM is reflected in a Statement of Compliance or equivalent documentation that is part of the aircraft's maintenance records. The FAA issues operator authorization via Operations Specifications (OpSpecs). For Part 121 and Part 135 carriers, OpSpec B036 (or the equivalent paragraph for the operation type) specifically authorizes RVSM operations. A dispatcher verifying release authority must confirm that the operating certificate includes this authorization and that the specific tail number being dispatched is on the approved aircraft list or is RVSM-approved per maintenance records.
Crew and Operator Approval
Beyond the aircraft, the operating organization must demonstrate that its policies, procedures, and training programs address RVSM-specific requirements. Flight crews must be familiar with the RVSM operating procedures, including altitude deviation reporting requirements and the proper response to an equipment failure that degrades height-keeping performance. Most Part 121 carriers incorporate RVSM initial and recurrent training into the standard ground and simulator curriculum. The dispatcher's role is to confirm the operation is within the scope of the carrier's OpSpecs — not to individually track each pilot's RVSM training record, which falls under crew scheduling and training departments.
Pre-Release Equipment Verification
When preparing a dispatch release for a flight that will operate at or between FL290 and FL410, the dispatcher must verify the following before signing the release:
- Aircraft RVSM approval status: Confirm the tail number is RVSM-approved. This information is typically available in the airline's aircraft tracking system, maintenance release, or Minimum Equipment List (MEL) status documentation.
- No open MEL deferrals that preclude RVSM: Certain deferred items — particularly those affecting altimetry, autopilot altitude-hold, or the altitude alerting system — may render the aircraft non-RVSM-compliant. The MEL will designate these items accordingly; the dispatcher must cross-reference any open deferrals against RVSM eligibility.
- Operator authorization (OpSpecs): The carrier's Operations Specifications must authorize RVSM operations for the route and aircraft type.
- Contingency planning: The release should reflect an awareness of what altitudes are available if RVSM equipment degrades en route. ATC must be notified immediately if an aircraft loses RVSM capability in RVSM airspace, and the crew must request a non-RVSM altitude, which may not be immediately available in congested airspace.
Why RVSM Matters Operationally and for Safety
The safety case for RVSM rests entirely on the integrity of each aircraft's height-keeping performance. The moment a non-approved or malfunctioning aircraft enters RVSM airspace, the separation assurance that ATC relies upon is undermined — not just for that aircraft, but for every other aircraft at adjacent altitudes. A failure to verify RVSM approval is not a paperwork technicality; it is a potential mid-air collision precursor.
From an operational efficiency standpoint, RVSM allows airlines to optimize cruise altitudes for fuel economy. The ability to step-climb from FL350 to FL370 to FL390 as weight decreases gives dispatchers powerful tools for fuel planning. Without RVSM, those intermediate altitudes would not exist in the separation framework, and aircraft would be forced to operate at less-optimal altitudes longer, burning more fuel and reducing payload capability.
Dispatchers must also be aware that some aging aircraft — particularly older freighters or general aviation turboprops operating under Part 135 — may not hold RVSM approval. A route that crosses RVSM airspace cannot legally be dispatched for such an aircraft without either rerouting to avoid FL290–FL410, obtaining an ATC deviation authorization (which is a crew-initiated action, not a pre-planned dispatcher workaround), or confirming that a waiver or exemption applies.
Key Numbers and Rules
- FL290 to FL410 inclusive: The vertical extent of U.S. RVSM airspace.
- 1,000 feet: The vertical separation minimum applied within RVSM airspace (versus 2,000 feet previously).
- ±200 feet: The normal altitude-keeping accuracy required of an RVSM-approved aircraft's altimetry system.
- Two independent altitude measurement systems plus one altitude alerting device are the minimum equipment requirements for RVSM operations.
- OpSpec B036 (or equivalent): The Part 121/135 authorization paragraph for RVSM operations that must appear on the carrier's Operations Specifications.
- Immediate ATC notification is required if an aircraft loses RVSM capability in RVSM airspace; the crew must request a block altitude or non-RVSM altitude.
- Non-RVSM aircraft may be cleared through RVSM airspace by ATC under special provisions, but this is an ATC accommodation, not an operator right, and does not eliminate the regulatory requirement for authorization.
Common Test Traps
- Assuming all jets are automatically RVSM-approved: Age, maintenance history, and avionics configuration matter. A dispatcher must affirmatively verify approval — never assume.
- Confusing FL290 and FL410 as exclusive boundaries: RVSM applies from FL290 through FL410, meaning both FL290 and FL410 are included in the RVSM regime. A cruise altitude of FL290 is inside RVSM airspace.
- Overlooking MEL items: An open deferral on the autopilot altitude-hold or a secondary ADC may silently disqualify an otherwise RVSM-approved airframe. Always cross-check MEL status as part of the release process.
- Thinking RVSM applies only over oceans: Domestic U.S. airspace between FL290 and FL410 is RVSM airspace. The North Atlantic RVSM rules are an additional (and in some ways stricter) overlay for oceanic operations, but the domestic requirement is equally binding.
- Believing ATC can waive the requirement on behalf of the operator: ATC can accommodate a non-RVSM aircraft in an emergency or coordination scenario, but the operator's legal obligation to hold authorization cannot be waived by ATC clearance alone.