1 / 11

AMC 20-xx with SBAS criteria (V3.2)

AMC 20-xx with SBAS criteria (V3.2). B. RABILLER DGAC/ DCS CNS/ATM Steering Group Koln, 10-11 October 2006. AMC 20-xx with SBAS criteria. AMC 20-XX status AMC 20-XX structure AMC 20-XX overview SBAS airborne Performance SBAS operational procedures. AMC 20-XX Status.

maxine
Download Presentation

AMC 20-xx with SBAS criteria (V3.2)

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. AMC 20-xx with SBAS criteria (V3.2) B. RABILLER DGAC/ DCS CNS/ATM Steering Group Koln, 10-11 October 2006

  2. AMC 20-xx with SBAS criteria • AMC 20-XX status • AMC 20-XX structure • AMC 20-XX overview • SBAS airborne Performance • SBAS operational procedures

  3. AMC 20-XX Status • AMC 20-xx V 3 addresses the vertical guidance aspect. • V 3.2 includes only SBAS criteria. • APV Baro VNAV will be addressed in the next draft and will be based on the ICAO PBN manual (VOL II, attachment A). • Approach naming and terminology should be standardised at International level (ICAO): • 2D and 3D RNAV(GNSS) approach ? • LPV, APV-SBAS ? • APV Baro VNAV ? • Not an easy task!!!!!!

  4. AMC 20-XX structure

  5. AMC 20-XX OverviewAPV-SBAS Airborne performance • Accuracy: • NSE (95%): Horizontal: 16 m ; Vertical: 20 m • FTE: “ILS look alike” • Display Full Scale Deflection (FSD) defined in DO 229() • Use of ILS auto pilot channel for coupled mode or equivalent • PDE: Procedure included in a FAS data block protected by a CRC • SIS Integrity • Is based on SBAS protection levels: HPLSBAS and VPLSBAS computation • Alert is based on the HPLSBAS/VPLSBAS comparison with the HAL/VAL stored in the FAS data block for the approach flown • FDE capability is also necessary (HPLFDE computation)

  6. AMC 20-XX OverviewAPV-SBAS airborne performance • Aircraft failure classification • Presentation of a misleading navigation information is classified HAZARDOUS (Extremely Remote) • Loss of all navigation information is classified MAJOR • Navigation System developed i.a.w DAL B • A system which is : • based on E/TSO C 146a class Gamma 3 or • A multisensor system using a SBAS sensor compliant with E/TSO C145a class Beta 3.

  7. AMC 20-XX OverviewAPV-SBAS airborne required function • In addition to 2D RNAV (GNSS) functions(§7.1) the navigation system must have the following functions/features: • “ILS Look Alike” display presentation (angular in the lateral and vertical axis) • Data Base with “FAS Data Block Capability” • “Altitude alert function at FAWP” if a/c not equipped with TAWS • Alert triggered when the aircraft is lower than: FAWP altitude –(50 m + VPL) • VTF (Vector To Final) function. • Enables Air Traffic Control to facilitate immediate transitioning onto the final approach segment through a “simple” crew action.

  8. AMC 20-XX OverviewEvaluation of performance for APV-SBAS approach • Case 1: Autopilot not modified and output signal is “ILS look alike” • Conduct several approaches while flying raw data, flight director and coupled to the autopilot. • Objective is to ensure that GNSS/SBAS system is compatible with the aircraft but not to verify strictly speaking the approach performance. • Case 2: Autopilot is modified or lateral/vertical control channel have not been assessed previously or deviation are not “ILS look alike” • Approach performance should be evaluated per CS xx.1329.

  9. AMC 20-XX OverviewOperational procedures • High commonality with 2D RNAV (GNSS) operational procedures • But some specificities: • Crew selection of the 3D procedure (by name or channel) • Check of the 3D procedure (e.g. Glide Path Angle) • Activation of the SBAS Final approach segment: • when FAWP is the active wpt and a/c is within +/- 45° of the final approach track or • VTF function is activated by the crew • Approach discontinued in case of: • Low altitude alert annunciated at FAWP • Lateral or Vertical Warning flag (loss of nav, integrity alert,…)

  10. AMC 20-XX OverviewOperational procedures (cont’d) • Open issues: • During a LPV procedure when a warning flag appears only in the vertical plane • Should the approach be aborted? or • Could the crew revert to 2D RNAV (GNSS) approach respecting the MDA? • Consideration of non-GNSS approach at destination or alternate. • Identical to 2D RNAV(GNSS)? Non GNSS based approach available Or • Take benefit of the better SBAS availability performance and not require a non-GNSS based approach? • Navigation Data Base Management: • It is proposed that no specific operator check is necessary thanks to the FAS data block protected by CRC

  11. QUESTIONS?

More Related