• 热门标签

当前位置: 主页 > 航空资料 > 国外资料 >

时间:2011-07-29 09:35来源:蓝天飞行翻译 作者:航空
曝光台 注意防骗 网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者

8.4.2 GNSS equipment compliant with TSO-C145a, TSO-C146a or an equivalent standard acceptable to CASA are suitable for use with ADS-B. 
8.4.3 Particular navigation packages that do not have a TSOA, but can be demonstrated to achieve the accuracy and integrity values required, may be acceptable to CASA. In assessing the suitability of GNSS avionics that do not have a TSO-C145a/146a authorisation, CASA may consider the system differences to the standards documented in RTCA/DO-229C (or later version), with particular regard to the following criteria:
.
The system’s capability of delivering position information with a periodic interval of at least one second; and
.
The system can continuously output the HPL value to the ADS-B transmitter or notify the pilot of an interruption due to availability issues (RAIM); and
.
If the system is intended primarily as a pilot navigation system with positional information being provided to the ADS-B system, it needs to meet the requirements of AC 21-36(0); and
.
The system takes advantage of GPS selective availability being set to zero.
11 April 2007
AC 21-45(0): Airworthiness Approval of Airborne Automatic Dependent Surveillance Broadcast Equipment
8.5 Positional integrity data
8.5.1 HPL integrity data needs to be provided to the ADS-B transmitter from the GNSS receiver on the same interface as the positional data. This data is typically available as ARINC429 label 130.
8.5.2 HFOM data shall be provided to the transponder on the same interface as the HPL data. HFOM typically uses ARINC429 label 247.
A RTCA/DO-260A compliant installation will use the HFOM value to calculate NAC.
In some cases, such as during rare periods of inadequate satellites, HPL may not be delivered to the interface. In this case, a RTCA/DO-260 compliant installation may use the HFOM value to generate NUC during the period of HPL non-availability.
8.5.3 In the case of RTCA/DO-260A compliant installations, the SIL is intended to reflect the integrity of the navigation source of the position information broadcast.  Where position integrity is based on HPL and the SIL cannot be unambiguously determined and set dynamically, the value should be set to 2. During periods where HPL is not available, the NIC should be set to 0 (zero), and the NAC should reflect the accuracy of the broadcast position.
8.6 Pressure altitude
8.6.1 Pressure altitude provided to transponders is to be in accordance with existing requirements for ATC transponders. It is preferable that 25 foot altitude encoding is used. This data is typically available on ARINC429 label 203.
8.7 Identity
8.7.1 Identity information is to be provided to the transponder so that the information is identical to the filed flight plan. This information may be provided from: 
.
a flight management system; 
.
a pilot control panel; or
.
for aircraft which always operates with the same flight identity (e.g. using registration as a callsign), it may be programmed into equipment at installation.
8.8 ADS-B data sources (Desirable)
8.8.1 GNSS altitude. GNSS altitude should be provided from an approved GNSS receiver to the ADS-B transmitter. Typically this data is available as GNSS Height (HAE) ARINC429 label 370 or GNSS Alt (MSL) ARINC429 label 076.
8.8.2 Vertical rate (GNSS or Barometric). Vertical rate may be provided from either a GNSS receiver or from a pressure source: 
.
GNSS vertical rate should be provided from an approved GNSS receiver, and is typically available as ARINC429 label 165, or
.
Barometric vertical rate. Barometric (BARO) vertical rate is typically available as ARINC429 label 212.
Note: The most accurate source should be used.
8.8.3 Velocity Information. Ground speed from an approved GNSS receiver in the form of East/West Velocity and North/South Velocity should be provided. This would be typically available as ARINC429 label 174.
 
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址:Notice of Final Rule Making(16)