U.S. DEPARTMENT OF TRANSPORTATION
FEDERAL AVIATION ADMINISTRATION
Air Traffic Organization Policy

ORDER
JO 7210.3
Y
Effective Date:
April 3, 2014
 
     
Subject:  Facility Operation and Administration
 Includes:  Change 1 and its Errata effective 7/24/14

Section 9. Reduced Vertical Separation Minimum (RVSM)

6-9-1. GENERAL

a. RVSM reduces the standard separation between FL290 and FL410 from 2,000 feet to 1,000 feet for those aircraft approved for operation within these altitude strata. The six additional altitudes provide the users fuel savings and operational efficiencies while providing ATC flexibility, mitigation of conflict points, enhanced sector throughput and reduced controller workload for air traffic control operations.

b. RVSM is applied in that airspace from FL290 through FL410 over the domestic United States, Alaska, the Gulf of Mexico where the FAA provides air traffic services, the San Juan FIR, across international borders with Canada and Mexico, and the Pacific and Atlantic Oceanic airspace controlled by the FAA. There are two forms of RVSM airspace:

1. RVSM Airspace. Use of the term RVSM airspace refers to the RVSM exclusive environment. Aircraft operating in this airspace must be RVSM approved.

NOTE-
1. The following non-RVSM aircraft are exceptions to the exclusive RVSM airspace. However, access will be on a workload-permitting basis:
a. DOD aircraft.
b. DOD-certified aircraft operated by NASA (T38, F15, F18, WB57, S3, and U2 aircraft only).
c. MEDEVAC aircraft.
d. Aircraft being flown by manufacturers for development and certification.
e. Foreign State aircraft.

2. Aircraft not approved for RVSM operations may transition through RVSM airspace to operate above or below.

2. Transition Airspace. Airspace where both RVSM aircraft and non-RVSM aircraft may be accommodated at all altitudes and RVSM approval is not required. Transition airspace connects airspace wherein conventional separation is applied to RVSM airspace. One thousand feet vertical separation can only be applied between RVSM aircraft. Two thousand feet separation must be applied between non-RVSM aircraft or whenever one of the aircraft is non-RVSM.

c. Non-RVSM exception aircraft may access RVSM airspace in one of the following ways:

1. LOA: Complies with a Letter of Agreement (LOA) for operations within a single or adjacent ARTCCs.

2. File-and-Fly: Files a flight plan and makes the initial request to access RVSM airspace by requesting an ATC clearance.

d. Facilities with RVSM airspace must:

1. Provide guidance in the facility Standard Operating Procedures (SOP) for managing non-RVSM flights.

2. Where available, display the Center Monitor on the Traffic Situation Display (TSD) in each area and the Traffic Management Unit (TMU). This will aid in the coordination and decision making process for approving non-RVSM flights.

6-9-2. FACILITY MANAGER RESPONSIBILITIES

a. Ensure all facility directives are current to support RVSM.

b. Ensure all LOAs, SOPs, and Sector Position Binders are current to support RVSM.

c. Ensure airspace is continually reviewed for impact of RVSM.

d. Ensure all height deviations of 300 feet or more are recorded and forwarded to the FAA Technical Center in Atlantic City, New Jersey at NAARMO@faa.gov.

REFERENCE-
FAAO 7210.56, para 4-1-9, Invalid Mode C Reporting.

6-9-3. OPERATIONS MANAGER-IN-CHARGE RESPONSIBILITIES

Responsibilities must include but not be limited to the following:

a. Maintain an operational awareness of RVSM impact specifically any non-RVSM aircraft being worked within RVSM airspace.

b. Ensure proper coordination is accomplished between the STMC/TMU and the operations supervisors/controllers-in-charge regarding the accommodation and handling of any non-RVSM aircraft.

c. Ensure, in conjunction with the Traffic Management Officer, that monitor alert values are addressed with RVSM impacts considered.

