REPORT OF THE ELEVENTH MEETING OF MIDANPIRG RVSM TASK FORCE (MID RVSM TF/11)

Transcription

1 INTERNATIONAL CIVIL AVIATION ORGANIZATION MIDDLE EAST OFFICE REPORT OF THE ELEVENTH MEETING OF MIDANPIRG RVSM TASK FORCE (MID RVSM TF/11) (Cairo, April 2004) The views expressed in this Report should be taken as those of the RVSM Task Force and not the Organization. This Report will, however, be submitted to the MIDANPIRG and any formal action taken will be published in due course as a Supplement to the Report. Approved by the Meeting And published by authority of the Secretary General

2 The designations employed and the presentation of material in this publication do not imply the expression of any opinion whatsoever on the part of ICAO concerning the legal status of any country, territory, city or area or of its authorities, or concerning the delimitation of its frontier or boundaries.

3 TABLE OF CONTENTS Page PART I - HISTORY OF THE MEETING 1. Place and Duration Opening Attendance Officers and Secretariat Language Agenda... 2 PART II - REPORT ON AGENDA ITEMS Report on Agenda Item Appendix 1A Report on Agenda Item Appendix 2A, 2B and 2C Report on Agenda Item Report on Agenda Item Report on Agenda Item Appendix A: Duties and responsibilities of MECMA Appendix B: Financial implications for the establishment and management of an RMA for the MID Region Appendix C: List of participants

4 -1- MID RVSM TF/11 REPORT MID RVSM TF/10 History of the Meeting PART I - HISTORY OF THE MEETING 1. PLACE AND DURATION 1.1 The Eleventh Meeting of MIDANPIRG Reduced Vertical Separation Minimum Task Force (RVSM TF/11), was held at the Conference Room of the ICAO Regional Office, Cairo from April OPENING 2.1 The meeting was opened by Mr. Zerhouni, Regional Director for the ICAO Middle East Office. He congratulated the Chairman of the RVSM Task Force, Mr. Sabri Said Al-Busaidy and the Rapporteurs of the ATC, OPS/AIR and SAM Working Groups, Mr. Mohamed Zainal, Mr. Ibrahim Negm and Mr. Riis Johansen for a job well done and expressed his personal thanks and appreciation and that of MIDANPIRG and the Air Navigation Commission to all those involved in the planning process. He however pointed out that the job will only be completed when RVSM is implemented within Baghdad and Kabul FIRs and requested the Task Force to give some thoughts to the issue Mr. Zerhouni also thanked Eurocontrol, FAA and IATA for their sustained support and assistance that have greatly contributed in the materialization of this challenging project Finally, Mr. Zerhouni paid tribute to the Director General of the UAE GCAA, Mr. Mohammad Al-Ghaith for his vision and involvement and reiterated that, he has been instrumental in paving the way for the safe implementation of RVSM in the region by hosting MECMA and all RVSM Task Force Meetings/Seminars Mr. Zerhouni pointed out the urgent need to set-up a Middle East mechanism for the establishment of the new Regional Monitoring Agency (RMA), on a permanent basis. 2.3 Mr. Sabri Said Al-Busaidy, of Oman, Chairman of the Task Force also welcomed the delegates and thanked all those who have contributed in the planning for the safe implementation of RVSM. 3. ATTENDANCE 3.1 The meeting was attended by a total of 54 participants from 11 States (Bahrain, Egypt, Iraq, Kuwait, Oman, Pakistan, Saudi Arabia, Syria, United Arab Emirates, the United States (FAA and ATC Cell-Qatar and Yemen) and 3 Organizations (AACO, EUROCONTROL, IATA). The list of participants is at Appendix C to the report. 4. OFFICERS AND SECRETARIAT 4.1 The meeting was chaired by Mr. Sabri Said Al-Busaidy of Oman. Mr. Dhiraj Ramdoyal, Regional Officer, Air Traffic Management from the ICAO Middle East Office was Secretary of the meeting supported by Mr. Mohamed Khonji, the Deputy Regional Director. The Regional Director also participated actively during the discussions. 5. LANGUAGE 5.1 The discussions were conducted in English. Documentation was issued in English.

5 MID RVSM TF/11 REPORT -2- MID RVSM TF/11 History of the Meeting 6. AGENDA 6.1 The following Agenda was adopted: Agenda Item 1: Status of Conclusions/Decisions emanating from the MIDANPIRG/8 Meeting concerning implementation of RVSM in the MID Region Agenda Item 2: Safety and Monitoring aspects Agenda Item 3: ATC operations aspects Agenda Item 4 Programme management issues - Interface issues - Implementation of RVSM within the Baghdad and Kabul FIRs. Agenda Item 5: Any other business

6 1-1 MID RVSM TF/11- REPORT MID RVSM TF/11 Report on Agenda Item 1 PART II: REPORT ON AGENDA ITEMS REPORT ON AGENDA ITEM 1: STATUS OF CONCLUSIONS/DECISIONS EMANATING FROM THE MIDANPIRG/8 MEETING CONCERNING IMPLEMENTATION OF RVSM IN THE MID REGION 1.1 Under this agenda item the meeting was appraised of the status of relevant conclusions and decisions endorsed by MIDANPIRG/ 8 relating to the safe implementation of RVSM in the Middle East Region. The meeting was informed of the concerns of the ICAO Air Navigation Commission and the Council regarding the decision by the UAE to stop supporting solely the activities of the Middle East Central Monitoring Agency (MECMA) and other activities related to the implementation/post-implementation of RVSM with effect from 1 June The urgent need for the establishment of a regional mechanism to take over the activities of Middle East Regional Monitoring Agency was highlighted. An update on the status of Conclusions/Decisions is at Appendix 1A to the report on Agenda Item

7 APPENDIX 1A MID RVSM TF/11 Appendix 1A to the Report on Agenda Item 2 Status of Conclusions/Decisions emanating from the MIDANPIR/8 meeting (Cairo 7-11 September 2003) Conclusions/Decisions Status Remarks CONCLUSION 8/12: ESTABLISHMENT OF A REGIONAL SAFETY AND MONITORING AGENCY Pending as from 1 June 2004 Note that as from 1 June 2004, the UAE has indicated that it will stop supporting solely the activities of MECMA That, a) the task of monitoring safety in conjunction with implementation of RVSM in the Middle East Region be assigned to a Central Monitoring Agency; b) the monitoring agency, referred to as the Middle East Central Monitoring Agency (MECMA), will be established and staffed by the United Arab Emirates General Civil Aviation Authority (UAE-GCAA) based at the Head Office in Abu Dhabi; and c) the Terms of Reference of MECMA be amended as indicated at Appendix 6F to the report on Agenda Item 6, to include additional tasks for carrying out safety and airspace monitoring in respect of RNP/RNAV implementation.

