1 / 15

RNAV Approach Status

RNAV Approach Status. B. RABILLER DGAC/ DCS CNS/ATM Steering Group Dublin, 21-22 June 2006. RNAV Approach Status. AMC 20-XX Status BARO VNAV Discussion SBAS Status. AMC 20-XX Status. V 2.4 dated 10 February 06 is the final Draft.

bracha
Download Presentation

RNAV Approach Status

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. RNAV Approach Status B. RABILLER DGAC/ DCS CNS/ATM Steering Group Dublin, 21-22 June 2006

  2. RNAV Approach Status • AMC 20-XX Status • BARO VNAV Discussion • SBAS Status

  3. AMC 20-XX Status • V 2.4 dated 10 February 06 is the final Draft. • No progress since this date. Issuance of this AMC is associated to EASA Task N°20-003. • It is not planned to modify this document before NPA issuance. • How to progress? • It is recalled that AMC 20-XX V 2.4 addresses only the lateral aspect (2D RNAV (GNSS) approach).

  4. AMC 20-XX StatusMinor modifications introduced in V 2.4 • Minor modification introduced just after the last CNS ATM steering group end of January. • Take into account JAA OPS directorate comment. • Clarification of the operational acceptance process: A formal operational approval is not required • Use of “operational criteria” or “operational authorisation” terminology instead of “operational approval”. • Navigation data base integrity section is now divided in two subsections one for the commercial air transportation and the other for the general aviation. • Enforce the importance of LOA for commercial air transportation and manual verification possible only in rare cases • For general aviation LOA process is the preferred method but manual verification is an acceptable alternative method.

  5. Baro VNAV discussion • RNPSORSG (ICAO) is developing requirement for the Baro VNAV Aspect. • Objective is to include this material in AMC 20-XX Step 2. • In an appendix Or • Merged in the text • This work should be validated this summer. A first draft exists but needs to be amended before circulation

  6. SBAS status • Work has already started (AMC 20-XX step 2) • A first mature version should be available after the summer period • Performance and functional requirement are merged in the text (not in an appendix) • Terminology used should be discussed and defined: • 3D RNAV(GNSS) approach? • LPV, APV-SBAS? • From a charting point of view title remains RNAV (GNSS) and the minimum box indicates LPV for the approach minima definition

  7. SBAS Charting example (WAAS) WAAS Channel Minimum box LPV minima

  8. AMC 20-XX and SBAS

  9. Airborne SBAS system and regulation (1/2) • Two Types of SBAS receiver: • “Standalone” system incorporating receiver, RNAV computer, nav data base and Man Machine Interface • SBAS sensor incorporating only the receiver part. Sensor must be used with an integrated navigation system (ex FMS). • The technical standard for the approval of these systems is the DO 229C (RTCA). • It specifies functional and operational classes. • It specifies technical requirements. • DO 229D will be published soon. • clarifies some technical point (SBAS and Baro VNAV, suppression of GLS reference, satellite selection hierarchy,…) • adds some functionalities : LP (Localizer Performance without vertical guidance).

  10. Airborne SBAS system and regulation (2/2) • FAA and European qualification standard is based on DO 229c: • TSO C146a or ETSO C146a (Draft) for « stand-alone » receiver • TSO C145a or ETSO C145a (Draft) for SBAS sensor. • Regulation for SBAS aircraft certification: • FAA AC 20-138A

  11. SBAS functional and operational classes (1/2) • «Standalone» System (E/TSO C146a) • 2 Functional classes: • GAMMA (receiver +RNAV +D/B+IHM) • DELTA (receiver +RNAV; without nav data base, only for precision approach: Operational class 3). • 4 Operational classes: • 1: Oceanic, Enroute continental, terminal (arrival and departure), non precision approach • 2 : Operational class 1+ LNAV/VNAV • 3 : Operational class 2+ LPV (APV I and II) • 4 : Precision Approach (same minima as ILS Cat I)

  12. SBAS functional and operational classes (2/2) • SBAS Sensor (E/TSO C145a). • 1 Functional Class: • BETA (receiver only) • 3 Operational classes • 1: Oceanic, Enroute continental, terminal (arrival and departure), non precision approach • 2 : Operational class 1+ LNAV/VNAV • 3 : Operational class 2+ LPV (APV I and II)

  13. The SBAS Integrity Concept « Protection Level » box: Variable over satelite geometry, GNSS accuracy,etc… HPL: Horizontal Protection Level VPL: Vertical Protection Level HAL: Horizontal Alert Limit VAL: Vertical Alert Limit « Alert Limit » box : Fixed and defined for an operation (e.g APV I or II)

  14. 50 m 50 m 10 m 20 m 556 m 40 m Performance levels • LNAV/VNAV  Basic GPS (lateral) + barometric (vertical) • APV I  SBAS: EGNOS, WAAS APV II SBAS: EGNOS, Galileo Cat I  GLS with GBAS Representation of relative Alarm Limit Box for the different performance levels. Represents the containment of the uncertainty on aircraft position at 10-7 probability

  15. QUESTION?

More Related