MonProc USOpr.doc 15 Mar 05

RVSM Monitoring Procedures for U.S. Operators

**[\*Document Updates.]{.underline}** This document was updated on
March10, 2005. Paragraphs containing clarifications or updates are
marked in the left margin.

**[\*Basic Guidance on RVSM Monitoring.]{.underline}** **(See page 2-3
for additional guidance).**

***\*1. Monitoring requirements do [NOT]{.underline} have to be
completed prior to the operator receiving RVSM authority (Letter of
Authorization (LOA) or Operations Specifications).***

***\*2. Operators have up to [six months after]{.underline} they receive
RVSM authority [or]{.underline} until six months after the start of RVSM
operations in an airspace, [whichever occurs later,]{.underline} to
complete RVSM monitoring requirements.***

***\*3. With only limited exceptions, operators must have FAA
authorization to cruise in RVSM airspace. This provision applies to
flights conducted for monitoring. FAA Notice GEN04009, paragraph j
discusses the exceptions for Non-RVSM aircraft. See page 2-3 for
additional detail.***

***\*4. The provision for ATC to accommodate operators/aircraft that do
not have RVSM authority in RVSM airspace for \"aircraft certification
and development\" purposes [is NOT intended to apply to flights
conducted for the specific purpose of accomplishing RVSM
monitoring.]{.underline}*** Guidance for monitoring conducted by
Aircraft Service Centers and Airplane Manufacturers is posted under
"Guidance For Conducting Monitoring Flights" on page 2.

***\*5. Operators are required to participate in the RVSM Monitoring
Program.***

**[Contacts and Responsibilities.]{.underline}** The Separation
Standards Group at the FAA Wm. J. Hughes Technical Center in Atlantic
City, New Jersey serves as the U.S. Operator/Aircraft RVSM Approvals
Database and Monitoring Coordinator. The group also provides staffing
and funding for the North American Approvals Registry and Monitoring
Organization (NAARMO) and the Asia/Pacific Approvals Registry and
Monitoring Organization (APARMO). The group coordinates monitoring
results and U.S. aircraft/operator RVSM approval information with
Regional Monitoring Agencies (RMA) in other regions such as the North
Atlantic and Europe.

Contacts in the Separation Standards Group are shown below. (+1
indicates the U.S. country code).

[U.S. Operator/Aircraft RVSM Approvals Database and Monitoring
Coordinator]{.underline}

> Phone: +1 609-485-5475
>
> Fax: +1 609-485-5078
>
> Email: wayne.smoot@faa.gov
>
> [RVSM Program Manager for Regulation & Certification
> (AVR)]{.underline}
>
> Phone: +1 202-385-4576
>
> Fax: +1 202-385-4653
>
> Email: <robert.swain@faa.gov>

[NAARMO/APARMO Operations Coordinator at FAA Technical
Center]{.underline}

Phone: +1 609-485-5678

Fax: +1 609-485-5078

Email: naarmo@faa.gov

**[\*Additional Guidance For Conducting Monitoring
Flights]{.underline}**

\*1. **[Aircraft Status For Monitoring.]{.underline} Aircraft must be
RVSM-compliant for monitoring to be conducted. [For in-service
aircraft,]{.underline}** aircraft modification and/or inspection
required by RVSM Service Bulletin, STC or other approved RVSM document
must be completed prior to the aircraft being monitored. **[For aircraft
manufactured RVSM-compliant,]{.underline}** the Airplane Flight Manual
and/or Type Certificate Data Sheet will show a statement of RVSM
compliance. **Any exception to this rule must be coordinated with
AFS-400.**

\*2. LOA\'s are issued to operators intending to conduct operations in a
Special Area of Operation (e.g., RVSM airspace). **[RVSM monitoring can
be conducted after the operator receives the LOA.]{.underline}**

\*3. Airplane manufacturers have authorization to fly RVSM-compliant
\"production\" airplanes in RVSM airspace as RVSM-compliant flights.
**[Monitoring can be accomplished on these flights when the aircraft is
in an RVSM-compliant configuration.]{.underline}**

