RVSM Group Aircraft. Aircraft within a group of aircraft, approved as a group by the Administrator, in which each of the aircraft satisfy each of the following:

(a) The aircraft have been manufactured to the same design, and have been approved under the same type certificate, amended type certificate, or supplemental type certificate.

(b) The static system of each aircraft is installed in a manner and position that is the same as those of the other aircraft in the group. The same static source error correction is incorporated in each aircraft of the group.

(c) The avionics units installed in each aircraft to meet the minimum RVSM equipment requirements of this appendix are:

(1) Manufactured to the same manufacturer specification and have the same part number; or

(2) Of a different manufacturer or part number, if the applicant demonstrates that the equipment provides equivalent system performance.

RVSM Nongroup Aircraft. An aircraft that is approved for RVSM operations as an individual aircraft.

RVSM Flight envelope. An RVSM flight envelope includes the range of Mach number, weight divided by atmospheric pressure ratio, and altitudes over which an aircraft is approved to be operated in cruising flight within RVSM airspace. RVSM flight envelopes are defined as follows:

(a) The full RVSM flight envelope is bounded as follows:

(1) The altitude flight envelope extends from FL 290 upward to the lowest altitude of the following:

(i) FL 410 (the RVSM altitude limit);

(ii) The maximum certificated altitude for the aircraft; or

(iii) The altitude limited by cruise thrust, buffet, or other flight limitations.

(2) The airspeed flight envelope extends:

(i) From the airspeed of the slats/flaps-up maximum endurance (holding) airspeed, or the maneuvering airspeed, whichever is lower;

(ii) To the maximum operating airspeed (Vmo/Mmo), or airspeed limited by cruise thrust buffet, or other flight limitations, whichever is lower.

(3) All permissible gross weights within the flight envelopes defined in paragraphs (1) and (2) of this definition.

(b) The basic RVSM flight envelope is the same as the full RVSM flight envelope except that the airspeed flight envelope extends:

(1) From the airspeed of the slats/flaps-up maximum endurance (holding) airspeed, or the maneuver airspeed, whichever is lower;

(b) The applicant for authorization shall submit the appropriate data package for aircraft approval. The package must consist of at least the following:

(1) An identification of the RVSM aircraft group or the nongroup aircraft;

(2) A definition of the RVSM flight envelopes applicable to the subject aircraft;

(3) Documentation that establishes compliance with the applicable RVSM aircraft requirements of this section; and

(4) The conformity tests used to ensure that aircraft approved with the data package meet the RVSM aircraft requirements.

(c) Altitude-keeping equipment: All aircraft. To approve an aircraft group or a nongroup aircraft, the Administrator must find that the aircraft meets the following requirements:

(1) The aircraft must be equipped with two operational independent altitude measurement systems.

(2) The aircraft must be equipped with at least one automatic altitude control system that controls the aircraft altitude --

(i) Within a tolerance band of ±65 feet about an acquired altitude when the aircraft is operated in straight and level flight under nonturbulent, nongust conditions; or

(ii) Within a tolerance band of ±130 feet under nonturbulent, nongust conditions for aircraft for which application for type certification occurred on or before April 9, 1997 that are equipped with an automatic altitude control system with flight management/performance system inputs.

(3) The aircraft must be equipped with an altitude alert system that signals an alert when the altitude displayed to the flight crew deviates from the selected altitude by more than:

(i) ±300 feet for aircraft for which application for type certification was made on or before April 9, 1997; or

(ii) ±200 feet for aircraft for which application for type certification is made after April 9, 1997.

(d) Altimetry system error containment: Group aircraft for which application for type certification was made on or before April 9, 1997. To approve group aircraft for which application for type certification was made on or before April 9, 1997, the Administrator must find that the altimetry system error (ASE) is contained as follows:

(1) At the point in the basic RVSM flight envelope where mean ASE reaches its largest absolute value, the absolute value may not exceed 80 feet.

(2) At the point in the basic RVSM flight envelope where mean ASE plus three standard deviations reaches its largest absolute value, the absolute value may not exceed 200 feet.

(3) At the point in the full RVSM flight envelope where mean ASE reaches its largest absolute value, the absolute value may not exceed 120 feet.

(4) At the point in the full RVSM flight envelope where mean ASE plus three standard deviations reaches its largest absolute value, the absolute value may not exceed 245 feet.

(5) Necessary operating restrictions. If the applicant demonstrates that its aircraft otherwise comply with the ASE containment requirements, the Administrator may establish an operating restriction on that applicant's aircraft to restrict the aircraft from operating in areas of the basic RVSM flight envelope where the absolute value of mean ASE exceeds 80 feet, and/or the absolute value of mean ASE plus three standard deviations exceeds 200 feet; or from operating in areas of the full RVSM flight envelope where the absolute value of the mean ASE exceeds 120 feet and/or the absolute value of the mean ASE plus three standard deviations exceeds 245 feet.

(e) Altimetry system error containment: Group aircraft for which application for type certification is made after April 9, 1997. To approve group aircraft for which application for type certification is made after April 9, 1997, the Administrator must find that the altimetry system error (ASE) is contained as follows:

(1) At the point in the full RVSM flight envelope where mean ASE reaches its largest absolute value, the absolute value may not exceed 80 feet.

(2) At the point in the full RVSM flight envelope where mean ASE plus three standard deviations reaches its largest absolute value, the absolute value may not exceed 200 feet.

(f) Altimetry system error containment: Nongroup aircraft. To approve a nongroup aircraft, the Administrator must find that the altimetry system error (ASE) is contained as follows:

(1) For each condition in the basic RVSM flight envelope, the largest combined absolute value for residual static source error plus the avionics error may not exceed 160 feet.

(2) For each condition in the full RVSM flight envelope, the largest combined absolute value for residual static source error plus the avionics error may not exceed 200 feet.

(g) Traffic Alert and Collision Avoidance System (TCAS) Compatibility With RVSM Operations: All aircraft. After March 31, 2002, unless otherwise authorized by the Administrator, if you operate an aircraft that is equipped with TCAS II in RVSM airspace, it must be a TCAS II that meets TSO C-119b (Version 7.0), or a later version.

(b) An applicant for authorization to operate within RVSM airspace shall apply in a form and manner prescribed by the Administrator. The application must include the following:

(1) An approved RVSM maintenance program outlining procedures to maintain RVSM aircraft in accordance with the requirements of this appendix. Each program must contain the following:

(i) Periodic inspections, functional flight tests, and maintenance and inspection procedures, with acceptable maintenance practices, for ensuring continued compliance with the RVSM aircraft requirements.

(ii) A quality assurance program for ensuring continuing accuracy and reliability of test equipment used for testing aircraft to determine compliance with the RVSM aircraft requirements.

(iii) Procedures for returning noncompliant aircraft to service.

(2) For an applicant who operates under part 121 or 135, initial and recurring pilot training requirements.

(3) Policies and Procedures. An applicant who operates under part 121 or 135 shall submit RVSM policies and procedures that will enable it to conduct RVSM operations safely.

(c) Validation and Demonstration. In a manner prescribed by the Administrator, the operator must provide evidence that:

(1) It is capable to operate and maintain each aircraft or aircraft group for which it applies for approval to operate in RVSM airspace; and

(b) No person may show, on the flight plan filed with air traffic control, an operator or aircraft as approved for RVSM operations, or operate on a route or in an area where RVSM approval is required, unless:

(1) The operator is authorized by the Administrator to perform such operations; and

(2) The operator submits an appropriate request with the air traffic control center controlling the airspace, (request should be made at least 48 hours in advance of the operation unless prevented by exceptional circumstances); and

(a) Total vertical error of 300 feet or more;

(b) Altimetry system error of 245 feet or more; or

(a) Committing one or more altitude-keeping errors in RVSM airspace;

(b) Failing to make an effective and timely response to identify and correct an altitude-keeping error; or

(2) RVSM may be effective in the Minimum Navigation Performance Specification (MNPS) airspace within the NAT. The MNPS airspace within the NAT is defined by the volume of airspace between FL 285 and FL 420 (inclusive) extending between latitude 27 degrees north and the North Pole, bounded in the east by the eastern boundaries of control areas Santa Maria Oceanic, Shanwick Oceanic, and Reykjavik Oceanic and in the west by the western boundaries of control areas Reykjavik Oceanic, Gander Oceanic, and New York Oceanic, excluding the areas west of 60 degrees west and south of 38 degrees 30 minutes north.

(b) RVSM in the Pacific. (1) RVSM may be applied in the Pacific in the following ICAO Flight Information Regions (FIRs): Anchorage Arctic, Anchorage Continental, Anchorage Oceanic, Auckland Oceanic, Brisbane, Edmonton, Honiara, Los Angeles, Melbourne, Nadi, Naha, Nauru, New Zealand, Oakland, Oakland Oceanic, Port Moresby, Seattle, Tahiti, Tokyo, Ujung Pandang and Vancouver.

[Doc. No. 28870, 62 FR 17487, Apr. 9, 1997, as amended by Amdt. 91-261, 65 FR 5942, Feb. 7, 2000; Amdt. 91-271, 66 FR 63895, Dec. 10, 2001]