8 APPENDIX 1A 1A-2 Status of Conclusions/Decisions emanating from the MIDANPIR/8 meeting (Cairo 7-11 September 2003) Conclusions/Decisions Status Remarks CONCLUSION 8/13: That, IMPLEMENTATION OF THE ATS SAFETY MANAGEMENT PROGRAMMES IN THE MID REGION a) In accordance with the provisions of Annex 11(Chapter 2 paragraph 2.26), States shall implement systematic and appropriate ATS safety management programme with a view to ensure that, i) the established level of safety applicable to the provision of ATS within an airspace or at an aerodrome is met; and ii) safety-related enhancements be implemented whenever necessary; b) with a view to ensure that the activities necessary for the implementation of safety management programmes be carried out in a timely manner, adequate budgetary provisions be made by States; c) sustained cooperation and co-ordination with adjacent States/service providers be made in the process; and On-going activity

9 APPENDIX 1A 1A-3 Status of Conclusions/Decisions emanating from the MIDANPIR/8 meeting (Cairo 7-11 September 2003) Conclusions/Decisions Status Remarks d) States explore ways and means of establishing a mechanism for setting up the standards, monitoring requirements and criteria for the regional implementation of ATS safety management programme and MECMA be invited to play a leading role in the process. Note: Support of UAE will not be expected after 1 June 2004 CONCLUSION 8/16: ATC PROFICIENCY On-going activity That States, with a view to ensure that the level and quality of services are maintained, be invited, through their safety management programme, to evaluate and identify the requirement for ATC refresher courses, including English language training for Air Traffic Controllers DECISION 8/17: AIR-GROUND COMMUNICATIONS PROBLEMS On-going activity That taking into account the number of recurring incidents attributed to poor air-ground communication problems in the region, the matter be addressed within the framework of the CNS/MET Sub-Group. CONCLUSION 8/20: ENDORSEMENT OF GUIDANCE MATERIALS DEVELOPED WITHIN THE FRAMEWORK OF THE RVSM TASK FORCE Actioned That States use the provisions of the ATC, Operations/Airworthiness Manuals and the RVSM Model Safety Plan developed within the framework of the RVSM Task Force for regional application and in the development of their own Manuals/Procedures

10 APPENDIX 1A 1A-4 Status of Conclusions/Decisions emanating from the MIDANPIR/8 meeting (Cairo 7-11 September 2003) Conclusions/Decisions Status Remarks CONCLUSION 8/21: AMENDMENT TO THE MID ATS ROUTE NETWORK On-going activity CONCLUSION 8/22: That, taking into account the fact that the safety assessment for the implementation of RVSM in the MID Region has been built on the existing ATS route structure, States adopt a conservative approach while carrying out major change(s) to the MID ATS route network and it be coordinated with MECMA. That, COORDINATION PROBLEMS OVER THE RED SEA AREA a) with effect from 27 November 2003, the procedures developed at *Appendix 6K to the report on Agenda Item 6, be followed by all uncoordinated flights operating over the Red Sea; b) States concerned publish an AIP Supplement as soon as possible, and no later than 30 October 2003 for the promulgation of these procedures; c) IATA ensures that concerned operators are fully conversant with these procedures; and On-going Need to follow-up on implementation States have raised concerns on flights not following established procedures Saudi Arabia has proposed some minor adjustments

11 APPENDIX 1A 1A-5 Status of Conclusions/Decisions emanating from the MIDANPIR/8 meeting (Cairo 7-11 September 2003) Conclusions/Decisions Status Remarks d) State/military aircraft when flying under Due Regard over the Red Sea be informed of the procedures to be followed by Civil Uncoordinated Flights and be requested to take into account the restrictions applicable within RVSM airspace. On-going Note:* Procedures have been finalized through: - informal meeting(s)/ consultations by Egypt; - two meetings organized by the Arab Civil Aviation Commission (ACAC); - Sustained support from IATA; - RVSM Task Force; and - Willingness of concerned States to find a solution to the problem in the interest of safety

12 APPENDIX 1A 1A-6 Status of Conclusions/Decisions emanating from the MIDANPIR/8 meeting (Cairo 7-11 September 2003) Conclusions/Decisions Status Remarks CONCLUSION 8/23: REGION That, IMPLEMENTATION OF RVSM IN THE MID On-going Having considered the issues listed under items a) through i), below, a reduced vertical separation minimum (RVSM) will be implemented on an exclusive basis between FL 290 and FL 410 on 27 November 2003 at 0200 UTC within the Middle East Region*: a) operator readiness has been assessed through traffic sampling and is found to be sufficient for safe and efficient implementation of RVSM; b) the target level of safety (TLS) for technical risk of 2.5 x 10-9 fatal accidents per aircraft flight hour** has been met through application of an operational concept based on a structure of dual unidirectional RNP trunk routes with application of the semi-circular level allocation system as set out in Annex 2, Appendix 3; c) safety objectives for operational risk are satisfied through evaluation and mitigation measures associated with functional hazard assessments (FHA) carried out in conjunction with development and continued updating of national safety plans (NSP);

13 APPENDIX 1A 1A-7 Status of Conclusions/Decisions emanating from the MIDANPIR/8 meeting (Cairo 7-11 September 2003) Conclusions/Decisions Status Remarks d) A regional monitoring agency, MECMA, has been established, staffed and equipped to perform the required safetyrelated tasks; Support from UAE will cease as from 1 June 2004 e) legal and regulatory measures have been taken by all States; f) guidance material for operations, airworthiness and air traffic management, including training, has been developed and issued; g) States within the MID RVSM Area have committed to complete all outstanding tasks in due time for implementation; h) operators have been given due notice through aeronautical information circulars (AIC) and AIP Supplements; and i) an awareness campaign has been developed and will be undertaken as a joint effort between States, ICAO and IATA. * Except Kabul and Baghdad FIRs. ** The Task Force applied a value of 1.25 x 10-9 as system performance specification to ensure continued satisfaction of TLS at least until the end of the decade, taking into account projected traffic growth.

14 APPENDIX 1A 1A-8 Status of Conclusions/Decisions emanating from the MIDANPIR/8 meeting (Cairo 7-11 September 2003) Conclusions/Decisions Status Remarks CONCLUSION 8/24: DATA FOR SUSTAINED SAFETY ASSURANCE OF RNP AND RVSM WITHIN THE MID REGION On-going Note: Support from UAE will cease as from 1 June 2004 That, considering the on-going requirement for safety assurance related to RVSM and RNP operations within the Middle East Region, a) all States report data and incidents necessary for performing collision risk calculations required for sustained safe RVSM operations to MECMA. The data will include, but not necessarily be limited to: i) assigned altitude deviations of 300 ft or more (monthly); ii) total number of IFR movements (monthly); iii) average time per movement spent in the level band FL290 - FL410; iv) ATC/ATC coordination failures (monthly); and v) traffic data (as requested by MECMA); b) risk associated with operational procedures prevailing within the MID Region.