\*4. **[Monitoring By Aircraft Service Centers, Repair Stations and
Designated Airworthiness Stations.]{.underline}** Monitoring flights are
often completed on behalf of operators by Aircraft Service Centers,
Certificated Repair Stations or Designated Airworthiness Stations.
(There are established provisions for these organizations to obtain FAA
RVSM authorization). STC or Service Bulletin work is completed to bring
an aircraft into RVSM-compliance and then, as part of the service,
monitoring is conducted. **In these circumstances, monitoring can be
conducted prior to the operator submitting aircraft RVSM documents to
the Flight Standards field office (FSDO or CMO).** Normally, however, it
is good practice to submit RVSM documents to the FSDO or CMO prior to
conducting monitoring.

\*5. **[Monitoring During RVSM STC or Service Bulletin (SB) Test
Flights.]{.underline}** Aircraft test flights flown for final STC or SB
sign off can be monitored as long as the aircraft is in an
RVSM-compliant condition and the FAA Tech Center is notified of the
circumstances on the "US Operator Application for RVSM Monitoring" form.
(See Appendix 1).

\*6. I**nstructions on use of trailing cone data to fulfill monitoring
requirements are posted on the minimum monitoring requirements charts.**

**[Monitoring Requirements Charts.]{.underline}** Monitoring
requirements charts are published on the RVSM Documentation Webpage
under "Monitoring Requirements and Procedures". They are used to
determine the number of airframes that operators are required to have
monitored. Instructions for using the monitoring requirements charts for
various regions are also posted on the Webpage. The first page of the
charts contains guidelines for monitoring and for using the charts.

**[Monitoring Not Required Prior to the Issue of Operational
Approval.]{.underline}** The "Minimum Monitoring Requirements" charts
are the source documents for monitoring requirements and deadlines. The
North American Minimum Monitoring Requirements Chart states that
monitoring requirements are **[not]{.underline}** required to be
completed until **"6 months after the issue of operational approval or
not later than 6 months after the start of North American RVSM
operations, [whichever occurs later.]{.underline}"** The Minimum
Monitoring Requirements Charts for other regions state that monitoring
requirements are **[not]{.underline}** required to be completed until
**"6 months after the issue of operational approval."** .

**[Required Participation.]{.underline}** Operators are required to
participate in the RVSM Monitoring Program. As stated in FAA Guidance
91-RVSM paragraph 11d (8), in its application for RVSM authority, the
operator should show its plan for completion of monitoring requirements.
Monitoring requirements are published on the FAA **"RVSM Documentation"
page.** This page can be accessed through the FAA RVSM Website homepage:

-   <http://www.faa.gov/ats/ato/rvsm1.htm>

**[Application of Monitoring Results To and From Different Regional
Programs.]{.underline}** Monitoring data obtained to fulfill the
monitoring requirements for one region can be used to fulfill the
monitoring requirements for another region. Regional Monitoring Agencies
coordinate with each other to exchange database information on
monitoring results.

**[Options for Participation in Monitoring Programs.]{.underline}** The
following options for operator participation in RVSM monitoring programs
are discussed in this paper:

-   Operators can fly a portable GPS-based Monitoring Unit (GMU) on
    their aircraft. See Appendix 2.

-   \*Operators can overfly the ground-based Height Monitoring Units
    (HMU) near Strumble in the U.K. **The HMU near Gander in Canada has
    been decommissioned.** See Appendix 3.

-   Operators can overfly one of the three HMU's deployed in Europe. See
    Appendix 4.

-   **[\*Domestic U.S. RVSM Monitoring System.]{.underline}** The first
    [Aircraft Geometric Height Measurement Element]{.underline} (AGHME)
    constellation was operational in January 2005. See Appendix 5 for
    details.

Procedures for successfully completing a monitoring flight using one of
these systems are discussed in detail in the Appendices.

**[Application for Monitoring.]{.underline}** All operators must
complete an "Application For Monitoring" form and fax it to the
organizations shown at the top of the form. This information will help
track and process operator monitoring efforts. **See Appendix 1.**

**[Appendices]{.underline}**

Appendix 1 Form: U.S Operator Application for RVSM
Monitoring.........................Page 4

Appendix 2 GPS-based Monitoring System (GMS)
Procedures..................\...\...\...\...\...\....Page 6

Appendix 3 Procedures for North Atlantic (Strumble) Height Monitoring
Unit...............Page 10

> (NAT HMU)

Appendix 4 Basic Monitoring Procedures for Europe: HMUs and
GMUs......\...\...\...\...\...\....Page 12

Appendix 5 \*Domestic U.S. AGHME GMS (Aircraft Geometric
Height..................\.....Page 15

> Measurement Element Ground-based Monitoring System)

