Publication: Magyar Közlöny
Issue: MK-2007-70 (Year: 2007, Number: 70)
Era: 2004-2010
Section: Melléklet a 2007. évi XLVI. törvényhez
Paragraph Index: 3765

d) use multipath-reducing receiver hardware and processing techniques. 6.5.6 GLONASS issue of data. Since the existing GLONASS design does not provide a uniquely defined identifier for sets of ephemeris and clock data, SBAS will use a specific mechanism to avoid any ambiguity in the application of the broadcast corrections. This mechanism is explained in Figure D-3. The definitions of the latency time and validity interval along with the associated coding requirements can be found in Appendix B, section 3.5.4. The user can apply the long-term corrections received only if the set of GLONASS ephemeris and clock data used on board have been received within the validity interval. 23/11/06 ATT D-14 2007/70/II. szám Attac ment Annex 10 — Aeronautical Communications 6.6 SBAS final approach segment (FAS) data block 6.6.1 The SBAS final approach segment (FAS) data block for a particular approach procedure is as shown in Table D-1. It is the same as the GBAS FAS data block defined in Appendix B, section 3.6.4.5, with the exception that the SBAS FAS data block also contains the HAL and VAL to be used for the approach procedure as described in 6.3.4. 6.6.2 FAS data blocks for SBAS and some GBAS approaches are held within a common on-board database supporting both SBAS and GBAS. Within this database, channel assignments must be unique for each approach and coordinated with civil authorities. States are responsible for providing the FAS data for incorporation into the database. The FAS block for a particular approach procedure is described in Appendix B, 3.6.4.5.1 and Table B-66. Table D-1. SBAS FAS data block Data content Bits used Range of values Resolution Operation type 0 to 15 SBAS provider ID 0 to 15 Airport ID – – Runway number (Note 1) 0 to 36 Runway letter – – Approach performance designator 0 to 7 Route indicator – – Reference path data selector 0 to 48 Reference path identifier – – LTP/FTP latitude ± 90.0° 0.0005 arcsec LTP/FTP longitude ± 180.0° 0.0005 arcsec LTP/FTP height –512.0 to 6 041.5 m 0.1 m ǻFPAP latitude ± 1.0° 0.0005 arcsec ǻFPAP longitude ± 1.0° 0.0005 arcsec Approach threshold crossing height (TCH) (Note 2) 0 to 1 638.35 m (0 to 3 276.7 ft) 0.05 m (0.1 ft) Approach TCH units selector – – Glide path angle (GPA) 0 to 90.0° 0.01° Course width at threshold (Note 1) 80.0 to 143.75 m 0.25 m ǻLength offset 0 to 2 032 m 8 m Horizontal alert limit (HAL) 0 to 50.8 m 0.2 m Vertical alert limit (VAL) (Note 3) 0 to 50.8 m 0.2 m Final approach segment CRC – – Note 1.— hen the runway number is set to 00, then the course width field is ignored and the course width is 3 m. Note 2.— Information can be provided in either feet or metres as indicated by the approach TC unit sector. Note 3.— VAL of 0 indicates that the vertical deviations are not to be used (i.e. a lateral guidance only approach). ATT D-15 23/11/06 2007/70/II. szám Annex 10 — Aeronautical Communications Volume I

Source: https://magyarkozlony.hu/hivatalos-lapok/4c6310a937d14bac566ee9c9d944896656c292dd/dokumentumok/5a6ac3c6db12e692ae41096677ad5f072d2cc9f3/letoltes