15 APPENDIX 1A 1A-9 Status of Conclusions/Decisions emanating from the MIDANPIR/8 meeting (Cairo 7-11 September 2003) Conclusions/Decisions Status Remarks c) monitoring States report navigational errors and traffic data in accordance with the Letter of Agreement concerning monitoring associated with RNP; d) air operators maintain procedures for reporting of turbulence; e) States report data on approval of operators and aircraft for RVSM operations (monthly); and MECMA ensures that further processing and evaluation of this data within its Terms of Reference and identifies or develops methodologies for assessing

16 2-1 MID RVSM TF/11 Report on Agenda Item 2 REPORT ON AGENDA ITEM 2: SAFETY AND MONITORING ASPECTS 2.1 Set-up of the Middle East Central Monitoring Agency Under this agenda item the meeting was informed of the decision by the UAE to stop supporting solely the activities of the Middle East Central Monitoring Agency (MECMA) with effect from 1 June The concerns of the Air Navigation Commission and the ICAO Council over followup action(s) which was/were agreed upon for post-implementation monitoring was noted. The ICAO Secretary General has been requested by the Air Navigation Commission to take appropriate action on an early resolution of funding requirements for MECMA The meeting was informed that MIDANPIRG Member States have been approached over the issue and several ways and means are being explored to establish a self-funding mechanism for the MID Region which will take over the responsibilities of MECMA (Ref. AN 6/ dated 11 February See Appendix A to the report). To that effect, the Task Force proposed the following options for consideration by MIDANPIRG Members and the respective DGCA Executives: A) Continuous support from UAE i) The UAE GCAA be requested to continue to maintain the database of State RVSM approvals on behalf of the region, until a regional mechanism has been established; ii) iii) The UAE GCAA be requested to consider the allocation of an Office at the GCAA Headquarters for the future activities of the Regional Monitoring Agency; Until, regional experience is gained, Mr. Riis Johansen, the Director of Air Navigation Services, from GCAA UAE be requested to act as team leader, with the support of RO/ATM Cairo in the new autonomous monitoring agency to be established for the MID Region B) Proposed set-up of MID RMA (OPTION 1) i) The activities of the Middle East Regional Monitoring Agency be carried out on a contractual basis. Funding be ensured through contributions from States and be calculated on the basis of the number of flights handled by each FIR. Amount of contributions for each member State will be revised once every 5 years; ii) ICAO provides Secretariat services to the Agency and all MIDANPIRG Member States act as board members. IATA will contribute as observer to MIDANPIRG; C) Proposed set-up of MID RMA (OPTION 2) i) In case the above mechanism does not materialize, ICAO, with the support of MIDANPIRG Member States, explore the possibility of finding an alternative solution based on assessment to ICAO contribution formula. D) Financial evaluation/implications based on MECMA experience i) The agency will take over all activities related to the implementation/post-implementation of RVSM, RNP, and Safety Management Programmes in the MID Region;

17 2-2 MID RVSM TF/11 Report on Agenda Item 2 ii) An estimate of the overall costs for the operation of the agency is at Appendix B to the report. 2.2 Monitoring requirements System performance monitoring is necessary to ensure that implementation and continued operation of RVSM meets the safety objectives. Monitoring of aircraft height-keeping performance is demanding, particularly as regards estimation of aircraft altimetry system error (ASE). While discussion of height-keeping performance monitoring considers both the technical requirements for a monitoring system and the application of monitoring before and after RVSM implementation in an airspace, the need for obtaining sufficient data on ASE to permit calculation of the vertical overlap probability, Pz(1000), with the required level of confidence was highlighted The meeting recalled that the Middle East RVSM Task Force established the preimplementation monitoring requirements applicable to the MID Region at its 4th meeting in March The requirements were aligned with those applied within the European Region, since calculation of Pz(1000) for the MID Region largely would be based on ASE measurements obtained in the EUR Region but applied to the MID aircraft population (Beta-values) it would be relevant to ensure that data, including type-grouping, was equivalent to that used in EUR. These requirements are summarised below: Monitoring had to take place after airworthiness approval by the State of Registry Monitoring was required for at least two (2) aircraft per group type per operator for operators with previous RVSM experience Monitoring was required for at least three (3) aircraft per group type per operator for operators without previous RVSM experience For the European RVSM area, monitoring requirements were implicitly tied to the airworthiness approval and to a considerable degree based on the large amount of data being generated by the three HMUs European monitoring results, gained through the HMUs, have shown significant variations in height-keeping performance, not only within groups, but also for individual airframes. Furthermore, marginal or inadequate performance has been observed for a number of types or groups of airframes within a given type. This has been the case for Avro RJ, AN72, AN124, E135, E145, FA50 and IL For the most commonly used type in the MID Region, the A320, European results have shown that height-keeping performance was well within the parameters for most operators, while the A320 fleet of one particular operator showed marginal performance. This problem has now been remedied, but would have gone unnoticed, and constituted a latent risk in the airspace system, except for the monitoring programme Given the lack of monitoring assets within the MID Region, it essential that maximum benefit be derived from the knowledge about height-keeping performance gained through monitoring extra-regional monitoring assets and, given the variability mentioned in paragraph 2.2.2, above, MECMA has revised the table in accordance with its terms of reference to take into account the experience gained in other regions. The revised table is in line with the one agreed in the ICAO SASP and included in the (draft) ICAO RMA Handbook, but requires monitoring of all airframes of type groups having displayed marginal performance The objectives for aircraft height-keeping performance stated in Doc 9574 are applicable to both the pre- and post-implementation phases. In general, however, evidence of ASE stability would not normally be expected to be a product of the pre-implementation phase monitoring as this is a longterm consideration.