##  Appendix 1

## [U.S. OPERATOR APPLICATION FOR RVSM MONITORING]{.underline}

**[Instructions]{.underline}**

**1. All operators: fax completed form to +1 609-485-5078.**

**2. Operators planning GMS monitoring, [also]{.underline} fax copy to
the appropriate GMS Support Contractor.**

> **CSSI: +1 202-863-2398; ARINC: +1 410-573-3007**

**Operator
Name**:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Operator's 3-letter ICAO Identifier
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**(For IGA operator, enter IGA. If no ICAO identifier assigned, enter
"None".**

**Address**:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Operator Primary Point of Contact**

Name:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_Title:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Telephone Number:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ Fax
Number: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Email Address:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

# Operator Secondary Point of Contact 

Name:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_Title:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Telephone Number:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ Fax
Number: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Email Address:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

# Responsible Flight Standards Office (FSDO or CMO) Point of Contact

Name:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_Title:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Address:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Telephone Number:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ Fax
Number: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Email Address:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**REGION WHERE RVSM OPERATIONS WILL BE CONDUCTED:**

(Check all that apply)

<table style="width:100%;">
<colgroup>
<col style="width: 4%" />
<col style="width: 7%" />
<col style="width: 4%" />
<col style="width: 6%" />
<col style="width: 4%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 6%" />
<col style="width: 4%" />
<col style="width: 6%" />
<col style="width: 4%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 7%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 7%" />
</colgroup>
<tbody>
<tr class="odd">
<td><table>
<colgroup>
<col style="width: 100%" />
</colgroup>
<tbody>
<tr class="odd">
<td></td>
</tr>
</tbody>
</table></td>
<td><p>North</p>
<p>America</p></td>
<td><table>
<colgroup>
<col style="width: 100%" />
</colgroup>
<tbody>
<tr class="odd">
<td></td>
</tr>
</tbody>
</table></td>
<td>Pacific</td>
<td><table>
<colgroup>
<col style="width: 100%" />
</colgroup>
<tbody>
<tr class="odd">
<td></td>
</tr>
</tbody>
</table></td>
<td><p>West</p>
<p>PAC/</p>
<p>SCS</p></td>
<td><table>
<colgroup>
<col style="width: 100%" />
</colgroup>
<tbody>
<tr class="odd">
<td></td>
</tr>
</tbody>
</table></td>
<td><p>Bay</p>
<p>Of</p>
<p>Bengal</p></td>
<td><table>
<colgroup>
<col style="width: 100%" />
</colgroup>
<tbody>
<tr class="odd">
<td></td>
</tr>
</tbody>
</table></td>
<td><p>North</p>
<p>Atlantic</p></td>
<td><table>
<colgroup>
<col style="width: 100%" />
</colgroup>
<tbody>
<tr class="odd">
<td></td>
</tr>
</tbody>
</table></td>
<td><p>Caribbean/</p>
<p>South</p>
<p>American</p></td>
<td><table>
<colgroup>
<col style="width: 100%" />
</colgroup>
<tbody>
<tr class="odd">
<td></td>
</tr>
</tbody>
</table></td>
<td>European</td>
<td><table>
<colgroup>
<col style="width: 100%" />
</colgroup>
<tbody>
<tr class="odd">
<td></td>
</tr>
</tbody>
</table></td>
<td>Asia</td>
<td><table>
<colgroup>
<col style="width: 100%" />
</colgroup>
<tbody>
<tr class="odd">
<td></td>
</tr>
</tbody>
</table></td>
<td><p>Other</p>
<p>(Please</p>
<p>Specify)</p></td>
</tr>
</tbody>
</table>

**Information on HMU Flights**

Approximate date(s) of HMU flight: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

HMU(s) planned to be overflown: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

(Requested Aircraft Information on next page)

**AIRCRAFT INFORMATION**

**(Please be sure to include data for the ENTIRE fleet)**

  ------------------ --------------- ------------------ ------------------
  Aircraft Model     Registration    Serial Number      Mode S Address
                     Number                             

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        

                                                        
  ------------------ --------------- ------------------ ------------------

Appendix 2

**[GPS-based Monitoring System (GMS) Procedures]{.underline}**

The NAARMO is responsible for all aircraft height monitoring activity
for North American RVSM operations (Domestic U.S., Southern Canadian
Domestic, and Mexico) and administers the GMU height-monitoring program.
CSSI Incorporated and ARINC, as GMS support contractors, will assist the
NAARMO with the monitoring program.

**GMS Description**

The GMS is composed of the equipment and procedures to collect and
process three required data elements: 1) GPS data; 2) pressure altitude
or Mode C data; and 3) meteorological data. The GPS-based Monitoring
Unit (GMU) is used to collect the GPS data during the monitoring flight.
The NAARMO will use information on the attached Flight Information Form
(FIF) to coordinate the collection of pressure altitude or Mode C data
from ATC facilities. Late transmittal of the FIF or illegible or blank
entries will delay post-flight processing of data and the dissemination
of results. Meteorological data will be obtained by the NAARMO without
operator involvement.

