Asia/Pacific GPS-based Monitoring System (GMS) Monitoring Procedures

Monitoring is required for all operators of aircraft that have received
RVSM operational approval. Current monitoring goals should be reviewed
for actual requirements; generally 2 or 3 aircraft of each type must be
monitored. Monitoring requirements as well as other RVSM information can
be found at the following web sites:

FAA RVSM

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

Asia-Pacific Approvals Registry and Monitoring Organization (APARMO)

-   <http://www.tc.faa.gov/act-500/niaab/rvsm/aparmo_intro.html>

Airworthiness Approval

In-production or new production aircraft attain airworthiness approval
through verification of RVSM eligibility in the Airplane Flight Manual
or Type Certificate Data Sheet. In-service aircraft attain airworthiness
approval through the application of the type-specific RVSM Service
Bulletin. The aircraft engineering requirements vary for individual
types or groups of aircraft. These requirements may include upgrades to
the air data computers, pitot-static modifications, skin waviness
testing, and visual or paint inspections. After airworthiness approval
is obtained, the operational approval process is completed by
incorporation of RVSM policy and procedures into the training program,
manuals, and maintenance program. **Monitoring may be conducted after
airworthiness approval information has been sent to the APARMO. Only
airworthiness approved aircraft will be monitored.**

APARMO

The APARMO is responsible for all monitoring activity and the operation
of the GMS. CSSI Inc., the GMS support contractor, will assist the
APARMO with the monitoring program.

GMS Description

The GMS is comprised of the equipment and procedures to collect and
process three required data elements: GPS data, pressure altitude or
Mode C data, and meteorological data. The GPS-based Monitoring Unit
(GMU) is used to collect the GPS data during the monitoring flight. The
APARMO, through the use of the attached Flight Information Form (FIF),
will coordinate with the operator the collection of pressure altitude or
Mode C data from ATC facilities. The operator will provide pressure
altitude data from the digital flight data recorder (DFDR) of the
aircraft being monitored. Late transmittal of the FIF and illegible or
blank entries will delay processing and the dissemination of results.
Meteorological data will be obtained by the APARMO without operator
involvement.

Monitoring Flights

Monitoring flights do not need to be conducted in Pacific Airspace.
Monitoring can be conducted on scheduled flights, ferry flights, or
monitoring-specific flights. To ensure collection of sufficient position
data, the flight must be straight and level at any altitude from FL290
to FL410, and should be at least thirty minutes in duration. Monitoring
should also be conducted in areas where Mode-C radar data can be
retrieved in a timely manner. In addition to Mode-C collected by the
APARMO, the operator should provide pressure altitude data from the
Digital Flight Data Recorder (DFDR) to the APARMO for Altimetry System
Error (ASE) calculation.

GMU Description

The GMU is a portable unit comprised of a Global Positioning System
(GPS) receiver, two GPS antennas, temporarily mounted on interior
windows, and a laptop computer. The unit requires plug in power from the
aircraft (draws 2.0 to 4.0 amperes maximum) and accepts multiple types
of power standard to 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 Monitoring Specialist
typically occupies a jump seat to monitor GMU performance. GMU
installation is transparent crew operations.

Monitoring Process

Upon receiving airworthiness approval, the operator should contact the
APARMO GMS Operations Coordinator to discuss monitoring options. To
start the monitoring process the operator should submit the attached
Monitoring Application to the APARMO. The Monitoring Application should
include all aircraft that will be operated in the Pacific Region. The
collection of GPS data with the GMU can be accomplished by a GMS
Monitoring Specialist or by an operator representative that has received
GMU training. The operator and the APARMO GMS Operations Coordinator
will develop a mutually agreed upon plan for monitoring.

The operator will take the necessary steps to retrieve pressure altitude
data from the digital flight data recorder (DFDR). The DFDR data should
be sent to the APARMO as an electronic file. The specific format of the
electronic file and the APARMO DFDR point of contact is contained in the
following section.

To conduct the monitoring flight, the Monitoring Specialist or operator
representative that has received GMS training, will perform the
following tasks:

-   Submit preflight FIF to APARMO and GMS Support Contractor

-   Operate GMU

-   Submit post-flight FIF to APARMO and GMS Support Contractor

-   Submit GPS data files to GMS Support Contractor

![](media/image1.wmf)The Monitoring process from the operator's
perspective is illustrated in Figure 1. The operator will be notified by
a facsimile memo as the FIF, GPS data file, and pressure altitude data
file move through the post-flight processing steps at the APARMO.

Digital Flight Data Recorder Data

Digital Flight Data Recorder (DFDR) data should contain altitude (ALT)
expressed in feet with corresponding time (UTC) expressed in hours,
minutes, and seconds HH/MM/SS to two decimal places and the aircraft
transponder code (TXP). Altitude data submitted to the APARMO should
have reports with 12-second or better intervals.

Providing aircraft position data for each level of flight further aids
the APARMO in ASE calculation. Position data can be provided in
latitude/longitude or range/azimuth (x/y) formats. A reference point is
helpful when providing position data in the range/azimuth (x/y) format.
Please provide the units of measurement for each piece of position data
submitted to the APARMO.

DFDR Data Samples:

Range/Azimuth (X/Y) Data

TXP X Y ALT HH/MM/SS

5113 -284.969 197.938 36900 13/23/21.00

Latitude/Longitude Data

TXP LAT LON ALT HH/MM/SS

2241 54.833 4.494E 28000 17/57/42.00

2241 54.826 4.489E 28000 17/57/47.00

Sending DFDR data to the APARMO as an ASCII or text file via e-mail is
recommended.

APARMO DFDR Point of Contact:

Phone: 1+609-485-5102

Fax: 1+609-485-5117

E-mail: <Anthony.Strazzeri@tc.faa.gov>

If e-mail is not available, the operator should send DFDR files on
PC-formatted 3.5" diskettes to:

Anthony Strazzeri

FAA William J. Hughes Technical Center

ACT-520

Atlantic City Airport, NJ 08405

# 

# 

# Monitoring Post-Flight Information

After completion of the monitoring flight, the GPS data will be
processed by the GMS Contractor and forwarded to the APARMO. The
operator will be advised by fax of the processing status of the data
file. For the computation of the ASE, Meteorological data and Mode C
data will be collected and merged with the GPS data at the APARMO. Final
ASE results should be available from the APARMO within three weeks of
the flight. The results will be sent to the State CAA and posted on the
APARMO web site.

APARMO GMS Contacts:

APARMO Activities Coordinator

Phone: 1+609-485-5678

Fax: 1+609-485-5078

Email: aparmo@tc.faa.gov

CSSI Inc., APARMO GMS Operations Coordinator:

Phone: 1+202-863-7426

Fax: 1+202-863-2398

Email: monitor@cssiinc.com

**. REDUCED VERTICAL SEPARATION MINIMUM (RVSM)**

## MONITORING APPLICATION

**(Return completed form by fax to 1+609-485-5078 and 1+202-863-2398)**

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

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

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

**Operator Primary Point of Contact**

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

Telephone Number:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_Fax
Number: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_Email
Address:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Secondary Point of Contact**

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

Telephone Number:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_Fax
Number: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_Email
Address:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Civil Aviation Authority Contact**

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

Telephone Number:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_Fax
Number: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_Email
Address:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

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

**AIRCRAFT INFORMATION**

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

  -------------------------------- ----------------- --------------------
  Aircraft Model                   Registration      Serial Number
                                   Number            

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

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

Flight Information Form (FIF)

Please Fax to the APARMO at 1+609 485 5078 and 1+202-863-2398,

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>