1 / 12

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 10-11 October 2006. Overview. Environmental context Oceanic and remote regions Trials and implementations Existing guideline material Operational requirements Navigation Specification

ginata
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 10-11 October 2006

  2. Overview • Environmental context • Oceanic and remote regions • Trials and implementations • Existing guideline material • Operational requirements • Navigation Specification • Surveillance/Communication considerations • Air France RNP 4 request • Conclusion Required Navigation Performance 4

  3. 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

  4. 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 are provisioned in doc 7030/4 Mid/Asia/RAC-10 7.1.6. • RNP 4 applications in Tasman sea as described in doc 7030/4 • 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/Fiji/Tahiti began 22 December 2005. • South China Sea Airspace (due to traffic growth on one pair of parallel routes causing delays) Required Navigation Performance 4

  5. 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 appendix F of Manual on RNP doc 9613. • Performance Based Navigation manual (to be published March 2007) developed by RNPSORSG ICAO group as an evolution and replacement of doc 9613. • FAA order 8400.33 dated 9/15/05 Required Navigation Performance 4

  6. 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

  7. Navigation specification • PBN manual : concept of navigation specification • Aircraft eligibility groups (airworthiness) • Navigation equipment : 2 fully serviceable independent LRNS including each a GNSS sensor (stand alone or sensor to a multi-sensors system) • Navigation accuracy : cross track TSE < 4Nm and along track NSE < 4Nm for 95% flight time • Onboard monitoring performances : Horizontal Alert Limit : 4Nm (TBC) • 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

  8. Navigation specification • PBN manual : concept of navigation specification • 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 • Recommended functionalities Required Navigation Performance 4

  9. Navigation specification • Operational requirements • Flight plan designation • Pre-Flight procedures • Operating procedures • Navigation Database • Pilot knowledge and training Required Navigation Performance 4

  10. Surveillance and Communication performances consideration • Additional communication and surveillance equipage may be required to satisfy ATM operational performance. (doc 4444, ICAO annex 11,regional supplementary 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

  11. Air France RNP 4 • Air France request from DGAC RNP 4 operational approval Required Navigation Performance 4

  12. Conclusion • Need to develop guideline material to support operational approval by European states. • Draft position paper based on existing guidelines, in particular ICAO PBN manual. Required Navigation Performance 4

More Related