**GMS Contacts:**

U.S. GMS Coordinator at FAA Technical Center,

Atlantic City, N.J.

> Phone: +1 609-485-5102

Fax: +1 609-485-5078

Email: rvsm@faa.gov

CSSI Inc. GMS Support Contractor:

\*Phone: +1 866-468-8111 or +1 202-554-1051

Fax: +1 202-863-2398

Email: [monitor@cssiinc.com]{.underline}

> ARINC GMS Support Contractor:
>
> Phone: +1 410-266-4707
>
> Fax: +1 410-573-3007
>
> Email: <rvsmops@arinc.com>

**Forms**

The following forms are required to be completed:

-   Application for Monitoring shown in Appendix 1

-   Flight Information Form attached to Appendix 2 (this appendix)

**GMU Monitoring Flights**

Height monitoring can be conducted on scheduled flights, ferry flights,
or monitoring-specific flights. To ensure collection of sufficient
position data the aircraft must fly straight and level at any altitude
from FL290 to FL 410 for at least thirty minutes in duration. Monitoring
flights do not need to be conducted in North American airspace; however,
monitoring should be conducted in areas where Mode-C radar data can be
retrieved by the FAA Technical Center staff in a timely manner.

**GMU Description**

The GMU is a portable unit composed of a Global Positioning System (GPS)
receiver, two GPS antennas (temporarily mounted on interior windows with
suction cups), and a laptop computer to record the GPS performance data.
The GMU requires plug-in power from the aircraft (draws 2.0 to 4.0
amperes maximum) and accepts multiple types of power standard to most
aircraft. The GMU can be installed in the aircraft cockpit or cabin,
depending upon aircraft type. Installation time is approximately 15
minutes. For most transport aircraft, the GMU is best installed using
the aft cockpit windows. The GMS Support Contractor typically occupies a
jump seat to monitor GMU performance. GMU installation and operation
will not interfere with crew operations.

**[GMU Monitoring Process]{.underline}**

The monitoring sequence for the operator is illustrated in Figure 1
below. The operator will be kept informed as the FIF, GPS data file, and
pressure altitude data file move through the

post-flight processing steps.

**\*Aircraft Status For Monitoring.** **Aircraft must be RVSM-compliant
for monitoring to be conducted.** For in-service aircraft, aircraft
modification and/or inspection required by RVSM Service Bulletin, STC or
other approved RVSM document must be completed prior to the aircraft
being monitored.

Any exception to this rule must be coordinated with AFS-400.

The operator should contact a GMS Support Contractor to discuss
monitoring options, such as time, date, origin and destination airport
and routing for the GMU flight. The operator should submit the
Monitoring Application to the U.S. GMS Coordinator [and]{.underline} the
GMS Support Contractor by facsimile. The operator should list on the
Monitoring Application each aircraft that will be operated in RVSM
airspace [or]{.underline} attach a list to the application. The
collection of GPS data with the GMU can be accomplished by a GMS Support
Contractor or by an operator representative that has received GMU
training. Operator representatives should coordinate directly with the
GMS Support Contractor to develop a monitoring plan as described above.

To conduct the monitoring flight, the GMS Support Contractor or a
trained operator representative will perform the following tasks:

1\. Submit pre-flight FIF to the U.S. GMS Coordinator [and]{.underline}
the GMS Support Contractor

2\. Conduct the height monitoring flight with the GMU

3\. Submit post-flight FIF to the U.S. GMS Coordinator [and]{.underline}
the GMS Support Contractor

4\. Submit GPS data files to GMS Support Contractor