d. Ensure the proper RVSM software is turned on.

6-9-4. FRONT-LINE MANAGER-IN-CHARGE/CONTROLLER-IN-CHARGE RESPONSIBILITIES

Responsibilities must include but not be limited to the following:

a. Maintain an awareness of all operational impacts associated with RVSM, specifically any non-RVSM aircraft currently within area sectors or projected to be in sectors under his/her area of responsibility.

b. Ensure sector personnel have been properly briefed regarding any known non-RVSM aircraft in or projected to be in sectors under his/her area of responsibility.

c. Ensure sector workload remains manageable when non-RVSM aircraft are in or projected to be in sectors under his/her area of responsibility.

d. Coordinate all non-RVSM aircraft with operational supervisors/CIC as appropriate, both internally and externally, to ensure the aircraft is coordinated and accepted along its route of flight.

e. Non-RVSM Exception Flights Outbound from the U.S. The operational supervisor/CIC from the last area to have communications and operational control of the aircraft in the facility where an aircraft departs RVSM airspace designated for U.S. air traffic control, or exit facility, must coordinate with the international point-of-contact in a timely manner.

f. Ensure controllers at applicable sectors have their DSR MDM properly aligned to display the RVSM indicator depicting those aircraft that are non-RVSM.

6-9-5. NON-RVSM REQUIREMENTS

a. RVSM approval is required for aircraft to operate within RVSM airspace. The operator must determine that the appropriate State authority has approved the aircraft.

b. DOD, DOD-certified aircraft operated by NASA (T38, F15, F18, WB57, S3, and U2 aircraft only), MEDEVAC, aircraft operated by manufacturers for certification and development, and Foreign State exception aircraft will be accommodated in RVSM airspace on a workload permitting basis.

c. Non-RVSM Exception Flights Inbound to U.S. The TMU at the facility where an aircraft penetrates RVSM airspace designated for U.S. air traffic control, or entry facility, receives the coordination from an international point-of-contact advising of an inbound non-RVSM exception. The TMU must coordinate with the operational supervisor/CIC in a timely manner.

6-9-6. EQUIPMENT SUFFIX AND DISPLAY MANAGEMENT

RVSM aircraft will file a “W" in the equipment field of an ICAO flight plan, or a suffix showing RVSM capability in a domestic flight plan (/H, /W, /L, or /Z). NAS automation shows non­RVSM aircraft with a coral box around the fourth character in the altitude segment of the data block. The conflict alert function uses the flight plan indication of RVSM capability to determine the appropriate separation standard to apply.

6-9-7. MOUNTAIN WAVE ACTIVITY (MWA)

In areas of known MWA, aircraft operators have been encouraged to report encountering this weather event and the severity of its impact. Operators may request assistance in the form of reroutes, change of altitude, vectors, or merging target procedures.

6-9-8. WAKE TURBULENCE AND WEATHER RELATED TURBULENCE

a. Domestic: Aircraft experiencing turbulence can be anticipated to advise ATC and request a clearance for mitigation in the form of vectors, altitude change, or to fly an offset.

b. Oceanic: Aircraft experiencing turbulence can be anticipated to advise ATC and request a revised clearance. In instances where a revised clearance is not possible or practicable, the aircraft may fly a lateral offset not to exceed 2NM from the assigned route or track. Advise ATC as soon as practical and return to the assigned route when the offset is no longer required.

6-9-9. SUSPENSION OF RVSM

a. Domestic: RVSM will not be suspended in domestic airspace. Should turbulence or other weather phenomena require, separation can be increased in a defined area and thoroughly coordinated operationally.

b. Oceanic: Air Traffic Service providers will consider suspending RVSM procedures within affected areas when pilot reports of greater than moderate turbulence are received. Within airspace where RVSM procedures are suspended, the vertical separation minimum between all aircraft will be 2,000 feet above FL290.

Return to Air Traffic Publications Library Return to Order Home Page Return to Table of Contents