Appendix 2 to AMC 20-24

• ED Decision 2008/004/R found in: AMC-20 Amdt 22 - Airworthiness of Products, Parts and Appliances (May 2021)

Appendix 2 to AMC 20-24 ED Decision 2008/004/R Appendix 2.1: Summary of core ADS-B-NRA Operational Assumptions — The ADS-B-NRA application assumes implementation of the procedures contained in the PANS-ATM ADS-B amendment. Fallback procedures from the radar environment apply to ADS-B-NRA when necessary. For example, ATC could apply alternate procedural separation (e.g., a vertical standard) during degraded modes. — En route traffic density is assumed to be the same as in the current environment in which single radar coverage would enable the provision of a 5NM separation service for en route regions. This corresponds to low or medium density. — Direct Controller-Pilot Communication (VHF) is assumed to be available at all times. — It is assumed that the ADS-B coverage is known to the Controller in the controlled airspace. Appendix 2.2: Summary of core ADS-B-NRA Ground Domain Assumptions — Controller operating procedures are assumed to be unaffected by the selection of an ADS-B data link, i.e., the ADS-B data link is assumed to be transparent to the controller. — Air Traffic Controllers are assumed to follow existing procedures for coordination and transfer of aircraft. This applies to coordinating appropriate information with downstream units and complying with local agreements established between ATC units regarding separation standards to be established prior to entry into a bordering ATC unit. — Appropriate ATS authorities are assumed to provide controllers with adequate contingency procedures in the event of ADS-B failures or degradation. — It is assumed that there is a monitoring capability in the ADS-B Receive Subsystem that monitors the health and operation of the equipment and sends alerts and status messages to the Air Traffic Processing Subsystem. [Amdt 20/3] Appendix 2 to AMC 20-24 ED Decision 2008/004/R Appendix 2.1: Summary of core ADS-B-NRA Operational Assumptions — The ADS-B-NRA application assumes implementation of the procedures contained in the PANS-ATM ADS-B amendment. Fallback procedures from the radar environment apply to ADS-B-NRA when necessary. For example, ATC could apply alternate procedural separation (e.g., a vertical standard) during degraded modes. — En route traffic density is assumed to be the same as in the current environment in which single radar coverage would enable the provision of a 5NM separation service for en route regions. This corresponds to low or medium density. — Direct Controller-Pilot Communication (VHF) is assumed to be available at all times. — It is assumed that the ADS-B coverage is known to the Controller in the controlled airspace. Appendix 2.2: Summary of core ADS-B-NRA Ground Domain Assumptions — Controller operating procedures are assumed to be unaffected by the selection of an ADS-B data link, i.e., the ADS-B data link is assumed to be transparent to the controller. — Air Traffic Controllers are assumed to follow existing procedures for coordination and transfer of aircraft. This applies to coordinating appropriate information with downstream units and complying with local agreements established between ATC units regarding separation standards to be established prior to entry into a bordering ATC unit. — Appropriate ATS authorities are assumed to provide controllers with adequate contingency procedures in the event of ADS-B failures or degradation. — It is assumed that there is a monitoring capability in the ADS-B Receive Subsystem that monitors the health and operation of the equipment and sends alerts and status messages to the Air Traffic Processing Subsystem. [Amdt 20/3] Appendix 2 to AMC 20-24 ED Decision 2008/004/R Appendix 2.1: Summary of core ADS-B-NRA Operational Assumptions — The ADS-B-NRA application assumes implementation of the procedures contained in the PANS-ATM ADS-B amendment. Fallback procedures from the radar environment apply to ADS-B-NRA when necessary. For example, ATC could apply alternate procedural separation (e.g., a vertical standard) during degraded modes. — En route traffic density is assumed to be the same as in the current environment in which single radar coverage would enable the provision of a 5NM separation service for en route regions. This corresponds to low or medium density. — Direct Controller-Pilot Communication (VHF) is assumed to be available at all times. — It is assumed that the ADS-B coverage is known to the Controller in the controlled airspace. Appendix 2.2: Summary of core ADS-B-NRA Ground Domain Assumptions — Controller operating procedures are assumed to be unaffected by the selection of an ADS-B data link, i.e., the ADS-B data link is assumed to be transparent to the controller. — Air Traffic Controllers are assumed to follow existing procedures for coordination and transfer of aircraft. This applies to coordinating appropriate information with downstream units and complying with local agreements established between ATC units regarding separation standards to be established prior to entry into a bordering ATC unit. — Appropriate ATS authorities are assumed to provide controllers with adequate contingency procedures in the event of ADS-B failures or degradation. — It is assumed that there is a monitoring capability in the ADS-B Receive Subsystem that monitors the health and operation of the equipment and sends alerts and status messages to the Air Traffic Processing Subsystem. [Amdt 20/3]