**FSDO OR CMO Action.** After determining that aircraft are
RVSM-compliant, the FSDO or CMO will forward operator and airframe
information to the U.S. Operator/Aircraft RVSM Approvals Database using
the Flight Standards Program Tracking and Reporting Subsystem (PTRS).

**Post-Flight Processing and Operator Notification**

After completion of the monitoring flight, the GPS data from the
monitoring flight will be processed by the GMS Support Contractor (CSSI
or ARINC) and forwarded to the U.S. GMS Coordinator for further
processing. The NAARMO will collect and merge Meteorological and Mode C
data with the GPS file to determine the aircraft's Altimetry System
Error (ASE). Final ASE results should be available from the NAARMO
within three weeks of the flight. The results will be sent to the
responsible FAA FSDO or CMO.

The operator can obtain a copy of the results from the FSDO or CMO.

Flight Information Form (FIF)

Please Fax to the U.S. GMS Coordinator at +1 609 485
5078[and]{.underline} the appropriate GMS Operations Coordinator

CSSI: +1 202-863-2398; ARINC: +1 410-573-3007

**\
Fax 24 hours prior to flight and within 6 hours of landing.**

<table>
<colgroup>
<col style="width: 10%" />
<col style="width: 6%" />
<col style="width: 2%" />
<col style="width: 11%" />
<col style="width: 11%" />
<col style="width: 0%" />
<col style="width: 7%" />
<col style="width: 2%" />
<col style="width: 9%" />
<col style="width: 9%" />
<col style="width: 8%" />
<col style="width: 7%" />
<col style="width: 0%" />
<col style="width: 14%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="14">INFORMATION TO BE RECORDED PRIOR TO FLIGHT</td>
</tr>
<tr class="even">
<td colspan="6">Airline/Operator:</td>
<td colspan="6">GMU Container Number:</td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td colspan="14"><p>Point of Contact for Operator:</p>
<p>Name: Phone: Fax:</p></td>
</tr>
<tr class="even">
<td colspan="6">Aircraft Type/Series:</td>
<td colspan="8">Aircraft Registration Number:</td>
</tr>
<tr class="odd">
<td colspan="6">Call Sign:</td>
<td colspan="8">Airframe Serial Number:</td>
</tr>
<tr class="even">
<td colspan="14">Planned: Origin: Departure Date (UTC): Departure Time
(UTC):</td>
</tr>
<tr class="odd">
<td colspan="14">Planned: Destination: Arrival Date (UTC): Arrival Time
(UTC):</td>
</tr>
<tr class="even">
<td colspan="7">Installer (Name/Org.):</td>
<td colspan="7">Retriever (Name/Org.):</td>
</tr>
<tr class="odd">
<td colspan="14">Mode S Equipped (Yes/No): Separation Between Mounted
Antennas (ft.):</td>
</tr>
<tr class="even">
<td colspan="14">Installer/Operator Comments:</td>
</tr>
<tr class="odd">
<td colspan="14">INFORMATION TO BE RECORDED BY FLIGHT CREW/GMU
OPERATOR</td>
</tr>
<tr class="even">
<td colspan="2">Data Collection:</td>
<td colspan="5">Start Date (UTC):</td>
<td colspan="7">Start Time (UTC):</td>
</tr>
<tr class="odd">
<td colspan="14">GMU File Name:</td>
</tr>
<tr class="even">
<td colspan="7">Departure Time (UTC):</td>
<td colspan="5">Origin (ICAO ID):</td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td colspan="14"><p>Please record the requested information as soon as
practical when:</p>
<ol type="1">
<li><p>Aircraft is first established in level flight at or above FL 290,
or</p></li>
<li><p>The ATC assigned transponder code is changed at or above FL 290,
or</p></li>
<li><p>There is a flight level change and aircraft remains at or above
FL 290, or</p></li>
<li><p>An autopilot change is initiated at or above FL 290, or</p></li>
<li><p>The ARTCC or FIR changes.</p></li>
</ol></td>
</tr>
<tr class="even">
<td>Time</td>
<td colspan="2">Assigned</td>
<td>Mach/Air</td>
<td>Xpndr</td>
<td colspan="4">Altimeter Reading</td>
<td colspan="2">Autopilot (L, R, C)</td>
<td colspan="2">FMS/PMS</td>
<td>ARTCC/FIR</td>
</tr>
<tr class="odd">
<td>(UTC)</td>
<td colspan="2">FL</td>
<td>Speed</td>
<td>Code/Source</td>
<td colspan="3">Pilot</td>
<td>Co-pilot</td>
<td>Pilot</td>
<td>Co-pilot</td>
<td colspan="2">(Y/N)</td>
<td>(ICAO ID)</td>
</tr>
<tr class="even">
<td></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2">Data Collection:</td>
<td colspan="5">End Date (UTC):</td>
<td colspan="7">End Time (UTC):</td>
</tr>
<tr class="even">
<td colspan="7">Arrival Time (UTC):</td>
<td colspan="5">Destination ICAO (ID):</td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td colspan="14">Comments on flight conditions affecting height keeping
performance, i.e. turb, and location</td>
</tr>
</tbody>
</table>

