1 / 16

RNP 4 in Oceanic and Remote Continental Area

RNP 4 in Oceanic and Remote Continental Area. H. LESPINASSE - DGAC/DCS Koln, CNS/ATM Steering Group 20-21 June 2006. Overview. Environmental context Oceanic and remote regions Trials and implementations Existing guideline material Operational requirements

summer-barr
Download Presentation

RNP 4 in Oceanic and Remote Continental Area

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RNP 4 in Oceanic and Remote Continental Area H. LESPINASSE - DGAC/DCS Koln, CNS/ATM Steering Group 20-21 June 2006

  2. Overview • Environmental context • Oceanic and remote regions • Trials and implementations • Existing guideline material • Operational requirements • Draft guidance for RNP 4 operational approval • Surveillance/Communication considerations • RNP 4 operational approval requests • Conclusion Required Navigation Performance 4

  3. Status on previous activities • Presentation during Oct CNS ATM meeting • Position paper presented to OST (20-22 November 2006) • OST meeting 06-5: OST decided to task CNS/ATM SG to develop further guidance material and/or to propose an amendment to JAR-OPS if it is considered necessary. • Reword the position paper into an information paper Required Navigation Performance 4

  4. Oceanic and remote regions • Ground based navigation aids do not exist except possibly at isolated locations • Oceanic and remote regions of the world are restructured to provide capacity and operating benefits. • Reduced route spacing : RNP 4 supports the application of 30Nm lateral 30Nm longitudinal distanced-based separation minima Required Navigation Performance 4

  5. Trials and implementations • Auckland Oceanic, Brisbane, Honiara, Melbourne, Naha, New Zealand, Port Moresby, Tokyo FIRs Routes or Oceanic control areas 30Nm lateral and longitudinal separation (doc 7030/4 Mid/Asia/RAC-10 7.1.6). • RNP 4 applications in Tasman sea as described in doc 7030/4 • AIP Fidji Islands ENR 1.8–6 • AIP New Zealand ENR 1.8-3 • South China Sea Airspace (due to traffic growth on one pair of parallel routes causing delays) Required Navigation Performance 4

  6. Trials and implementations • Operational Trial of 30-NM Lateral and Longitudinal Separation Standards in the Oakland Air Route Traffic Control Centre (ARTCC) oceanic sector 3 (OC3), which spans the airspace roughly between California and Australia/New Zealand/Fidji/Tahiti began 22 December 2005 (Notam ooperational Policy/Procedures For Operational Trial of Thirty Nautical Mile (nm) Lateral and 30nm Longitudinal Separation in Oakland Oceanic Sector 3). Required Navigation Performance 4

  7. Existing guideline material • ICAO state letter ref. N 13/33.7-04/86 "Guidance for a Required Navigation Performance (RNP-4) Operational Approval Process for Initial Application in Oceanic or Remote Airspace” planned to cover introduction of RNP4 in Pacific pending official release. • FAA order 8400.33 dated 9/15/05, CAA N-Z AC 91-10 • Final Draft Performance Based Navigation manual developed by RNPSORSG ICAO group as an evolution and replacement of doc 9613. Required Navigation Performance 4

  8. Operational requirements • Annex 6 • State Letter ref. N 13/33.7-04/86 • ICAO Supplementary Regional Procedures doc 7030 Mid/Asia/Rac-10 • JAR-OPS 1.243 – Operations in areas with specified navigation performance requirements Required Navigation Performance 4

  9. Draft guidance for RNP 4 operational approval • Based on RNP 4 Nav. Spec. (Draft PBN manual) • Aircraft eligibility groups (airworthiness) • Navigation equipment : 2 fully serviceable independent LRNS. GNSS must be used either as stand alone or sensor to a multi-sensors system Required Navigation Performance 4

  10. Draft guidance for RNP 4 operational approval • Based on RNP 4 Nav. Spec. (Draft PBN manual) • System performance, monitoring and alerting • Navigation accuracy: cross track TSE < 4Nm and along track NSE < 4Nm for 95% flight time • Integrity: malfunction of the a/c nav. Equipment classified Major • Continuity: loss of the function is Major for oceanic and remote navigation • Performances monitoring and Alerting: alert (system or pilot+system) if accuracy requirement is not met or if the P(TSE > 8NM) > 10-5 Required Navigation Performance 4

  11. Draft guidance for RNP 4 operational approval • Based on RNP 4 Nav. Spec. (Draft PBN manual) • System performance, monitoring and alerting • Signal-In-Space: with GNSS, alert if P(lateral position error > 8NM) > 10-7. RAIM and FDE functions required except in case of Aircraft Autonomous Integrity Monitoring (AAIM) with the use of inertial navigation systems. Required Navigation Performance 4

  12. Draft guidance for RNP 4 operational approval • Based on RNP 4 Nav. Spec. (Draft PBN manual) • Maximum FDE outage time : 25 minutes - only applicable to stand alone GNSS and multi-sensor integrating GNSS w/o INS sensors inputs. • Required functionalities • Display of navigation, TF, DF, Direct to, CF, ... • WGS84 geodetic reference system Required Navigation Performance 4

  13. Draft guidance for RNP 4 operational approval • Operational requirements • Flight plan designation • Pre-Flight procedures • Operating procedures • Pilot knowledge and training • Navigation Database Management (LOA type 2) • Flight Operation Documentation (MEL, Operations Manuals and Check-List) Required Navigation Performance 4

  14. Surveillance and Communication performances consideration • Additional communication and surveillance equipage may be required to satisfy ATM operational performance. (doc 4444, ICAO annex 11, regional supplement procedures 7030/4) • In non radar environment where 30 Nm separation is applied : direct voice CPC or CPDLC and ADS-C (with lateral deviation event report at 5Nm) is defined (attachment B annex 11) with a maximal report rate of 14 minutes (see doc 4444) • e.g. Tasman Sea, Pacific - Communication mean : Direct Voice CPC required or CPDLC ATS - Surveillance mean : ADS-C with a reporting rate of 14 minutes Required Navigation Performance 4

  15. RNP 4 approval requests • Air Calédonie International (A320, A330) request from DGAC RNP 4 operational approval - FIR NADI (Fidji), New Zealand • Air France - RNP 4 China on hold Required Navigation Performance 4

  16. Conclusion • Draft guidance material based on existing guidelines, in particular ICAO PBN manual. • Need to support RNP 4 operational approval by European states. Required Navigation Performance 4

More Related