18 2-3 MID RVSM TF/11 Report on Agenda Item Post-implementation monitoring differs somewhat from the pre-implementation in background as well as objectives. The large amount of monitoring data has conferred an increased knowledge of the height-keeping performance of various aircraft type-groups. To the extent that data indicates consistency, this tends to reduce the need for monitoring. However, while this has led to recategorisation of a number of type-groups, it does not support conclusions about stability over time Also, there is a continued requirement for Initial Monitoring as new operators are formed within the Region or extra-regional operators without RVSM experience wish to commence operations into MID RVSM airspace. Therefore, all new operators that intend to operate in the airspace were RVSM is applied are required to participate in the monitoring programme. Appendix 2A, Table 1, sets out the revised initial monitoring requirement Aircraft condition when subjected to monitoring. For an HMU measurement to be used, the data must meet the following requirements: i. Be positively identified and linked to an individual airframe that has been confirmed by the State Authority as having received RVSM approval. This is achieved by matching the Mode S code record by the measurement system to that notified by the operator. In the case of aircraft not fitted with a Mode S transponder the Mode A code record shall be compared to that noted by the operator on the flight. ii. iii. All engineering/modification and maintenance work required to achieve RVSM airworthiness approval must be completed. The date of the measurement is compared to the date that the operator stated the aircraft had been modified in accordance with the RVSM airworthiness requirements. Only measurements on or after this date are classed as valid. The data has been recorded correctly and passed through quality control checks Additionally, follow-on monitoring is required, partly to ensure that percentage rules continue to be observed for increasing fleets, and partly to provide assurance that height-keeping performance remains within MASPS over time. This is also referred to as ASE stability and on-going monitoring in accordance with Appendix 2A, Table 1 to the report on Agenda Item 2 is required at least once every two years MID and non-mid operators having met the pre-implementation monitoring requirements for EUR, PAC or NAT for given fleet/type of aircraft were accepted as having satisfied the preimplementation monitoring requirements for the MID Region Requirements for initial monitoring for new MID operators or MID operators increasing their fleets are set out in Appendix 2A to the report on Agenda Item Requirements for follow-on monitoring for MID operators are as detailed in Appendix 2A to the report on Agenda Item Documentation for monitoring, i.e. results, shall be provided to the RMA in the format specified in Appendix 2B to the report on Agenda Item 2 for all MID operators / airframes as well as for non-mid operators about whose approval status doubt exist Based on the foregoing, the meeting accordingly adopted the following Draft Conclusion:

19 2-4 MID RVSM TF/11 Report on Agenda Item 2 DRAFT CONCLUSION 11/1- REQUIREMENTS FOR MONITORING That, a) Operators having met the monitoring requirements as tabulated in Appendix2A for a given fleet/type of aircraft will be accepted as having satisfied the requirements for the Middle East Region. In case of Middle East operators, documentation for monitoring shall be provided to the Regional Monitoring Agency. b) For non-mid operators, about whose approval status doubt exist, documentation for monitoring shall be provided to the Regional Monitoring Agency. c) The Regional Monitoring Agency will update the table in the light of data and experience gained in other Regions.. Note: IATA expressed strong objections over the requirements for monitoring to be carried out every two years to ensure ASE stability is satisfactory for sustained RVSM operations. It requested that it be changed to read The need for operators to meet continuing airworthiness requirements associated with RVSM approval in order to remain valid. He reiterated that the MID Region should work within the framework of a global post-implementation strategy. This proposal was not endorsed by the meeting 2.3 Apparent False filings One of MECMA s responsibilities is to provide the means for identifying non-rvsm approved operators using Middle East airspace where RVSM is applied; and notifying the appropriate State approval authority.... This task is given to ensure that application of RVSM within MID RVSM airspace is limited to aircraft and operators actually having been granted the necessary approvals by their State authorities..correspondingly, it should be noted that application of RVSM to an aircraft pair, where either or both aircraft do not hold the required approvals, constitutes a technical loss of separation. Consequently, checking of flight plans with letter W capability indicator in Item 10 against the approvals database is necessary to ensure the integrity of flight plan data upon which Middle East providers of air traffic services base their procedures Since RVSM was implemented on 27 November 2003, MECMA has received only one query concerning approval status of operators. This may be interpreted as being indicative of a faith in the correctness of flight data submitted by operators that unfortunately appears to be unwarranted The first indication that the system was being abused was detected soon after RVSM implementation and MECMA forwarded notification on non-rvsm status to Bahrain, Emirates, Jeddah and Tehran ACCs for Ariana Afghan Airlines (AFG) on 08 December 2003 concurrent with a noncompliance notice to the Afghan CAA. No reply has been received from the Afghan civil aviation authorities In the absence of queries from the States, MECMA has carried out a check of flight plans for flights within the Emirates FIR (OMAE) with the W capability indicator in Item 10 against the RVSM approvals registry. The survey encompasses 67,687 flights, of which 2,161 (3.19%) cannot be confirmed as being RVSM-approved based on the contents of the RVSM registry. This percentage is ten times higher than that obtained through a similar survey in the European Region after the first few months of RVSM operations and casts serious doubts on the safety assurance measures associated with MID RVSM. A list of the flights, for which the actual RVSM status is in doubt, is reproduced in Appendix 2C to the report on Agenda Item 2.

20 2-5 MID RVSM TF/11 Report on Agenda Item Table 1, below: Two explanations are possible: Cognisant RMA Flights Percentage APARMO % EURO % MAAR % MECMA % NAARMO % SATMA % CARSAMMA % Unknown % Approved 65, % Totals 67, % Table 1. Summary of non-approved RVSM flight survey d) The RVSM approvals registry is incomplete, resulting in flights being included in the list, although operator and aircraft actually are approved; or e) Operators are erroneously filing flight plans with the RVSM qualifier W in item Notwithstanding repeated pleas from MECMA, provision of information to the approvals registry has been inadequate. It is, therefore, likely that some of the flights registered as being falsely filed as RVSM capable actually had the required approvals. Table 2 contains the status of approvals for the MECMA-cognisant States according to the RVSM approvals database. State Initial Info Received Update Acft. on Register RVSM Approved Afghanistan No Bahrain 21/05/03 10/03/ Qatar 07/07/02 21/12/ Egypt 23/09/02 30/10/ Iran 18/10/02 12/02/ Iraq No --- Jordan 06/07/02 31/08/ Kuwait 24/07/02 22/02/ Lebanon 27/06/02 11/09/ Libya No --- Oman 13/08/02 23/03/ Saudi Arabia 09/07/03 30/08/ Sudan No --- Syria 25/07/02 29/09/ UAE 15/05/02 31/03/ Yemen 16/06/ Table 2. Summary of approvals

21 2-6 MID RVSM TF/11 Report on Agenda Item It should be noted that 82% of the 2,161 flights being listed as having falsely filed flight plans as being RVSM compliant were operated by agencies registered in States cognizant to other RMAs. However, as MECMA is exchanging data with other RMAs on a regular basis, this type of discrepancies indicate a more widespread problem To ascertain the actual status of operators, MECMA has, within its terms of reference, made enquiries to a number of State authorities. The correspondence is summarised in Table 3, below: Operator State MECMA Query Reply / Observation AFG Afghanistan 08 December 2003 None PIA Pakistan 30 December 2003 Given dispensation by MAAR KQA Kenya 31 December 2003 KCAA has approved B737 aircraft RSO Pakistan 31 December 2003 None BAH Bahrain 05 January 2004 A9CBDF type is RJ85 CPN Iran 05 January 2004 EJO UAE 05 January 2004 Approval mentioned in AOC IRC Iran 05 January 2004 F100 are approved IRK Iran 05 January 2004 T154 are approved IRM Iran 05 January 2004 A30B are approved LAA Libya 07 January 2004 None SUD Sudan 07 January 2004 None CLX Luxemburg 13 January 2004 Operated by approved SOO AGN Gabon 25 January 2004 None DAH Algeria 25 January 2004 None SVK Slovakia 25 January 2004 None CSN China 25 January 2004 None KZR Kazakhstan 25 January 2004 None RNA Nepal 25 January 2004 None THJ Thailand 25 January 2004 HSOGA & HSOGB are approved HMS Bulgaria 25 January 2004 Leased B733 approved for LAZ

22 2-7 MID RVSM TF/11 Report on Agenda Item 2 Operator State MECMA Query Reply / Observation PHG Kyrgyzstan 25 January 2004 None RSO Pakistan 12 April 2004 None SAI Pakistan 12 April 2004 None KQA Kenya 17 April 2004 None PHG Kyrgyzstan 17 April 2004 None RNA Nepal 17 April 2004 None IRA Iran 17 April 2004 None SUD Sudan 17 April 2004 None AZH Azerbaijan 17 April 2004 None SVK Slovakia 18 April 2004 None CSN China 18 April 2004 None IRK Iran 18 April 2004 None ACU Kenya 18 April 2004 None Table 3. Summary of Enquiries The survey of flight planning furthermore revealed a widespread lack of adherence to ICAO standards and procedures, manifested in: late filing of FPL no filing of FPL use of incorrect aircraft type designators incorrect procedures for filing of changes to FPL duplicate filing of FPL incorrect addressing of FPL These deficiencies are hampering ATC units in carrying out their tasks of ensuring that correct separation minima are applied within RVSM airspace. From the information provided in paragraph 2.4, above, it is clear that serious questions exist with regards to the integrity of the basis upon which access to RVSM airspace is granted. As indicated in Table 2, MECMA is in the process of ascertaining the approval status of operators and aircraft. However, the effectiveness of this process hinges on several conditions: To the extent that queries are not resolved with conclusive and positive responses, it is essential that flights by operators, for which doubt exists, be excluded from access to RVSM airspace.

23 2-8 MID RVSM TF/11 Report on Agenda Item The traffic sample of 67,687 flights was obtained from a single FIR (Emirates) and it is probable that other non-conformances exist for flights / operators not navigating within the surveyed airspace. To ensure compliance, traffic samples from all MID RVSM States will be required The Task Force accordingly adopted the following Draft Conclusions: DRAFT CONCLUSION 11/2: - PROVISION OF UP-TO-DATE INFORMATION TO THE MID RVSM APPROVALS REGISTRY. Considering the requirement for a correct and up-to-date registry of RVSM approvals of operators and aircraft in the on-going safety efforts related to RVSM operations within the Middle East Region; that States are reminded to provide regular updates to the regional database of operator and aircraft approvals. DRAFT CONCLUSION 11/3-: - EXCLUSION FROM MID RVSM AIRSPACE OF AIRCRAFT AND OPERATORS NOT REGISTERED AS BEING RVSM APPROVED. Considering the on-going requirement for safety assurance related to RVSM operations within the Middle East Region, That: a) Operators from the attached list, for whom MECMA has not received positive approval data by 15 May 2004, be excluded from MID RVSM airspace with immediate effect until approval status, supported by data from an approved monitoring service provider, has been received; and b) MID RVSM provider States, States of Registry and adjacent RMAs be informed about the exclusion. DRAFT CONCLUSION 11/4-: - REGION-WIDE TRAFFIC SAMPLE AS BASIS FOR FOLLOW-UP AGAINST INCORRECT FLIGHT PLAN FILING That: Considering the need to identify operators who are filing flight plans incorrectly indicating RVSM approval status, traffic samples from all MID RVSM States will be required as the basis for a survey and regulatory action against fraudulent filing of flight plans

24 MID RVSM TF/11 Appendix 2A to the Report on Agenda Item 2 APPENDIX 2A MIDDLE EAST RVSM MINIMUM MONITORING REQUIREMENTS AS OF 01 MAY 2004 Initial Monitoring All operators that operate or intend to operate in airspace where RVSM is applied are required to participate in the RVSM monitoring program. The table of monitoring requirements shown below establishes requirements for initial RVSM monitoring, applicable to operators without previous RVSM status, intending to commence operations in MID RVSM airspace. In their application to the appropriate State authority for RVSM approva l, operators must show a plan for meeting the applicable initial monitoring requirements. Aircraft Status for Monitoring Aircraft engineering work required for the aircraft to receive RVSM airworthiness approval must be completed prior to the aircraft being monitored. Any exception to this rule will be co-ordinated with the State authority. Follow-on Monitoring Monitoring is an on-going program that will be maintained after the initial RVSM approval process. A follow-on sampling program for additional operator aircraft shall ensure continued fulfilment of the percentage rules set out in Table 1. Additionally, monitoring shall be carried out every two years to ensure that ASE stability is satisfactory for sustained RVSM operations. Monitoring of Airframes that are RVSM Compliant on Delivery If an operator adds new RVSM compliant airframes of a type for which it already has RVSM operational approval and has completed monitoring requirements for the type in accordance with the table below, the new airframes are not required to be monitored except as targeted at a later date in the follow-on monitoring program. If an operator adds new RVSM compliant airframes of an aircraft type for which it has NOT previously received RVSM operational approval, then the operator should complete monitoring in accordance with the table below. Applicability of European, North Atlantic and Asia/Pacific Monitoring Monitoring data obtained in conjunction with RVSM monitoring programmes from other regions can be used to meet Middle East monitoring requirements. Update of Monitoring Requirements Table and Website As significant data is obtained, monitoring requirements for specific aircraft types may change. When the table is updated, States and operators will be informed by the Regional Monitoring Agency.

25 2A-2 APPENDIX 2A MONITORING IS REQUIRED IN ACCORDANCE WITH THIS CHART Monitoring prior to the issue of RVSM approval is not a requirement 1 2 Category Group Approved: Data indicates compliance with the RVSM MASPS Group Approved: Insufficient data on approved aircraft Aircraft Type [A30B, A306], [A312 (GE) A313(GE)], [A312 (PW) A313(PW)], A318, [ A319, A320, A321], [A332, A333], [A342, A343], A345, A346 B712, [ B721, B722], B732, [B733, B734, B735], B737(Cargo), [B736, B737/BBJ, B738/BBJ, B739], [B741, B742, B743], B74S, B744 (5 Probe), B744 (10 Probe), B752, B753, [B762, B763], B764, B772, B773 CL60(600/601), CL60(604), C560, [CRJ1, CRJ2], CRJ7, DC10, F100, GLF4, GLF5, LJ60, MD10, MD11, MD80 (All series), MD90, T154 Other group aircraft other than those listed above including: ASTR, B703, B731, BE20,BE40, C500, C25A, C25B, C525, C550**, C56X, C650, C750, CRJ9, [DC86, DC87], DC93, DC95, [E135, E145], F70, [F900, F900EX], FA20, FA10, GLF2(II), GLF(IIB), GLF3, GALX, GLEX, H25B(700), H25B(800), H25C, IL62, IL96, J328, L101, L29(2), L29(731), LJ31, [LJ35,LJ36], LJ45, LJ55, SBR1, T134, T204, P180, PRM1,YK42 Minimum Operator Monitoring For Each Aircraft Group 10% or Two airframes from each fleet* of an operator to be monitored as soon as possible but not later than 6 months after the issue of RVSM approval and thereafter as directed by the RMA * Note. For the purposes of monitoring, aircraft within parenthesis [ ] may be considered as belonging to the same fleet. For example, an operator with six A332 and four A333 aircraft may monitor one A332 and one A333 or two A332 aircraft or two A333 aircraft. 60% of airframes from each fleet of an operator or individual monitoring, as soon as possible but not later than 6 months after the issue of RVSM approval and thereafter as directed by the RMA. ** Refer to aircraft group table for detail on C550 monitoring 3 Non-Group Aircraft types other than those listed under categories 1 and 2, above. Table 1. MID-RVSM Monitoring Requirements 100% of aircraft shall be monitored as soon as possible, but not later than 6 months after the issue of RVSM approval. In order to achieve the operator-monitoring requirement, monitoring results from other regions may be used. An individual aircraft that has demonstrated satisfactory height-keeping performance through monitoring in another region will not require re-monitoring as part of the MID-RVSM monitoring programme.

26 2A-3 APPENDIX 2A Table 2. Pre Applied Monitoring Groups for Aircraft Certified under Group Approval Requirements ICAO Type A/C Type Monitoring Group Designator A124 A124 AN-124 RUSLAN ALL SERIES A300 A306 A30B A300 A300 A310-GE A310 A , 200F,300, 300F A310-PW A310 A , 220F,320 A318 A318 A318 ALL SERIES A319 A319 CJ, 110, 130 A320 A320 A , 210, 230 A321 A , 130, 210, 230 A/C Series 600, 600F, 600R, 620, 620R, 620RF B2-100, B2-200, B4-100, B4-100F, B4-120, B4-200, B4-200F, B4-220, C4-200 A330 A332, A333 A , 220, 240, 300, 320, 340 A340 A342, A343, A , 310 A345 A345 A A346 A346 A A3ST A3ST A R ST BELUGA AN72 AN72 AN-74, AN-72 ALL SERIES ASTR ASTR 1125 ASTRA ALL SERIES ASTR-SPX ASTR ASTR SPX ALL SERIES AVRO RJ1H, RJ70, AVRO RJ70, RJ85, RJ100 RJ85 B712 B712 B B727 B721 B , 100C, 100F,100QF, 200, 200F B722 B732 B732 B , 200C B733 B , 400, 500 B737CL B734 B735 B737NX B736 B737 B738 B739 B737 B737 B737 B , 700BBJ 800, BBJ2 900 B737C B737 B C B747CL B741 B742 B743 B , 100B, 100F, 200B, 200C, 200F, 200SF, 300 B74S B74S B747 SR, SP B744-5 B744 B , 400D, 400F (With 5 inch Probes) B B744 B , 400D, 400F (With 10 inch Probes) B752 B752 B , 200PF B753 B753 B

27 2A-4 APPENDIX 2A Monitoring Group ICAO Type A/C Type A/C Series Designator B767 B762 B , 200EM, 200ER, 200ERM, 300, B ER, 300ERF B764 B764 B ER B772 B772 B , 200ER, 300, 300ER B773 B773 B , 300ER BE40 BE40 BEECHJET 400A ALL SERIES BE20 BE20 BEECH 200 -KINGAIR ALL SERIES C CITATION, ALL SERIES 500 CITATION I, C CITATION I SINGLE PILOT C CITATIONJET, ALL SERIES C CITATIONJET I C525-II C25A 525A CITATIONJET II ALL SERIES C525 CJ3 C25B CITATIONJET III ALL SERIES C C CITATION II ALL SERIES C550-B C CITATION BRAVO ALL SERIES C CITATION II, 551 ALL SERIES C550-II CITATION II SINGLE PILOT C550-SII C550 S550 CITATION ALL SERIES SUPER II C CITATION V, 560 ALL SERIES C560 CITATION V ULTRA, 560 CITATION V ULTRA ENCORE C56X C56X 560 CITATION EXCEL ALL SERIES C CITATION III, 650 ALL SERIES C650 CITATION VI, 650 CITATION VII C750 C CITATION X ALL SERIES CARJ CRJ1, CRJ2 REGIONALJET 100, 200, 200ER, 200LR CRJ-700 CRJ7 REGIONALJET 700 CRJ-900 CRJ9 REGIONALJET 900 CL600 CL60 CL-600 CL-601 CL604 CL60 CL-604 CL-600-2B16 BD100 CL30 CHALLENGER 300 ALL SERIES BD700 GL5T GLOBAL 5000 ALL SERIES CONC CONC CONCORDE ALL SERIES CL-600-1A11 CL-600-2A12, CL-600-2B16 DC10 DC10 DC-10 10, 10F, 15, 30, 30F, 40, 40F DC86-7 DC86, DC87 DC-8 62, 62F, 72, 72F DC93 DC93 DC-9 30, 30F DC95 DC95 DC-9 SERIES 51 E E135, E145 EMB-135, EMB-145 ALL SERIES F100 F100 FOKKER 100 ALL SERIES

28 2A-5 APPENDIX 2A Monitoring Group ICAO Type A/C Type Designator F2TH F2TH FALCON 2000 ALL SERIES F70 F70 FOKKER 70 ALL SERIES F900 F900 FALCON 900, ALL SERIES FALCON 900EX FA10 FA10 FALCON 10 ALL SERIES FA20 FA20 FALCON 20 ALL SERIES FALCON 200 FA50 FA50 FALCON 50, FALCON ALL SERIES 50EX GALX GALX 1126 GALAXY ALL SERIES GLEX GLEX BD-700 GLOBAL ALL SERIES EXPRESS GLF2 GLF2 GULFSTREAM II (G- ALL SERIES 1159), GLF2B GLF2 GULFSTREAM IIB (G- ALL SERIES 1159B) GLF3 GLF3 GULFSTREAM III (G- ALL SERIES 1159A) GLF4 GLF4 GULFSTREAM IV (G- ALL SERIES 1159C) GLF5 GLF5 GULFSTREAM V (G- ALL SERIES 1159D) H25B-700 H25B BAE 125 / HS B A/C Series H25B BAE 125 / HAWKER ALL SERIES/A, B/ XP, BAE 125 / H25B-800 HAWKER 800, BAE 125 / HS125 H25C BAE 125 / HAWKER A, B H25C 1000 IL86 IL86 IL-86 NO SERIES IL96 IL96 IL-96 M, T, 300 J328 J JET ALL SERIES L101 L-1011 TRISTAR 1 (385-1), 40 (385-1), 50 (385-1), 100, 150 L101 ( ), 200, 250 ( ), 500 (385-3) L29B-2 L29B L-1329 JETSTAR 2 ALL SERIES L29B-731 L29B L-1329 JETSTAR 731 ALL SERIES LJ31 LJ31 LEARJET 31 NO SERIES, A LJ35/6 LJ35 LJ36 LEARJET 35 LEARJET 36 NO SERIES, A LJ40 LJ40 LEARJET 40 ALL SERIES LJ45 LJ45 LEARJET 45 ALL SERIES LJ55 LJ55 LEARJET 55 NO SERIES B, C LJ60 LJ60 LEARJET 60 ALL SERIES MD10 MD10 MD-10 ALL SERIES MD11 MD11 MD-11 COMBI, ER, FREIGHTER, PASSENGER MD81, MD-80 81, 82, 83, 87, 88 MD80 MD82,

29 2A-6 APPENDIX 2A Monitoring Group ICAO Type A/C Type Designator MD83, MD87, MD88 MD90 MD90 MD-90 30, 30ER P180 P180 P-180 AVANTI ALL SERIES PRM1 PRM1 PREMIER 1 ALL SERIES T134 T134 TU-134 A, B A/C Series T154 T154 TU-154 A, B, M, S T204, T224, TU-204, TU-224, TU- 100, 100C, 120RR, 200, C T204 T YK42 YK42 YAK-42 ALL SERIES Note: This list is not considered exhaustive

30 MID RVSM TF/11 Appendix 2B to the Report on Agenda Item 2 APPENDIX 2B MINIMUM INFORMATION FOR EACH MONITORED AIRCRAFT TO BE MAINTAINED IN ELECTRONIC FORM BY THE RMA AIRCRAFT HEIGHT-KEEPING PERFORMANCE MONITORING DATA RECORD FORMAT FIELD FIELD IDENTIFIER FIELD DATA TYPE WIDTH RANGE 1 Validity Indicator Alphabetic 1 C : Compliant A : Aberrant N : Non-Compliant 2 Date of Measurement (dd/mm/yyyy) Date 8 e.g. 01/01/ Time of Measurement (hh:mm:ss) Time 8 e.g. 12:00:00 4 Measuring Instrument Alphanumeric 4 e.g. HYQX G123 5 Aircraft Mode A Identity (octal) Alphanumeric 4 6 Aircraft Mode S Address (hexadecimal) Alphanumeric 6 7 Aircraft Registration Number Alphanumeric 10 8 Flight Call Sign Alphanumeric 7 9 Operator Alphabetic 3 10 Aircraft Type Alphanumeric 4 11 Aircraft Mark/Series Alphanumeric 6 12 Flight Origin Alphabetic 4 13 Flight Destination Alphabetic 4 14 Mean Mode C Altitude Numeric During Measurement 1 This field may be Null for GMS 15 Assigned Altitude at Numeric Time of Measurement 1 16 Mean Estimated Geometric Height of Aircraft 17 SD of Estimated Geometric Height of Aircraft 18 Mean Geometric Height of Assigned Altitude Numeric Numeric Numeric Estimated TVE Numeric Minimum Estimated TVE* Numeric Maximum Estimated TVE* Numeric SD of Estimated TVE* Numeric Estimated AAD Numeric Minimum Estimated AAD* Numeric Maximum Estimated AAD* Numeric SD of Estimated AAD* Numeric Estimated ASE Numeric Minimum Estimated ASE* Numeric Maximum Estimated ASE* Numeric SD of Estimated ASE* Numeric Indicator for Reliability of Geometric Height Numeric 3 HMU: Measurement GMU: Indicator of Reliability of Met Data Numeric Aircraft Serial/Construction Number Alphanumeric 12 e.g * only when more than one data point is available

31 MID RVSM TF/11-Report Appendix 2C 2C-1 MID RVSM TF/11 Appendix 2C to the Report on Agenda Item 2 Ident Type Flights Operator Country Cat. RMA Action RSO B AERO ASIA PAKISTAN OPR MAAR Yes RSO DC AERO ASIA PAKISTAN OPR MAAR Yes MD P3 130 USAF USA MIL NAARMO KQA B KENYA AIRWAYS KENYA OPR EURO Yes IRA A IRAN AIR IRAN OPR MECMA Yes SAI T SHAHEEN AIR INT'L PAKISTAN OPR MAAR Yes OMA AT45 59 OMAN AIR OMAN OPR MECMA PHG B PHOENIX AVIATION KYRGYSTAN OPR EURO Yes RNA B ROYAL NEPAL AIRLINES NEPAL OPR MAAR Yes SVK B AIR SLOVAKIA SLOVAKIA OPR EURO Yes RCH B USAF USA MIL NAARMO AZH IL76 35 SKY WIND AZERBAIJAN OPR EURO Yes CSN B CHINA SOUTHERN CHINA OPR MAAR Yes SUD B SUDAN AIRWAYS SUDAN OPR MECMA Yes SUD A SUDAN AIRWAYS SUDAN OPR MECMA Yes LYN T ALTYN AIR KYRGYSTAN OPR EURO DHX SW4 21 DHL INT'L BAHRAIN OPR MECMA RRR L ASCOT UK MIL EURO ETH DC86 20 ETHIOPIAN AIRLINES ETHIOPIA OPR EURO KZK T AIR KAZAKHSTAN KAZAKHSTAN OPR EURO SUD A30B 20 SUDAN AIRWAYS SUDAN OPR MECMA Yes THA A THAI INTERNATIONAL THAILAND OPR MAAR RRR VC10 17 ASCOT UK MIL EURO KACN135 E MIL FC B FALCON CARGO OPR DAO B DAALLO AIRLINES DJIBOUTI OPR EURO PGP T PERM STATE AIR RUSSIAN FED. OPR EURO IRM T MAHAN AIR IRAN OPR MECMA RCH B USAF USA MIL NAARMO A6OME GLF4 12 HITECH FZE UAE PVT MECMA DHX A30B 12 DHL INT'L BAHRAIN OPR MECMA JAF B JETALLIANCE AUSTRIA OPR EURO LAA A LIBYAN ARAB AIRLINE LIBYA OPR MECMA LTC A LATCHARTER LATVIA OPR EURO HXL B OPR ACE B RACE CARGO GHANA OPR EURO BRZ T SAMARA RUSSIAN FED. OPR EURO CGK IL76 10 CLICK AIRWAYS KYRGYSTAN OPR EURO GMA B GAMA AVIATION UK OPR EURO AAS B732 9 ASKARI AVIATION PAKISTAN OPR MAAR FLM B738 9 FLY AIR TURKEY OPR EURO LIMO34 H25B 9 MIL RRR C17 9 ASCOT UK MIL EURO