Appendix 3

**[Procedures for North Atlantic (Strumble) Height Monitoring
Unit]{.underline}**

1\. [Options for Monitoring Flights.]{.underline} In the North Atlantic
Region, monitoring can be completed by overflying ground-based Height
Monitoring Units (HMUs) or utilizing the portable, airborne GPS-based
Monitoring System (GMS). Procedures for using the GMS are provided in
Appendix 2.

2\. [Monitoring Requirements.]{.underline} Monitoring requirements
charts for the North/West Atlantic are posted on the FAA RVSM
Documentation webpage
([www.faa.gov/ats/ato/rvsm1.htm](http://www.faa.gov/ats/ato/rvsm1.htm))
and on the North Atlantic Programme Coordination Office website
([www.nat-pco.org](http://www.nat-pco.org/)). As a general rule,
operators seeking RVSM approval will be required to have a number of
their aircraft monitored within 6 months of receiving RVSM approval.

3\. [Monitoring Using the HMU Method]{.underline}

a\. \*An HMU is located near the Strumble (STU) VOR below the centreline
of UG1. The horizontal coverage areas for the Strumble HMU is a 13.8 nm
radius circle centered on position N51 56' 00'' W004 40' 00''. In the
vertical dimension, the coverage is from FL 290 to FL 410 inclusive. The
site is unmanned and designed to operate continuously.

b\. \*The HMU near the Gander (YQX) VORTAC in Canada was decommissioned
on 1/20/05.

c\. While straight and level flight through the area of coverage should
normally result in successful monitoring, operators of aircraft making a
flight with the specific intention of getting monitored should, where
possible, plan to meet the requirements outlined in the ensuing
paragraphs:

d\. [Pre-Flight Procedures.]{.underline}

\(1\) Operators complete and fax a copy of the "Application for
Monitoring" form to the U.S. Operator/Aircraft RVSM Approvals Database
and Monitoring Coordinator. See Appendix 1.

\(2\) \*Operators proposing to divert from an optimum route in order to
fly over an HMU are strongly advised to call the Strumble HMU status
line on 44 (\*0) 189 542-3823 (\*0 not required from U.S. locations) for
HMU serviceability information. Every effort will be made to ensure that
the promulgated information is accurate; however, operators should note
that the equipment may become unserviceable at short notice.

\(3\) \*Aircraft for monitoring by an HMU should be flight planned to
route via STU. Dispatchers should ensure that Item 18 of the flight plan
(CA48) includes both aircraft registration (if it is not already
included in Item 7) and "RMK/HMU FLT STU".

d\. [In Flight Procedures.]{.underline} For overflights of the Strumble
HMU, crews should aim to fly straight and level while within the
coverage area of the respective HMU. Failure to do so may invalidate the
result. Prior to an overflight of the Strumble HMU, crews should
transmit **"\... for HMU Flight"** to London Control on initial contact.
Operational requirements permitting, the controller will endeavor to do
his/her best to allow the aircraft to route through the HMU coverage
area in straight and level flight.

-   The HMU is capable of tracking many aircraft simultaneously. To that
    end, provided the above procedures are followed, aircraft height
    will be monitored and there will, therefore, be no necessity to
    carry out a second consecutive overflight.

e\. [Post Flight Procedures.]{.underline} Operators wishing to ascertain
the result of the overflight may fax a request to the NAT Central
Monitoring Agency (CMA) on +44 (\*0) 189 542-3931. (\*0 not required
from U.S. locations). Any request for information regarding the result
of monitoring will be more speedily dealt with if the Mode S or Mode A
codes and approximate time of overflight are included in the enquiry.

Appendix 4

**[Basic Monitoring Procedures for Europe: HMU's and
GMU's]{.underline}**

**Introduction.** The information below was adopted for U.S. operators
from Monitoring Procedures on the Eurocontrol RVSM website. The full
document can be found under "Aircraft Operators" in the European RVSM
website. The address is:
[http://www.eur-rvsm.com](http://www.eur-rvsm.com/)

**Options for Monitoring Flights.** Operators have the option of
overflying an HMU or using the GMS. Basic GMS procedures are addressed
in Appendix 2. For operators based outside the U.S., a contact is
provided below for the ARINC European Division GMS monitoring program.

**[HMU Procedures]{.underline}**

**Pre-Flight Coordination with U.S. Operator/RVSM Approvals Database and
Monitoring Coordinator.** U.S. operators planning to complete monitoring
using an HMU located in Europe should complete the following steps:

1\. Operator obtains FAA Flight Standards field office RVSM
airworthiness and operational approval

> for the aircraft to be monitored in European airspace. (Airframe and
> operational approval information will be forwarded to the U.S. RVSM
> Approvals Database through the AFS Program Tracking and Reporting
> Subsystem (PTRS)).

2\. Operator completes the "Application for Monitoring" form shown in
Appendix 1 and faxes it to U.S. Operator/RVSM Approvals Database and
Monitoring Coordinator at +1 609-485-5078 and...

3\. If it has not already been accomplished, the U.S. Operator/RVSM
Approvals Database and Monitoring Coordinator will coordinate the
operator's FAA RVSM Approvals Database information with Eurocontrol.

4\. If not previously accomplished, the operator also faxes USC Form 2
(see below) to the AMN User Support Cell.

**Flight Procedures.** The **HMU** is a passive ground based system that
measures aircraft height keeping over an approximately circular area.
Each system consists of a set of ground stations arranged as a central
site with four additional receivers arranged in a square. Each site
receives aircraft SSR replies (Modes A, C and S) from which the 3D
position of the aircraft is derived. Using meteorological information
and the Mode C/S height data the altimetry system error is calculated.
The HMUs are operating at the following locations:

a)  Linz in Austria \[centre 48°12'N, 014°18'E\]

```{=html}
<!-- -->
```
a)  Nattenheim in Germany \[centre 49°57'N, 006°28'E\]

b)  Geneva in Switzerland \[centre 46°22'N, 005°56'E\]

[HMU Range.]{.underline} ATS route segments within HMU coverage can be
determined by considering a circle with 45 NM radius around the center
coordinates given above. Up-to-date information can be obtained from the
RMA.

[Level Flight.]{.underline} For a successful measurement by an HMU, it
is required that the aircraft is in level flight for approximately 5
minutes, between FL290 and FL410 (inclusive) within the coverage of the
HMU.

**Monitoring Flight Results and Eurocontrol Database Information.**
Operators may consult the Eurocontrol RVSM Web Site
([www.eur-rvsm.com](http://www.eur-rvsm.com/)) or contact the User
Support Cell (see contact details below) to ascertain that the
information stored about the aircraft is correct and to identify whether
the aircraft have been monitored and acceptable performance has been
demonstrated.

**Contacts.**

Eurocontrol (currently acting as RMA for European RVSM):

> AMN User Support Cell (USC)
>
> Tel +32-2-729-3785
>
> Fax +32-2-729-4634

##  Email <amn.user.support@eurocontrol.int> 

## 

ARINC European Division Programme/Logistics Manager

(European RVSM Programme)

Kevin Harling

Tel: +44 1293 763 342

Mbl: +44 7720 075 208

Fax: +44 1293 763 212

Email: kharling@arinc.com

![](media/image1.wmf){width="7.59375in" height="9.885416666666666in"}
Appendix 5

**[Domestic U.S. AGHME GMS (Aircraft Geometric Height]{.underline}**

**[Measurement Element Ground-based Monitoring System)]{.underline}**

\*For information on AGHME locations and procedures, please access the
AGHME Main Page at:

<http://www.tc.faa.gov/act-500/niaab/rvsm/AGHME_main.asp>

\*On the "AGHME Locations" Webpage, in the "[Flight Plan
Information]{.underline}" column, you can click on "[Location
Overview]{.underline}" and "[Optimal Coverage Area]{.underline}" for
details on location and coverage.