# Presentation: 103216

## RVSM APPROVALS DATABASE AND MONITORING 

- Presentation 13

**RVSM APPROVALS DATABASE AND MONITORING **

**Separation Standards Group                                           FAA Technical Center**
**Atlantic City, New Jersey**

- V. 1.6

## Access to Information on RVSM Approvals Database

- Information on RVSM approvals databases is posted on the RVSM Documentation Webpage
- See “_Registration on RVSM Approvals Databases_” in the Table of Contents
- US aircraft and operators are registered on
- 	“_US Operator/Aircraft RVSM Approvals Database_” primarily through FAA inspector inputs to PTRS
- Normally no action required of operators

## CONTACT FOR U.S. OPERATORS

**For U.S. operators and AFS field offices,** contact for RVSM Approvals Database or RVSM Monitoring questions is:
- “U.S. Operator/Aircraft: RVSM Approvals DB and Monitoring Coordinator”:
- Wayne.Smoot@faa.gov
- Ph 609-485-5475
- Fax 609-485-5078

## Contact For Non-U.S. Operators

**NAARMO Website is linked from FAA RVSM Homepage**
**Also linked from RVSM Documentation Webpage “Registration” section**
**http://www.tc.faa.gov/act-500/niaab/rvsm/naarmo_intro.asp**
**Contact: Richard Soper, NAARMO Operations Coordinator,  at:  NAARMO@faa.gov**

**Monitoring Requirements and Procedures**

## Access to Information

- See Monitoring Requirements/Procedures section on RVSM Documentation Webpage:
- “Instructions for Using Minimum Monitoring Charts and Procedures from Different Regions”
- “Monitoring Procedures for US Operators”
- “North American RVSM Minimum Monitoring Requirements” and requirements for other regions
- ICAO group working to harmonize requirements

## TWO ASPECTS OF MONITORING GOALS

**Need to ensure that individual operators and aircraft meet applicable safety goals**
**Need to ensure that North American airspace system as a whole meets applicable safety goal - the Target Level of Safety (TLS)**
**Monitoring of aircraft height-keeping performance assists in confirming that both aspects of safety goals are satisfied**

## MONITORING HEIGHT-KEEPING PERFORMANCE 

*FL 350  Geometric Height*

*FL 350  = Constant Pressure Altitude*

**MONITORING HEIGHT-KEEPING PERFORMANCE**** **

## HEIGHT-KEEPING PERFORMANCE ERRORS

*FL 350  Geometric Height*

**HEIGHT-KEEPING PERFORMANCE ERRORS**

*Aircraft geometric height*

*            **Total Vertical Error  (TVE)*
*            **=  Altimetry System Error +*
*           **Assigned Altitude Deviation    *
*            **= ASE +AAD *

## GMS MONITORING AND THE STATE  APPROVAL PROCESS

**	****GPS-based Monitoring System (GMS), improved with enhanced GPS Monitoring Unit, plays a prominent role in supporting operator/aircraft satisfaction of monitoring requirements associated with RVSM approval process---including those for DRVSM**

## GPS Monitoring Unit (GMU)

## Enhanced GPS Monitoring Unit (EGMU)

## Typical GMU Installation

## GPS-Based Monitoring SystemData Flow

**Differential Data**

**Via Internet/Direct**

**Data Transmitted Post-Flight**

**Post-flight Processing Station**

**Vertical Error Processing**
**FAA Technical Center**

**Airborne GPS-based Monitoring Unit (GMU)**

**Remote Reference Station**

**FAA Technical Center Database**

- ASE Results

**Database (Monitoring Results)**

**Mode C Data**

**Meteorological Data (Height of flight level)**

- Flight Information Form (FIF)

- Flight Information Form (FIF)

**Queries**

## GMS Vertical Error Calculation Process

- Determine Flight Level (FL) Height

- Determine Aircraft Geometric Height

- Compare Cleared FL to Actual Altitude

- GMU

- GPS Reference Station

- Meteorological Data

- Cleared FL (FIF)

- Mode C Data

- Cleared FL (FIF)

- TVE (Total Vertical Error)

- ASE (Altimetry System Error)

- AAD (Assigned Altitude Deviation)

## Height Monitoring Unit (HMU)

- EUROCONTROL and North Atlantic Ground-based system capable of monitoring height-keeping performance of an aircraft within (roughly) 40-nm of ground stations and producing estimate of ASE in near real-time
- Advantage: able to monitor large number of aircraft per day (conceptually, all which pass over ground stations)
- Disadvantage: aircraft must fly over HMU site

## Slide 17

## DRVSM Monitoring System

- Aircraft Geometric Height Measurement Element (AGHME) Atlantic City prototype in final stages of testing
- Wichita AGHME shipped to site
- Cleveland and Roanoke, Va. AGHME constellations scheduled for deployment
- AGHME constellations to be located near Ottawa and Lethbridge in Canada.
- Aircraft should fly straight and level at or above FL290 over the AGHME monitoring area.

## AGHME Constellation

**AGHME Constellation**

## Sites Under Investigation

## MONITORING GOALS ASSOCIATED WITH STATE RVSM APPROVAL

## MINIMUM AIRCRAFT SYSTEM PERFORMANCE SPECIFICATION (MASPS)

**Performance which aircraft group must be capable of achieving in service, regardless of airspace where RVSM is applied**
**Mean altimetry system error (ASE) of the group < 80 ft in magnitude**
**Sum of the absolute value of the mean plus 3 standard deviations of ASE for group < 245 ft**
**Errors in altitude-keeping symmetric about a mean of     0 ft, have a standard deviation < 43 ft and have error frequency which decreases at least exponentially with increasing error magnitude**

## Monitoring Policies

**INITIAL MONITORING. **In application to the appropriate State authority for RVSM approval, operators must show plan for meeting monitoring requirements necessary to receive RVSM approval.
**AIRCRAFT STATUS FOR MONITORING. **Aircraft engineering work that is required to bring the aircraft into compliance with RVSM standards must be completed prior to the aircraft being monitored.
**Participation in an approved monitoring program **_**is required**_ in accordance with the chart, _**however**_, monitoring _not_ required _prior to the grant of RVSM operational approval_

## Monitoring Policies (cont.)

**APPLICABILTY OF MONITORING FROM OTHER REGIONS.  **Operator monitoring results obtained from one region may be used to satisfy other regions’ requirements.
**TRAILING CONE DATA.  **If aircraft documented to be in approved RVSM configuration, trailing cone data can be used to fulfill monitoring requirements
**FOLLOW-ON MONITORING.  **Monitoring will continue after initial RVSM implementation.  A
- 	follow-on program will be coordinated after reviewing results.

## BACKGROUND TO ESTABLISHMENT OF CURRENT MONITORING GOALS 

**FAA participated actively in the introduction of the North Atlantic (NAT) and Pacific RVSM**
**NAT, Pacific and European monitoring has produced substantial number of height-keeping performance estimates for aircraft types typically observed **
**Monitoring requirements reduced substantially from original 1997 set as monitoring results for individual aircraft types became available and compliance with requirements was established with high confidence**

## MONITORING GOALS – Category 1

## MONITORING GOALS – Category 2

- *Note:  If 60 percent of the North American fleet yields a fractional number, round up to the next whole aircraft
- (e.g., for a fleet of 2 aircraft, 0.6 x 2 = 1.2; therefore, 2 aircraft must be monitored).

## MONITORING GOALS – Category 3

## Process to Perform Monitoring

- See RVSM Documentation Webpage
- See “Monitoring Requirements and Procedures” section