32 MID RVSM TF/11-Report Appendix 2C 2C-2 ADH A30B 8 AIR ONE ITALY OPR EURO RCH B772 8 USAF USA MIL NAARMO TUA B733 8 TURKMENISTAN AIRLINES TURKMENISTAN OPR EURO GGO B732 7 AVIAL GEORGIA OPR EURO KGL T154 7 AIRCOMPANY KOGALYMAVIA RUSSIAN FED. OPR EURO PIA B772 7 PAKISTAN INT'L PAKISTAN OPR MAAR TAK T154 7 OPR TXC IL76 7 TRANSAVIAEXPORT BELARUS OPR EURO AAS B742 6 ASKARI AVIATION PAKISTAN OPR MAAR AEW A320 6 AEROSVIT AIRLINES UKRAINE OPR EURO AFG A30B 6 ARIANA AFGHAN AFGHANISTAN OPR MECMA AXK DC93 6 AFRICAN EXPRESS KENYA OPR EURO BRQ IL76 6 EL-BURAQ AIR TRANSPORT LIBYA OPR MECMA BTC T154 6 BASHKIRIAN AIRLINES RUSSIAN FED. OPR EURO CTM A310 6 FRENCH A/F FRANCE MIL EURO DMO IL62 6 DOMODEDOVO AIRLINES RUSSIAN FED. OPR EURO EEZ B763 6 EUROFLY ITALY OPR EURO IRC AT72 6 IRAN ASSEMAN AIRLINES IRAN OPR MECMA ISD T134 6 ISD AVIA UKRAINE OPR EURO RCH MD11 6 USAF USA MIL NAARMO DHX CVLT 5 DHL INT'L BAHRAIN OPR MECMA DJB B733 5 DJIBOUTI AIRLINES DJIBOUTI OPR EURO JAV A320 5 JORDANIAN AVIATION JORDAN OPR MECMA KIW B752 5 ROYAL NEW ZEALAND A/F NEW ZEALAND MIL APARMO MCC IL76 5 AEROCOM MOLDOVA OPR EURO OST YK42 5 AIRLINE ALANIA RUSSIAN FED. OPR EURO VTDHA GLEX 5 INDIA PVT AYZ IL76 4 ATLANT - SOYUZ RUSSIAN FED. OPR EURO CFC C130 4 CANADIAN A/F CANADA MIL NAARMO D3701 AN12 4 PVT DHX A310 4 DHL INT'L BAHRAIN OPR MECMA HZ103 GLF4 4 ROYAL SAUDI A/F SAUDI ARABIA MIL MECMA IAX L101 4 INT'L AIR SERVICES LIBERIA OPR EURO IRK B734 4 KISH AIR IRAN OPR MECMA Yes JOL T154 4 ATYRAU AUE JOLY KAZAKHSTAN OPR EURO KAZ T154 4 OPR KRT IL62 4 KOKSHETAU AIRLINE KAZAKHSTAN OPR EURO N215CX C750 4 Balmoral Air Pty., Ltd. USA PVT NAARMO N222CX C750 4 USA PVT NAARMO N351BA CRJ2 4 BOMBARDIER AEROSPACE CORPUSA PVT NAARMO N40HB GLF4 4 USA PVT NAARMO PHOLI F900 4 NETHERLANDS PVT EURO RBA B752 4 ROYAL BRUNEI BRUNEI OPR APARMO S6758 B737 4 USAF USA PVT NAARMO S7125 B737 4 USAF USA PVT NAARMO SUD B722 4 SUDAN AIRWAYS SUDAN OPR MECMA Yes

33 MID RVSM TF/11-Report Appendix 2C 2C-3 SVK B738 4 AIR SLOVAKIA SLOVAKIA OPR EURO TCNOA L29B 4 TURKEY PVT EURO TCW B753 4 THOMAS COOK BELGIUM BELGIUM OPR EURO IRK F50 3 KISH AIR IRAN OPR MECMA Yes ADH L101 3 AIR ONE ITALY OPR EURO AFG B742 3 ARIANA AFGHAN AFGHANISTAN OPR MECMA AIA LJ60 3 AVIES ESTONIA OPR EURO ALK B744 3 SRI LANKAN SRI LANKA OPR MAAR BGH A320 3 BH AIR BULGARIA OPR EURO BULG003 T154 3 PVT CGZPX CL60 3 CANADA PVT NAARMO CNK F900 3 SUNWEST HOME AVIATION CANADA OPR NAARMO CTM A319 3 FRENCH A/F FRANCE MIL EURO D3179A AN12 3 PVT DHX B722 3 DHL INT'L BAHRAIN OPR MECMA FLM B734 3 FLY AIR TURKEY OPR EURO FYG C56X 3 FLYING SERVICE BELGIUM OPR EURO HXL B763 3 OPR P4JLI B722 3 ARUBA PVT EURO PLF T154 3 POLISH A/F POLAND MIL EURO RMAF136 GLF3 3 MIL STH AN12 3 SOUTH-AIRLINES ARMENIA OPR EURO UAF C130 3 EMIRATES A/F UAE MIL MECMA VPBFF GLF2 3 SHUKRA LTD BERMUDA PVT AAP B732 2 AEROVISTA AIRLINES KYRGYSTAN OPR EURO ACI A320 2 AIR CALEDONIE INT'L FRANCE OPR EURO AMV A320 2 ACFT MAINTENANCE CO. EGYPT OPR MECMA ASY P3 2 ROYAL AUSTRALIAN A/F AUSTRALIA MIL APARMO AWZ IL76 2 AIRWEST SUDAN OPR MECMA AYZ T154 2 ATLANT - SOYUZ RUSSIAN FED. OPR EURO AZA B743 2 ALITALIA ITALY OPR EURO AZV IL76 2 ASOV-AVIA AIRCOMPANY UKRAINE OPR EURO AZZ IL76 2 AZZA TRANSPORT SUDAN OPR MECMA BAH B461 2 BAHRAIN AMIRI FLIGHT BAHRAIN PVT MECMA BEC B762 2 STATE AIRCOMPANY BERKUT KAZAKHSTAN OPR EURO BIS IL18 2 IRBIS KAZAKHSTAN OPR EURO BRP T154 2 AIRPORT BRATSK RUSSIAN FED. OPR EURO CAX DC86 2 CENTRAL AIR EXPRESS CONGO OPR EURO CGRFO LJ35 2 CANADA PVT NAARMO DAH A321 2 ALGERIAN AIRLINES ALGERIA OPR EURO EDW B763 2 EDELWEISS AIR USA OPR NAARMO ESK B735 2 SKYEUROPE AIRLINES SLOVAKIA OPR EURO ETH C130 2 ETHIOPIAN AIRLINES ETHIOPIA OPR EURO GMA H25B 2 GAMA AVIATION UK OPR EURO HL7576 GLEX 2 KOREA PVT APARMO