Annex C: Height-Monitoring Performance Monitoring
C-1. General. This annex identifies the aircraft height monitoring requirements, procedures and points of contact for RVSM monitoring.
C-2. Height keeping performance monitoring of aircraft is necessary to ensure continued safe operations in RVSM airspace. RVSM is a "performance-based" operation requiring ongoing independent monitoring to ensure that the aircraft population adheres to stringent altimetry system requirements.
C-3. In addition to the continued airworthiness requirements described in advisory paragraph 4.3.1, aircraft are to be checked in flight as per the requirements of paragraph C-4.
C-4. Requirements. The OAA is to ensure that DND/CAF RVSM aircraft are monitored for their height keeping performance. The DTAES RVSM Registration Coordinator may periodically sample the NAARMO RVSM monitoring reports to confirm that the monitoring requirements are being met. The requirements are the following:
- Initial height monitoring must follow within six months of initial RVSM TAC and OAC;
- Recurrent height monitoring must follow at least once every two years, or within intervals of 1,000 flight hours per aircraft, whichever period is longer; and
- The minimum number of airframes specified in the following table need to be monitored based on monitoring group and category, as per advisory reference 3.2.h:
Monitoring Group | Minimum Monitoring Requirement Category | Minimum Number of Airframes Monitored |
---|---|---|
C130 | Military, Category 1 | 2 |
CL604 | Civilian, Category 1 | 2 |
CL605 | Civilian, Category 1 | 2 |
A310-M | Military, Category 3 | 100% |
C17 | Military, Category 1 | 2 |
BE30 | Civilian, Category 2 | 60% rounded up to the nearest integer |
A330-M | Military, Category 3 | 100% |
C-5. GPH 204A Procedure. The DND/CAF RVSM monitoring procedures are published in GPH204A (advisory reference 3.2.g), Article 432, paragraph 9.
C-6. ADS-B Monitoring Procedures. Upon request, aircraft equipped with qualified ADS-B out systems will be height-monitored during normal operations, at RVSM altitudes in airspace where sufficient ADS-B data is available to the FAA to determine RVSM performance. The following requirements for monitoring must be met:
- The aircraft must be equipped with a qualified ADS-B OUT System (v2);
- The Flight ID/Call Sign transmitted by ADS-B must match the Flight ID/Call Sign specified in the flight plan; and
- The operation must include at least 15 minutes of level flight at an RVSM flight level (FL290-FL410)
Notes:
1. United States: Aircraft equipped with qualified ADS-B out systems are height-monitored EACH DAY during normal operations in US ADS-B rule airspace at RVSM altitudes. Aircraft that are due for periodic monitoring or that must verify performance can fly any day to obtain a monitoring result. For assistance validating ADS-B, request an ADS-B Performance Report.
2. Canada: Aircraft equipped with qualified ADS-B out systems are height-monitored on MONDAYS (UTC) during normal operations in Canadian ADS-B rule airspace at RVSM altitudes. Aircraft that are due for periodic monitoring or that must verify performance can fly any Monday in Canadian airspace to obtain a monitoring result. For assistance validating ADS-B, request an ADS-B Performance Report.
3. A period of four to six weeks must be allowed for complete processing.
4. Most RVSM monitoring is accomplished using the aircraft’s Mode S address, which is then translated to a registration number and associated with the records contained in the RVSM Registry that is maintained by the NAARMO.
C-7. AGHME Monitoring Procedures. For aircraft not eligible for ADS-B Out monitoring, AGHME is an alternative. This ground-based system uses fixed location to automatically produce estimates of the geometric height of suitably equipped aircraft flying within the coverage area of an AGHME constellation. Overflight of ground-based height monitoring systems is transparent to the pilot. The following procedures should be used to maximize the chance of successful monitoring by an AGHME constellation:
- Ensure that the aircraft is in RVSM-approved configuration.
- Ensure that the aircraft has serviceable Mode S transponder. Without Mode S, there will be no measurement.
- Obtain acceptance of a RVSM monitoring plan from the SSO OA.
- Confirm with the DTAES RVSM Registration Coordinator that the aircraft is properly listed on the register (e.g., aircraft type, serial number, Mode S code, etc.).
- Choose an AGHME location for monitoring (see AGHME Locations for choices and to verify operational status).
- Plan flight on a route through the centre of the AGHME coverage area between FL290 and FL410.
- Ensure that the flight plan provides for straight and level flight operation through the AGHME coverage area.
- There are no special monitoring routings; therefore, do not ask ATC for any special treatment to accommodate AGHME measurement, as it is not an ATC responsibility.
C-8. The systems are continuously recording data. Prior coordination is not required to conduct a monitoring flight.
C-9. RVSM Approvals and Monitoring Status Results. Online reports for DND/CAF aircraft are available on the NAARMO website. A sample extract of the July 2019 NAARMO monitoring report for the DND and the CAF aircraft is provided in Figure C-1.
C-10. Height Monitoring Results. Confirmation of successful monitoring is stored in the abridged version of the NAARMO RVSM Approvals database. Monitoring status results will not be distributed. OAA, TAA, WSM and Operational staff may refer to this database for confirmation of a successful monitoring flight. If an aircraft does not appear in the approvals database, then this is an indication that the RVSM approval information for this aircraft is not complete, it is not an indication of an unsuccessful monitoring flight.
C-11. Non-Compliant Monitoring Report. If the TCCA RVSM Coordinator (Annex B, paragraph B-8) receives a notification from NAARMO that a DND/CAF aircraft was monitored and found non-compliant, the TCCA RVSM Coordinator has been instructed to send the notification to the following DND addressees:
- For action: SSO OA
- For information: DTAES RVSM Registration Coordinator (See Annex B, Paragraph B-6)
C-12. Upon receipt of a non-compliant report, the SSO OA point of contact for RVSM is responsible for taking the following actions:
- The affected aircraft is to be restricted from RVSM operations.
- The Wing is to be instructed to take actions that they deem appropriate to investigate all possible causes and correct the conditions causing the failure.
- A successful monitoring flight must be flown on the affected aircraft to remove the RVSM restriction.
- The DTAES RVSM Registration Coordinator must be notified when the non-compliance has been resolved.
Figure C-1 Sample Extract of the NAARMO approvals and monitoring status report for Canada, the Canadian Armed Forces Aircraft Section dated December 22th 2023
- The examples below illustrate the status of some of the DND/CAF flights recorded in the NAARMO Operators with RVSM Approval Reported by Canada database on 22 December 2023. The data are not relevant, each login will reflect a different set. The table is provided only as a snapshot of the type of information that NAARMO uses in its monitoring reporting.
- AGHME Monitoring Flights were recorded on 11/7/2023 (excluding 1/13-1/31/22; 8/6-8/7/20, 8/11-8/14/20; 7/6/15, 3/19/15-3/31/15); YOW 3/6/2022; YQL 3/20/21 (excluding 8/4-8/5/20; operational 7/16/20-8/1/20; operational 6/13/20-6/26/20, operational 5/20-5/26/20 excluding 7/6/15).
- All ADS-B Monitoring Flights were recorded 11/30/2023; Mondays Only up to 1/30/2023 (excluding 12/10/20 and 12/11/20; 04/05/21; 2/1/23 to 2/3/2023; 2/12/2023 to 2/14/2023; 2/16/23 to 2/28/23).
- For FULL RVSM: FALSE means missing LOA/MSpec/OpSpec.
Operator Name | Registration | ICAO Type | Series | Serial Number | FULL RVSM | ADS-B | AGHME | GMS | Other RM |
---|---|---|---|---|---|---|---|---|---|
Canadian Armed Forces | CC15003 | A310 | 304 | 425 | TRUE | 2023-07-21 | 2023-07-03 | nil | 2019-03-17 |
Canadian Armed Forces | CC15005 | A310 | 304 | 441 | TRUE | 2023-11-29 | 2023-05-19 | nil | 2014-01-06 |
Canadian Armed Forces | CC15004 | A310 | 304 | 444 | TRUE | 2023-10-20 | 2023-08-27 | nil | nil |
Canadian Armed Forces | CC15001 | A310 | 304 | 446 | TRUE | 2023-11-25 | 2023-02-06 | nil | 2019-09-30 |
Canadian Armed Forces | CC15002 | A310 | 304 | 482 | TRUE | 2023-11-30 | 2023-08-30 | nil | 2018-07-13 |
Canadian Armed Forces | CC330002 | A332 | 243 | 1653 | TRUE | 2023-11-30 | nil | nil | nil |
Canadian Armed Forces | CGPDC | B350 | B300 | FL-114 | TRUE | 2023-11-03 | 2023-03-19 | 2006-09-05 | nil |
Canadian Armed Forces | CGSYC | B350 | B300 | FL-20 | TRUE | 2023-11-16 | 2022-12-09 | nil | nil |
Canadian Armed Forces | CC177705 | C17 | GLOBEMAS | CA-5 | TRUE | 2023-11-05 | 2023-07-19 | nil | 2017-02-18 |
Canadian Armed Forces | CC177701 | C17 | GLOBEMAS | CA-1 | TRUE | 2023-11-29 | 2022-09-15 | nil | nil |
Canadian Armed Forces | CC177702 | C17 | GLOBEMAS | CA-2 | TRUE | 2023-11-24 | 2023-01-31 | nil | nil |
Canadian Armed Forces | CC177703 | C17 | GLOBEMAS | CA-3 | TRUE | 2023-11-30 | 2020-09-25 | nil | 2014-05-21 |
Canadian Armed Forces | CC177704 | C17 | GLOBEMAS | CA-4 | TRUE | 2023-11-02 | 2022-01-05 | nil | 2013-12-09 |
Page details
- Date modified: