The European Organisation for Civil Aviation Equipment

L’Organisation Européenne pour l’Equipement de l’Aviation Civile

TECHNICAL SPECIFICATION FOR A 1090 MHz EXTENDED

SQUITTER ADS-B GROUND STATION

This document is the exclusive intellectual and commercial property of EUROCAE.

It is presently commercialised by EUROCAE.
This electronic copy is delivered to your company/organisation for internal use exclusively.
In no case it must be re-sold, or hired, lent or exchanged outside your company.

ED-129
June 2010

102 Rue Etienne Dolet Tel: 33 1 40 92 79 30

92240 Malakoff, France Fax: 33 1 46 55 62 65
Web Site: www.eurocae.net Email: [email protected]
TECHNICAL SPECIFICATION FOR A 1090 MHz EXTENDED
SQUITTER ADS-B GROUND STATION

This document is the exclusive intellectual and commercial property of EUROCAE.

It is presently commercialised by EUROCAE.
This electronic copy is delivered to your company/organisation for internal use exclusively.
In no case it must be re-sold, or hired, lent or exchanged outside your company.

ED-129
June 2010

© EUROCAE, 2010
 i

FOREWORD
1. The Council of EUROCAE on 7 June 2010 accepted this document, prepared
by EUROCAE Working Group WG-51, Subgroup SG4.
2. EUROCAE is an international non-profit making organisation. Membership is
open to European users and manufacturers of equipment for aeronautics, trade
associations, and national civil aviation administrations and, under certain
conditions, non-European organisations. Its work programme is principally
directed to the preparation of performance specifications and guidance
documents for civil aviation equipment, for adoption and use at European and
worldwide levels.
3. EUROCAE performance specifications are recommendations only. EUROCAE
is not an official body of the European Governments; its recommendations are
valid as statements of official policy only when adopted by a particular
government or conference of governments. In particular, the inclusion of
references to standards published by ARINC or any other standardisation
bodies, or the inclusion of extracts from those standards, has no safety or
regulatory implications.
4. Copies of this document may be obtained from:
EUROCAE
102 Rue Etienne Dolet
92240 Malakoff
France
Tel: 33 1 40 92 79 30
Fax: 33 1 46 55 62 65
Email: [email protected]
Web Site: www.eurocae.net

© EUROCAE, 2010
 ii

TABLE OF CONTENTS
CHAPTER 1 GENERAL.............................................................................................................. 1
1.1 PURPOSE AND SCOPE........................................................................ 1
1.1.1 Structure of this Document ..................................................... 1
1.2 APPLICATIONS ..................................................................................... 1
1.2.1 Mandating and Recommendation Phrases............................. 1
1.3 BASIC ASSUMPTIONS ......................................................................... 2
1.4 RELATIONSHIP TO OTHER DOCUMENTS ......................................... 3
1.4.1 ICAO ....................................................................................... 3
1.4.2 Other EUROCAE/RTCA Documents ...................................... 3
1.5 DESCRIPTION OF SYSTEM ................................................................. 3
1.5.1 ADS-B ..................................................................................... 4
1.5.2 ADS-B Surveillance Applications - Package I......................... 4
1.5.3 The ADS-B-NRA Application .................................................. 5
1.5.4 The ADS-B-RAD Application .................................................. 6
1.5.5 Assumed Airborne & Ground Generic Functional Architecture 6
1.6 SCOPE OF THE 1090 ES GROUND STATION .................................... 7
1.7 COMPOSITION OF EQUIPMENT ......................................................... 8
1.8 DEFINITIONS AND ABBREVIATIONS .................................................. 9
1.8.1 Acronyms and Abbreviations .................................................. 9
1.8.2 Definitions ............................................................................... 13
1.9 REFERENCES ....................................................................................... 16
1.9.1 ICAO ....................................................................................... 16
1.9.2 EUROCONTROL .................................................................... 16
1.9.3 EUROCAE/RTCA.................................................................... 17
1.9.4 ETSI ........................................................................................ 17
1.9.5 Miscellaneous ......................................................................... 17
CHAPTER 2 GENERAL DESIGN REQUIREMENTS................................................................. 18
2.1 INTRODUCTION .................................................................................... 18
2.2 1090 ES GROUND STATION SERVICES............................................. 18
2.3 1090 ES GROUND STATION MODES AND STATES .......................... 18
2.3.1 1090 ES Ground Station Modes ............................................. 18
2.3.2 1090 ES Ground Station States.............................................. 18
2.3.3 Time Source States................................................................. 19
2.4 FUNCTIONAL REQUIREMENTS .......................................................... 20
2.4.1 1090 ES Reception and Decoding Function........................... 21
2.4.2 Report Assembly Function...................................................... 21
2.4.3 UTC Time Synchronisation Function ...................................... 22
2.4.4 Ground Station Management and Status Reporting Function 22
2.5 EQUIPMENT DESIGN ASSURANCE.................................................... 23
2.6 ADDITIONAL REQUIREMENTS............................................................ 23
2.6.1 Power Supply .......................................................................... 23
2.6.2 Receiver Selectivity................................................................. 23

© EUROCAE, 2010
 iii

CHAPTER 3 MINIMUM PERFORMANCE SPECIFICATION UNDER STANDARD CONDITIONS 25

3.1 INTRODUCTION .................................................................................... 25
3.1.1 Equipment Classes ................................................................. 25
3.1.2 Antenna................................................................................... 25
3.1.3 Horizontal Pattern ................................................................... 25
3.1.4 Gain......................................................................................... 25
3.1.5 Frequency ............................................................................... 25
3.2 COVERAGE AND DETECTION............................................................. 25
3.2.1 Coverage................................................................................. 25
3.2.2 Performance in the presence of 1090 MHz Interference ........ 26
3.3 SYSTEM CAPACITY.............................................................................. 26
3.3.1 Overall Capacity...................................................................... 26
3.3.2 Target Overloads .................................................................... 26
3.3.3 Communications Overloads.................................................... 26
3.3.4 Overload Mitigation ................................................................. 26
3.4 SYSTEM LATENCY ............................................................................... 27
3.5 CONTINUITY.......................................................................................... 27
3.6 INTEGRITY ............................................................................................ 27
3.7 ACCURACY ........................................................................................... 27
3.7.1 Time of Applicability Accuracy ................................................ 27
3.7.2 Time of Message Reception Accuracy ................................... 27
3.7.3 Data Accuracy......................................................................... 27
3.8 AVAILABILITY ........................................................................................ 28
3.9 EQUIPMENT CONTROL AND STATUS ............................................... 28
3.9.1 Assumptions............................................................................ 28
3.9.2 General ................................................................................... 28
3.9.3 Monitoring Functions (Local & Remote) ................................. 29
3.9.4 Control Functions .................................................................... 32
3.9.5 Security ................................................................................... 32
3.9.6 Data Logging........................................................................... 33
3.10 MESSAGE PROCESSING AND REPORT ASSEMBLY ....................... 33
3.10.1 General Message Processing Requirements ......................... 33
3.10.2 Report Triggering .................................................................... 36
3.10.3 Data Item Inclusion ................................................................. 42
3.10.4 ASTERIX Category 021 Report Assembly ............................. 50
3.11 RECEIVER CHARACTERISTICS .......................................................... 62
3.11.1 Receiver Sensitivity................................................................. 62
3.11.2 Receiver Desired Signal Dynamic Range............................... 63
CHAPTER 4 MINIMUM PERFORMANCE SPECIFICATION UNDER ENVIRONMENTAL TEST
CONDITIONS ........................................................................................................ 64
4.1 ENVIRONMENTAL SPECIFICATION.................................................... 64
4.2 STORAGE .............................................................................................. 64
4.3 TRANSPORT ......................................................................................... 64
4.4 INDOOR USE......................................................................................... 64
4.5 EQUIPMENT ROOM USE ..................................................................... 64

© EUROCAE, 2010
 iv

4.6 OUTDOOR USE..................................................................................... 64

4.7 EUROPEAN LEGISLATIVE REQUIREMENTS ..................................... 65
CHAPTER 5 TEST PROCEDURES ........................................................................................... 66
5.1 INTRODUCTION .................................................................................... 66
5.1.1 Test Equipment Setup ............................................................ 66
5.1.2 Default Configuration, Mode and State................................... 69
5.1.3 Message Set Construction...................................................... 70
5.1.4 Common Procedures .............................................................. 71
5.2 COVERAGE AND DETECTION............................................................. 71
5.2.1 Coverage................................................................................. 71
5.2.2 Performance in the presence of 1090 MHz Interference ........ 71
5.3 SYSTEM CAPACITY.............................................................................. 72
5.3.1 Overall Capacity...................................................................... 72
5.3.2 Target Overloads .................................................................... 72
5.3.3 Communications Overloads.................................................... 73
5.3.4 Overload Mitigation ................................................................. 73
5.4 SYSTEM LATENCY ............................................................................... 74
5.5 CONTINUITY.......................................................................................... 74
5.6 INTEGRITY ............................................................................................ 74
5.6.1 Objectives ............................................................................... 74
5.6.2 Test Equipment Setup ............................................................ 74
5.6.3 Scenario Design...................................................................... 75
5.6.4 Test Procedure........................................................................ 75
5.7 ACCURACY ........................................................................................... 75
5.7.1 Time of Applicability Accuracy ................................................ 75
5.7.2 Time of Message Reception Accuracy ................................... 75
5.7.3 Data Accuracy......................................................................... 77
5.8 AVAILABILITY ........................................................................................ 77
5.9 EQUIPMENT CONTROL AND STATUS ............................................... 77
5.9.1 Assumptions............................................................................ 77
5.9.2 General ................................................................................... 77
5.9.3 Monitoring Functions (Local & Remote) ................................. 77
5.9.4 Control Functions .................................................................... 87
5.9.5 Security ................................................................................... 90
5.9.6 Data Logging........................................................................... 90
5.10 MESSAGE PROCESSING AND REPORT ASSEMBLY ....................... 91
5.10.1 General Message Processing Requirements ......................... 91
5.10.2 Report Triggering .................................................................... 101
5.10.3 Data Item Inclusion ................................................................. 111
5.10.4 ASTERIX Category 021 Report Assembly ............................. 138
5.11 RECEIVER CHARACTERISTICS .......................................................... 138
5.11.1 Receiver Sensitivity................................................................. 138
5.11.2 Receiver Desired Signal Dynamic Range............................... 139

© EUROCAE, 2010
 v

CHAPTER 6 INSTALLED EQUIPMENT PERFORMANCE........................................................ 140

6.1 INTRODUCTION .................................................................................... 140
6.2 EQUIPMENT INSTALLATION ............................................................... 140
6.2.1 Environment ............................................................................ 140
6.2.2 Failure Protection .................................................................... 140
6.2.3 Interference Effects ................................................................. 140
6.2.4 Inadvertent Turnoff.................................................................. 140
6.2.5 Power Source.......................................................................... 140
6.2.6 Transmission Lines ................................................................. 140
6.2.7 Antenna Type.......................................................................... 141
6.2.8 Antenna Location .................................................................... 141
6.2.9 Time Source............................................................................ 141
6.2.10 Lightning Protection ................................................................ 141
6.2.11 Communications ..................................................................... 141
6.2.12 Remote Control and Monitoring .............................................. 141
6.2.13 End to End System Testing .................................................... 141
6.3 EXTERNAL EQUIPMENT ...................................................................... 141
6.4 INSTALLED EQUIPMENT PERFORMANCE ........................................ 141
6.5 CONDITIONS OF TEST......................................................................... 142
6.5.1 Power Input ............................................................................. 142
6.5.2 Associated Equipment or Systems ......................................... 142
6.5.3 Environment ............................................................................ 142
6.5.4 Adjustment of Equipment........................................................ 142
6.5.5 Warm-up Period ...................................................................... 142
6.6 TEST PROCEDURES FOR INSTALLED EQUIPMENT PERFORMANCE 142
6.6.1 Ground Test Procedures......................................................... 142
APPENDIX A GROUND STATION CONFIGURATION AND MONITORING PARAMETERS.... 144
A.1 REQUIRED CONFIGURATION PARAMETERS ................................... 144
A.2 OPTIONAL CONFIGURATION PARAMETERS .................................... 146
A.3 REQUIRED SNMP MONITORING PARAMETERS............................... 147
A.4 OPTIONAL SNMP MONITORING PARAMETERS ............................... 148
APPENDIX B BITE TEST SUMMARY ......................................................................................... 149
B.1 BITE TESTS ........................................................................................... 149
APPENDIX C 1090 ES GROUND STATION INTEGRITY REQUIREMENT ............................... 150
C.1 OVERVIEW ............................................................................................ 150
C.2 REQUIREMENT ..................................................................................... 150
C.3 ANALYSIS .............................................................................................. 151
APPENDIX D PROCESSING OF DUPLICATE ADDRESSES .................................................... 153
D.1 INTRODUCTION .................................................................................... 153
D.2 CAUSES OF DUPLICATED ADDRESSES ........................................... 153
D.2.1 Accidental re-use of an address ............................................. 153
D.2.2 Incorrect Decoding of a Garbled Message ............................. 153
D.2.3 Deliberate Transmission of Incorrect Messages..................... 154
D.3 DESIRABLE BEHAVIOUR IN THE EVENT OF DUPLICATE ADDRESSES154

© EUROCAE, 2010
 vi

APPENDIX E THROTTLED REPORTING MODE ....................................................................... 155

E.1 INTRODUCTION .................................................................................... 155
E.2 DATA-DRIVEN REPORTING MODE..................................................... 155
E.3 PERIODIC REPORTING MODE............................................................ 155
E.4 THROTTLED REPORTING MODE........................................................ 156
E.5 RECOMMENDED REQUIREMENTS FOR THROTTLED REPORTING
MODE..................................................................................................... 157
APPENDIX F REFERENCE 1090 ES SIGNAL POWER BUDGET............................................. 158
F.1 1090 ES SYSTEM CHARACTERISTICS............................................... 158
F.2 SIGNAL DYNAMIC RANGE ON GROUND 1090 ES RECEIVER......... 159
APPENDIX G REFERENCE ANTENNA ...................................................................................... 161
APPENDIX H NRA 1090 MHZ FRUIT LEVELS ASSESSMENT ................................................. 162
H.1 BACKGROUND...................................................................................... 162
H.2 NON-RADAR AIRSPACES (NRA) CASE STUDIES ............................. 162
H.3 AIR AND GROUND SCENARIOS.......................................................... 163
H.4 FRUIT MODEL ....................................................................................... 163
H.5 CONCLUSIONS ..................................................................................... 163
APPENDIX I ADS-B PERFORMANCE IN NRA 1090 MHZ FRUIT ENVIRONMENT ................ 166
I.1 INTRODUCTION .................................................................................... 166
I.2 REQUIRED SURVEILLANCE PERFORMANCE................................... 166
I.2.1 En-Route Surveillance ............................................................ 166
I.2.2 Terminal Surveillance ............................................................. 166
I.3 ADS-B POSITION UPDATE RATE ........................................................ 166
I.4 WANTED SIGNAL AMPLITUDE ............................................................ 166
I.4.1 Terminal Airspace Power Budget Calculation ........................ 167
I.4.2 En-Route Application .............................................................. 168
I.5 FRUIT MODELLING............................................................................... 169
I.5.1 The EUROCONTROL NRA Study .......................................... 169
I.5.2 ADS-B Interference Model ...................................................... 169
I.5.3 Mode A/C FRUIT..................................................................... 169
I.5.4 Mode S FRUIT ........................................................................ 173
I.6 CONCLUSIONS ..................................................................................... 175
APPENDIX J DME INTERFERENCE EFFECTS ........................................................................ 176
J.1 INTRODUCTION .................................................................................... 176
J.2 CHARACTERISTICS OF DME SIGNALS AND SYSTEMS................... 176
J.2.1 Principle of Operation ............................................................. 176
J.2.2 Modulation Scheme ................................................................ 176
J.2.3 Frequency Allocation .............................................................. 177
J.2.4 DME Transponder Antenna Pattern........................................ 181
J.2.5 DME Transponder Transmitted Power Levels........................ 182
J.2.6 DME Transmission Rates ....................................................... 182
J.3 CHARACTERISTICS OF 1090 MHZ RECEIVERS................................ 182
J.4 EFFECTS OF DME PULSES ON 1090 MHZ RECEPTION .................. 185
J.4.1 Effects of DME Pulse Amplitude on ADS-B Reception........... 185
J.4.2 Effects of DME Pulse Frequency on ADS-B Reception.......... 192

© EUROCAE, 2010
 vii

J.5 RECEIVED DME SIGNAL AMPLITUDES.............................................. 195

J.5.1 Power Budget Calculation....................................................... 195
J.5.2 Effects of Range and Relative Elevation on DME Signal Amplitude195
J.6 EXPECTED ADS-B SIGNAL AMPLITUDES.......................................... 197
J.7 AN EXAMPLE CALCULATION .............................................................. 198
J.7.1 The Scenario........................................................................... 198
J.7.2 The DME Received Power Calculation................................... 199
J.7.3 The ADS-B Power Budget Calculation ................................... 200
J.7.4 The Analysis Result ................................................................ 201
J.8 CONCLUSIONS ..................................................................................... 201
J.9 RECOMMENDATIONS .......................................................................... 201
APPENDIX K SOFTWARE ASSURANCE LEVEL (SWAL) REQUIREMENTS........................... 202
K.1 SUMMARY ............................................................................................. 202
K.2 INTRODUCTION .................................................................................... 202
K.3 REFERENCES ....................................................................................... 202
K.4 OBJECTIVE............................................................................................ 202
K.5 METHOD ................................................................................................ 202
K.6 ANALYSIS .............................................................................................. 204
K.7 CONCLUSION........................................................................................ 205
APPENDIX L ED-129 TRACEABILITY MATRIX TO ED-126 REQUIREMENTS........................ 206
L.1 INTRODUCTION .................................................................................... 206
L.2 ED-126 SAFETY AND PERFORMANCE REQUIREMENTS ................ 206
L.3 ED-126 INTEROPERABILITY REQUIREMENTS.................................. 207
L.4 ED-126 INTEROPERABILITY RECOMMENDATIONS ......................... 209
L.5 ED-126 1090 SPECIFIC INTEROPERABILITY REQUIREMENTS....... 209
APPENDIX M ASTERIX CATEGORY 021 EDITION 0.23 ........................................................... 212
M.1 INTRODUCTION .................................................................................... 212
M.2 DATA ITEM INCLUSION........................................................................ 212
M.2.1 Position Reports...................................................................... 212
M.2.2 Data Driven Velocity Reports.................................................. 213
M.3 DIFFERENCES BEWTEEN EDITION 0.23 AND EDITION 1.4 ............. 215
M.4 ASTERIX CATEGORY 021 EDITION 0.23 REPORT ASSEMBLY ...... 217
M.4.1 I021/010 Data Source Identification (SAC/SIC)...................... 218
M.4.2 I021/020 Emitter Category ...................................................... 218
M.4.3 I021/030 Time of Day.............................................................. 219
M.4.4 I021/040 Target Report Descriptor ......................................... 219
M.4.5 I021/080 Target Address ........................................................ 220
M.4.6 I021/090 Figure of Merit (FOM) .............................................. 220
M.4.7 I021/095 Velocity Accuracy..................................................... 221
M.4.8 I021/130 Position in WGS-84 Coordinates ............................. 221
M.4.9 I021/140 Geometric Altitude ................................................... 221
M.4.10 I021/145 Flight Level............................................................... 221
M.4.11 I021/146 Intermediate State Selected Altitude ....................... 221
M.4.12 I021/150 Air Speed ................................................................. 221
M.4.13 I021/151 True Air Speed......................................................... 222

© EUROCAE, 2010
 viii

M.4.14 I021/152 Magnetic Heading .................................................... 222

M.4.15 I021/155 Barometric Vertical Rate .......................................... 222
M.4.16 I021/157 Geometric Vertical Rate........................................... 222
M.4.17 I021/160 Ground Vector.......................................................... 222
M.4.18 I021/170 Target Identification ................................................. 222
M.4.19 I021/200 Target Status ........................................................... 222
M.4.20 I021/210 Link Technology Indicator ........................................ 223
LIST OF MEMBERS OF EUROCAE WORKING GROUP 51 Sub-Group 4 ................................... 224
ED-129 MODIFICATION SUGGESTION FORM ............................................................................ 225

© EUROCAE, 2010
 ix

LIST OF TABLES
Table 1: Out of Band Characteristics .................................................................................................... 23
Table 2: Alternative Out of Band Characteristics .................................................................................. 24
Table 3: Mapping of the 1090 ES Ground Station Status into ASTERIX Category 023 ....................... 30
Table 4: 1090 ES Ground Station Report Types and Transmission Modes ......................................... 36
Table 5: ASTERIX Category 021 Periodic or Data Driven Position Report: Minimum Items................ 43
Table 6: ASTERIX Category 021 Periodic or Data Driven Position Report: Optional Items................. 44
Table 7: ASTERIX Category 021 Data Driven Velocity Report: Minimum Items .................................. 46
Table 8: 1090 ES Ground Station Status Report: Minimum items ........................................................ 47
Table 9: Service Status Report: Minimum items ................................................................................... 47
Table 10: ASTERIX Version Reports – Minimum Items........................................................................ 48
Table 11: ADS-B Message Subfield Validity Periods............................................................................ 49
Table 12: Aircraft Operational Status Field Mapping ............................................................................ 51
Table 13: Emitter Category Field Mapping Requirements .................................................................... 52
Table 14: Mode 3/A Code Field Mapping Requirements ...................................................................... 54
Table 15: Mapping of Data for Quality Indicators.................................................................................. 56
Table 16: I021/146 Source Field Mapping ............................................................................................ 58
Table 17: Capability Classes and Operational Modes for Surface Targets .......................................... 62
Table 18: Message Rates for Desired Messages ................................................................................. 67
Table 19: Amplitude and Message Type Distribution of the Injected FRUIT ........................................ 68
Table 20: 1090 ES Message Scenario – Time of Message Reception Accuracy................................. 76
Table 21: Scenario of the Test Procedure for Status Reporting ........................................................... 78
Table 22: Scenario 1 - Receiver Sensitivity........................................................................................... 86
Table 23: Testing of Required Configuration Parameters..................................................................... 88
Table 24: Requirements Tested in Other Test Procedures................................................................... 91
Table 25: ES Messages for Message Type Filtering Test .................................................................... 92
Table 26: ES Version State Processing Test ........................................................................................ 95
Table 27: Simulating of Two Duplicate Targets in Scenario 1 .............................................................. 97
Table 28: Simulating of Two Duplicate Targets in Scenario 2 .............................................................. 99
Table 29: Simulating of Two Duplicate Targets in Scenario 3 ............................................................ 100
Table 30: ASTERIX Category 021 Periodic Report Test Scenario ..................................................... 102
Table F-1: Received Signal Strength .................................................................................................. 160
Table H-1: Worst Case Cumulative FRUIT Rates at -92 dBm per NRA in 2015 Scenario................. 164
Table I-1: Received Signal Power for Several Common Range Values ............................................. 169
Table J-1: List of DME Channels with Ground-to-Air Frequencies within 30 MHz of 1090 MHz ........ 177
Table J-2: List of DME Channels with Air-to-Ground Frequencies within 30 MHz of 1090 MHz ........ 178
Table J-3: Required ADS-B Receiver Frequency Response .............................................................. 183
Table K-1: SWAL Based on Severity and Likelihood .......................................................................... 203
Table K-2: SWAL Determination based on severity............................................................................ 205
Table K-3: Assumed Probabilities for the likelihood a Failure to Propagate to the Effect................... 205
Table M-1A: ASTERIX Category 021 Edition 0.23 Periodic or Data Driven Position Report: Minimum
Items .................................................................................................................................................... 212
Table M-1B: ASTERIX Category 021 Edition 0.23 Periodic or Data Driven Position Report: Optional
Items .................................................................................................................................................... 213
Table M-2: ASTERIX Category 021 Edition 0.23 Data Driven Velocity Report: Minimum Items........ 214

© EUROCAE, 2010
 x

Table M-3: Changes from ASTERIX Category 021 Edition 0.23 to 1.4 .............................................. 215
Table M-4: Summary of ASTERIX Category 021 Edition 0.23 Data Items ......................................... 217
Table M-5: Emitter Category Field Mapping Requirements for ASTERIX Category 021 Edition 0.23 218
Table M-6: PA for Version 0 Targets................................................................................................... 220
Table M-7: PA for Version 1 Targets................................................................................................... 221
Table M-8: Surveillance Status to Target Status Mapping.................................................................. 222
Table M-9: Emergency/Priority Status to Target Status Mapping for Surveillance Status = 1............ 223
Table M-10: I021/210 CDTI Determination ......................................................................................... 223

LIST OF FIGURES
Figure 1: ADS-B and TIS-B System Diagram ......................................................................................... 4
Figure 2: ADS-B Functional Architecture ................................................................................................ 7
Figure 3: 1090 ES Ground Station Context Diagram .............................................................................. 7
Figure 4: 1090 ES Ground Station Functional Block Diagram ................................................................ 8
Figure 5: 1090 ES Ground Station States ............................................................................................. 19
Figure 6: UTC Time State Machine....................................................................................................... 20
Figure 7: 1090 ES Ground Station Modes ............................................................................................ 29
Figure 8: Example of version number processing with a version validity period................................... 35
Figure 9: Initial Position Solution Range Check .................................................................................... 39
Figure 10: CPR Validation Test............................................................................................................. 40
Figure 11: Example of Even and Odd 0.2 UTC Second Epochs .......................................................... 55
Figure 12: Track Angle and Ground Speed........................................................................................... 61
Figure 13: Standard Test Equipment Setup (Logical Connections)...................................................... 66
Figure 14: Initial Position Messages...................................................................................................... 70
Figure C-1: High-Level View of 1090 ES Ground Station and Airborne Segments per ED-126......... 150
Figure C-2: Assumed Relation between Airborne Position Reports and CWP Screen updates ........ 152
Figure E-1: Processing Timeline for Data-Driven Reporting Mode ..................................................... 155
Figure E-2: Processing Timeline for Periodic Mode Showing Potential Data Age Variation .............. 156
Figure E-3: Processing Timeline for Throttled Reporting Mode .......................................................... 157
Figure F-1: Desired Signal Levels versus Target Distance from 1090 ES Receiver .......................... 160
Figure H-1: Evaluated NRAs ............................................................................................................... 162
Figure H-2: FRUIT Rate versus Signal Level at Girona, Spain, 2015................................................. 165
Figure I-1: Mode A / C / 2 Reply Format ............................................................................................. 169
Figure I-2: Mode S Modulation Format................................................................................................ 170
Figure I-3: Girona Baseline 2004 Scenario Results for Mode A/C FRUIT .......................................... 171
Figure I-4: Girona Baseline 2015 Scenario Results for Mode A/C FRUIT .......................................... 171
Figure I-5: Girona Low Level 2015 Scenario Results for Mode A/C FRUIT........................................ 172
Figure I-6: Girona High Level 2015 Scenario Results for Mode A/C FRUIT....................................... 172
Figure I-7: Girona Baseline 2004 Scenario Results for Mode S FRUIT.............................................. 173
Figure I-8: Girona 2015 Scenario Results for Baseline Mode S FRUIT.............................................. 174
Figure I-9: Girona 2015 Scenario Results for Low FRUIT Level......................................................... 174
Figure I-10: Girona 2015 Scenario Results for High FRUIT Level ...................................................... 175
Figure J-1: Standard DME Pulse Shape (linear amplitude scale)....................................................... 176
Figure J-2: A Typical DME Antenna (dB Systems Inc. type 5100A) ................................................... 181

© EUROCAE, 2010
 xi

Figure J-3: DME antenna Vertical Gain Profile (dB Systems Inc. type 5100A) .................................. 182
Figure J-4: Frequency Response of Modelled ADS-B Receiver (half shown) .................................... 183
Figure J-5: Pair of 1090 MHz DME Pulses as detected in an ADS-B Receiver.................................. 184
Figure J-6: Pair of 1085 MHz DME Pulses as detected in an ADS-B Receiver.................................. 184
Figure J-7: -84 dBm............................................................................................................................. 185
Figure J-8: -83 dBm............................................................................................................................. 185
Figure J-9: -82 dBm............................................................................................................................. 186
Figure J-10: -81 dBm........................................................................................................................... 186
Figure J-11: -80 dBm........................................................................................................................... 186
Figure J-12: -79 dBm........................................................................................................................... 187
Figure J-13: -78 dBm........................................................................................................................... 187
Figure J-14: -77 dBm........................................................................................................................... 187
Figure J-15: -76 dBm........................................................................................................................... 188
Figure J-16: -75 dBm........................................................................................................................... 188
Figure J-17: -74 dBm........................................................................................................................... 188
Figure J-18: -73 dBm........................................................................................................................... 189
Figure J-19: -72 dBm........................................................................................................................... 189
Figure J-20: -71 dBm........................................................................................................................... 189
Figure J-21: -70 dBm........................................................................................................................... 190
Figure J-22: -69 dBm........................................................................................................................... 190
Figure J-23: -68 dBm........................................................................................................................... 190
Figure J-24: -67 dBm........................................................................................................................... 191
Figure J-25: -66 dBm........................................................................................................................... 191
Figure J-26: -65 dBm........................................................................................................................... 191
Figure J-27: 1075 MHz, 42 dB Filter Attenuation; DME Pulses are not detectable in the Receiver ... 192
Figure J-28: 1080 MHz, 25 dB Filter Attenuation ................................................................................ 192
Figure J-29: 1081 MHz, 22 dB Filter Attenuation ................................................................................ 192
Figure J-30: 1082 MHz, 16 dB Filter Attenuation ................................................................................ 193
Figure J-31: 1083 MHz, 12 dB Filter Attenuation ................................................................................ 193
Figure J-32: 1084 MHz, 7 dB Filter Attenuation .................................................................................. 193
Figure J-33: 1085 MHz, 3 dB Filter Attenuation .................................................................................. 194
Figure J-34: 1086 MHz, 1 dB Filter Attenuation .................................................................................. 194
Figure J-35: 1087 MHz, 0 dB Filter Attenuation .................................................................................. 194
Figure J-36: Relative Positions of DME and ADS-B Antennas ........................................................... 195
Figure J-37: Received DME Signal Amplitude for an En-route DME Transponder ............................ 196
Figure J-38: Received DME signal amplitude for a terminal transponder........................................... 196
Figure J-39: Assumed Aircraft Distribution with Range from a Ground Receiver ............................... 197
Figure J-40: Probability of a Signal at the ADS-B Receiver having a Specific Amplitude .................. 198
Figure J-41: Elevation Angle Calculation ............................................................................................ 199
Figure K-1: Determination of the Likelihood of a Software Failure Leading to an Effect .................... 203

© EUROCAE, 2010
 1

CHAPTER 1

GENERAL

1.1 PURPOSE AND SCOPE

This Technical Specification defines the minimum technical specification for a 1090
MHz Extended Squitter (1090 ES) Ground Station. The Ground Station is part of an
Automatic Dependent Surveillance – Broadcast (ADS-B) system providing airspace
situational awareness to air traffic controllers and other users in non-radar airspaces
(NRA) in accordance with ED-126 [REF16] within the European Air Navigation
Region.
This Technical Specification for 1090 ES Ground Stations is designed to ensure that
Ground Station equipment certified to it will be compatible with aircraft Mode S
transponder equipment certified to ED-102/DO-260 or DO-260A [REF20, REF21] and
capable of satisfying the requirements specified in ED-126 [REF16].
A list of document references can be found in section 1.9.

1.1.1 Structure of this Document

Section 1 of this document provides information required to understand the need for
the equipment characteristics and tests defined in the remaining Sections. It
describes typical equipment applications and operational objectives and is the basis
for the performance criteria stated in Section 2 to Section 4. Definitions essential to
proper understanding of this document are also provided in Section 1.
Section 2 contains general design requirements.
Section 3 contains the minimum performance specification for the equipment, defining
performance under standard operating conditions.
Section 4 prescribes the environmental test conditions, which provide a laboratory
means of determining the overall performance characteristics of the equipment under
conditions representative of those, which may be encountered in actual operations.
Section 5 describes recommended test procedures for demonstrating compliance with
Sections 3 and 4.
Section 6 specifies the performance required of the installed equipment. Ground and
flight tests for the installed equipment are included when performance cannot be
adequately determined through testing under standard test conditions.

1.2 APPLICATIONS

Compliance with this Technical Specification by manufacturers, installers and users is

recommended as a means of assuring that the equipment will satisfactorily perform its
intended function(s) under all conditions normally encountered in air traffic control
surveillance operations foreseen in ED-126 [REF16].
Any regulatory application of this document in whole or in part is the sole responsibility
of appropriate government agencies.
As the measured values of equipment performance characteristics may be a function
of the method of measurement, standard test conditions and methods of test are
recommended in this document.

1.2.1 Mandating and Recommendation Phrases

1.2.1.1 "Shall"

The use of the word "Shall" indicates a mandated criterion; i.e. compliance with the
particular procedure or specification is mandatory and no alternative may be applied.
 2

1.2.1.2 "Should"

The use of the word "Should" (and phrases such as "It is recommended that...” etc.)
indicate that though the procedure or criterion is regarded as the preferred option,
alternative procedures, specifications or criteria may be applied, provided that the
manufacturer, installer or tester can provide information or data to adequately support
and justify the alternative.

1.3 BASIC ASSUMPTIONS

ASS1 The 1090 ES Ground Station is to be used to support the

ADS-B NRA application in accordance with ED-126 [REF16].
ASS2 The 1090 ES Ground Station may also be used to support
Aircraft Performance Monitoring, which is needed to ensure
that the ADS-B performance of aircraft stays conformant to
their certification.
ASS3 This specification will define the minimum functionality and
performance needed for ASS1 and ASS2.
ASS4 Requirements for other surveillance applications (such as
ADS-B RAD) are not covered in this edition of the
specification.
ASS5 The 1090 ES Ground Station is to be interoperable with all
ADS-B Mode S transmitters conformant to ED-73B/DO-181C
[REF25].
ASS6 The 1090 ES Ground Station is a component of the ground
domain as defined in ED-126 and can be used in stand-alone
mode or in association with a (multi-sensor) tracker. It can
also be part of a network of multiple ADS-B stations.
Furthermore it may be implemented as a distributed
architecture where 1090 ES reception functionality is located
remotely and the report assembly for one or more such sites
is hosted centrally in a common server. This will allow a Wide
Area Multilateration (WAM) system with the appropriate
functionality to be treated as an ADS-B Ground Station.
Tracking and data filtering or networking functions are outside
the scope of this specification. It is noted however that a
tracking function would be necessary with any stand alone
1090 ES Ground Station in order to conform to ED-126
requirements (see ED-126 Annex D) [REF16].
ASS7 The 1090 ES Ground Station can be connected to multiple
client ground systems (serving possibly different applications)
and will provide a standard interface to them based on the
ASTERIX Category 021 and 023 specifications [REF13 and
REF14] (all references to these categories in this document
are taken to include any future backward compatible
versions).
ASS8 The 1090 ES Ground Station may also optionally support
ASTERIX Category 021 Edition 0.23, ensuring compatibility
with existing surveillance data processing systems and tools.
ASS9 The 1090 ES Ground Station will provide a control and
monitoring interface based on industrial standards including at
a minimum Simple Network Management Protocol (SNMP).
ASS10 Additional capabilities such as Traffic Information Service –
Broadcast (TIS-B), multiple receivers, multilateration (notably
for integrity checking) and/or a data logging function are not
considered part of the minimum requirement.

© EUROCAE, 2010
 3

ASS11 In a service intended for ATC operational use, ASTERIX

Category 021 reports will be output only when a validated
WGS-84 position has been received. In accordance with ED-
126 [REF16], reports will not be output if only the altitude has
been received.

NOTE: All ASTERIX Category 021 and 023 references in this document refer to
the versions specified in ASS7 except where a particular version is
explicitly stated.

1.4 RELATIONSHIP TO OTHER DOCUMENTS

1.4.1 ICAO

This document considers International Civil Aviation Organisation (ICAO) material

whenever appropriate. Terminology used in this specification is consistent with ICAO
use.
• ICAO Circular 311 “Assessment of ADS-B to support Air Traffic Services
and guidelines for implementation” [REF10]
• ICAO Annex 2 [REF3], ICAO Annex 10 [REF4, REF5, REF6] and ICAO
Annex 11 [REF1]: including Standards and Recommended Practices (SARPS)
for the provision and use of ATS. Unless explicitly stated, this document
assumes the provision and use of ATS are implemented in accordance with
these SARPS.

1.4.2 Other EUROCAE/RTCA Documents

This Technical Specification is compliant with the following EUROCAE and RTCA
documents:
• EUROCAE ED-126 / RTCA DO-303h: Safety Performance and
Interoperability Requirements for ADS-B NRA Application [REF16]
• EUROCAE ED-102 / RTCA DO-260: Minimum Operational Performance
Standards for 1090 MHz Automatic Dependent Surveillance [REF20]
• RTCA DO-260A: Minimum Operational Performance Standards for 1090
MHz Automatic Dependent Surveillance [REF21]
• EUROCAE ED-73C / RTCA DO-181D: Minimum Operational Performance
Standards for Air Traffic Control Radar Beacon System/Mode Select
(ATCRBS/Mode S) Airborne Equipment [REF25]

1.5 DESCRIPTION OF SYSTEM

The 1090 ES Ground Station is part of a system that provides airspace and airport
surface situational awareness to aircraft pilots, air traffic controllers and other users.
The system provides services that are used by higher-level applications as described
below in this section. The ADS-B service collects position, velocity and status
information from systems and sensors on the aircraft and broadcasts this information
to other targets and Ground Stations. The TIS-B service collects surveillance data
from surveillance data processing sources and broadcasts it to aircraft. Figure 1
shows the system elements that support the ADS-B and TIS-B services. The TIS-B
service is not a part of the present Technical Specification and is therefore shown as
shaded in the figure.

© EUROCAE, 2010
 4

FIGURE 1: ADS-B AND TIS-B SYSTEM DIAGRAM

Radars
1090 ES
TIS-B Messages
Processing

TIS-B Reports
Surveillance
Data ADS-B Reports Airborne and Surface
ATC and Processing 1090ES Participants
other users Ground
Stations

1.5.1 ADS-B

Automatic Dependent Surveillance – Broadcast (ADS-B) is a means by which aircraft,

aerodrome vehicles and other objects can automatically transmit and/or receive
identification, position, velocity and additional data in a broadcast mode via a data link.
ADS-B is automatic because no external stimulus is required; it is dependent because
it relies on on-board navigation sources and on-board broadcast transmission systems
to provide surveillance information to other users. The aircraft originating the
broadcast will have no knowledge of which users are receiving its broadcast; any user,
either aircraft or ground based, within range of this broadcast, may choose to process
the received ADS-B surveillance information.

1.5.2 ADS-B Surveillance Applications - Package I

A first package of ground and airborne surveillance applications enabled by ADS-B

and collectively called “Package I” [REF12] was initiated in 2003 by CARE/ASAS. All
applications defined within Package I are enabled by ADS-B given a sufficient level of
equipage of aircraft broadcasting ADS-B positional information and Ground Stations
and other aircraft receiving and processing that same data.
The applications within Package I fall into two categories and are dealt with by the
Requirement Focus Group using the following terms:
ADS-B Package I Ground Based Surveillance Applications, which are:
• ADS-B-NRA Enhanced ATS in non-radar areas using ADS-B Surveillance
• ADS-B-RAD Enhanced ATS in radar areas using ADS-B surveillance
• ADS-B-APT Airport surface surveillance
• ADS-B-ADD Aircraft derived data for ATC tools

ADS-B Package I Airborne based Surveillance Applications, which are:

• ATSA-VSAEnhanced visual separation on approach
• ATSA-ITP In-trail procedure in oceanic airspace
• ATSA-AIRB Enhanced traffic situational awareness during flight operations
• ATSA-SURF Enhanced traffic situational awareness on the airport surface
• ASPA-S&M Enhanced sequencing and merging operations

© EUROCAE, 2010
 5

NOTE: ADS-B-RAD is a combination of ADS-B-ACC and ADS-B-TMA, which

defined ATC services based on ADS-B in en-route and terminal areas,
respectively in Package I.
The packaging approach is regarded as pragmatic and aims at the early
implementation of these applications on a worldwide basis.
For the purpose of this document, only the requirements derived for the ADS-B-NRA
applications have been considered in order to specify the minimum requirements and
inherent testing applicable to a 1090 ES Ground Station, for qualification purposes.
However, it is already anticipated that further versions of this document may take into
account other applications. The next version of the specification is expected to cover
ADS-B-RAD applications in addition to ADS-B-NRA.

1.5.3 The ADS-B-NRA Application

The ADS-B-NRA application as defined in ED-126 will provide enhanced Air Traffic
Services in areas where radar surveillance currently does not exist.
Examples of environments that might be candidates for the ADS-B-NRA application
include remote continental areas of low-to-medium aircraft traffic density, oceanic
airspace, areas with oilrigs or other concentrated operations, and small islands.
Further, areas now under radar coverage might have a business case for introducing
ADS-B instead of replacing aging radar systems.
The ADS-B-NRA application is designed to enhance the following ICAO Air Traffic
Services [REF2]:
a) Air Traffic Control Service and Flight Information Service principally for:
• Air traffic control separation services
• Transfer of responsibility for control
• Air traffic control clearances
• Flight information services
b) Alerting services, principally for
• Notification of rescue co-ordination centres
• Plotting of aircraft in a state of emergency
The introduction of ADS-B is expected to provide enhancements to the services
currently provided. The enhanced services are expected to be similar to the services
provided in an SSR environment. The extent of these enhancements is dependent on
the level and nature of ADS-B equipage on aircraft. The benefits will be maximised in
regions where all aircraft are ADS-B equipped.
In particular, the Air Traffic Control Service will be enhanced by providing controllers
with improved situational awareness of aircraft positions, along with the possibility of
applying separation minima smaller than those presently used with procedural
separation. The Alerting Service will be enhanced by more accurate information on the
latest position of aircraft.
Hence, it is expected that this application will provide benefits to capacity, efficiency
and safety, similar to the benefits that would be achieved by use of SSR where it is not
in use today.
Whilst the responsibilities of the controller and pilot remain unchanged, there may be a
slight impact on procedures with the introduction of surveillance services. The flight
crews will interface to the ADS-B transmitter in a similar way as to an SSR
transponder.

© EUROCAE, 2010
 6

An important distinction between operations in radar surveillance and operations in

ADS-B surveillance is that the source of the position information in ADS-B NRA is
dependent (e.g. on GNSS), and some of the hazards and/or mitigation strategies may
differ from those in a radar environment. The method of detecting failures or errors
may also differ due to the dependent nature of the position source.
ED-126 [REF16] assumes that there is no change to the controller–pilot
communications infrastructure, and that no changes are made to the existing
navigational aid infrastructure. The application is designed for use in airspace classes
A to E and complies with ATC procedures detailed in [REF2].

1.5.4 The ADS-B-RAD Application

The ADS-B-RAD application will enable an enhancement of Air Traffic Services in

areas where radar surveillance currently exists and will apply to en-route and terminal
phases of flight in airspace classes (A to E).
The introduction of ADS-B may enhance these services by improving the overall
quality of surveillance (i.e. radar + ADS-B), especially when (and where) many aircraft
become ADS-B equipped.
Benefits are expected from the improvements in quality of surveillance when ADS-B
information is added to the existing radar surveillance environment. Furthermore, in
the longer term, surveillance infrastructure costs may be reduced by replacing some of
the SSR stations required to provide multi-radar cover by ADS-B (assuming that the
costs of ADS-B sensors will be significantly less than SSR). In this scenario
consideration would need to be made of ADS-B equipage rates (in a similar way to
Mode A/C equipage rates). The intention of this application is to allow the procedures
currently using radar to be continued and enhanced by ADS-B.

1.5.5 Assumed Airborne & Ground Generic Functional Architecture

Figure 2 below presents the generic ADS-B functional architecture considered by the
Requirement Focus Group for all its applications. The elements of this architecture
that form the 1090 MHz ES Ground Station are described below in sections 1.6 and
1.7.
For the ADS-B-NRA and ADS-B-RAD applications, only the airborne ADS-B
transmission (or “ADS-B out”) domain and ground domain are pertinent, as ADS-B
information is not required to be received by other aircraft for the ground surveillance
applications.

© EUROCAE, 2010
 7

FIGURE 2: ADS-B FUNCTIONAL ARCHITECTURE

External Data Sources

(e.g., GNSS)

Receive Aircraft Domain

D A2 B2
ADS-B
Messages Aircraft sensors
Transmit Aircraft Domain (e.g., GNSS Aircraft Processing Functions
receiver)
A1 B1 C
Ownship
Surveillance
Aircraft sensors Aircraft systems Transmit
(e.g., GNSS (e.g., FMS) Processing
Receiver) Ownship (STP) of
Surveillance ADS-B SSR
Nav. Data
Transmit Transmit Replies
Processing Function
Aircraft systems (STP)
Cockpit
(e.g., FMS) Aircraft
Display of
Surveillance
ADS-B/ Traffic
ADS-B, and
TIS-B Information Flight
TIS-B Separation
Receive and Crew
Reports Assistance
Function Control
Data Sources on SSR Processing
Interrogation Panel
(ASSAP)
Transmitting Reply (CDTI)
Aircraft
ADS-B &
TIS-B
Messages E1 F1 G1
ADS-B messages and
SSR replies
TIS-B Messages

G2 F2 E2

ADS-B
Receive
Air ATC ADS-B, Subsystem TIS-B Processing
ATC
Traffic Processing Surv and other and Transmit
Display Reports Surveillance Subsystem
Co. System
Inputs
(e.g. radar)

Ground Domain

NOTE: Pilot interface corresponds to B1 on the transmitting aircraft and G1 on

aircraft receiving ADS-B information.
Figure 2 provides various functional interfaces, which have been used in ED-126 as
measurement points for the specification of Safety and Performance requirements
(e.g. D, E2).

1.6 SCOPE OF THE 1090 ES GROUND STATION

The 1090 ES Ground Station defined in this specification will not support TIS-B
services. TIS-B performance requirements necessary to support applications are
evolving and are not currently mature enough to include in an equipment specification.
A context diagram for the 1090 ES Ground Station is shown in Figure 3.

FIGURE 3: 1090 ES GROUND STATION CONTEXT DIAGRAM

Time Sync Management

Interface Interface
1090 ES Ground Station
Air Ground
Interface Interface

Operating
Environment Power

© EUROCAE, 2010
 8

The 1090ES Ground Station interfaces are:

• Time Synchronisation Interface – This interface provides time reference signals
that are used to synchronise the Ground Station’s internal timekeeping
functions with Coordinated Universal Time (UTC). UTC time is used to express
the time of applicability and/or time of message reception in ADS-B reports and
may also be used in other functions.
• Air Interface – 1090 MHz RF input is received via the Air Interface.
• Management Interface – The Management Interface is used to control,
configure and monitor the Ground Station.
• Ground Interface – ADS-B reports derived from 1090 ES messages are sent to
other ground equipment via the Ground Interface.
• Power Interface – The Ground Station receives electrical power via the Power
Interface.
• Operating Environment – The operating environment consists of physical
interfaces and constraints, heat sources and sinks, electromagnetic interference
sources and other entities that are not signal interfaces.

1.7 COMPOSITION OF EQUIPMENT

A functional block diagram of the 1090 ES Ground Station is shown in Figure 4. The
primary function of the 1090 ES Ground Station is to receive 1090 MHz RF input on
the Air Interface, extract data from the 1090 MHz ES messages, assemble the data
into ASTERIX Category 021 reports and send these reports over the Ground
Interface. Other functions support this primary function.

FIGURE 4: 1090 ES GROUND STATION FUNCTIONAL BLOCK DIAGRAM

BITE

Time Sync UTC Time GS Management & Management

Interface Synchronization Status Reporting Interface

Air Ground
1090 ES Reception Report Assembly
Interface Interface

The partitioning shown in Figure 4 is for the purpose of describing the high level
behaviour of the Ground Station and is not intended to convey an implementation
requirement. Compliant 1090 ES Ground Stations may partition the functions
differently.
This specification is not intended to dictate the physical architecture of the equipment.
For example [see ASS6] the definition of a 1090 ES Ground Station is intended to
include a distributed architecture where 1090 ES reception functionality is located
remotely and the report assembly for one or more such sites is hosted centrally in a
common server. This will allow a Wide Area Multilateration (WAM) system with the
appropriate functionality to be treated as an ADS-B Ground Station.

© EUROCAE, 2010
 9

The functional requirements of the 1090 ES Ground Station are described in Section
2.

1.8 DEFINITIONS AND ABBREVIATIONS

1.8.1 Acronyms and Abbreviations

1090 ES - 1090 MHz Extended Squitter

AC - Alternating Current
ACARS - Aircraft Communications, Addressing and Reporting System
ACAS - Airborne Collision Avoidance System
ADS - Automatic Dependent Surveillance
ADS-B - Automatic Dependent Surveillance-Broadcast
AGL - Above Ground Level
A-SMGCS - Advanced Surface Movement Guidance and Control System
ASTERIX - All Purpose Structured EUROCONTROL Surveillance Information
Exchange
ATCRBS - Air Traffic Control Radar Beacon System
ATC - Air Traffic Control
ATM - Air Traffic Management
ATS - Air Traffic Services
ATSU - Air Traffic Service Unit
A/V - Aircraft/Vehicle
AVOL - Airport Visibility Operational Level
BDS - Data Selector Code (for Comm-B)
BITE - Built-in Test Equipment
CDTI - Cockpit Display of Traffic Information
CENELEC - Comité Européen de Normalisation Electrotechnique (European
Committee for Electrotechnical Standardisation)
CMS - Control and Monitoring System
CPR - Compact Position Reporting
Comm-A - Short Uplink Communication Message (Mode S)
Comm-B - Short Downlink Communication Message (Mode S)
Comm-C - Long Uplink Communication Message (Mode S)
Comm-D - Long Downlink Communication Message (Mode S)
Comm-U - ACAS Air-Air 'Uplink' Communication Message (Mode S)
Comm-V - ACAS Air-Air 'Downlink' Communication Message (Mode S)
CRC - Cyclic Redundancy Check
DC - Direct Current
DF - Downlink Format
DME - Distance Measuring Equipment
ECAC - European Civil Aviation Conference
ERP - Effective Radiated Power

© EUROCAE, 2010
 10

ES - Extended Squitter
ETSI - European Telecommunications Standards Institute
EUROCAE - European Organisation for Civil Aviation Equipment
FAA - Federal Aviation Administration
FIS-B - Flight Information Services-Broadcast
FDPS - Flight Data Processing System
FMS - Flight Management System
FOM - Figure of Merit
fpm - Feet Per Minute
FS - Flight Status
FTC - Format Type Code (ADS-B)
GICB - Ground Initiated Comm-B
GNSS - Global Navigation Satellite System
GPS - Global Positioning System
GS - Ground Station
Hz - Hertz
IAS - Indicated Airspeed
ICAO - International Civil Aviation Organisation
IEC - International Electrotechnical Commission
IFR - Instrument Flight Rules
ILS - Instrument Landing System
IMC - Instrument Meteorological Conditions
INS - Inertial Navigation System
I/O - Input and/or Output
IP - Internet Protocol
ITC - In-Trail Climb
ITD - In-Trail Descent
ITP - In-Trail Procedure
ITU - International Telecommunication Union
JAA - Joint Aviation Authorities
JAR - Joint Aviation Requirements
LAN - Local Area Network
lb - pounds
LRU - Line Replaceable Unit
LSB - Least Significant Bit
MASPS - Minimum Aviation System Performance Standards
MA - Message Field In Comm-A (Mode S)
MB - Message Field In Comm-B (Mode S)
MC - Message Field in Comm-C (Mode S)
MD - Message Field in Comm-D (Mode S)

© EUROCAE, 2010
 11

ME - Message Field in Extended Squitter

MHz - Megahertz
MIB - Management Information Base
MLAT - Multilateration
MOPS - Minimum Operational Performance Standards
MSB - Most Significant Bit
MSL - Minimum Signal Level
MTBF - Mean Time Between Failure
MTL - Minimum Trigger Level
MTOW - Maximum Take-Off Weight
MTTR – Mean Time To Repair
MU - Message Field in Comm-U (Mode S)
MV - Message Field in Comm-V (Mode S)
NACP - Navigation Accuracy Category for Position
NACV - Navigation Accuracy Category for Velocity
NAV - Navigation
NAVAID - Navigation Aid
NIC - Navigation Integrity Category
NICBARO - Navigation Integrity Category for Barometric Altitude
NM - Nautical Mile
NOTAM - Notice to Airmen
NRA - Non Radar Airspace
NUCP - Navigation Uncertainty Category for Position
NUCR - Navigation Uncertainty Category for Velocity
Pr - Probability of Receipt
PRF - Pulse Repetition Frequency
PSR - Primary Surveillance Radar
RA - Resolution Advisory
RAIM - Receiver Autonomous Integrity Monitoring
RF - Radio Frequency
RTCA - Radio Technical Commission for Aeronautics
s - Seconds
SAC - System Area Code
SAE - Standard Aerospace Equipment
SAR - Search And Rescue
SARPS - Standards and Recommended Practices
SAT - Site Acceptance Test
SDPD - Surveillance Data Processing and Distribution system
SIC - System Identification Code
SIL - Surveillance Integrity Level

© EUROCAE, 2010
 12

SMR - Successful Message Reception

SNMP - Simple Network Management Protocol
SPI - Special Position Identification
SPR - Safety & Performance Requirements
SS - Short Squitter
SSR - Secondary Surveillance Radar
TA - Traffic Advisory
TAS - True Airspeed
TCAS - Traffic Alert and Collision Avoidance System
TCP - Trajectory Change Point
TCP - Transmission Control Protocol (an Internet Protocol)
TDOA - Time Difference of Arrival
TIS - Traffic Information Service
TIS-B - Traffic Information Service-Broadcast
TMA - Terminal Area
TOA - Time of Applicability
TOMR - Time of Message Reception
TSD - Traffic Situation Display (see also CDTI)
TSO - Technical Standards Order
TTL - Time to Live
UAV - Unmanned Air Vehicle
UDP - User Datagram Protocol (an Internet Protocol)
UF - Uplink Format
UPS - Un-interruptible Power System
U.S. - United States
UTC - Coordinated Universal Time
VFR - Visual Flight Rules
VHF - Very High Frequency
VOR - VHF Omnidirectional Radio Range
VS - Vertical Status
VSWR - Voltage Standing Wave Ratio
WAM - Wide Area Multilateration
WAN - Wide Area Network
WGS-84 - World Geodetic System 1984

© EUROCAE, 2010
 13

1.8.2 Definitions

1090 ES Ground Station - refers to the 1090 MHz ADS-B receiver, decoder,
message processing, communications output and other general functions.
1090 ES Ground Station System - refers to all of the 1090 ES Ground Station units,
LAN/WAN and data communications to ATC and local or remote Control and
Monitoring units that constitute the ADS-B System.
ADS-B - Automatic Dependent Surveillance - Broadcast. A means by which aircraft,
aerodrome vehicles and other objects can automatically transmit and/or receive
identification, position, velocity and additional data in a broadcast mode via a data link.
ADS-B Message - A packet of information broadcast by an aircraft/vehicle. Each
ADS-B message contains a defined set of aircraft/vehicle parameters. Multiple
messages may be used to transmit all required data. Message formats are link
specific, as is the number of different messages required to provide a complete set of
parameters.
Advanced Surface Movement Guidance and Control System (A-SMGCS) -
Systems providing routing, guidance, surveillance and control to aircraft and ground
vehicles in order to maintain movement rate under all local weather conditions within
the Airport Visibility Operational Level (AVOL) whilst maintaining the required level of
safety.
Aircraft Address - The term “address” is used to indicate the information field in an
ADS-B message that identifies the ADS-B unit that issued the message. The address
provides a means by which ADS-B receiving units—or end applications—can sort
messages received from multiple transmitting units. See also ICAO 24-bit address.
Algorithm - A set of well-defined rules for the solution of a problem in a finite number
of steps.
Applications - Specific uses of systems that address particular user requirements.
For the case of ADS-B, applications are defined in terms of specific operational
scenarios.
Availability - The probability that a system will perform its required function at the
initiation of the intended operation. Availability is calculated as mean time between
failures divided by the mean time between failures plus the mean time to restore
service (periods of planned maintenance are discounted from the availability figures).
MTBF/(MTBF+MTTR).
Barometric Altitude - Geopotential altitude in the earth's atmosphere above mean
standard sea level pressure datum surface, measured by a pressure (barometric)
altimeter.
Barometric Altitude Error - For a given true barometric pressure, Po, the error is the
difference between the transmitted pressure altitude and the altitude determined using
a standard temperature and pressure model at Po.
Call Sign - The term “aircraft call sign” means the radiotelephony call sign assigned to
an aircraft for voice communications purposes. (This term is sometimes used
interchangeably with “flight identification” or “flight ID”). For general aviation aircraft,
the aircraft call sign is normally its national registration number; for airline and
commuter aircraft, it is usually comprised of the company name and flight number
(and therefore not linked to a particular airframe); and for the military, it usually
consists of numbers and code words with special significance for the operation being
conducted.
Cockpit Display of Traffic Information (CDTI) - A function that provides the
pilot/flight crew with surveillance information about other aircraft, including their
position. The information may be presented on a dedicated multi-function display
(MFD), or be processed for presentation on existing cockpit flight displays. Traffic
information for the CDTI function may be obtained from one or multiple sources
(including ADS-B, TCAS and TIS) and it may be used for a variety of purposes.

© EUROCAE, 2010
 14

Continuity of Service - The probability that a system will perform its required function
without unscheduled interruption throughout the duration of the intended operation,
assuming that the system is available when the operation is initiated. Continuity is
expressed per unit time.
Coverage Area - The geographic area of interest within which the system must
provide surveillance of the targets.
Desensitisation - A temporary reduction of receiver sensitivity after receipt of a
signal. May be used to reduce echo (multipath) effects.
Detection - Detection is defined as successful calculation of a valid target position.
Downlink - A signal propagated from the transponder.
Dynamic Range - ratio between the overload level and the minimum triggering level
in a receiver.
En-Route - A phase of navigation covering operations between the departure and
termination phases. The en-route phase of navigation has two subcategories: en-route
domestic/continental and enroute oceanic.
Extended Squitter - a long squitter message (DF = 17, 18 or 19) that transponders
transmit automatically, without needing to be interrogated by radar, to send
information to other aircraft or Ground Stations.
Field - A group of bits in a message treated as a single unit of information.
Format - The specific order in which fields of information appear in an ADS-B or other
digital message transmission.
FRUIT - Transponder replies unsynchronised in time. See Garble, Non-synchronous.
Garble, Non-synchronous - Interfering reception of two or more transmissions. Reply
pulses received from a transponder that is being interrogated from some other source
are also called FRUIT.
Geometric Height - The minimum altitude above or below a plane tangent to the
earth’s ellipsoid as defined by WGS-84.
Geometric Height Error - Geometric height error is the error between the true
geometric height and the transmitted geometric height.
Global Navigation Satellite System (GNSS) - GNSS is a worldwide position,
velocity, and time determination system, that includes one or more satellite
constellations, receivers, and system integrity monitoring, augmented as necessary to
support the required navigation performance for the actual phase of operation.
ICAO 24-bit Address - The unique address by which each aircraft's transponder can
be identified. Sometimes referred to as “Mode S address”.
Integrity - An attribute of a system or an item indicating that it can be relied on to
perform correctly on demand. It includes the ability of the system to inform the user in
a timely manner of any performance degradation.
Latency - The amount of time it takes to deliver data from one interface point to
another interface point. The latency of an ADS-B transmission is the time period from
the time of applicability of the aircraft/vehicle ADS-B message until the transmission of
that ADS-B message is completed. The latency of the 1090 ES Ground Station is the
time period from the reception of an ADS-B message to the output of the
corresponding target report.
Latency Compensation - High accuracy applications may correct for latency-
introduced position errors by using time synchronised ADS-B position and velocity
information.
Line Replaceable Unit (LRU) - refers to a replaceable unit within the 1090 ES
Ground Station. This might for example be a receiver.

© EUROCAE, 2010
 15

Message - An arbitrary amount of information whose beginning and end are defined
or implied. See also ADS-B Message.
Minimum Triggering Level (MTL) - The minimum input power level that results in a
90% successful reception ratio if the received messages are correctly formatted with
nominal pulse spacing and width.
Mode A/C - For the purpose of this document, Mode A/C is taken as referring to non-
Mode S SSR transactions. Where specific Mode A or Mode C transactions are
involved, these are identified individually. NOTE: non-Mode S SSR is also known as
ATCRBS (Air Traffic Control Radar Beacon System).
Mode S - A selective addressing mode of the Secondary Surveillance Radar (SSR)
system that operates using addressed interrogations on 1030 MHz and transponder
replies on 1090 MHz. Mode S also supports a two-way data link and an ADS-B
service known as Extended Squitter.
Multilateration - Multilateration is the process of determining the target location in two
(or three) dimensions by solving the mathematical intersection of multiple hyperbolas
(or hyperboloids). It is based on the TDOA principle, the Time Difference Of Arrival of
a message from a transponder at several different receivers.
Multipath - The propagation phenomenon that results in signals reaching the
receiving antenna by two or more paths, generally with a time or phase difference.
Navigation Uncertainty Category (NUC) - Uncertainty categories for the state vector
navigation variables are characterised by a NUC data set provided in the ADS-B
sending system. The NUC includes both position and velocity uncertainties.
Protocol - A set of conventions between communicating processes on the formats
and contents of messages to be exchanged.
Reception Ratio - The ratio of the number of successfully received messages to the
number of transmitted messages
Reliability - The probability of performing a specified function without failure under
given conditions for a specified period of time.
Resolution - The smallest increment reported in an ADS-B message or output report
field.
Special Position Identification (SPI) - A special pulse used in Mode A/C replies,
located 4.35 μs after the second framing pulse. When used with Mode S, SPI appears
as a code in the Flight Status (FS) field. In 1090 ES it appears in the Surveillance
Status field of airborne position messages.
Squitter - A spontaneous transmission generated at a pseudo random rate or on an-
event driven basis by a transponder without the need to be interrogated.
State Vector - An aircraft or vehicle’s current kinematic state.
Surveillance - A function of the system that provides identification and accurate
positional information on aircraft, vehicles and objects within the required area.
System Capacity - the minimum number of targets that the system must process
within a specified time interval.
Target - For the purposes of this document, a target is specifically defined as any
vehicle or aircraft equipped with an ADS-B capable transponder or equivalent, which
has been turned on and is functioning in compliance with its Minimum Operating
Performance Standards.
Target Report - A data record containing all relevant information pertaining to a target
detected by the Ground Station.
Terminal Area (TMA) - A general term used to describe airspace in which an
approach control service or airport traffic control service is provided.
Track - A progressive series of estimates of a target position.

© EUROCAE, 2010
 16

Time of Applicability - The time at which the data (e.g. position data) contained in an
ADS-B message is assumed to be valid. This time may be different for different data
links and is specified in ADS-B link MOPS
Track Angle - Instantaneous angle measured from either true or magnetic north to the
aircraft's track.
Transmission Rate - The sustained rate at which periodic messages are transmitted.
Trajectory Change Point (TCP) - TCPs provide tactical information specifying
space/time points at which the current trajectory of the vehicle will change. This
change in vehicle trajectory could be in the form of a change in altitude
(climb/descent), a change in heading, a change in airspeed (increase/decrease), or
any combination thereof.
Uplink - A signal propagated toward a transponder.
Wide Area Multilateration - A multilateration system designed for use in TMA or En-
Route airspace, as compared to airport surface applications (see A-SMGCS).
World Geodetic Survey (WGS) - A consistent set of parameters describing the size
and shape of the earth, the positions of a network of points with respect to the centre
of mass of the earth, transformations from major geodetic datums, and the potential of
the earth (usually in terms of harmonic coefficients).
World Geodetic System 1984 (WGS-84) - A set of quantities, developed by the U.S.
Department of Defense for determining geometric and physical geodetic relationships
on a global scale, based on a geocentric origin and a reference ellipsoid with semi-
major axis 6378137 and flattening 1/298.257223563

1.9 REFERENCES

1.9.1 ICAO

REF1 “Air Traffic Services”, ICAO, Annex 11 to the convention on International

Civil Aviation, Thirteenth edition, July 2001.
REF2 “Air Traffic Management”, ICAO, Procedures for Air Navigation Services,
Document 4444, Fourteenth edition - proposal to update Amendment 4 to
include ADS-B procedures in Chapter 8 ‘Surveillance Services’.
REF3 Annex 2, Rules of the Air.
REF4 Annex 10, Aeronautical Telecommunications - Volume II (Communications
Procedures including those with PANS status).
REF5 Annex 10, VOL III Amendment 80.
REF6 Annex 10, VOL IV, including proposed amendment 82.
REF7 Doc 8400, ABC - ICAO Abbreviations and Codes.
REF8 Annex 15, Aeronautical Information Services.
REF9 Annex 6, Operation of Aircraft, Part I - International Commercial Air
Transport – Aeroplanes.
REF10 Circular 311 “Assessment of ADS-B to support Air Traffic Services and
guidelines for implementation“.

1.9.2 EUROCONTROL

REF11 EUROCONTROL Standard Document for Radar Surveillance in En-Route

Airspace and Major Terminal Areas.
REF12 Description of a First Package of GS/AS Applications, CARE/ASAS Ref. CA-
02-040(2.2), version 2.2, September 2002
REF13 EUROCONTROL Standard Document for Surveillance Data Exchange Part
12: Category 021 ADS-B Messages, Edition 1.4, June 2009

© EUROCAE, 2010
 17

REF14 EUROCONTROL Standard Document for Surveillance Data Exchange Part

16: Category 023 CNS/ATM Ground Station Service Messages, Edition 1.2,
April 2009
REF15 EUROCONTROL Standard Document for Surveillance Data Exchange Part
20: Category 247 Version Number Exchange, Edition 1.2, July 2008

1.9.3 EUROCAE/RTCA

REF16 EUROCAE ED-126 / RCTA DO-303h: Safety, Performance and

Interoperability Requirements Document for ADS-B NRA Application,
December 2006
REF17 EUROCAE ED-78A / RTCA DO-264: Guidelines for Approval of the
Provision and Use of air Traffic Services Supported by Data
Communications, March 2002.
REF18 RTCA DO-283A: Minimum Operational Performance Standards for Required
Navigation Performance for Area Navigation, October 28, 2003
REF19 EUROCAE ED-120 / RTCA DO-290: Safety and Performance Requirements
for Air Traffic Data Link Services in Continental Airspace, May 2004
REF20 EUROCAE ED-102 / RTCA DO-260: Minimum Operational Performance
Standards for 1090 MHz Automatic Dependent Surveillance – Broadcast
(ADS-B) and Traffic Information Services (TIS-B)
REF21 RTCA DO-260A: Minimum Operational Performance Standards for 1090
MHz Automatic Dependent Surveillance – Broadcast (ADS-B) and Traffic
Information Services (TIS-B)
REF22 RTCA DO-208: Minimum Operational Performance Standards for Airborne
Supplemental Navigation Equipment Using Global Positioning System
(GPS)
REF23 RTCA DO-229C: Minimum Operational Performance Standards for Global
Positioning System/Wide Area Augmentation System Airborne Equipment
REF24 RTCA DO-242A: Minimum Aviation System Performance Standards for
Automatic Dependent Surveillance Broadcast (ADS B)
REF25 EUROCAE ED-73C / RTCA DO-181D: Minimum Operational Performance
Standards for Air Traffic Control Radar Beacon System/Mode Select
(ATCRBS/Mode S) Airborne Equipment
REF26 EUROCAE ED-12B / RTCA DO-178B: Software Considerations in Airborne
Systems and Equipment Certification
REF27 EUROCAE ED-114: MOPS for Global Navigation Satellite GBAS Ground
Equipment to support Category I operations
REF28 EUROCAE ED-117: MOPS for Mode S Multilateration Systems for Use in A-
SMGCS
REF29 EUROCAE ED-109: Guidelines For Communication, Navigation,
Surveillance, And Air Traffic Management (CNS/ATM) Systems Software
Integrity Assurance

1.9.4 ETSI

REF30 ETSI EN 300 019. Environmental conditions and environmental tests for
telecommunications equipment

1.9.5 Miscellaneous

REF31 C. Tamvaclis, A. Parkinson, and A. Woogara, 1090 MHz NRA Interference

Study, Version 1.0, Jan 2007
REF32 Michael C. Stevens. Secondary Surveillance Radar.

© EUROCAE, 2010
 18

CHAPTER 2

GENERAL DESIGN REQUIREMENTS

2.1 INTRODUCTION

This Section establishes the design considerations and general specification for the
equipment comprising the 1090 ES Ground Station.

2.2 1090 ES GROUND STATION SERVICES

The 1090 ES Ground Station provides ADS-B Services to client systems connected to
it via a data communications network. An ADS-B Service consists of the provision of
ADS-B reports in ASTERIX Category 021 format for 1090 MHz Extended Squitter
ADS-B targets within a defined geographic area and/or service volume, with a given
reporting mode (data driven or periodic) and a given reporting rate (in periodic mode).
Additionally, ADS-B Services include the periodic provision of Ground Station Status
reports and ASTERIX Version reports in ASTERIX Category 023 and 247 format,
respectively. Ground Station Status reports indicate to the client system the status of
the Ground Station and the characteristics of the ADS-B service provided. ASTERIX
Version reports indicate the ASTERIX message format version used for ADS-B
reports. These report types are specified in further detail in section 3.10 of this
specification.
Optionally a 1090 ES Ground Station may provide distinct ADS-B Services to distinct
groups of client systems. In that case each ADS-B Service will be configurable
independently of the other ADS-B Services and will include its own Ground Station
Status, Service Status and ASTERIX Version reports.
The minimum configuration items required per ADS-B Service may be found in
APPENDIX A, subsection 1.
The present specification considers only the minimum case of a 1090 ES Ground
Station providing a single ADS-B Service.

2.3 1090 ES GROUND STATION MODES AND STATES

The 1090 ES Ground Station has various modes and states. Modes are commanded
by an operator, while a state is a property of the Ground Station which the Ground
Station will determine automatically based on BITE results.

2.3.1 1090 ES Ground Station Modes

Two modes are defined for the Ground Station: Operational and Maintenance.
Maintenance mode is used for changing the configuration of the Ground Station.
Configuration changes are not permitted in Operational mode.

2.3.2 1090 ES Ground Station States

This section uses a state machine to help the reader understand the external
behaviour. The method of implementing such behaviour, including the use of the state
machine, is optional and may be chosen by the manufacturer. The required external
behaviour is described in chapter 3.
Three states are defined for the 1090 ES Ground Station: Initialisation, On-Line and
Failed.
The Initialisation state is entered on power up.
Following completion of the power-on self-test, the Ground Station enters either the
On-Line state or the Failed state depending on the result of BITE.

© EUROCAE, 2010
 19

The On-Line state is the normal operating state of the Ground Station. It indicates that
it is either providing an operational service meeting the minimum performance
requirements, or is capable of doing so.
The Failed state is entered when an error condition is detected that means that the
minimum operational performance requirements cannot cannot be met.
The Ground Station does not enter the Failed state as a result of warning conditions.
NOTE: The Ground Station may transition automatically from the Failed state to
the On-Line state if a transient failure has cleared such that no BITE test
any longer reports a failure condition.
This specification does not exclude the possibility of sub-states. For example the
Ground Station may have “On-Line: Normal” and “On-Line: Degraded” sub-states
which are contained within the On-Line state.

FIGURE 5: 1090 ES GROUND STATION STATES

Initialisation

successful completion a fault detected in

of power-on self test power-on self test

BITE
reports
a fault
On-line Failed

BITE no longer reports a fault

2.3.3 Time Source States

This section uses a state machine to help the reader understand the external
behaviour. The method of implementing such behaviour, including the use of the state
machines, is optional and may be chosen by the manufacturer. The required external
behaviour is described in chapter 3.
Three states are defined with respect to UTC synchronisation (see section 2.4.3).
These states are: Not Coupled, UTC Coupled and Coasting.
The Not Coupled state indicates that the Ground Station is not synchronised to a UTC
time source and is not providing valid UTC time.
The UTC Coupled state indicates that the Ground Station is synchronised to a UTC
time source and is providing valid UTC time.
The Coasting state indicates that the Ground Station is no longer synchronised to a
UTC time source but is able to maintain UTC time internally with the required
accuracy. When this accuracy can no longer be maintained the Time Source state
reverts to Not Coupled.

© EUROCAE, 2010
 20

When power is first applied to the system or when there is a system reset, the UTC
Time State is "Not Coupled." After a valid UTC time has been obtained, the UTC Time
State becomes "UTC Coupled." If the UTC time reference degrades or is lost while in
the "UTC Coupled" state, the state changes to "Coasting." The coasting state
continues until the Ground Station is no longer able to assure the required UTC time
accuracy. The operation of the UTC Time State machine is depicted in Figure 6.
NOTE:
For the transition from Coasting to Not Coupled the manufacturer must
ensure that the transition occurs before the required UTC performance is
lost. This may be implemented through a fixed timeout that is validated or
by a method of monitoring the performance.

FIGURE 6: UTC TIME STATE MACHINE

UTC Time State

Not Coupled

Coasting GS capable of
timeout timestamping with
exceeded required accuracy
UTC
reference
reacquired UTC Coupled
or accuracy
restored UTC reference lost or
accuracy degraded

Coasting

2.4 FUNCTIONAL REQUIREMENTS

The 1090 ES Ground Station provides at least the following functions:

a) 1090 ES Reception and Decoding: Reception of 1090 MHz RF and extraction
of Extended Squitter messages broadcast by ADS-B Out transponders;
b) Report Assembly: Compilation of ADS-B reports to be forwarded to third party
client ground systems (e.g. ADS-B servers, SDPD, etc.);
c) UTC Time Synchronisation: UTC time synchronisation of the 1090 ES Ground
Station for output report time stamping;
d) Ground Station Management and Status Reporting: Station management,
monitoring and control functions, and service status, including Built In Test
Equipment (BITE).
The characteristics of each of the above functions are detailed below.

© EUROCAE, 2010
 21

2.4.1 1090 ES Reception and Decoding Function

This function handles the reception and decoding of 1090 MHz Extended Squitter
messages transmitted over the 1090 MHz channel, including integrity checking. It
therefore consists of a reception and demodulation sub-function and a decoder sub-
function.
It is supported by one or more 1090 MHz antennas, which are designed such that the
1090 ES Ground Station is capable of performing its intended functions.
The reception and demodulation sub-function is designed to receive, and process in
real time, 1090 MHz Extended Squitter RF Signals conformant to the RTCA MOPS for
1090 MHz ES ADS-B (DO-260 and DO-260A) [REF20, REF21] and EUROCAE ED-
102 [REF20] from airborne aircraft operating in Non-Radar Airspace.
The decoding sub-function should be capable of receiving and processing Extended
Squitter messages of Downlink Format (DF) 17, 18 (CF = 0 or CF = 1) and 19 (AF = 0)
including at least the following types:
• Airborne Position (FTC = 9-18 and 20-22)
• Aircraft Identification and Type (FTC = 1-4)
• Airborne Velocity (subtypes 1-4, FTC = 19)
• Test Messages – Mode A Code (sub-type 7, FTC = 23)
• Aircraft Status (subtype 1, FTC = 28)
• Target State and Status (subtype 0, FTC = 29)
• Aircraft Operational Status (subtypes 0-1, FTC = 31)
NOTE: It is not necessary to process Airborne Position messages with FTC = 0
(see ASS11 in section 1.3).
NOTE: Surface Position messages (FTC = 5-8) may optionally be processed.
The full requirements for the processing of ADS-B messages are described in Section
3.10 of this specification.

2.4.2 Report Assembly Function

This function processes the information extracted from received Extended Squitter
messages by the ADS-B Message Reception and Decoding function, and assembles
ASTERIX Category 021 reports in real time. Each report refers to a single target and
contains the latest information available. ASTERIX reports are transmitted over a
ground network to client systems.
ASTERIX Category 021 reports include information that has to be extracted from
multiple Extended Squitter messages. The ADS-B Report Assembly function performs
all the necessary correlation, data age tracking and data conversion operations which
are required to assemble and translate squitter information to ASTERIX Category 021
format, using the mapping specified in Section 3.10.
The ADS-B Report Assembly function can be configured to produce ASTERIX
Category 021 reports either in Data Driven (Real Time) mode, or in Periodic mode as
described in Section 3.10.2.

© EUROCAE, 2010
 22

2.4.3 UTC Time Synchronisation Function

The 1090 ES Ground Station should ensure autonomous, reliable and accurate UTC
time stamping of the generated ASTERIX reports. For this purpose the 1090 ES
Ground Station should include a sufficiently reliable and accurate UTC time reference
source, or alternatively it should be able to interface to an external standard UTC time
source of equivalent quality. The internal or external time source supplies all the data
necessary for the establishment of the UTC times of reception of position and velocity
information.

2.4.4 Ground Station Management and Status Reporting Function

The 1090 ES Ground Station is intended to operate unattended and autonomously. It

must however provide a monitoring, maintenance and control function allowing an
operator to:
• Monitor the Ground Station status, and the status of each subsystem and
service, including BITE and end-to-end system checks;
• Perform maintenance, configuration, and control actions, including changes of
mode for the Ground Station.
The 1090 ES Ground Station should provide protection against unauthorised access
to the system maintenance and control functions.

2.4.4.1 Status Reports

The 1090 ES Ground Station includes a status reporting function, which reports the
status of the Ground Station and its services to client systems over a ground network.
These status reports will use the ASTERIX Category 023 message format.
Status reports are generated periodically, with a configurable reporting period.
Reports are also generated immediately following any change in the status of a 1090
ES Ground Station function or subsystem.

2.4.4.2 BITE Function

The 1090 ES Ground Station includes a Built In Test Equipment (BITE) capability,
such that there is a continuous monitoring of the operating status of the equipment,
which is achieved by the monitoring and analysis of critical system parameters at all
relevant system levels.
The 1090 ES Ground Station BITE is able to detect faults affecting the performance of
the Ground Station. BITE should register the faulty equipment (at LRU level) locally at
the system and notify the monitoring, logging, and control subsystems accordingly.
The BITE tests include an end-to-end system check including the RF input to the
antenna. This check may make use of a Site Monitor, which is an external 1090 ES
ADS-B emitter, allowing an overall integrity check of the system including the antenna.
The 1090 ES Ground Station executes BITE tests both at start-up and periodically.
The tests should be summarised in the form of an overall BITE status signal to be
used for failure indications to the operator and to client systems.
The behaviour of the Ground Station when a failure is detected is described in Section
3.9.3.
In addition to BITE the 1090 ES Ground Station may also support diagnostics and
other relevant tests, including manual runs of built-in tests.

© EUROCAE, 2010
 23

2.5 EQUIPMENT DESIGN ASSURANCE

The safety assessment in ED-126 [REF16] is relied on in this Technical Specification.

Appropriate assurance means must be used (such as ED-109 [REF29]). The required
software integrity level is ED-109 AL4 on the basis of the ED-126 requirements. An
additional integrity check is required as specified in Section 3.6.

2.6 ADDITIONAL REQUIREMENTS

2.6.1 Power Supply

The power supply requirements may vary depending upon application and location.
The following specifications are provided as guidance to be considered by the
implementing authority. It should be noted that it may not be necessary to include
each of the following as requirements, but only those that pertain to the power supply
being used. Consideration should also be given to the use of Uninterruptible Power
Supplies (UPS), with appropriate monitoring as necessary, to meet Operational
Availability requirements
The 1090 ES Ground Station may operate from any of the following power supplies:
• A 230V ± 10% AC power supply with a nominal frequency of 50 Hz ± 2Hz.
• A 24V ± 20% DC power supply.
• A 48V ± 20% DC power supply.

2.6.2 Receiver Selectivity

When designing the receiver, consideration should be given to protection from

interference from out-of-band signals such as DME. Table 1 shows receiver out-of-
band rejection characteristics that are extensively used within the industry. It shows
the 1090 ES Ground Station ADS-B message signal level required to provide a 90%
Successful Message Reception rate at various frequency offsets from 1090 MHz.

TABLE 1: OUT OF BAND CHARACTERISTICS

Frequency Offset Minimum Input Level Above Specified Receiver

from 1090 MHz Sensitivity (90% SMR)
±5.5 MHz 3 dB
±10.0 MHz 20 dB
±15.0 MHz 40 dB
±25.0 MHz 60 dB

Alternative out-of-band rejection characteristics may be used provided that the

performance requirements of Section 3 are met. For example the characteristics
shown in Table 2 may be suitable for a receiver that is used for both ADS-B and
multilateration.

© EUROCAE, 2010
 24

TABLE 2: ALTERNATIVE OUT OF BAND CHARACTERISTICS

Minimum Input Level

Frequency Offset Above Specified
from 1090 MHz Receiver Sensitivity
(90% SMR)
±12.5 MHz 3 dB
±19.0 MHz 20 dB
±29.0 MHz 40 dB
±46.0 MHz 60 dB

© EUROCAE, 2010
 25

CHAPTER 3

MINIMUM PERFORMANCE SPECIFICATION UNDER STANDARD CONDITIONS

3.1 INTRODUCTION

3.1.1 Equipment Classes

It is not considered necessary to define different classes of 1090 ES Ground Station

equipment at this time. Two or more classes of equipment may be defined in future
versions of this specification however, based on performance criteria such as range.

3.1.2 Antenna

The RF performance specifications in this Section assume that the Ground Station
equipment is connected to a Reference Antenna having the characteristics in sections
3.1.2.1 to 3.1.2.3 below. The rationale of the Reference Antenna is described in
APPENDIX G.
NOTE: The actual gain characteristics chosen for the Reference Antenna are not
important, as it is being defined purely to form part of a theoretical analysis.
The antenna gain does however affect figures such as MTL that are
included in this Technical Specification, and so has been kept within a
realistic range in order to avoid confusion.

3.1.3 Horizontal Pattern

The antenna pattern is nominally omni-directional in the horizontal plane.

3.1.4 Gain

The antenna gain is 0 dB with respect to isotropic.

3.1.5 Frequency

The antenna receives signals on the nominal operating frequency of 1090 MHz.

3.2 COVERAGE AND DETECTION

3.2.1 Coverage

Surveillance coverage is defined in ED-126 [REF16] as the geographical volume in

which all the required service surveillance attributes can be provided. In the case of
ADS-B ground based surveillance, coverage depends upon the detection range,
location and number of ADS-B Ground Stations. The detection range of a 1090 ES
Ground Station depends on the FRUIT environment and on the Ground Station’s
receiver configuration (single or multiple receivers), sensitivity, antenna type(s) and
siting considerations.
In practice, coverage requirements are determined by local operational environment
considerations. For this reason ED-126 does not state any requirements concerning
the size of the coverage volume which could be translated into a detection range
requirement for the 1090 ES Ground Station. It is therefore considered inappropriate
to specify a detection range requirement in this specification. Instead the minimum
receiver sensitivity is specified in section 3.11 based on the reference link budget
specified in APPENDIX F.

© EUROCAE, 2010
 26

3.2.2 Performance in the presence of 1090 MHz Interference

APPENDIX I contains an analysis based on the worst-case scenario from

EUROCONTROL’s European NRA FRUIT study [REF31], which itself is summarised
in APPENDIX H. This analysis shows that the expected FRUIT rate in the worst case
NRA environment will be low enough that approximately 1 in 3 messages will still be
correctly decoded, even without any special provision in the decoder to cope with
FRUIT. This is sufficient to meet the Probability of Detection requirements in ED-126
[SPR-19 to 26].
The preceding paragraph applies to use of the 1090 ES Ground Station in Non-Radar
Airspace only. Where the Ground Station is used within other applications, improved
decoding performance may be required.

3.3 SYSTEM CAPACITY

3.3.1 Overall Capacity

In accordance with ED-126 [REF16], system capacity refers to the maximum number
of aircraft for which all the service surveillance performance parameters must be
provided. ED-126 Requirement PR 41 (Annex B, section B.4.5.2) states that the
ground segment of the system shall have the capacity to handle the reports from the
maximum load of aircraft in the environment as described in ED-126 Annex A, section
A.2.4 (i.e. a maximum instantaneous count of traffic of 15 aircraft en-route and 7 in
TMA).
In ECAC, NRA airspaces are generally underneath RAD airspaces and the number of
aircraft that a ground ADS-B station would have to handle can be much larger than the
ED-126 minimum requirement.
Consequently the 1090 ES Ground Station shall have the capacity to:
a) Simultaneously process 1090 MHz ADS-B messages from at least 300
individual airborne targets, transmitting such messages at the standard rates
defined in DO-260/A [REF21], and
b) Output corresponding ASTERIX Category 021 reports at a maximum event
driven rate of four ASTERIX Category 021 reports per target per second, unless
constrained by Ground Station configuration, while meeting the latency
requirements specified in Section 3.4.

3.3.2 Target Overloads

An overload mechanism shall be provided to detect when the number of targets

exceeds a configurable capacity threshold. When the threshold is exceeded the 1090
ES Ground Station shall set the ODP bit in item I023/100 of ASTERIX Category 023
Ground Station Status reports.

3.3.3 Communications Overloads

1
The 1090 ES Ground Station shall include the capability to detect communications
overloads. When such an overload is detected, the 1090 ES Ground Station shall set
the OXT bit in item I023/100 of ASTERIX Category 023 Ground Station Status reports.

3.3.4 Overload Mitigation

Optionally the 1090 ES Ground Station may act to mitigate an overload condition, for
example by reducing sensitivity or range of coverage. However, such mitigation
actions are outside the scope of this specification.

1
This condition might be detected as output buffer overload which may be implemented by counting UDP output
bytes per second to ensure that it does not overload a downstream link.

© EUROCAE, 2010
 27

3.4 SYSTEM LATENCY

The maximum latency from the time of receipt of a 1090 ES message sent by the
transponder on board an aircraft to the output of the corresponding ASTERIX
Category 021 report shall be 0.5 seconds for all targets within the service volume up
to the maximum stated in ED-126 and under the worst case FRUIT environment
specified in APPENDIX H.
This requirement, which is derived from ED-126, shall apply to all data-driven
ASTERIX Category 021 reports. It does not apply to reports generated in periodic
mode.

3.5 CONTINUITY

ED-126 defines continuity as the probability that a system will perform its required
function without unscheduled interruption, assuming that the system is available when
the function is initiated, and states that continuity requirements for ground equipment
are left to local authorities.
Consequently this 1090 ES Ground Station specification does not set any specific
continuity requirements. Vendors should expect that continuity requirements might
vary depending on local implementation needs and the architecture of the local ground
ADS-B infrastructure.

3.6 INTEGRITY

Based on the system integrity level defined in ED-126, the 1090 ES Ground Station
Software Assurance Level shall be equivalent to at least ED-109 level AL4.
5
The decoder undetected message error rate shall be better than 1 in 10 messages.
An undetected message error is assumed for the purposes of this requirement to be
one which results in an error in either a position or a position quality field in an
ASTERIX Category 021 position report. The analysis leading to these requirements is
included in APPENDIX C.

3.7 ACCURACY

3.7.1 Time of Applicability Accuracy

Time of Applicability is output only when the T bit is set to 1 in the incoming 1090 ES
position messages.
ED-126 SPR 17 requires that the Time of Applicability for Position output by the 1090
ES Ground Station in ASTERIX Category 021 reports shall have an absolute accuracy
relative to UTC of ±0.2 seconds or less. This ED-126 requirement is met by the
provisions of section 3.10.4.8, since when T=1 the GS can determine the precise 0.2
second UTC epoch that the incoming position message is associated with.

3.7.2 Time of Message Reception Accuracy

The absolute accuracy of the Time of Message Reception items for position and
velocity relative to UTC shall be ±25 milliseconds or less. The 1090 ES Ground
Station shall be able to maintain this level of accuracy in the coasting state for at least
30 minutes.

3.7.3 Data Accuracy

Position, velocity, altitude and other data shall be reported as received from the
aircraft without loss of accuracy, when allowed by the ASTERIX Category 021 format.
Where an ASTERIX report field has a different resolution from the corresponding data
field in a 1090 ES ADS-B message, the value included in the ASTERIX report shall be
of no greater resolution than the value received from the aircraft.

© EUROCAE, 2010
 28

3.8 AVAILABILITY

In accordance with ED-126, availability is considered to be a part of reliability, and is

defined as the probability that a system will perform its required function at the
initiation of the intended operation.
NOTE: While availability is defined in paragraph B.4.4.1 of ED-126, availability
requirements are not specified for the ground system in ED-126.
Availability is quantified as the ratio of the time the system is actually available to the
time the system is planned to be available.
MTBF
Availability =
MTBF + MTTR
MTBF: Mean Time Between Failure
MTTR: Mean Time To Repair
The 1090 ES Ground Station shall achieve an Availability of 99.99%.
Assumptions:
MTTR is based on time to repair assuming all required tools, spares and procedures
are available on site and personnel are suitably trained and experienced. Travel time
is excluded.
Periods of planned maintenance are discounted from the availability figures.
The Availability requirement applies to the 1090 ES Ground Station as defined in this
specification only. External equipment such as antenna, cables and power supplies
are not included.

3.9 EQUIPMENT CONTROL AND STATUS

3.9.1 Assumptions

The 1090 ES Ground Station will be polled for its monitoring data using Simple
Network Management Protocol (SNMP), at a frequency that will depend on system
performance criteria.
Polling will form part of an ADS-B Ground Station health check mechanism, which is
performed by a connected central Control & Monitoring system, which is outside the
scope of this Technical Specification.
If the downstream monitoring system does not receive a response to a poll request, it
will re-send the request.

3.9.2 General

The 1090 ES Ground Station system shall provide an external control and monitoring
interface utilising the Simple Network Management Protocol (SNMP).
The supplier of the ADS-B system shall provide the Management Information Base
(MIB), used to locate data within the ADS-B system.

3.9.2.1 1090 ES Ground Station Modes

Two modes are defined for the 1090 ES Ground Station: Operational and
Maintenance.
The transition between Operational and Maintenance mode, and between
Maintenance and Operational mode, shall occur only as the result of a manual
command from an operator.
The 1090 ES Ground Station shall not allow configuration changes while in
Operational mode.

© EUROCAE, 2010
 29

After power-on initialisation, the 1090 ES Ground Station shall enter the mode it was
previously in before power-off.

FIGURE 7: 1090 ES GROUND STATION MODES

power-on initialisation

Manual
Command
Maintenance Operational

Manual
command

3.9.3 Monitoring Functions (Local & Remote)

3.9.3.1 Status Reporting

a) The mode of the 1090 ES Ground Station shall be made available to the SNMP
interface.
b) The operational state of the 1090 ES Ground Station shall be made available to
the SNMP interface.
c) If the Ground Station incorporates redundant LRUs to meet the Availability
requirement defined in 3.8, then the status of each LRU shall be made available
to the SNMP interface.
d) When the 1090 ES Ground Station is in the Failed state the NOGO bit in item
I023/100 of ASTERIX Category 023 Ground Station Status reports shall be set
to 1, and the STAT field in item I023/110 of Service Status reports shall be set
to “Failed”.
e) When the 1090 ES Ground Station is in the Initialisation state, including the
period up until the UTC Time Source becomes UTC Coupled for the first time,
the NOGO bit in item I023/100 of ASTERIX Category 023 Ground Station
Status reports shall be set to 1, and the STAT field in item I023/110 Service
Status reports shall be set to “Initialisation” in any ASTERIX Category 023
messages sent.
f) When the 1090 ES Ground Station is in the Online state, the NOGO bit in item
I023/100 of ASTERIX Category 023 Ground Station Status reports shall be set
to 0 if the Ground Station is in the Operational mode, or 1 if it is in Maintenance
mode. The STAT field in item I023/110 Service Status reports shall be set to
“Normal”.
g) By default the 1090 ES Ground Station shall not output ASTERIX Category 021
reports in Maintenance mode or in the Initialisation or Failed state. If however
the Ground Station is capable of being configured to output such reports for
diagnostic purposes, the NOGO bit in Item 021/040 shall be set to 1 and the CL
field shall also be set to 1 while in Maintenance mode or in the Initialisation or
Failed state.
NOTE: A summary of BITE tests and corresponding states and actions can be
found in APPENDIX B.

© EUROCAE, 2010
 30

TABLE 3: MAPPING OF THE 1090 ES GROUND STATION STATUS INTO ASTERIX CATEGORY
023

GS Status ASTERIX ASTERIX Category 023 output

Category 021
Mode Operational Time State Output NOGO STAT TSV
State
- Initialisation - No Output 1 5 (Initialisation) 1
2
UTC Coupled No Output 1 4 (Normal) 0
2
On-line Coasting No Output 1 4 (Normal) 0
1 2
Not Coupled No Output 1 1 (Failed) 1
Maintenance 2
UTC Coupled No Output 1 1 (Failed) 0
2
Failed Coasting No Output 1 1 (Failed) 0
2
Not Coupled No Output 1 1 (Failed) 1
UTC Coupled State Vector 0 4 (Normal) 0
On-line Coasting State Vector 0 4 (Normal) 0
1 2
Not Coupled No Output 1 1 (Failed) 1
Operational 2
UTC Coupled No Output 1 1 (Failed) 0
2
Failed Coasting No Output 1 1 (Failed) 0
2
Not Coupled No Output 1 1 (Failed) 1

NOTES:
1. If the time state becomes Not Coupled when the 1090 ES Ground
Station is in the On-line state then it will immediately transition to the
Failed state.
2. Default is no output. See section 3.9.3.1(g)

3.9.3.2 Buffer Overflows

a) Where buffers are used in the 1090 ES Ground Station implementation, the
1090 ES Ground Station should monitor buffer overflows.
b) The status of the buffer overflow test should be made available to the SNMP
interface.
c) Failure of the buffer overflow test should cause the 1090 ES Ground Station to
enter the Failed state.

3.9.3.3 Processor Overloads

a) The 1090 ES Ground Station should monitor processor overloads.

b) The status of the processor overload test should be made available to the
SNMP interface.
c) Failure of the processor overload test should cause the 1090 ES Ground
Station to enter the Failed state.
d) Failure of the processor overload test should cause the 1090 ES Ground
Station to set the ODP bit of item 023/100 in ASTERIX Category 023 Ground
Station Status reports.

© EUROCAE, 2010
 31

3.9.3.4 Target Overloads

a) The 1090 ES Ground Station shall monitor target overloads.

b) The status of the target overload test shall be made available to the SNMP
interface.
c) Failure of the target overload test shall cause the 1090 ES Ground Station to
generate a warning condition both on SNMP and by setting the ODP bit of item
023/100 in ASTERIX Category 023 Ground Station Status reports.
NOTE: Target overloads occur where the target acquisition tests have been
passed.

3.9.3.5 Communications Overload

a) The 1090 ES Ground Station shall monitor communication link overloads.

b) The status of the communication link overload test shall be made available to
the SNMP interface.
c) Exceeding the configured bandwidth shall result in a warning condition being
made available to the SNMP interface.
d) Failure of the communication link overload test shall cause the 1090 ES Ground
Station to set the OXT bit of item 023/100 in ASTERIX Category 023 Ground
Station Status reports.

3.9.3.6 Communications Loss

a) The 1090 ES Ground Station shall indicate any communications losses

detectable at the Ground Station, including as a minimum loss of Ethernet
physical connectivity.
b) The status of the communication link test shall be made available to the SNMP
interface if a separate physical port is available.

3.9.3.7 Time Synchronisation

a) The time state of the 1090 ES Ground Station shall be made available to the
SNMP interface.
b) The 1090 ES Ground Station shall enter the Failed state if the time state
becomes Not Coupled.
c) The TSV bit of item I023/100 in ASTERIX Category 023 Ground Station Status
reports shall be set to 1 when the time state is “Not Coupled”. The TSV bit shall
be zero when the time state is “Coasting” or “UTC Coupled”.

3.9.3.8 Temperature Range

a) The 1090 ES Ground Station should monitor the equipment temperature.

b) The status of the equipment temperature test should be made available to the
SNMP interface.
c) If the equipment temperature exceeds the maximum value expected over the
specified operating temperature range, a warning condition should be reported
to the SNMP interface.

3.9.3.9 End to End System Test

NOTE: The ability to detect loss of RF input or loss of receiver sensitivity due to
antenna problems is an important part of installed performance for many
surveillance applications. However as this section covers the ground
station only, excluding the antenna, the requirement is specified in terms of
the functionality required to support an end to end system test as required
in Sections 2.4.4.2 and 6.2.13.

© EUROCAE, 2010
 32

a) The 1090 ES Ground Station shall include a function to detect the loss of RF
input from an external test transmission.
b) The 1090 ES Ground Station shall process the test transmissions used in the
end-to-end test, in order to verify correct reception.
c) The 1090 ES Ground Station shall detect a loss of test transmissions of greater
than x seconds, where x may be configurable but shall have a default value of
10 seconds.
d) The 1090 ES Ground Station shall report loss of test transmissions to the
SNMP interface.
e) The 1090 ES Ground Station shall detect a loss of receiver sensitivity that
prevents the Ground Station from meeting its surveillance requirements. A site
monitor or equivalent method as required in Section 6.3 may be used to
facilitate this test. If the sensitivity falls below a threshold then a failure shall be
indicated. This sensitivity threshold shall be set by a configurable parameter.
f) The 1090 ES Ground Station shall report loss of receiver sensitivity to the
SNMP interface. In addition it shall report as a warning on the SNMP interface if
the receiver sensitivity falls below a configurable warning threshold.
g) The 1090 ES Ground Station shall verify the decoder functionality to ensure that
Extended Squitter test messages are decoded correctly. A site monitor or
equivalent method as required in Section 6.3 may be used to facilitate this test.
h) The status of the decoder functionality test shall be made available to the
SNMP interface.
i) The 1090 ES Ground Station shall automatically enter the Failed state if any
part of the end-to-end test fails.
j) It is recommended that the 1090 ES Ground Station should return automatically
to the On-line state if and when all parts of the end-to-end test succeed again.

3.9.4 Control Functions

a) It shall be possible to command the 1090 ES Ground Station between all

available operating modes from the SNMP interface.
b) It shall be possible to modify all configurable 1090 ES Ground Station
parameters via the control and monitoring interface.
c) It shall be possible to install the 1090 ES Ground Station software via the
control interface.
d) It shall be possible to save and restore configurable parameters of the 1090 ES
Ground Station to and from external electronic media.
e) All configurable parameters listed as mandatory in Appendix A shall be
implemented.
f) The settings of all configuration parameters shall be preserved during power
interruption or restart of the Ground Station.

3.9.5 Security

a) The 1090 ES Ground Station shall allow a change of mode to be commanded

by authorised users only.
b) The 1090 ES Ground Station shall permit a change of configuration to be
commanded by authorised users only.

© EUROCAE, 2010
 33

3.9.6 Data Logging

a) The 1090 ES Ground Station shall have the capability to log user access
activity.
b) The 1090 ES Ground Station shall have the capability to log all warnings and
changes of state or mode.
c) The 1090 ES Ground Station shall have the capability to log control instructions.
d) The 1090 ES Ground Station shall timestamp Log File Messages with a
minimum resolution of 1 second.
e) The 1090 ES Ground Station shall include the functionality to save log files to
an external storage device.
f) The 1090 ES Ground Station shall have the capability to retain log files in the
event of loss of power.

3.10 MESSAGE PROCESSING AND REPORT ASSEMBLY

The 1090 ES Ground Station receives Extended Squitter messages and produces
ASTERIX reports. The Ground Station must decide when to send an ASTERIX report,
what data items to include in the report and how to generate the data items in the
report from the received Extended Squitter messages. These decisions are described
in the following sections on report triggering, data item inclusion, and target version
determination and report assembly.

3.10.1 General Message Processing Requirements

3.10.1.1 Message Type Filtering

The 1090 ES Ground Station processes certain ADS-B 1090 MHz Extended Squitter
messages defined in DO-260A. These requirements assume that the data in all
received messages is structured in accordance with section 2.2.3.2 of DO-260A with
the exceptions noted for Version 0 targets (i.e. DO-260) in DO-260A, Appendix N. See
DO-260A, section 2.2.3.2 for definitions of the ADS-B message subfield names used
in this document.
The 1090 ES Ground Station shall process the following 1090 MHz Extended Squitter
messages:
1. Messages with DF = 17 from an airborne target
2. Messages with DF = 18 and CF = 0 or 1 from an airborne target
3. Messages with DF = 19 and AF = 0
As an option, the 1090 ES Ground Station may process non-ADS-B Mode S
messages, TIS-B messages, surface target messages or other message types.
Characteristics of the output from such message processing are not specified in this
document. A configuration item or items shall be provided to disable the output from
any optional message processing.

3.10.1.2 Extended Squitter Version Processing

The interpretation of Extended Squitter messages depends on the version state (i.e.
DO-260 vs. DO-260A) of the target. The version state is reported in message type 31
(Aircraft Operational Status). The only valid values for the version number field as of
the date of this Technical Specification are 0 (indicating a DO-260 compliant target)
and 1 (indicating DO-260A), however the majority of version 0 participants do not
transmit this message. In accordance with DO-260A, Par. 2.2.3.2.7.2.5, ADS-B
Receiving Subsystems initially shall assume a version number of ZERO (binary 000)
for each target, until received data indicates otherwise. It must therefore be assumed
that participants are transmitting messages in accordance with version 0 until a type
31 message is received indicating otherwise.

© EUROCAE, 2010
 34

The ground station shall incorporate means to prevent the permanent assignment of
an incorrect version number to version 0 participants.
NOTE:
Wherever a received message is found to contain errors and subsequently
corrected there is a small possibility that the message is in error but with a
zero checksum. In extremely rare cases this could produce a false type 31
message with an incorrect version number. If this occurs for a version 1
participant this situation is only temporary, since the correct version
number will be received a few seconds later. For a version 0 participant no
such version update is likely. Care must therefore be taken to prevent a
version 0 target becoming permanently given an incorrect version number.
An example of how this may be achieved is given below:
Example: Time of Validity for Version Information
A possible solution to the problem of permanently incorrect version numbers is to assign
a maximum validity period to the version information received from a participant. If a
single type 31 message is received the participant will be assigned that version number
for a fixed duration. If that received version number is correct then a few seconds later
an additional message will be received thus updating the version information for that
participant. The validity period should be chosen such that there is a very high likelihood
of receiving an update before the version information expires; a value of 90 seconds is
recommended. If however the type 31 message was erroneous, then the version
number will be set to an incorrect value for the duration of the validity period, but will
then revert back to the assumed version 0 state. This approach is illustrated in Figure 8..

© EUROCAE, 2010
 35

FIGURE 8: EXAMPLE OF VERSION NUMBER PROCESSING WITH A VERSION VALIDITY

PERIOD

Ty31 (OS) with

ME[41-43]=000

Confirmed
version 0
0
00

Ty
]=

31
- 43

(O
41

Ty

S)
E[ s

31
ire

w
M
xp

(O

i th
th
wi e

S)

M
n
S) io

E[
wi
at

ME[41-43]>001
Ty31 (OS) with

41
(O

th
31 rm

-4
M
fo

3]
Ty

E[
in

=0
41
io n

01
-4
rs

3]
ve

=0
00
version information expires
first Assumed
message version 0 version 1
Ty31 (OS) with
ME[41-43]=001
Ty
ME[41-43]=000
Ty31 (OS) with

31

01
( OS

=0
)

3]
wi

-4
ve th

01
41
rs M

>0
E[
E[
io n 41 M

3]
-4
in -4
th
fo

41
3
wi

rm ]>
E[
00
S)

at 1
M
(O

io
i th

n
31

ex
w
Ty

pir
S)
(O

es
31
Ty

unrecognised
version

Ty31 (OS) with

ME[41-43]>001

Message formats in future versions of the 1090 ES MOPS are expected to be

backward compatible with the messages defined in DO-260A (see DO-260A, 2.2.7.1).
The ASTERIX I021/210 MOPS Version VNS subfield provides a mechanism to flag
reports from targets using unsupported MOPS versions should this expectation
become invalid.
The 1090 ES Ground Station shall process Extended Squitter messages using the
formats described in DO-260A, Appendix N when the target version state is Assumed
Version 0 or Confirmed Version 0. The Ground Station shall process Extended
Squitter messages using the formats described in DO-260A, Section 2.2.3.2 when the
target version state is Confirmed Version 1. For unrecognised versions, messages
shall be processed in accordance with DO-260A, Section 2.2.3.2 and the I021/210
VNS subfield shall be set as specified in section 3.10.4.31.

© EUROCAE, 2010
 36

3.10.1.3 Duplicate Mode S Address Processing

At a minimum, the 1090 ES Ground Station shall be able to produce separate

ASTERIX Category 021 reports for at least two targets with the same Mode S
address. The targets can be assumed to have at least 6 nautical miles of horizontal
separation but could be at any altitude, including the same altitude. The first position
message from one target may arrive at any point in the lifecycle (i.e. acquisition,
maintenance) of the other target. Targets with duplicate addresses shall meet the
requirements for target acquisition, maintenance and termination described in sections
3.10.2.3.3, 3.10.2.5 and 3.10.2.6 respectively. ASTERIX Category 021 reports for
targets with duplicate addresses shall be transmitted as dictated by selected reporting
mode (i.e. data-driven or periodic) as described in sections 3.10.2.2 and 3.10.2.3.
Guidance on the processing of duplicate addresses is included in Appendix D.

3.10.2 Report Triggering

3.10.2.1 Report Types

At a minimum, the 1090 ES Ground Station shall be able to process received

Extended Squitter messages and generate for transmission to client systems the
report types listed in Table 4 with the indicated ASTERIX format and transmission
mode, containing the data items specified in section 3.10.3.
NOTE: Manufacturers may choose to support additional data items provided they
can be turned off in the Ground Station configuration.

TABLE 4: 1090 ES GROUND STATION REPORT TYPES AND TRANSMISSION MODES

Report Type ASTERIX Format Purpose Transmission Mode

State Vector Category 021 Provision of target state vector data Data Driven or Periodic
and other information
Edition 1.4 or later
(and optionally
Edition 0.23)
Status Category 023 Ground Station Status and Service Event Driven and
Status reporting Periodic
Edition 1.2 or later
ASTERIX Category 247 ASTERIX version used Initial message and
Version Periodic
Edition 1.2 or later

3.10.2.1.1 Report Content

The transmitted reports shall contain valid and unambiguous information obtained
from the received Extended Squitter messages and compiled in accordance with the
report assembly requirements stated in section 3.10.4.

3.10.2.1.2 Report Transmission Protocol

The reports of Table 4 shall be transmitted to (optionally multiple) external client

systems over a wide area and/or local network.
At a minimum, the 1090 ES Ground Station shall support transmission of the above
ASTERIX Category 021, 023, and 247 reports over UDP/IP/Ethernet with a
configurable IP address.
The 1090 ES Ground Station shall be able to support transmission using IP Multicast.

© EUROCAE, 2010
 37

NOTE: 1090 ES Ground Station manufacturers may choose to support additional

protocols and interface types, for example TCP for ASTERIX Category
023.
For UDP a configuration parameter shall be provided to specify the maximum output
rate permissible, in order that a communications overload can be flagged.

3.10.2.1.3 Report Transmission Modes

The 1090 ES Ground Station shall support the transmission modes listed in Table 4 as
defined in the following subsections 3.10.2.2 and 3.10.2.3.

3.10.2.2 Data Driven Transmission Mode

3.10.2.2.1 ASTERIX Category 021 Data Driven Reports

In this mode, the 1090 ES Ground Station shall generate and transmit an ASTERIX
Category 021 report containing state vector information after every successful
decoding (per ED-102 / DO-260 and DO-260A, and including track (re)-initialisation
whenever required) of a Position or Velocity squitter. These reports shall contain the
items specified in section 3.10.3.1.2.

3.10.2.2.2 ASTERIX Category 023 Event Driven Reports

The 1090 ES Ground Station shall be able to transmit a Ground Station Status report
in ASTERIX Category 023 format whenever a change is detected in the Ground
Station status.
The 1090 ES Ground Station shall be able to transmit a Service Status report in
ASTERIX Category 023 format whenever a change is detected in the status of a
service.

3.10.2.3 Periodic Transmission Mode

3.10.2.3.1 ASTERIX Category 021 Periodic Reports

The 1090 ES Ground Station shall periodically transmit an ASTERIX Category 021
state vector report with a period of x seconds, where x shall be configurable at a
minimum within the range 0.5 to 15 seconds with 0.5 second increments.
Periodic State Vector reports shall contain the fields specified in section 3.10.3.1.1.
Periodic State Vector reports shall be transmitted only when the following condition
applies: Position information has been updated at least once (through the reception of
one or more new position squitter messages with FTC ≠ 0) since the transmission of
the previous periodic state vector report.
The 1090 ES Ground Station shall transmit a Position State Vector report within 5
seconds of a change in either the Emergency/Priority Status or Surveillance Status
value (section 3.10.4.30) for any target that has been fully acquired under the
provisions of section 3.10.2.4. Such reports shall always include the latest position
and other available data.
NOTE: If the Ground Station is configured for periodic reporting with an interval
greater than 5 seconds, a Data Driven Position State Vector Report could
be issued to meet the 5 second time to alert requirement.
NOTE: This is in order to meet the requirement in ED-126 for a maximum alerting
time of 5 seconds with 95% probability, allowing for the possibility that an
individual 1090 ES message with FTC = 28 or 29 may be missed.
NOTE: The SPI field in 1090 ES messages with FTC = 31 will be ignored and the
Ground Station will rely on the Surveillance Status field in position
messages for SPI information.

© EUROCAE, 2010
 38

3.10.2.3.2 ASTERIX Category 023 Periodic Reports

ASTERIX Category 023 Ground Station Status and Service Status reports shall also
be transmitted in periodic mode, each with an independently configurable period. See
section 3.10.3.2.

3.10.2.3.3 ASTERIX Category 247 Periodic Reports

ASTERIX Category 247 version reports shall also be transmitted in periodic mode with
an independently configurable period. See section 3.10.3.3.

3.10.2.4 Target Acquisition

The acquisition phase begins with the first message received from a target, or with the
first message received from a target after all previously received position data has
expired.
By default, the 1090 ES Ground Station shall not output ASTERIX Category 021
reports for targets that are in the acquisition phase, and are therefore not yet
validated. An optional configuration parameter {ReportNonValidated} may be provided
to enable transmission of ASTERIX Category 021 reports for targets that are not
validated, for example in monitoring applications. By default reports shall not be sent
for targets that have not been validated.
NOTE: If reporting of non-validated targets is enabled, then for ASTERIX Category
021 Edition 0.23 there is no indication that the data in the report is suspect.

3.10.2.4.1 Range Check

The 1090ES Ground Station shall determine whether the initial position it determines
for a target lies within a credible area (or volume) relative to the Ground Station
location.
NOTE: The credible area/volume is often bounded by the maximum range of a
Ground Station. Other factors such as antenna directivity or terrain could
limit the extent of the credible area/volume.
An example method is shown in Figure 9. Other methods of validating the position can
be used.

© EUROCAE, 2010
 39

FIGURE 9: INITIAL POSITION SOLUTION RANGE CHECK

Receive new even-odd airborne position msg

pair with FTC != 0 within 10 sec of each other
or even-odd surface position msg pair with
FTC != 0 within X sec of each other. If Ground
Speed in the Movement subfield of either
surface position message is > 25 knots or is
unknown, X=10 sec. If Ground Speed in both
surface pos msgs is <= 25 knots, X=50 sec.

[even-odd pair of new [even-odd pair of new

airborne position msgs] surface position msgs]

determine determine
airborne surface
position position

[range from sensor > [range from sensor >

CPR_MAX_AIRBORNE [range OK] [range OK] CPR_MAX_SURFACE
_RANGE] _RANGE]

See Note 3

create report
CL=1 RC=1

NOTES:
1. The terms "even" and "odd" in Figure 9 refer to the CPR Format (F)
conveyed in ME bit 22 of the position messages.
2. Implementation of surface position processing is optional. If
implemented, messages should be processed as shown.
3. Report will be created only if the reporting of non-validated targets
has been enabled.
The position calculated during the range check shall be reported only if reporting of
non-validated targets has been enabled by the optional ReportNonValidated
configuration parameter, and the range check is successful. In this case the CL
subfield in the Target Report Descriptor item (I021/040) in ASTERIX Category 021
reports shall be 1 (“Report Suspect”) and RC shall be 1 (“Range Check Passed, CPR
Validation Pending”).

© EUROCAE, 2010
 40

3.10.2.4.2 CPR Validation

The CPR encoded position information used in the range check could be decoded into
a credible position that is incorrect. Depending on the decoding method used, this
incorrect position could corrupt subsequent decodes. The Ground Station shall
validate that the first position reported is reasonable given the ES messages received.
One method of validation is shown in Figure 10, but other methods with comparable
assurance may be used.

FIGURE 10: CPR VALIDATION TEST

<<decisionInput>>
Even-odd airborne position
message pair with FTC != 0
received in last 10 seconds Receive new position
or even-odd surface position message from
message pair with FTC != 0 participant that has
received in last X seconds. If passed range check
Ground Speed in the Create report
Movement subfield of either CL=1 RC=1
surface position message is
Local decode
> 25 knots or is unknown,
X=10 sec. If Ground Speed
in both surface pos msgs is See Note 3
<= 25 knots, X=50 sec.
[false]
<<decisionInput>>
[true]
global decode ==
local decode ± 1 CPR LSB
in Latitude and Longitude Global
[See Note 4] decode

Create report [true]

CL=0 RC=0
[false]

CPR <<localPrecondition>> Discard all position CPR validation

validation If reporting is not data failed. Restart
successful. precluded by config
acquisition process
Continue with options
(i.e. range check)
participant with new messages
maintenance

© EUROCAE, 2010
 41

NOTES:
1. The terms "even" and "odd" in Figure 10 refer to the CPR Format (F)
conveyed in ME bit 22 of the position messages.
2. Implementation of surface position processing is optional. Process
as shown if implemented.
3. Before the Global Decode check has been passed, reports (with
CL=1 and RC=1) will be created only if the reporting of non-validated
targets is enabled by a configuration parameter. This may be done
for a non-operational application such as monitoring. In this case the
report should be sent at the point indicated. By default a report of the
position determined prior to the completion of CPR validation is not
sent for operational applications such as ED-126 NRA surveillance.
4. The CPR LSB is the same as the LSB of the latitude and longitude
encoded in ES messages. For latitude, the LSB (in degrees) is
Dlati/2Nb and for longitude, the LSB is Dloni /2Nb. Dlati is defined in
DO-260A, section A.1.7.3a and Dloni is defined in A.1.7.3d. Nb is
defined in DO-260A, section A.1.7.2
If the target has passed CPR Validation, the CL subfield of item I021/040 in the first
ASTERIX Category 021 report following CPR validation shall be 0 (“Report Valid”).
The RC subfield shall be 0.

3.10.2.5 Target Data Maintenance

For targets that have passed the range check and CPR validation, the 1090 ES
Ground Station shall process new Extended Squitter position messages using Locally
Unambiguous CPR Decoding. Position squitter messages with FTC = 0 are not
considered a position update and they shall be ignored.
If a new airborne position message results in a position change that exceeds 6
nautical miles in less than 30 seconds, an ASTERIX Category 021 report shall not be
generated unless the optional ReportNonValidated configuration parameter is set to
“enabled”. In this case, CL should be set to 1 and LDPJ shall be set to 1 in item
I021/040 Target Report Descriptor.
NOTE: for ASTERIX Category 021 Edition 0.23 reports there is no indication that
the report is suspect.
NOTE: The 6 nautical miles in less than 30 seconds criterion is also known as the
Local Decoding Reasonableness Test and is specified in DO-260A
Change 2 section 2.2.10.6.
Position updates which fail the Local Decoding Reasonableness Test shall not be
used as a reference position for a subsequent local decode. They shall however be
included in duplicate address processing (see section 3.10.1.3) where they may be
used to establish a new target.
The position jump distance limit in the Local Decoding Reasonableness Test for
airborne targets shall be 6 nautical miles by default but may be configurable to other
values.
NOTE: If the 1090 ES Ground Station processes 1090 ES surface position
messages for targets, then it is recommended that the Ground Station
should implement a separate 30-second position jump distance limit for the
first airborne position message from the preceding surface position
message when a target transitions from surface to airborne messages.
This limit should be configurable with a default value of 2.5 nautical miles.

© EUROCAE, 2010
 42

3.10.2.6 Target Termination (Re-initialisation)

Targets shall be reinitialised after no more than 120 seconds without a position
update. Messages received after the 120-second timeout shall be treated as
messages from a new target (i.e. the requirements for target acquisition in section
3.10.2.4 apply). Positions excluded under the provisions of section 3.10.2.5 shall not
be counted for the purposes of the 120-second timeout.

3.10.3 Data Item Inclusion

3.10.3.1 State Vector Reports

These reports may be produced in Periodic and Data Driven Transmission mode in
accordance with the configuration of the surveillance data service on the 1090 ES
Ground Station.
NOTE: 1090 ES Ground Stations may provide multiple services with different
characteristics to different user groups.
State Vector reports shall be produced in ASTERIX Category 021 Edition 1.4 format.
Optionally Edition 0.23 format may also be supported (configurable).
NOTE: the provisions of this section relate to ASTERIX Category 021 Edition 1.4.
Recommended minmum and optional items for ASTERIX Category 021
Edition 0.23 reports are listed in APPENDIX M.
State Vector reports shall contain the fields specified in sections 3.10.3.1.1 (for
periodic reports) or 3.10.3.1.2 (for data driven reports).
State Vector report field contents shall be in accordance with the provisions in section
3.10.4.

3.10.3.1.1 Periodic State Vector Reports

Each state vector report shall contain at least the minimum data set shown in Table 5.
Periodic ASTERIX Category 021reports for targets with duplicate addresses shall
contain the items specified in Table 5 except for item I021/170 Target Identification.
The 1090 ES Ground Station may additionally include in Periodic reports the following
optional ASTERIX Category 021 items shown in Table 6 (provided that they are
configurable). In the case of targets with duplicate addresses, items or sub-fields shall
be included in the report only if the Ground Station is able to associate the data they
contain unambiguously with the target whose position is transmitted in the ASTERIX
Category 021 message.

© EUROCAE, 2010
 43

TABLE 5: ASTERIX CATEGORY 021 PERIODIC OR DATA DRIVEN POSITION REPORT:

MINIMUM ITEMS

Item Content Notes

I021/010 Data Source 1090 ES Ground Station SIC and 1090 ES GS configuration
Identification SAC
I021/040 Target Report Type and characteristics of data Per the provisions in section
Descriptor transmitted 3.10.4.6
I021/071 Time of Time of applicability of the received Per the provisions in 3.10.4.8
Applicability for Position position (measurement by the and 3.10.4.10
aircraft) or time of ES message
OR
reception at the Ground Station
I021/073 Time of Message
Reception of Position
I021/080 Target Address Target identifier as specified in the 24 bit ICAO address as
Extended Squitter messages specified in the Position
squitter
I021/090 Quality Indicators ADS-B quality indicators transmitted Per the provisions in section
by aircraft according to MOPS 3.10.4.16
version
I021/130 WGS-84 Position Position in WGS-84 Coordinates Latest Position squitter and
previous track information
[note 1]
I021/145 Flight Level Flight Level from barometric Per the provisions in section
measurements, not QNH corrected 3.10.4.21
I021/170 Target Target (aircraft or vehicle) Latest Identification squitter.
Identification identification in 8 characters This field is not included in the
report when no Identification
squitter has been received
[note 2].
I021/200 Target Status Status of the target Per the provisions in section
3.10.4.30
I021/210 MOPS Version Identification of MOPS version used Link Technology Type = 2 for
by aircraft to supply ADS-B 1090 ES
information and link technology

NOTES:
1. State Vector report shall not be transmitted if no new position
squitter has been received since the previous State Vector report.
2. This item shall be included only if it contains new information
received in an extended squitter message since the previous State
Vector report. If the value of newly received information is equal to
the value conveyed in the last State Vector Report, the information is
still considered “new” and reported.

© EUROCAE, 2010
 44

TABLE 6: ASTERIX CATEGORY 021 PERIODIC OR DATA DRIVEN POSITION REPORT:

OPTIONAL ITEMS

Item Content Notes

I021/008 Aircraft Identification of the operational Latest Aircraft Status squitter
operational status services available in the aircraft while
airborne
I021/015 Service Identifier Identification of the service offered to 1090 ES GS configuration
the receivers of this report [note 1]
I021/016 Service Identification of services offered by 1090 ES GS configuration
Management the 1090 ES Ground Station
I021/020 Emitter Category Characteristics of the originating Latest Identification squitter
ADS-B unit
I021/070 Mode 3/A Code Mode-3/A code converted into octal Latest Test squitter
representation
I021/074 Time of Message Fractional second time of receipt of
Reception of Position – the latest position squitter with 2-30
High Precision second (~1 ns) resolution
I021/075 Time of Message Time of receipt of the latest velocity 1090 ES GS UTC clock
Reception of Velocity squitter with 1/128th second resolution
I021/076 Time of Message Fractional second time of receipt of May be included only when
Reception of Velocity – the latest velocity squitter with 2-30 I021/075 is included
High Precision second (~1 ns) resolution
I021/077 Time of Report Time of transmission of the ASTERIX 1090 ES GS UTC clock
Transmission report
I021/132 Message Amplitude, in dBm, of latest ADS-B 1090 ES GS measurement
Amplitude report received at the Ground Station
I021/140 Geometric Minimum altitude from a plane Latest Position squitter [note 2]
Altitude tangent to the earth’s ellipsoid,
defined by WGS-84
I021/146 Intermediate State The short-term vertical intent as Latest Target State squitter
Selected Altitude described by either the FMS selected [note 2]
altitude, the Altitude Control Panel
Selected Altitude, or the current
aircraft altitude according to the
aircraft's mode of flight
I021/150 Air Speed Calculated Air Speed Latest velocity squitter [note 2]
I021/151 True Air Speed True Air Speed Latest velocity squitter [note 2]
I021/152 Magnetic Heading Magnetic Heading Latest velocity squitter [note 2]
I021/155 Barometric Barometric Vertical Rate Latest velocity squitter [note 2]
Vertical Rate
I021/157 Geometric Geometric Vertical Rate Latest velocity squitter [note 2]
Vertical Rate
I021/160 Ground Vector Ground Speed and Track Angle Latest velocity squitter [note 2]

© EUROCAE, 2010
 45

NOTES:
1. A 1090 ES Ground Station may support multiple services with
different characteristics (for example different volumes of coverage
or different reporting periods).
2. This item shall be included only if it contains new information
received in an extended squitter message since the previous State
Vector report. If the value of newly received information is equal to
the value conveyed in the last State Vector Report, the information is
still considered “new” and reported.

3.10.3.1.2 Data Driven State Vector Reports

In data driven mode, State Vector reports shall be of two types, namely position and
velocity.
a. Data Driven Position Reports
Data driven position reports shall be issued on the reception of a new position squitter
(after track initialisation) and shall contain at a minimum the fields listed in Table 5.
Data driven position reports for targets with duplicate addresses shall contain the data
items specified in Table 5 except for I021/170 Target Identification.
Data driven position reports may also contain any of the optional items listed in Table
6 for which new information has been received since the previous state vector
(position or velocity) report. In the case of targets with duplicate addresses, items or
sub-fields shall be included in the report only if the Ground Station is able to associate
the data they contain unambiguously with the target whose position is transmitted in
the ASTERIX Category 021 message.
b. Data Driven Velocity Reports
Data driven velocity reports shall be issued on the reception of a new velocity squitter
provided at least one position report has been transmitted for the target since its last
track (re)initialisation.
These reports shall contain at a minimum the items listed in Table 7.
Data driven velocity reports may also contain any of the optional items listed in Table
6 for which new information has been received since the previous state vector
(position or velocity) report.
Data-driven velocity reports shall not be issued for targets with duplicate addresses.

© EUROCAE, 2010
 46

TABLE 7: ASTERIX CATEGORY 021 DATA DRIVEN VELOCITY REPORT: MINIMUM ITEMS

Item Content Notes

I021/010 Data Source 1090 ES Ground Station SIC and Set by 1090 ES GS
Identification SAC configuration
I021/077 Time of Report Time of transmission of the ASTERIX 1090 ES GS UTC clock
Transmission report message
I021/040 Target Report Type and characteristics of data Per the provisions in section
Descriptor transmitted 3.10.4.6
I021/075 Time of Message Time at which the velocity information Per the provisions in section
Reception of Velocity was received by the Ground Station 3.10.4.12
I021/080 Target Address Target identifier as specified in the 24 bit ICAO address as
Extended Squitter messages specified in the position
squitter
I021/090 Quality Indicators Navigation accuracy category for Value equal to the Navigation
velocity set in the primary subfield of Uncertainty Category (NUCR)
I021/090, bits 6 to 8. or Navigation Accuracy
Category for Velocity (NACV)
Only the primary subfield shall be
as reported in the velocity
included, and bits 2 to 5 shall be set
squitter
to zero
I021/150 Air speed Target velocity as reported in the Reporting of airspeeds may be
squitter disabled as a Ground Station
OR
configuration option
I021/151 True Air speed
OR
I021/160 Ground Vector
I021/170 Target Target (aircraft or vehicle) Latest identification squitter
Identification identification in 8 characters
I021/200 Target Status Status of the target Per the provisions in section
3.10.4.30
I021/210 MOPS Version Identification of MOPS version used Link Technology Type = 2 for
by a/c to supply ADS-B information 1090 ES
and link technology

3.10.3.2 Status Reports

In accordance with Table 4, the 1090 ES Ground Station shall report the status of the
system and its components through the use of ASTERIX Category 023 reports.
This standard specifies three types of status reports (Ground Station Status, Service
Status and Service Statistics). The 1090 ES Ground Station shall be able to generate
at least Ground Station Status and Service Status reports.
These reports shall include at a minimum the items listed in Table 8 for Ground
Station Status Reports and in Table 9 for Service Status Reports.

© EUROCAE, 2010
 47

TABLE 8: 1090 ES GROUND STATION STATUS REPORT: MINIMUM ITEMS

Item Content Notes

I023/000 Message 1 (= Ground Station Status Report) Fixed
Type
I023/010 Data Source 1090 ES Ground Station SAC and SIC Set by 1090 ES GS configuration
Identifier
I023/070 Time of Day UTC time stamp corresponding to the From the 1090 ES GS UTC time
time of transmission of the report source
I023/100 Ground Status of the monitoring system and 1090 ES GS monitoring outputs
Station Status time source

TABLE 9: SERVICE STATUS REPORT: MINIMUM ITEMS

Item Content Notes

I023/000 Message 2 (= Service Status Report) Fixed
Type
I023/010 Data Source 1090 ES Ground Station SAC and SIC Set by 1090 ES GS configuration
Identifier
I023/070 Time of Day UTC time stamp corresponding to the From the 1090 ES GS UTC time
time of transmission of the report source
I023/101 Service Service configuration settings Service class and report periods
Configuration
I023/110 Service Status Status of this Service

The above status reports shall in each case be transmitted periodically with a period of
x seconds, where x shall be configurable from 1 to 127 seconds in one-second
increments. The period of the Ground Station Status reports shall be transmitted in
the GSSP field of I023/100. The period of the Service Status reports shall be
transmitted in the SSRP field of I023/101.
The RP field of I023/101 in Service Status reports shall contain the report period for
ASTERIX Category 021 reports on that service. The SC field of I023/101 shall be set
to 1 for an operational NRA service.
Additionally the 1090 ES Ground Station shall transmit status reports in event driven
mode, whenever a change occurs in the Ground Station status or configuration data
items.

3.10.3.3 ASTERIX Version Reports

These reports shall indicate the ASTERIX Category 021 and 023 versions currently
used by the 1090 ES Ground Station.
ASTERIX Category 247 Edition 1.2 or later shall be used for ASTERIX Version
reports, and they shall be transmitted periodically with a period of x minutes, where x
shall be configurable from 0 (meaning no transmission) to at least 60 minutes in ten
minute increments.
1090 ES Ground Stations with multiple service capability may support different
ASTERIX Category 021 and 023 versions per service. In that case a separate version
report shall be issued for each service.

© EUROCAE, 2010
 48

An ASTERIX Category 247 report shall be the first report transmitted after the 1090
ES Ground Station service is initialised. This is in order that the ASTERIX Category
021 and 023 reports can be correctly interpreted.
The ASTERIX Version reports shall include at a minimum the items listed in Table 10.

TABLE 10: ASTERIX VERSION REPORTS – MINIMUM ITEMS

Item Content Notes

I247/010 Data Source 1090 ES Ground Station SAC and Set by 1090 ES GS configuration
Identifier SIC
I247/140 Time of Day Absolute Time stamping expressed as From the 1090 ES GS UTC time
UTC source
I247/550 Category Version number of categories used Set by 1090 ES GS configuration
Version Number report

3.10.3.4 Data Validity Periods

Data items extracted from ADS-B messages shall be included in ASTERIX target
reports for a time period that does not exceed a value dependent on the data item and
which may be configured differently per Ground Station Service. If the validity time of a
data item has been exceeded, the data item shall not be included in a report.
Fields for position, altitude, velocity, heading, NIC/NUCP and NACV/NUCR shall be
included only when they contain new information received from the target since the
last State Vector Report.
NOTE: If the new information received from the target has the same values as the
field contents of the last State Vector Report, it is still considered new
information and is included in the next report. If no update is received for a
value, there is no new information and the corresponding field of the report
is excluded or encoded to indicate “no information.”
Reports triggered by Emergency or SPI status changes shall include the latest values
received for the aforementioned fields as long as the information is still valid, even if
the data has been sent in a prior report.
These validity periods must be set taking into account the requirements of the ADS-B
applications supported and the targeted operational environment. Table 11 lists
recommended validity periods based, where available, on ED-126 and DO-260/A
requirements. Adaptations may be necessary for specific local conditions.
The reported NIC supplement, NACP, SIL or HRD shall be taken from the message
closest in time to the message containing the reported position (or velocity in the case
of HRD). If they are equally spaced from the position message, the lower value shall
be reported.

© EUROCAE, 2010
 49

TABLE 11: ADS-B MESSAGE SUBFIELD VALIDITY PERIODS

Maximum
ASTERIX
Report Validity Period
FTC Category 021 Origin of Validity Requirement
Parameter in Seconds
Item
[note 1]
Call Sign 1-4 I021/170 100 ED-126 SPR21 and 25 [note 3]
Emitter
1-4 I021/020 200 DO-260A Table 2-102
Category

Emergency/ 28/1
I021/200 100 [note 2] DO-260A Change 1, Par 1.23
Priority Status 29/0
Capability
31/0 I021/008 24 DO260A Table 2-90 [note 4]
Class Codes
Operational 29/0
I021/008 24 DO260A Table 2-90 [note 4]
Mode [note 5] 31/0

SV Quality - 29/0
I021/090 24 DO260A Table 2-90 [note 4]
NACP 31/0
SV Quality
±5 from position
NIC 31/0 I021/090 DO260A, Sec. 2.2.3.2.7.6
message
supplement
Reported only with the associated
SV Quality – See Airborne
I021/090 position contained in the same
NIC or NUCP Position
message
Reported only with the associated
SV Quality - See Airborne
19 I021/090 velocity contained in the same
NACV or NUCR Velocity
message

SV Quality - 29/0
I021/090 24 DO260A Table 2-90 [note 4]
SIL 31/0

SV Quality - 29/0
I021/090 100 DO-260A Table 2-102
NICBARO 31/0
Horizontal
Reference
31/0 I021/152 100 DO-260A Table 2-102
Direction
(HRD)
Reported only with the associated
Vertical Rate I021/155 or See Airborne
19 airborne velocity (contained in the
and Type 157 Velocity
same message)
Mode A Code 23/7 I021/070 100 ED126 SPR 21 and 25 [note 6]
Airborne 19/1
Velocity - N/S I021/160 10 ED126 SPR19 and 23
Direction 19/2

Airborne 19/1
Velocity - E/W I021/160 10 ED126 SPR19 and 23
Direction 19/2

19/3
Airspeed I021/150 10 Per Airborne Velocity
19/4

© EUROCAE, 2010
 50

Maximum
ASTERIX
Report Validity Period
FTC Category 021 Origin of Validity Requirement
Parameter in Seconds
Item
[note 1]
19/3
True Airspeed I021/151 10 Per Airborne Velocity
19/4

Magnetic 19/3
I021/152 10 Per Airborne Velocity
Heading 19/4
Selected
29/0 I021/146 24 DO260A Table 2-90 [note 4]
Altitude
9-18, I021/140 or Per associated position contained in
Altitude 10
20-22 145 the same message
Airborne 9-18,
I021/143 10 ED126 SPR19 and 23
Position 20-22

NOTES:
1. A parameter is considered valid if a 1090 ES ADS-B Message has
been received containing the data associated with this parameter,
within the indicated validity time. If an update has not been received
within the indicated validity time, then there is no longer a valid value
for this parameter. Validity times apply from when messages are
received, even if they are received prior to completion of the range
check and CPR validation tests.
2. The most recently received value for "Emergency/Priority Status" is
reported unless no update has been received within the specified
Validity Time, in which case an ALL ZEROs value is reported for the
parameter.
3. DO-260A Table 2-102 specifies 200 s.
4. DO-260A Table 2-102 specifies 100 s.
5. = TCAS RA on/off per Table 3-21.
6. DO-260A Sec 2.2.3.3.1.4.4 specifies a 12 s update period for the
TEST message providing the Mode A code.

3.10.4 ASTERIX Category 021 Report Assembly

This section defines report assembly for ASTERIX Category 021 [REF13].
NOTE: report assembly for ASTERIX Category 021 Edition 0.23 reports is
described in Appendix M.

© EUROCAE, 2010
 51

3.10.4.1 I021/008 Aircraft Operational Status

Aircraft Operational Status subfields shall be populated from Aircraft Operational

Status messages (FTC = 31) in accordance with Table 12.

TABLE 12: AIRCRAFT OPERATIONAL STATUS FIELD MAPPING

DO-260A (Version 1) DO-260 (Version 0) I021/008

ME Msg ME Msg
Subfield Subfield Subfield Bits
bits Bits bits Bits
OM-RA 27 59 Not Available RA 8
CC-TC 17-18 49-50 Not Available TC 6-7
CC-TS 16 48 Not Available TS 5
CC-ARV 15 47 Not Available ARV 4
CC-CDTI 12 44 CC_4-CDTI 12 44 CDTI 3
CC-not TCAS 11 43 CC_4-not TCAS 11 43 Not TCAS 2

Subfield bit values in I021/008 shall be the same as the respective subfield bit values
in the Aircraft Operational Status Extended Squitter message. I021/008 subfields shall
be ZERO if the corresponding subfield is not available in the Extended Squitter
message. If all subfields are zero, then the I021/008 item shall be omitted from the
ASTERIX report, as a zero value will be implied.

3.10.4.2 I021/010 Data Source Identification

The SIC and SAC reported in data item I021/010 shall be equal to the values of the
SIC and SAC configuration items. The SIC and SAC values shall be formatted as
binary unsigned integers.

3.10.4.3 I021/015 Service Identifier

The Service Identifier reported in data item I021/015 shall be equal to the value of the
Service Identifier configuration item for the service that produced the report. The
Service Identifier values shall be formatted as a binary unsigned integer.

3.10.4.4 I021/016 Service Management

The Report Period item shall be set to zero for data driven reporting. In periodic mode
the report period shall be encoded in accordance with the ASTERIX specification.

3.10.4.5 I021/020 Emitter Category

Emitter Category (I021/020) shall be assigned as shown in Table 13.

© EUROCAE, 2010
 52

TABLE 13: EMITTER CATEGORY FIELD MAPPING REQUIREMENTS

Aircraft Identification and

I021/020 ECAT
Type Message
Emitter Category Version State = Version State = Assumed or
FTC (SET)
Code Confirmed Version 1 Confirmed Version 0
1 (D) 0 0 0
1 (D) 1-7 DNP DNP
2 (C) 0 0 0
2 (C) 1 20 20
2 (C) 2 21 21
2 (C) 3 22 22
2 (C) 4 23 DNP
2 (C) 5 24 DNP
2 (C) 6-7 DNP DNP
3 (B) 0 0 0
3 (B) 1 11 11
3 (B) 2 12 12
3 (B) 3 16 16
3 (B) 4 15 15
3 (B) 5 DNP DNP
3 (B) 6 13 13
3 (B) 7 14 14
4 (A) 0 0 0
4 (A) 1 1 1
4 (A) 2 2 2
4 (A) 3 3 3
4 (A) 4 4 4
4 (A) 5 5 5
4 (A) 6 6 6
4 (A) 7 10 10

NOTE: “DNP” means do not populate (i.e. include) I021/020 in reports.

The Emitter Category data item shall not be included in the report if the data in the
ADS-B Emitter Category subfield of the ADS-B Aircraft Identification and Type
Message has not been received or has expired.

© EUROCAE, 2010
 53

3.10.4.6 I021/040 Target Report Descriptor

ATP (Address Type, bits 8, 7, 6 in the primary subfield) shall be 1 (duplicate address)
if the Ground Station determines that this target may have the same 24-bit address as
another target. If the Extended Squitter messages received from the target have DF =
18 with CF set to 1, ATP shall be 3. Otherwise the ATP field shall be 0 (24 bit ICAO
address), indicating either DF = 17, or DF =18 and CF = 0, or DF = 19 and AF = 0.
ARC (Altitude Reporting Capability, bits 5, 4 in the primary subfield). If an airborne
position message with Q (ME bit 16, message bit 48) equals 1 has been received from
the target and has not expired, the ARC field shall be 0. The ARC field shall be 1 if the
Q bit in the airborne position message equals 0. If no airborne position message has
been received, or if it has expired, then the ARC field shall be 2.
RC (Range Check, bit 3 in the primary subfield) shall be set if the range check has
been passed but the CPR validation check is not yet complete.
RAB (bit 2 in the primary subfield) shall be 1 if the target address corresponds to a
configured Site Monitor for the Ground Station {SiteMonitorAddress}, otherwise it
shall be 0.
FX (Bit 1 of the primary subfield) shall be one and the first extend included if any of
GBS, SIM, TST, SAA or CL (as defined below) are nonzero.
DCR (Differential Correction, bit 8 in the first extend) shall be 0.
GBS (Ground Bit Set, bit 7 in the first extend) shall be 0 for targets broadcasting
airborne position messages.
SIM (Simulated Target, bit 6 in the first extend) shall be 0 when the Ground Station is
reporting actual targets detected from Extended Squitter messages received over the
RF interface in real time. If the Ground Station supports an optional reprocessing
capability, SIM shall be 1 when the Ground Station is reprocessing recorded or
simulated target data.
TST (Test Target, bit 5 in the first extend) shall be 1 if the target corresponds to a
configured internal test target address for the Ground Station, otherwise it shall be 0.
SAA (Selected Altitude, bit 4 in the first extend) shall be 1 if the target transponder
version has been confirmed as version 1 (DO-260A, and the last Target State and
Status message (FTC = 29, Subtype 0) received for this target has not expired and
has the Target Altitude Capability field set to either 1 or 2. In all other cases the SAA
bit shall be 0.
CL (Confidence Level, bits 3 and 2 in the first extend) shall indicate the confidence
level (CL) of the report. CL shall be 0 (“Report Valid”) unless otherwise specified in
this document. If CL = 1 (“Report Suspect“) and the reason for the report being
suspect is defined in the second extend of I021/040, FX (bit 1 of the first extension)
shall be 1 and the appropriate error bit or bits in the second extension shall be equal
to 1.
NOTE: the circumstances under which the NOGO bit is set are described in
section 3.9.3.1. and the circumstances under which the LDPJ bit is set are
described in section 3.10.2.5.

© EUROCAE, 2010
 54

3.10.4.7 I021/070 Mode 3/A Code

The Mode 3/A Code field shall be constructed from FTC = 23 subtype 7 messages in
accordance with Table 14.

TABLE 14: MODE 3/A CODE FIELD MAPPING REQUIREMENTS

I021/070 Bits Encoding Rationale

bit 13-16 (spare) Always 0

bits 1-12 Map the received ES bits to the corresponding bits in the ASTERIX
Category 021 report, as defined in the ASTERIX specification.

NOTE: The order of bits for Mode 3/A code is different in ES messages and
ASTERIX Category 021 reports.

3.10.4.8 I021/071 Time of Applicability for Position

Time of Applicability for Position values shall be rounded to the nearest 1/128th second
to satisfy ASTERIX Category 021 constraints.
I021/071 shall be included in the report if the T bit (ME bit 21, message bit 53) of the
last position message equals 1, the FTC of the last position message is 5, 6, 9, 10, 20
or 21, and the Ground Station is in either the UTC Coupled or the Coasting time state.
NOTE: the accuracy requirement in section 3.7 is sufficient to allow the Time of
Applicability to be determined correctly in either the UTC Coupled or the
Coasting time state. The Ground Station does not emit ASTERIX Category
021 messages by default in the Not Coupled time state.
I021/071 shall be determined as follows:
if (TOMR - tFprevious) < 200 ms then
Time of Applicability = tFprevious
else
Time of Applicability = tFnext
endif
Where:
• TOMR is the time of message receipt of the position message used in the
current report.
• Time of Applicability is the time of applicability reported in I021/071, rounded to
1/128th of a second.
• tFprevious is the previous even or odd 0.2 second epoch relative to TOMR If F = 0,
the even epoch is used and if F = 1, the odd epoch is used.
• tFnext is the next even or odd 0.2 second epoch relative to TOMR. If F = 0, the
even epoch is used and if F = 1, the odd epoch is used.
• F is the value of the "CPR Format" subfield (i.e. "F" bit) in the Airborne or
Surface position message used in the current report.
• F = 0 indicates that the Time of Applicability is an even 0.2 second epoch and F
= 1 indicates that Time of Applicability is an odd 0.2 second epoch.

© EUROCAE, 2010
 55

• Even 0.2 second epochs are even multiples of 0.2 seconds after an even
numbered second. For example, 12, 54 and 61,200 seconds are even
numbered seconds and even epochs, 12.4, 12.8, 13.2, 13.6 and 14.0 seconds
are even epochs.
• Odd 0.2 second epochs are odd multiples of 0.2 seconds after an even
numbered second. For example, 12.2, 12.6, 13.0, 13.4 and 13.8 seconds are
odd epochs.

FIGURE 11: EXAMPLE OF EVEN AND ODD 0.2 UTC SECOND EPOCHS

3.10.4.9 I021/072 Time of Applicability for Velocity

I021/072 is not applicable for a 1090 ES Ground Station.

3.10.4.10 I021/073 Time of Message Reception for Position

I021/073 shall be included in the report when position is reported and any of the
following apply:
• The T bit (ME bit 21, message bit 53) of the last position message equals 0.
• The T bit (ME bit 21, message bit 53) of the last position message equals 1 and
the FTC of the last position message is 7, 8, 11-18 or 22.
I021/073 shall indicate the UTC time at which the leading edge of the P1 pulse of the
last position squitter was received. The time of message reception shall be rounded to
the nearest 1/128th second (LSB of I021/073) for this item.

3.10.4.11 I021/074 Time of Message Reception for Position – High Precision

I021/074 shall indicate the fractional UTC second at which the leading edge of the P1
pulse of the last position squitter was received. The fractional time of message
reception shall be rounded to the nearest multiple of 2-30 s. I021/074 shall not be
included in the report unless I021/073 is also included. FSI in I021/074 shall refer to
the whole second in I021/073.
NOTE: I021/074 is valid only for Ground Stations that are UTC coupled.

3.10.4.12 I021/075 Time of Message Reception for Velocity

I021/075 shall indicate the UTC time at which the leading edge of the P1 pulse of the
last velocity squitter was received. The time of message reception shall be rounded to
the nearest 1/128th second (LSB of I021/075) for this item.

3.10.4.13 I021/076 Time of Message Reception for Velocity – High Precision

I021/076 shall indicate the fractional UTC second at which the leading edge of the P1
pulse of the last velocity squitter was received. The fractional time of message
reception shall be rounded to the nearest multiple of 2-30 s. FSI in I021/076 shall refer
to the whole second in I021/075.
NOTE: I021/076 is valid only for Ground Stations that are UTC coupled.

© EUROCAE, 2010
 56

3.10.4.14 I021/077 Time of Report Transmission

I021/077 shall contain the time of transmission of the current ASTERIX report with an
accuracy of ±30 ms with respect to UTC.

3.10.4.15 I021/080 Target Address

I021/080 bits 24 through 1 shall be equal to message bits 9 through 32 of the first
position message received from a target.

3.10.4.16 I021/090 Quality Indicators

Item I021/090 shall be encoded as specified in Table 15.

TABLE 15: MAPPING OF DATA FOR QUALITY INDICATORS

DO-260A (Version 1) DO-260 (Version 0) I021/090

ME Msg Subfiel ME Msg Subfiel

Subfield FTC bits Bits d bits Bits d Bits
NUCR or
NACV 19 11-13 43-45 NUCR 11-13 43-45 8-6
NACV
9-18, NUCp or
NIC See below NUCp 1-5 33-37 5-2
20-22 NIC
31 53 85
NICBARO Not Available NICBARO 8
29 44 76
31 51-52 83-84
SIL Not Available SIL 7-6
29 45-46 77-78
31 45-48 77-80
NACP Not Available NACP 5-2
29 40-43 72-75

Subfield bit values in I021/090 shall be the same as the respective subfield bit values
in the Extended Squitter message. I021/090 subfields shall be ZERO if the
corresponding subfield in the Extended Squitter is not available or has expired.
NUCp shall be determined from the position message FTC and Table 2-11 in DO-260
Change 1.
NIC shall be determined from the FTC of the latest position squitter message, the NIC
supplement in the FTC = 31 Aircraft Operational Status squitter message closest in
time to the position message, and Table 2-16 of DO-260A.
NICBARO, SIL and NACP shall be derived from the information received in the Target
State and Status (FTC = 29) or Aircraft Operational Status (FTC = 31) Extended
Squitter message closest in time to the position squitter message being reported.
For periodic state vector reports containing no velocity data (no item I021/150,
I021/151 or I021/160), the NACV subfield shall be set to zero.
Targets with duplicate addresses shall be reported with the NUCR and NUCp
parameters only, as for assumed version 0 targets.
NOTE: For targets with duplicate addresses it is problematic to determine which
target the MOPS version, NIC supplement, NAC and SIL information
relates to, as these are not transmitted within the airborne position squitter
messages.

© EUROCAE, 2010
 57

3.10.4.17 I021/130 Position in WGS-84 Coordinates

Encoded Latitude and Longitude received in Airborne Position Messages FTC = 9-18
or 20-22 shall be decoded into latitude and longitude in accordance with sections
3.10.2.4 and 3.10.2.5 using the Compact Position Reporting algorithms in Appendix A
of DO-260A. The result shall be encoded according to the ASTERIX specification for
I021/130.

3.10.4.18 I021/131 High-Resolution Position in WGS-84 Coordinates

Encoded Latitude and Longitude received in Airborne Position Messages FTC = 9-18
or 20-22 shall be decoded into latitude and longitude in accordance with sections
3.10.2.4 and 3.10.2.5 using the Compact Position Reporting algorithms in Appendix A
of DO-260A. The result shall be encoded according to the ASTERIX specification for
I021/131.

3.10.4.19 I021/132 Message Amplitude

I021/132 shall contain the amplitude of either:

a) The ES message that triggered the current report when in data driven mode
or
b) The most recent ES message from the target when in periodic mode
The amplitude shall be the reference level determined by the preamble detector,
encoded in dBm.
NOTE: Message amplitude for a target at a particular location will be a function of
the antenna gain pattern, the losses in the antenna feed cable and the gain
in any masthead preamplifier.

3.10.4.20 I021/140 Geometric Altitude

If the FTC of the last airborne position message is 20-22 and the “Altitude” data is
valid, Geometric Altitude shall be equal to the “Altitude” in the last airborne position
message converted to the encoding specified for I021/140 in the ASTERIX
specification.
NOTE: “Altitude” data is valid if an airborne position message has been received,
the “Altitude” data has not expired and the contents of the “Altitude”
subfield are not all zeros.
If the FTC of the last airborne position message is 9-18 and the data in the “Altitude,”
“Difference From Baro Altitude Sign,” and “Difference from Baro Altitude” fields are all
valid, the Geometric Altitude shall be “Altitude” plus “Difference from Baro Altitude” if
“Difference from Baro Altitude Sign” is zero and, “Altitude” minus “Difference from
Baro Altitude” if “Difference from Baro Altitude Sign” is one.
NOTE: “Altitude” and “Difference from Baro Altitude” in the preceding requirement
are converted to feet from their encoded values in the 1090 ES message.
Geometric Altitude is calculated altitude in feet converted to the encoding
specified for I021/140.
NOTE: “Difference from Baro Altitude” is valid when a velocity message has been
received, the “Difference from Baro Altitude” data has not expired, and the
encoded value is neither 0 nor 127 (decimal).
NOTE: “Difference from Baro Altitude Sign” is valid when a velocity message has
been received and the “Difference from Baro Altitude Sign” data has not
expired.
I021/140 shall not be included in the report if either the “Difference from Baro Altitude”
or “Altitude” field is all ZEROs.
If the “Difference from Baro Altitude” field is all ONEs, I021/140 shall be encoded
using the “greater than” value specified in the ASTERIX Category 021 specification.

© EUROCAE, 2010
 58

3.10.4.21 I021/145 Flight Level

Altitude received in FTC = 0 messages shall not be reported.

If an unexpired airborne position message (FTC = 9-18) has been received from the
target since the last State Vector Report was sent, then the Flight Level field shall be
included in the report with the value derived from the Altitude field of the airborne
position message as follows:
If the Q bit in the altitude field is 1 then the Flight Level field shall be the decimal value
of the remaining bits, less 40, expressed as a 16-bit two’s complement binary number.
If the Q bit is 0 then the Flight Level field shall be set according to the altitude
extracted from the remaining bits using the 100-ft encoding specified in the Appendix
to Chapter 3 of ICAO Annex 10, Volume IV. This altitude value (in feet) is divided by
100, multiplied by 4 and expressed as a 16-bit two’s complement binary number.
NOTE: The Flight Level field has a resolution of ¼ flight level (25 feet).
The Flight Level field shall not be included in the report if one or more of the following
apply:
a) All bits in the Altitude field of the airborne position message are equal to zero;
b) The Altitude field has the Q bit set to zero and does not contain a valid Gillham-
encoded altitude;
c) The last airborne position message has FTC = 0, 20, 21 or 22;
d) The airborne position message has expired;
e) No surface or airborne position messages have been received since the last
State Vector Report was sent;
f) A surface position message has been received more recently than the last
airborne position report.

3.10.4.22 I021/146 Intermediate State Selected Altitude

SAS shall be 0 (“no source information provided”) if the field “Vertical Data
Available/Source Indicator” in the Target State and Status squitter is equal to “No valid
vertical target state data is available” (value 0).
SAS shall be 1 (“source information provided”) if the field “Vertical Data
Available/Source Indicator” in the Target State and Status squitter is not equal to “No
valid vertical target state data is available” (value 0).
The “Source” subfield in I021/146 shall be in accordance with Table 16.

TABLE 16: I021/146 SOURCE FIELD MAPPING

Target State and Status (FTC = 29) Subfield Intermediate State Selected Altitude
“Vertical Data Available/Source Indicator” (I021/146) subfield “Source”
0: No valid vertical target state data is available 0: Unknown
1: Autopilot control panel selected value (MCP,
2: FCU/MSP selected altitude
FCU)
2: Holding altitude 1: Aircraft altitude
3: FMS/RNAV System 3: FMS selected altitude

© EUROCAE, 2010
 59

The value in the “Altitude” subfield of I021/146 shall be:

Altitude = (100*N – 1000)/25
where N is the value received in the Target State and Status Message field “Target
Altitude”.
I021/146 shall not be included in the report if N > 1010 (decimal) or if FTC = 29 has
not been received or has expired.

3.10.4.23 I021/150 Air Speed

I021/150 shall be included in reports only when the subtype of the last unexpired
airborne velocity message (FTC = 19) is 3 or 4, the “Airspeed Type” is 0 and the value
in the “Airspeed” subfield does not equal 0 or 1023 decimal.
The I021/150 “IM” subfield shall be 0 (“IAS”).
The I021/150 “Air Speed” subfield shall be the result of the following equations
rounded to the nearest integer and expressed as an unsigned integer in binary format:
Subtype 3 (normal): Air Speed =
214 * (value in Velocity Message field AIRSPEED – 1)/3600
Subtype 4 (supersonic): Air Speed =
4*214 * (value in Velocity Message field AIRSPEED – 1)/3600

3.10.4.24 I021/151 True Air Speed

I021/151 shall be included in the report only if all of the following conditions are true:
a) An airborne velocity message (FTC = 19, subtype 3 or 4) has been received;
b) The True Air Speed data from the last airborne velocity message has not
expired;
c) The Airspeed Type (ME bit 25) is 1;
d) The Airspeed field (ME bits 26 through 35) does not equal 0.
If the last airborne velocity message is of subtype 3 (subsonic) and the value in the
airspeed field is not 1023, then the True Airspeed field shall be:
(Value in the airspeed field of the airborne position message) - 1
If the last airborne velocity message is of subtype 4 (supersonic) and the value in the
airspeed field is not 1023, then the True Airspeed field shall be:
4 * (Value in the airspeed field of the airborne position message - 1)
If the value of the Airspeed field is 1023, the Range Exceeded bit shall be 1 and the
True Airspeed shall be 1022 knots for subtype 3 velocity messages and 4085 knots for
subtype 4 velocity messages.

3.10.4.25 I021/152 Magnetic Heading

For Version 0 targets, I021/152 shall be included only when the subtype of the last
unexpired airborne velocity message (FTC = 19) is 3 or 4 and the “Magnetic Status
Heading Bit” equals 1.
For Version 1 targets, I021/152 shall be included only when the subtype of the last
unexpired airborne velocity message (FTC = 19) is 3 or 4, the “Heading Status Bit”
equals 1 and the “Horizontal Reference Direction” from the last unexpired aircraft
operational status message is 1.
The I021/152 “Magnetic Heading” subfield shall equal the “Magnetic Heading” (for
Version 0 targets) or “Heading” (for Version 1 targets) in the last unexpired airborne
velocity message.

© EUROCAE, 2010
 60

3.10.4.26 I021/155 Barometric Vertical Rate

I021/155 shall be included only if all of the following are true:

a) An airborne velocity message has been received and the information for vertical
rate has not expired;
b) The Source Bit for Vertical Rate in the airborne velocity message equals 1;
c) The Vertical Rate in the airborne velocity message does not equal 0.
If the value in the Vertical Rate field of the airborne velocity message is between 1 and
510 inclusive, and the Vertical Rate Sign Bit (ME bit 37) is equal to 1, then the value of
the Barometric Vertical Rate field shall be:
-floor ((((value in the Vertical Rate field - 1) * 64) / 6.25) + 0.5)
If the value in the Vertical Rate field of the airborne velocity message is between 1 and
510 inclusive, and the vertical rate sign bit (ME bit 37) is equal to 0, then the value of
the Barometric Vertical Rate field shall be:
floor (((value in the Vertical Rate field - 1) * 64) / 6.25) + 0.5)
If the value in the Vertical Rate field equals 511, the RE field shall be 1 and the
Barometric Vertical Rate shall be determined using the equations above.

3.10.4.27 I021/157 Geometric Vertical Rate

I021/157 shall be included only if all of the following are true:

a) An airborne velocity message has been received and the information for vertical
rate has not expired;
b) The Vertical Rate Source bit in the airborne velocity message equals 0;
c) The Vertical Rate in the airborne velocity message does not equal 0.
If the value in the Vertical Rate field of the airborne velocity message is between 1 and
510 inclusive, and the Vertical Rate Sign Bit (ME bit 37) is equal to 1, then the value of
the Geometric Vertical Rate field shall be:
-floor ((((value in the Vertical Rate field - 1) * 64) / 6.25) + 0.5)
If the value in the Vertical Rate field of the airborne velocity message is between 1 and
510 inclusive, and the vertical rate sign bit (ME bit 37) is equal to 0, then the value of
the Geometric Vertical Rate field shall be:
floor (((value in the Vertical Rate field - 1) * 64) / 6.25) + 0.5)
If the value in the Vertical Rate field equals 511, the RE field shall be 1 and the
Geometric Vertical Rate shall be determined using the equations above.

3.10.4.28 I021/160 Ground Vector

The Ground Vector field shall be included in the ASTERIX Category 021 report only
when all of the following are true:
a) An Airborne Velocity Message (FTC = 19) with a subtype of 1 or 2 has been
received since the last ASTERIX Category 021 report for the target;
b) The data in that Airborne Velocity Message has not expired;
c) Neither the N/S Velocity nor the E/W Velocity subfields contain all zeros.
Ground Speed shall be the magnitude of the vector sum of the N/S Velocity and the
E/W velocity reported in the Airborne Velocity Message expressed as a 15 bit
unsigned integer with a least significant bit of 2-14 nautical miles per second.
The Track Angle shall be the direction of the vector sum of the N/S Velocity and the
E/W Velocity measured in degrees from True North in a clockwise direction,
expressed as a 16 bit unsigned integer with a least significant bit equal to 360°/216.

© EUROCAE, 2010
 61

FIGURE 12: TRACK ANGLE AND GROUND SPEED

Track Angle

N/S Vel

W E/W Vel E

Ground Speed

S
Ground Speed and Track Angle shall be rounded to the nearest multiple of LSB in the
ASTERIX Category 021 report.
If the value in either the N/S Velocity or the E/W Velocity is 1023, the RE bit shall be 1
and the Ground Speed and Track Angle fields shall be determined as described
above.

3.10.4.29 I021/170 Target Identification

Target Identification Data Item bits 48 through 1 shall contain a bit-for-bit copy of bits
9-56 of the last Aircraft Identification and Type Message received from the target.
The Target Identification Data Item shall not be included in ASTERIX Category 021
reports when the Aircraft Identification and Type message data has never been
received or has expired.

3.10.4.30 I021/200 Target Status

The value of the Priority Status subfield shall be determined from the latest Extended
Squitter Aircraft Status Message (FTC = 28) or Target State and Status Message
(FTC = 29, available from Version 1 targets only). The value of I021/200 Priority
Status shall be equal to the value of the Emergency/Priority Status from the latest FTC
= 28 or 29 message. Priority status for reports from targets with duplicate addresses
shall be 0.
The value of the Surveillance Status subfield shall be equal to the value of the
Surveillance Status field in the latest Airborne Position Message.
Expired data in either Priority Status or Surveillance Status shall be encoded with a
value of ZERO.

3.10.4.31 I021/210 MOPS Version

The Version Not Supported (VNS) field (bit 7) shall be 0 if the target version state is
Assumed Version 0, Confirmed Version 0 or Confirmed Version 1. Bit 7 shall be 1 if
the target version state is Unrecognised Version.
The Version Number (VN) field (bits 6-4) shall be 0 if the target version state is
Assumed Version 0 or Confirmed Version 0. VN shall be 1 if the target version state is
Confirmed Version 1. VN shall be the value reported in the latest aircraft operational
status message (FTC = 31, ME bits 41-43) if the target version state is Unrecognised
Version. VN shall be 0 in reports for targets with duplicate addresses.
The Link Technology Type shall be 2 (1090 ES).

© EUROCAE, 2010
 62

3.10.4.32 I021/271 Surface Capabilities and Characteristics

Reporting of Surface Capabilities and Characteristics is optional. The material in this

section is provided as guidance only.

TABLE 17: CAPABILITY CLASSES AND OPERATIONAL MODES FOR SURFACE TARGETS

DO-260A (Version 1), FTC = DO-260 (Version 0), FTC =

I021/271
31, Subtype 1 31
ME Msg ME Msg
Subfield Subfield Subfield Bits
bits Bits bits Bits

I021/271 Primary Subfield Items

CC-POA 11 43 Not Available POA 6
CC-CDTI 12 44 CC-CDTI 12 44 CDTI/S 5
CC-B2 Low 15 47 Not Available B2 Low 4
OM-RAS 29 61 Not Available RAS 3
OM-IDENT 28 60 Not Available IDENT 2
I021/271 First Extend Items
L+W Code 21-24 53-56 Not Available L+W Code 4-1

Subfield bit values in I021/271 shall be the same as the respective subfield bit values
in the Extended Squitter message. I021/271 subfields shall be ZERO if the
corresponding subfield in the Extended Squitter is not available or has expired.

3.11 RECEIVER CHARACTERISTICS

NOTE: the signal power levels specified in this section may need to be adjusted to
take into account any differences between the antenna system with which
the Ground Station is designed to operate, and the Reference Antenna
described in section 3.1.2. Further guidance is given in APPENDIX G.

3.11.1 Receiver Sensitivity

The receiver sensitivity requirements a) and b) below apply to a standalone 1090 ES

Ground Station made up of a single ADS-B receiver in order to support a range of up
to 160NM as assumed in ED-126. As stated above they assume the Reference (0dB
gain) Antenna. Where a different configuration is used (such as a different antenna
gain or where there are multiple distributed receivers making up the ground station, as
in a WAM system) and/or a different coverage volume is required, the manufacturer
may specify and test against alternative receiver sensitivity figures provided this is fully
justified by analysis. That analysis shall show that the receiver sensitivity is sufficient
to meet the range requirement.
a) Valid 1090 ES ADS-B Messages with a carrier frequency between 1089 and
1091 MHz applied directly to the connector at the 1090 ES Ground Station
Receiver at a level of -88 dBm shall produce a Successful Message Reception
(SMR) rate of 90% or better.
b) Additionally, valid 1090 ES ADS-B Messages with a carrier frequency between
1089 and 1091 MHz applied directly to the connector at the 1090 ES Ground
Station Receiver at a level of –91 dBm shall produce a rate of Successful
Message Reception of 15% or better at ambient temperature conditions.

© EUROCAE, 2010
 63

These receiver sensitivity requirements apply in the absence of interference and

overloads and for valid 1090 ES ADS-B Message signals that comply with the pulse
shape and pulse location requirements specified in EUROCAE ED-73C, sections
3.6.1, 3.6.2, 3.6.4 and 3.6.5.

3.11.2 Receiver Desired Signal Dynamic Range

In the absence of interference or overloads, the standalone 1090 ES Ground Station

made up of a single ADS-B receiver shall achieve a Successful Message Reception
(SMR) rate of 99% or better when the desired signal level applied directly to the
connector at the 1090 ES Ground Station receiver is between -85 dBm and -20 dBm.

© EUROCAE, 2010
 64

CHAPTER 4

MINIMUM PERFORMANCE SPECIFICATION UNDER ENVIRONMENTAL TEST

CONDITIONS

4.1 ENVIRONMENTAL SPECIFICATION

The 1090 ES Ground Station equipment will be used in a similar manner to, and in
conjunction with, civil telecommunications equipment. The ETSI EN 300 019 [REF30]
has been chosen as an appropriate specification for environmental performance.

4.2 STORAGE

Equipment (including standard packaging) shall be capable of storage at weather-

protected, partly temperature-controlled locations as defined by ETSI EN 300 019
Class 1.1.

4.3 TRANSPORT

All equipment (including standard packaging) shall be capable of being transported by

careful transportation as defined by ETSI EN 300 019 Class 2.2.
Where equipment is to be transported to remote sites over unmade roads the
capability to be carried on public transportation as defined by ETSI EN 300 019 Class
2.3 is recommended.

4.4 INDOOR USE

Equipment installed at indoor locations shall be capable of use at partly temperature-

controlled locations as defined by ETSI EN 300 019 Class 3.2.

4.5 EQUIPMENT ROOM USE

Equipment installed at indoor locations where the environment is fully controlled in

terms of temperature and humidity shall be capable of use in temperature-controlled
locations as defined by ETSI EN 300 019 Class 3.1.

4.6 OUTDOOR USE

Equipment installed at outdoor locations shall be capable of use in a non-weather

protected environment as defined by ETSI EN 300 019 Class 4.1.
If the equipment is to be used in a location subject to the extremes of heat or cold it is
recommended one of the following more stringent classes is selected:
a) Class 4.1E: Non-weather protected – extended (extreme Europe);
b) Class 4.2L: Non-weather protected – extremely cold (worldwide);
c) Class 4.2H: Non-weather protected – extremely warm (worldwide).

© EUROCAE, 2010
 65

4.7 EUROPEAN LEGISLATIVE REQUIREMENTS

The system shall comply with all current EU regulatory standards including:
• 2006/95/EC Low Voltage Directive;
• 2004/108/EC Electromagnetic compatibility (EMC);
• 2002/96/EC Waste electrical and electronic equipment (WEEE);
• 2002/95/EC The restriction of the use of certain hazardous
substances in electrical and electronic equipment
(ROHS).
The system shall be CE marked to demonstrate compliance with EU directives for
product safety.
This list is not authoritative. It is the responsibility of the manufacturer to ensure all
applicable legislative requirements are complied with.

© EUROCAE, 2010
 66

CHAPTER 5

TEST PROCEDURES

5.1 INTRODUCTION

This section contains a set of type approval tests that can be used to demonstrate
compliance with the requirements in section 3. These type approval tests are intended
to be performed once in order to provide evidence that the ground station design
complies with these requirements, and therefore is not intended as a production test
or factory acceptance test activity. These test procedures may also be used as part of
a regression test following a design change. It is up to the manufacturer to determine
the scope and suitability of regression test activity.
These test procedures were written with the intention of saving manufacturers the time
and expense of developing their own tests while providing equipment buyers with a
minimum level of assurance that the equipment is compliant with the requirements in
section 3. Alternative tests may be substituted if it is more convenient to do so as long
as any substituted test procedures fully cover all the mandatory requirements of the
relevant part of section 3.
Since many test procedures require a similar test equipment setup, a standard setup
is defined here and specific test procedures reference this section, specifying
exceptions when necessary.
Specific test procedures are defined in this Section starting with section 5.2. Except
where otherwise noted, the sub-section number of each test procedure matches the
corresponding sub-section number within Section 3 containing the requirements being
tested.
Only mandatory requirements are covered by these tests.

5.1.1 Test Equipment Setup

A diagram of the standard test equipment setup is shown in Figure 13.

FIGURE 13: STANDARD TEST EQUIPMENT SETUP (LOGICAL CONNECTIONS)

UTC Time
Reference

RF Source
Desired
Messages
Ground ASTERIX
Station Recording

FRUIT

Control &
Power
Monitoring

Equipment used in the standard setup is described in Sections 5.1.1.1 to 5.1.1.5.

© EUROCAE, 2010
 67

NOTE: Figure 13 and the remainder of this section describe the test equipment in
terms of functions. The functions may be implemented with one or more
items of equipment as long as the required capabilities are provided.

5.1.1.1 RF Source of Desired Messages

Desired messages shall meet the requirements of sections 2.2.2.2.1 and 2.2.3.1 of
DO-260A. The source shall be capable of producing messages with an adjustable
power level from MTL to -10 dBm at the Ground Station input. The source shall be
capable of producing messages simulating 300 targets simultaneously. Desired
messages shall not overlap each other. The source shall be capable of producing
messages for each simulated target at the rates shown in Table 18.

TABLE 18: MESSAGE RATES FOR DESIRED MESSAGES

Message Type Message Rate (per Notes

second)
2 one even, one odd
Airborne Position
FTC = 9-18, 20-22
2 FTC = 19, Subtype = 1-
Airborne Velocity
4
Aircraft Identification 0.2 FTC = 1-4
Target State and Status 0.8 FTC = 29, Subtype = 0
Aircraft Operational 0.4 FTC = 31, Subtype = 0
Status
Aircraft Status 0.4 FTC = 28, Subtype = 1

Dithered transmission intervals, as specified in DO-260A section 2.2.3.3.1, are

permissible but not required. Simulated targets may be moving or stationary.
Stationary targets must have velocity messages.

© EUROCAE, 2010
 68

5.1.1.2 RF Source of FRUIT

The FRUIT source shall be capable of producing Mode A/C, Mode S short and Mode
S long messages randomly distributed in time with the power distribution shown in
Table 19.

TABLE 19: AMPLITUDE AND MESSAGE TYPE DISTRIBUTION OF THE INJECTED FRUIT

Signal
A/C Short Extended Cumulativ Cumulativ Cumulativ Cumulative
Level
Squitters Squitters Squitters e A/C e SS e ES SS+ES
dB
-74 0.0 0.0 0.0 0.0 0.0 0.0 0.0
-75 0.0 0.0 0.0 0.0 0.0 0.0 0.0
-76 11.4 27.6 6.2 11.4 27.6 6.2 33.8
-77 0.0 0.0 0.0 11.4 27.6 6.2 33.8
-78 5.7 24.8 9.3 17.1 52.4 15.5 67.9
-79 4.0 20.4 15.5 21.1 72.7 31.0 103.7
-80 3.5 12.0 6.2 24.5 84.7 37.2 121.9
-81 27.6 85.4 24.8 52.2 170.1 62.0 232.1
-82 19.7 91.3 24.8 71.8 261.4 86.8 348.2
-83 12.3 47.8 21.7 84.2 309.2 108.5 417.7
-84 30.7 95.6 34.1 114.9 404.8 142.6 547.4
-85 45.7 118.3 46.5 160.6 523.1 189.1 712.2
-86 60.4 189.5 55.8 221.0 712.6 244.9 957.5
-87 119.5 299.5 93.0 340.4 1012.1 337.9 1350.0
-88 85.8 218.1 62.0 426.2 1230.1 399.9 1630.0
-89 108.9 271.3 80.6 535.1 1501.5 480.5 1982.0
-90 163.7 405.9 105.4 698.8 1907.4 585.9 2493.3
-91 177.2 443.2 114.7 876.0 2350.6 700.6 3051.2
-92 169.8 502.6 124.0 1045.8 2853.2 824.6 3677.8
-93 100.4 277.9 65.1 1146.2 3131.1 889.7 4020.8
-94 113.7 259.4 55.8 1259.9 3390.5 945.5 4336.0
-95 134.2 313.6 49.6 1394.1 3704.1 995.1 4699.2
-96 48.7 164.2 27.9 1442.8 3868.3 1023.0 4891.3
-97 42.3 84.2 12.4 1485.1 3952.5 1035.4 4987.9
-98 1.2 5.7 3.1 1486.3 3958.1 1038.5 4996.6
-99 2.8 13.2 3.1 1489.1 3971.3 1041.6 5012.9
-100 0.0 0.0 0.0 1489.1 3971.3 1041.6 5012.9
-101 0.0 0.0 0.0 1489.1 3971.3 1041.6 5012.9

The quoted amplitudes assume a zero gain reference antenna. These amplitudes
must be adjusted to match the typical gain of the antenna the 1090 ES Ground Station
is to be used with.

© EUROCAE, 2010
 69

NOTE: The data content of the Mode S FRUIT transmissions is not critical, since
one and zero bits have equal energy content. The Mode A/C replies should
have half the code bits set (e.g. 0707 or 2525) to reflect the average
energy content of all messages. It may be useful to use non-ADS-B DF
codes (e.g. 20) for the Mode S ES messages to prevent valid FRUIT ADS-
B messages from appearing in the ASTERIX data.

5.1.1.3 UTC Time Reference

A means of disabling or disconnecting the UTC time reference shall be provided.

5.1.1.4 Control and Monitoring Equipment

The control and monitoring equipment shall interface with the 1090 ES Ground Station
via SNMP. A means of polling the Ground Station for values of all parameters shall be
provided. The control and monitoring equipment shall allow a user to authenticate with
and control the Ground Station.

5.1.1.5 ASTERIX Recording Equipment

The ASTERIX recording equipment shall timestamp and record all ASTERIX reports
sent from the 1090 ES Ground Station.
The control and monitoring equipment, ASTERIX recording equipment and any other
network capable test equipment may be connected through suitable networking
equipment.
All test equipment requiring calibration shall have documentation showing that the
equipment calibration is valid.

5.1.2 Default Configuration, Mode and State

a) The 1090 ES Ground Station and all of the test equipment shall be powered on
before the beginning of each test.
b) The 1090 ES Ground Station shall be configured to the default parameter
values shown in Appendix A.
c) The mode shall be Operational.
d) The state shall be Online.
e) The time state shall be UTC coupled.
f) The 1090 ES Ground Station shall have no information on any targets.
g) Network configuration parameters shall be assigned so that the 1090 ES
Ground Station can communicate with the control and management equipment,
the ASTERIX recording equipment and any other network connected test
equipment.
h) The MaxBitRate parameter shall be set to the maximum value appropriate for
the network.
i) The 1090 ES Ground Station shall have a suitable configured own position
(GSLatitude, GSLongitude) or self-determined (e.g. GPS self-survey) Ground
Station location.
j) The default power level for injected test messages shall be MTL + 3dB.
k) FRUIT generation shall not be enabled by default.

© EUROCAE, 2010
 70

5.1.3 Message Set Construction

Message sequences for individual targets must be constructed carefully to produce

ASTERIX Category 021 output.

5.1.3.1 Initial Position Messages

Sequences must begin with two even-odd (or odd-even) pairs of messages to allow
the Ground Station to acquire the target.
The position messages in each of the first two pairs of messages must be less than 10
seconds apart.

FIGURE 14: INITIAL POSITION MESSAGES

Participant PE1 PO2 PO3 PE4

ES input

Participant PO1 PE2 PE3 PO4

ES input Any of these
combinations are
Participant PO1 PE2 PO3 PE4 OK
ES input

Participant PE1 PO2 PE3 PO4

ES input

Participant R1
ASTERIX output

10s 120s 10s

max max max
Legend
PE# Position msg – even CPR encoding
PO# Position msg – odd CPR encoding
R# ASTERIX report from participant

The position conveyed in the first pair of messages must be within

CPRAirborneMaxRange of the configured (GSLatitude, GSLongitude) or self-
determined (e.g. GPS self-survey) Ground Station location.
If moving targets are used, the position change from one message to the next in each
of the first two pairs of messages (i.e. from 1 to 2 and from 3 to 4) must be less than
3NM in both latitude and longitude.
If the scenario is correct, the first ASTERIX report will be produced after the 2nd pair
of even-odd messages.
Scenario design may be easier to verify in data-driven reporting mode.

© EUROCAE, 2010
 71

5.1.3.2 Field Values

Most tests will use data from just a few 1090 ES message fields. If the number of
values that can be conveyed by a field is small, then all the values should be tested. A
one bit field has only two possible values, so both should be tested. If the number of
values that can be conveyed by a field is large, a subset of the values should be
checked. For example, there are thousands of possible altitude values that can be
conveyed in position messages. An appropriate subset of these values would include
minimum, minimum + 1 LSB, maximum, maximum – 1 LSB and a value in the middle
of the altitude range.
Fields that are not relevant for a specific test should be assigned random values. The
values may be static throughout a scenario or they may change. Random values in
seemingly irrelevant fields will confirm that the outputs are dependent only on the
expected fields. The random values must be chosen so they do not stop the output of
the Ground Station. For example, if the Flight Level data item is being verified,
randomised position values must not change by more than 6NM between successive
reports less than 30 seconds apart.

5.1.3.3 Altitude Values

Airborne position messages should contain barometric altitude unless geometric

altitude is required for a specific test.

5.1.4 Common Procedures

5.1.4.1 Configuration Changes

When a specific test procedure calls for changing a 1090 ES Ground Station
configuration parameter value, assume that the user will authenticate with the Ground
Station, put the Ground Station in maintenance mode, change the parameter(s), put
the Ground Station back into operational mode and then log out of the Ground Station.
If the Ground Station was in maintenance mode or the user was already
authenticated, then the mode change and authentication steps are not necessary.

5.1.4.2 Checking of Log Files

Ground Station logs shall be checked at the conclusion of each test for unexpected
warnings, errors or other anomalies. Any unexpected error or anomaly constitutes a
test failure.

5.2 COVERAGE AND DETECTION

5.2.1 Coverage

There are no specific tests for Section 3.2.1.

5.2.2 Performance in the presence of 1090 MHz Interference

There are no specific tests for Section 3.2.2.

© EUROCAE, 2010
 72

5.3 SYSTEM CAPACITY

5.3.1 Overall Capacity

5.3.1.1 Objectives

The aim of this test is to verify the overall system capacity requirements in Section
3.3.1.
This is a test of the basic system capacity and so no FRUIT will be used in the test.
If the manufacturer has specified a capacity higher than 300 for the 1090 ES Ground
Station, then this higher number shall be used instead of 300 in the tests for section
3.3.

5.3.1.2 Test Equipment Setup

The test equipment shall be set up as described in Section 5.1.1.

5.3.1.3 Scenario Design

The test messages shall be configured for 300 targets, all within the coverage range of
the 1090 ES Ground Station.

5.3.1.4 Test Procedure

Test Steps:
1. Make the following configuration or mode changes:
a. Set the CapacityThreshold parameter to 305.
2. Enable the injection of the RF test signals.
3. At least 10 seconds after the target injection is started, start the ASTERIX data
recording. Note: this delay is required to acquire all targets.
4. Confirm from the SNMP client that no target capacity overload is reported.
5. Allow the recording to run for at least two minutes, then stop the recording and
signal injection.
6. From the recorded data, confirm that the average number of ASTERIX
Category 021 target reports output by the Ground Station for each target is 4 ±
1% per second for the duration of the recording.
7. Confirm also that the recorded ASTERIX Category 023 messages do not have
the ODP bit set (in item I023/100).

5.3.2 Target Overloads

5.3.2.1 Objectives

The aim of this test is to verify the target overload requirements in Section 3.3.2 and
3.9.3.4.

5.3.2.2 Test Equipment Setup

The test equipment shall be as described in Section 5.1.1.

5.3.2.3 Scenario Design

The test messages shall be configured for 300 targets all within the coverage range of
the 1090 ES Ground Station.

© EUROCAE, 2010
 73

5.3.2.4 Test Procedure

Test Steps:
1. Make the following configuration or mode change:
a. Set the CapacityThreshold parameter to 295.
2. Enable the injection of the RF test signals.
3. At least 10 seconds after the target injection is started, commence the
ASTERIX data recording. Note: this delay is required to acquire all targets.
4. Confirm using the SNMP client that a target capacity overload is reported.
5. Allow the recording to run for at least two minutes, then stop the recording and
signal injection.
6. From the recorded data, confirm that the average number of ASTERIX
Category 021 target reports output by the Ground Station per target per second
is 4 ± 1% for the duration of the recording.
7. Confirm also that the recorded ASTERIX Category 023 reports have the ODP
bit set (in item I023/100).

5.3.3 Communications Overloads

5.3.3.1 Objectives

The aim of this test is to verify the requirements in Section 3.3.3 and 3.9.3.5.

5.3.3.2 Test Equipment Setup

The test equipment shall be set up with a means for injecting extended 1090 MHz
squitter signals representing at least 300 simultaneous DO-260A compliant aircraft as
described in Section 5.1.1.

5.3.3.3 Scenario Design

The test messages shall be configured so that all 300 targets are within the coverage
range of the 1090 ES Ground Station.

5.3.3.4 Test Procedure

Test Steps:
1. Make the following configuration or mode change:
a. Set the CapacityThreshold parameter to 305.
2. Enable the injection of the RF test signals.
3. At least 10 seconds after the target injection is started start the ASTERIX data
recording. Note: this delay is required to acquire all targets.
4. Configure the MaxCommBitRate parameter to a value equivalent to 50% of the
observed ASTERIX report data rate.
5. Confirm from the SNMP client that a communications overload is reported.
6. Allow the recording to run for at least two minutes, then stop the recording and
signal injection.
7. Confirm that the recorded ASTERIX Category 023 messages have the OXT bit
set (in item I023/100).

5.3.4 Overload Mitigation

There are no specific tests for Section 3.3.4.

© EUROCAE, 2010
 74

5.4 SYSTEM LATENCY

5.4.1.1 Objectives

Verify the requirements in Section 3.4.

5.4.1.2 Test Equipment Setup

The test equipment setup shall be the same as the standard setup described in
Section 5.1.1 with the following exceptions:
• Since the objective of this test is to measure latency through the Ground
Station, a method of determining the difference between the time of arrival of
the 1090 ES message at the RF input of the Ground Station and the time of
transmission of the corresponding ASTERIX report must be devised. The sum
of the measurement uncertainty and the measured latency must be less than
the maximum latency specified in Section 3.4.

5.4.1.3 Scenario Design

The test requires the standard maximum FRUIT load specified in section 5.1.1 and a
target load of 30 simulated airborne targets, all within range of the Ground Station.
The simulated targets must have DF17 position, velocity and identification squitters.
The signal levels of the messages from the 30 targets shall be MTL + 3dB. The
scenario must be designed to produce ASTERIX reports for the 30 targets of interest
for a period of at least 10 seconds. It may be useful to use consecutively numbered
aircraft addresses for the targets, so that they can be readily identified during the
analysis of the recorded data.
The Mode S component of the FRUIT shall have 24-bit addresses randomly drawn
from a list of 270 which shall be different from the addresses used for the targets.

5.4.1.4 Test Procedure

Preconditions:
• If UTC synchronisation is part of the latency measurement method, all UTC
synchronised devices are in the UTC synchronised state.
Test Steps:
1. Inject the target and FRUIT messages into the 1090 ES Ground Station and
record the resulting reports.
2. Latency is determined by calculating the latency of each ASTERIX report for all
30 targets. The sum of the calculated latency and the measurement uncertainty
for each report must be less than the maximum specified in Section 3.4.

5.5 CONTINUITY

There are no specific tests for Section 3.5.

5.6 INTEGRITY

5.6.1 Objectives

The objective of this test is to verify the system integrity requirement in Section 3.6:
The decoder undetected message error rate shall be better than 1 in 105 messages.
This error level will be measured in the presence of a realistic FRUIT environment as
specified in Section 3.6.

5.6.2 Test Equipment Setup

The test equipment will be set up as described in Section 5.1.1, with FRUIT generator
enabled.

© EUROCAE, 2010
 75

5.6.3 Scenario Design

The test messages and FRUIT shall be configured as described for the System
Latency test (Section 5.4.1.3).

5.6.4 Test Procedure

Test Steps:
1. Enable the injection of the valid aircraft.
2. Start the FRUIT generator.
3. Allow the recording to run for sufficient time to record at least 500,000
messages.
4. Stop the recording.
5. By comparison of the recorded data against the known aircraft positions,
confirm that no more than 1 in 100,000 position reports contain either an
incorrect position (I021/130, I021/145) or incorrect position quality values
(I021/090).
NOTE: The recorded data may contain data received from real aircraft in the
vicinity. This extra data may be ignored.

5.7 ACCURACY

5.7.1 Time of Applicability Accuracy

There are no specific tests for Section 3.7.1.

5.7.2 Time of Message Reception Accuracy

5.7.2.1 Objectives

This test procedure verifies that the 1090 ES Ground Station timestamps received
position and velocity messages relative to UTC with the accuracy as specified in
Section 3.7.2.

5.7.2.2 Test Equipment Setup

The test equipment setup shall be the same as the standard setup described in
Section 5.1 with the following exceptions:
• a means of determining the time of message reception by the 1090 ES Ground
Station.

5.7.2.3 Scenario Design

The accuracy of the timestamp for both the position and velocity reports is tested.
These values are tested on 100 position and 100 velocity messages when the time
source is valid and on 100 position and 100 velocity messages after the 1090 ES
Ground Station has been coasting for a period of CoastingTimeOut -1 minutes. All of
the ASTERIX Category 021 reports shall pass the accuracy test.
The accuracy is verified on data items I021/073 and I021/075 of ASTERIX Category
021 reports as a minimum. If data items I021/074 and I021/076 are supported, it is
permitted to verify the accuracy on these data items.
In order to generate data item I021/073 in the ASTERIX Category 021 reports, the
position messages must satisfy one of the conditions listed in Section 3.10.4.10, for
example the T bit may be set to zero.

© EUROCAE, 2010
 76

The message scenario consists of injecting position and velocity messages as

specified in Table 20. When the simulated target has been acquired, i.e. it has
successfully passed the range check and CPR validation, one hundred position (PE4 -
PO103) and one hundred velocity (V1 - V100) messages are injected. Then the 1090
ES Ground Station is forced into the Coasting Time State. After a period of
CoastingTimeOut - 1 minutes (29 minutes by default) the simulated target is re-
initialised and another set of one hundred position and velocity messages is injected.
For each message the difference between the reported Time of Message Reception
and the known time of message reception shall be ± 25 milliseconds or less.

TABLE 20: 1090 ES MESSAGE SCENARIO – TIME OF MESSAGE RECEPTION ACCURACY

Expected ASTERIX
ES Input Expected Result
Category 021 Output
Time T1 I021/073 or I021/075 or
Message ID |TOMR - T1| (ms)
[note 1] (s) I021/074 I021/076
0 PO1
0.5 PE2
1 PO3
1.5 PE4 TOMR(PE4) |TOMR(PE4) - T1| < 25
1.7 V1 TOMR(V1) |TOMR(V1) - T1| < 25
2.0 PO5 TOMR(PO5) |TOMR(PO5) - T1| < 25
2.2 V2 TOMR(V2) |TOMR(V2) - T1| < 25
2.5 PE6 TOMR(PE6) |TOMR(PE6) - T1| < 25
2.7 V3 TOMR(V3) |TOMR(V3) - T1| < 25
... ... ... ... ...
51.0 PO103 TOMR(PO103) |TOMR(PO103) - T1| <
25
51.2 V100 TOMR(V100) |TOMR(V100) - T1| < 25
... [note 2] ... ... ... ...
... [note 2] ... ... ... ...
1800 [note 3] xPO1
[note 4]
1800.5 xPE2
1801.0 xPO3
1801.5 xPE4 TOMR(xPE4) |TOMR(xPE4) - T1| < 25
1801.7 xV1 TOMR(xV1) |TOMR(xV1) - T1| < 25
1802.0 xPO5 TOMR(xPO5) |TOMR(xPO5) - T1| < 25
1802.2 xV2 TOMR(xV2) |TOMR(xV2) - T1| < 25
... ... ... ... ...
1851.0 xPO103 TOMR(xPO103) |TOMR(xPO103) - T1| <
25
1851.2 xV100 TOMR(xV100) |TOMR(xV100) - T1| <
25
NOTES:

© EUROCAE, 2010
 77

1. Time T1 is the known UTC time of reception of the position or

velocity 1090 ES message.
2. After disconnecting UTC synchronisation wait until CoastingTimeOut
- 1 minutes, which defaults to 29 minutes.
3. In this example the Coasting Time State started at Time T1 = 60 s.
The CoastingTimeOut is equal to 30 min (1800 s).
4. xPO, xPE and xV are odd position, even position and velocity
messages of the same target or a new target.
NOTE: This test can be combined with the test procedure for 3.9.3.1 Status
Reporting (Section 5.9.3.1).

5.7.2.4 Test Procedure

Test Steps:
1. Play the scenario described in Section 5.7.2.3 of this test procedure with
injecting the sequence of both position and velocity messages as specified in
Table 20.
2. Verify that the data items I021/073 or I021/074 and I021/075 or I021/076 of
ASTERIX Category 021 reports produced are within ± 25 milliseconds of the
time that the corresponding 1090 ES messages were injected for both position
and velocity messages in both UTC Coupled and Coasting Time States

5.7.3 Data Accuracy

There are no specific tests for Section 3.7.3.

5.8 AVAILABILITY

The manufacturer shall demonstrate by analysis that the availability of the 1090 ES
Ground Station meets the requirements of Section 3.8.

5.9 EQUIPMENT CONTROL AND STATUS

5.9.1 Assumptions

There are no specific tests for Section 3.9.1.

5.9.2 General

There are no specific tests for Section 3.9.2.

5.9.3 Monitoring Functions (Local & Remote)

5.9.3.1 Status Reporting

5.9.3.1.1 Objectives

This test procedure verifies that the 1090 ES Ground Station reports all its Modes,
States and Time States through SNMP and ASTERIX Category 023 reports in
accordance with the requirements specified in Section 3.9.3.1 and Table 3.
Requirement 3.9.3.1 c) is not included in the test procedure, because this requirement
is manufacturer dependent. If the design uses LRUs then the manufacturer shall test
that the requirements of section 3.9.3.1 c) are met.
This test procedure also verifies the requirements 3.9.6 a) capability to log the user
access activity, 3.9.6 b) capability to log warning and failure messages and 3.9.6 c)
capability to log control instructions.

© EUROCAE, 2010
 78

5.9.3.1.2 Test Equipment Setup

The test equipment setup shall be the same as the standard setup described in
Section 5.1.

5.9.3.1.3 Scenario Design

The scenario of this test procedure consists of injecting a continuous sequence of

even-odd (or odd-even) pairs of position messages while the 1090 ES Ground Station
is driven through all its Modes, States and Time States. The 1090 ES Ground Station
is commanded between the two modes manually and the transition between its States
and Time States is achieved through enabling and disabling of the UTC
synchronisation. The relevant SNMP parameters and ASTERIX Category 023 Outputs
are verified for each status of the 1090 ES Ground Station during the test.
As a part of the test procedure the issuing of ASTERIX Category 021 output is also
verified. The scenario is listed in Table 21.

TABLE 21: SCENARIO OF THE TEST PROCEDURE FOR STATUS REPORTING

ASTERIX ASTERIX
Category 023 Category
1090 ES Ground Station Status ASTERIX Type 1 023 Type 2
Step Category Output Output
[note 1] 021 [note 2] [note 3]
Output
Time
Mode State NOGO TSV STAT
State
UTC State 4
1 Operational On-Line 0 0
Coupled Vector (Normal)
No 5
0 - Initialisation - 1 1
Output (Initialisation)
UTC State 4
7 Operational On-Line 0 0
Coupled Vector (Normal)
UTC No 4
11 Maintenance On-Line 1 0
Coupled Output (Normal)
No 5
14 - Initialisation - 1 1
Output (Initialisation)
UTC No 4
15 Maintenance On-Line 1 0
Coupled Output (Normal)
UTC State 4
18 Operational On-Line 0 0
Coupled Vector (Normal)
State 4
21 Operational On-Line Coasting 0 0
Vector (Normal)
UTC State 4
24 Operational On-Line 0 0
Coupled Vector (Normal)
State 4
27 Operational On-Line Coasting 0 0
Vector (Normal)
Not No 1
28 Operational Failed 1 1
Coupled Output (Failed)

© EUROCAE, 2010
 79

NOTES:
1. Test Step of this test procedure, see 5.9.3.1.4.
2. ASTERIX Category 023 Type 1 report is the Ground Station Status
report. NOGO and TSV are flags in the data item I023/100 Ground
Station Status.
3. ASTERIX Category 023 Type 2 report is the Service Status report.
STAT is a three bit field in the data item I023/110 Service Status.

5.9.3.1.4 Test Procedure

Test Steps:
1. Start injecting a continuous sequence of position messages for a test target.
Wait until the target is acquired. Confirm that ASTERIX Category 021 reports
are produced. Confirm from the SNMP client that the Operational Mode, On-
Line State and UTC Coupled Time State are indicated using the following
SNMP monitoring parameters:
SNMP Monitoring Parameter Expected Value
{GSMode} Operational
{GSState} On-Line
{TimeSourceState} UTC Coupled

2. Confirm that a ASTERIX Category 023 Type 1 report is issued, in which the
data item Ground Station Status (I023/100) is reported as indicated in the
table below:

Bit 8 7 6 5 4 3 2 1
Flag NOGO ODP OXT MSC TSV SPO RN FX
Value 0 0 0 0 0 0 0 0

3. Confirm that an ASTERIX Category 023 Type 2 report is issued, in which the
data item Service Status (I023/110) is reported as indicated in the table below:
Bit 8 7 6 5 4 3 2 1
Flag STAT FX
Value 0 0 0 0 1 0 0 0

4. Restart the 1090 ES Ground Station. The Ground Station will enter the
Initialisation State. Confirm from the SNMP client that the Initialisation State is
indicated as listed in the table below:
SNMP Monitoring Parameter Expected Value
{GSMode} -
{GSState} Initialisation
{TimeSourceState} -

© EUROCAE, 2010
 80

5. Confirm that an ASTERIX Category 023 Type 1 report is issued, in which the
data item Ground Station Status (I023/100) is reported as indicated in the
table below:
Bit 8 7 6 5 4 3 2 1
Flag NOGO ODP OXT MSC TSV SPO RN FX
Value 1 0 0 0 1 0 0 0

6. Confirm that an ASTERIX Category 023 Type 2 report is issued, in which the
data item Service Status (I023/110) is reported as indicated in the table below:
Bit 8 7 6 5 4 3 2 1
Flag STAT FX
Value 0 0 0 0 1 0 1 0
Confirm that no ASTERIX Category 021 output is issued until the next test step.

7. After the successful completion of the power-on self-test the Ground Station
enters the On-Line State. Confirm from the SNMP client that the On-Line State
and UTC Coupled Time State are indicated as listed in the table below:
SNMP Monitoring Parameter Expected Value
{GSMode} Operational
{GSState} On-Line
{TimeSourceState} UTC Coupled

8. Confirm that the current mode is the same as the previous mode before the
switch off, i.e. the Operational Mode.

9. Confirm that an ASTERIX Category 023 Type 1 report is issued, in which the
data item Ground Station Status (I023/100) is reported as indicated in the
table below:
Bit 8 7 6 5 4 3 2 1
Flag NOGO ODP OXT MSC TSV SPO RN FX
Value 0 0 0 0 0 0 0 0

10. Confirm that an ASTERIX Category 023 Type 2 report is issued, in which the
data item Service Status (I023/110) is reported as indicated in the table below:
Bit 8 7 6 5 4 3 2 1
Flag STAT FX
Value 0 0 0 0 1 0 0 0
Confirm that ASTERIX Category 021 reports are produced.

© EUROCAE, 2010
 81

11. Switch the 1090 ES Ground Station into the Maintenance mode manually.
Confirm from the SNMP client that the Maintenance mode is indicated as listed
in the table below:
SNMP Monitoring Parameter Expected Value
{GSMode} Maintenance
{GSState} On-Line
{TimeSourceState} UTC Coupled

12. Confirm that an ASTERIX Category 023 Type 1 report is issued, in which the
data item Ground Station Status (I023/100) is reported as indicated in the
table below:
Bit 8 7 6 5 4 3 2 1
Flag NOGO ODP OXT MSC TSV SPO RN FX
Value 1 0 0 0 0 0 0 0

13. Confirm that an ASTERIX Category 023 Type 2 report is issued, in which the
data item Service Status (I023/110) is reported as indicated in the table below:
Bit 8 7 6 5 4 3 2 1
Flag STAT FX
Value 0 0 0 0 1 0 0 0
Confirm that ASTERIX Category 021 reports are not produced.

14. Restart the 1090 ES Ground Station and wait until successful completion of the
power-on self-test.

15. When the power-on self-test is successfully completed confirm that the 1090 ES
Ground Station enters the Maintenance Mode. Confirm from the SNMP client
that the Maintenance mode is indicated as listed in the table below:
SNMP Monitoring Parameter Expected Value
{GSMode} Maintenance
{GSState} On-Line
{TimeSourceState} UTC Coupled

16. Confirm that an ASTERIX Category 023 Type 1 report is issued, in which the
data item Ground Station Status (I023/100) is reported as indicated in the
table below:

Bit 8 7 6 5 4 3 2 1
Flag NOGO ODP OXT MSC TSV SPO RN FX
Value 1 0 0 0 0 0 0 0

© EUROCAE, 2010
 82

17. Confirm that an ASTERIX Category 023 Type 2 report is issued, in which the
data item Service Status (I023/110) is reported as indicated in the table below:
Bit 8 7 6 5 4 3 2 1
Flag STAT FX
Value 0 0 0 0 1 0 0 0
Confirm that ASTERIX Category 021 reports are not produced.

18. Switch the 1090 ES Ground Station into the Operational mode manually.
Confirm from the SNMP client that the Operational mode is indicated as listed in
the table below:
SNMP Monitoring Parameter Expected Value
{GSMode} Operational
{GSState} On-Line
{TimeSourceState} UTC Coupled

19. Confirm that an ASTERIX Category 023 Type 1 report is issued, in which the
data item Ground Station Status (I023/100) is reported as indicated in the
table below:
Bit 8 7 6 5 4 3 2 1
Flag NOGO ODP OXT MSC TSV SPO RN FX
Value 0 0 0 0 0 0 0 0

20. Confirm that an ASTERIX Category 023 Type 2 report is issued, in which the
data item Service Status (I023/110) is reported as indicated in the table below:
Bit 8 7 6 5 4 3 2 1
Flag STAT FX
Value 0 0 0 0 1 0 0 0
Confirm that ASTERIX Category 021 reports are produced.

21. Disable the UTC synchronisation in order to achieve loss of time

synchronisation. The Time State will change to Coasting. Confirm from the
SNMP client that the Coasting Time State is indicated as listed in the table
below:
SNMP Monitoring Parameter Expected Value
{GSMode} Operational
{GSState} On-Line
{TimeSourceState} Coasting

© EUROCAE, 2010
 83

22. Confirm that an ASTERIX Category 023 Type 1 report is issued, in which the
data item Ground Station Status (I023/100) is reported as indicated in the
table below:
Bit 8 7 6 5 4 3 2 1
Flag NOGO ODP OXT MSC TSV SPO RN FX
Value 0 0 0 0 0 0 0 0

23. Confirm that an ASTERIX Category 023 Type 2 report is issued, in which the
data item Service Status (I023/110) is reported as indicated in the table below:
Bit 8 7 6 5 4 3 2 1
Flag STAT FX
Value 0 0 0 0 1 0 0 0
Confirm that ASTERIX Category 021 reports are still produced.

24. Enable the UTC synchronisation in order to obtain a valid UTC before the
Ground Station Coasting Timeout has expired. Confirm from the SNMP client
that the UTC Coupled Time State is indicated as listed in the table below:
SNMP Monitoring Parameter Expected Value
{GSMode} Operational
{GSState} On-Line
{TimeSourceState} UTC Coupled

25. Confirm that an ASTERIX Category 023 Type 1 report is issued, in which the
data item Ground Station Status (I023/100) is reported as indicated in the
table below:
Bit 8 7 6 5 4 3 2 1
Flag NOGO ODP OXT MSC TSV SPO RN FX
Value 0 0 0 0 0 0 0 0

26. Confirm that an ASTERIX Category 023 Type 2 report is issued, in which the
data item Service Status (I023/110) is reported as indicated in the table below:
Bit 8 7 6 5 4 3 2 1
Flag STAT FX
Value 0 0 0 0 1 0 0 0
Confirm that ASTERIX Category 021 reports are produced.

27. Disable the UTC synchronisation in order to achieve loss of time

synchronisation. The Time State will change to Coasting. Wait until the Ground
Station Coasting Timeout is exceeded.

© EUROCAE, 2010
 84

28. When the Ground Station Coasting Timeout is exceeded the 1090 ES Ground
Station will enter the Not Coupled Time State. Confirm from the SNMP client
that the Not Coupled Time State and Failed State are indicated as listed in the
table below.
SNMP Monitoring Parameter Expected Value
{GSMode} Operational
{GSState} Failed
{TimeSourceState} Not Coupled

29. Confirm that an ASTERIX Category 023 Type 1 report is issued, in which the
data item Ground Station Status (I023/100) is reported as indicated in the
table below:
Bit 8 7 6 5 4 3 2 1
Flag NOGO ODP OXT MSC TSV SPO RN FX
Value 1 0 0 0 0 0 0 0

30. Confirm that an ASTERIX Category 023 Type 2 report is issued, in which the
data item Service Status (I023/110) is reported as indicated in the table below:

Bit 8 7 6 5 4 3 2 1

Flag STAT FX

Value 0 0 0 0 0 0 1 0

Confirm that no ASTERIX Category 021 output is produced.

31. Confirm that all the user access activity, i.e. restart in steps 0 and 14, mode
changeover in steps 11 and 18, warning messages from steps 21 and 27 and a
failure message from step 28 are logged. Confirm that all the state changes are
also logged.

5.9.3.2 Buffer Overflows

There are no specific tests for Section 3.9.3.2 as it does not contain mandatory
requirements.

5.9.3.3 Processor Overloads

There are no specific tests for Section 3.9.3.3 as it does not contain mandatory
requirements.

5.9.3.4 Target Overloads

The requirements of Section 3.9.3.4 are tested under Section 5.3.2.

5.9.3.5 Communications Overload

The requirements of Section 3.9.3.5 are tested under Section 5.3.3.

5.9.3.6 Communications Loss

There are no specific tests for Section 3.9.3.6 as the requirements are dependent on
the system design.

© EUROCAE, 2010
 85

5.9.3.7 Time Synchronisation

The requirements of Section 3.9.3.7 are tested under Section 5.9.3.1.

5.9.3.8 Temperature Range

There are no specific tests for Section 3.9.3.8 as it does not contain mandatory
requirements.

5.9.3.9 End to End System Test

5.9.3.9.1 Objectives

This test procedure verifies that the 1090 ES Ground Station is able to detect a loss of
test transmissions and a loss of receiver sensitivity as specified in section 3.9.3.9. The
requirements 3.9.3.9 c), d), e) and f) are addressed.
Requirements 3.9.3.9 a), b), g), h) and i) are not tested because they cannot be tested
directly. Requirement j) is optional.
This test procedure also verifies the requirements 3.9.6 a) capability to log the user
access activity, 3.9.6 b) capability to log warning and failure messages, 3.9.6 c)
capability to log control instructions, and 3.9.6 d) capability to timestamp log file
messages.

5.9.3.9.2 Test Equipment Setup

The test equipment setup shall be the same as the standard setup described in
Section 5.1.1 with the following exceptions:
• a means of varying the power level of injected end-to-end test messages, for
example by use of an attenuator.
NOTE: The exact messages used in end-to-end system test transmissions will be
manufacturer specific. In this test procedure any valid 1090 ES ADS-B
message may be used.

5.9.3.9.3 Scenario Design

Scenario 1 - Receiver Sensitivity

Three cases of injecting 1090 ES messages of a test target with the known Mode S
address are simulated for a period of at least 60 seconds.
NOTE: the default value for the {GSReportInterval} configuration parameter is 60
seconds. Therefore the scenario must be run for at least 60 seconds in
order to get at least one ASTERIX Category 023 report of type 1.
• In case 1 the power of the transmitted messages is above the power level
specified by the 1090 ES Ground Station parameter {TestTargetAlertPower}.
In this case the SNMP status of End to End System Test is expected to be
"Passed".
• In case 2 the power of 1090 ES position messages is between the levels
specified by the 1090 ES Ground Station parameters {TestTargetAlertPower}
and {TestTargetFailurePower}. In this case the SNMP status of End to End
System Test is expected to be "Warning".
• In the third case the power of 1090 ES position messages is below the
{TestTargetFailurePower}. In this case the SNMP status of End to End
System Test is expected to be "Failed". The NOGO bit in ASTERIX Category
023, Type 1 Report is expected to be set to one.
The scenario of this test is listed inTable 22.

© EUROCAE, 2010
 86

TABLE 22: SCENARIO 1 - RECEIVER SENSITIVITY

Expected Value of SNMP ASTERIX Category

Parameter 023 Type 1 Output
Case Power of 1090 ES
{ReceiverSensitivity} for
Receiver Sensitivity NOGO
Power of 1090 ES [note 0]
1 > Passed 0
{TestTargetAlertPower}
{TestTargetAlertPower}
>
2 power of 1090 ES [note 2] Warning 0
>
{TestTargetFailurePower}
{TestTargetFailurePower}
3 > Failed 1
Power of 1090 ES [note 3]

NOTES:
1. It is recommended to set the power of 1090 ES test messages to the
level of 1 dB above {TestTargetAlertPower}.
2. It is recommended to set the power of 1090 ES test messages to the
level of 1 dB above {TestTargetFailurePower}.
3. It is recommended to set the power of 1090 ES test messages to the
level of 1 dB below {TestTargetFailurePower}.

Scenario 2 - Loss of Test Transmission

1090 ES messages of a test target with the known address are injected at the rate
specified by the manufacturer for a period of at least 60 seconds. The configuration
parameter {TestTransmissionTimeout} is set to the default value of 10 seconds. The
transmission period of the test messages shall be at least half of the period specified
by the configuration parameter {TestTransmissionTimeout}. The power level of the
messages is above the alert level specified by the 1090 ES Ground Station parameter
{TestTargetAlertPower}.
Injection of the 1090 ES messages of the test target is then stopped. When no
messages of the test target have been received for 10 seconds the 1090 ES Ground
Station is expected to set the SNMP parameter {TestTransmission} to "Failed" and
NOGO bit in ASTERIX Category 023, Type 1 report to one.

© EUROCAE, 2010
 87

5.9.3.9.4 Test Procedure

Test Steps:
1. Put the 1090 ES Ground Station in the default configuration as specified in
Section 5.1 and switch it to the Maintenance Mode.
2. Set the following parameters to appropriate values in correct order:
{TestTargetAlertPower},
{TestTargetFailurePower},
The correct order means that the {TestTargetAlertPower} is above
the {TestTargetFailurePower} by at least 2 dB.
3. Prepare the message source to play scenario 1.
4. Play all three cases of scenario 1. Confirm from the SNMP client that for each
the case of scenario 1 the SNMP monitoring parameter for the receiver
sensitivity {ReceiverSensitivity} is set according toTable 22. Confirm also that
the SNMP monitoring parameter for overall End to End Test {EndToEnd} is set
to Failed when the parameter {ReceiverSensitivity} indicates Failed.
5. From the recorded ASTERIX Category 023 outputs confirm that ASTERIX
Category 023 reports agree with Table 22. (NOGO bit set when Failure is
reported in the SNMP parameters).
6. Prepare the message source to play scenario 2.
7. Play scenario 2 for at least 60 seconds. Confirm from the SNMP client that the
SNMP parameter for Loss of Test Transmission {TestTransmission} is set to
Passed.
8. Confirm that at least one ASTERIX Category 023 report is issued with NOGO
bit set to zero.
9. Stop injecting messages of the test target.
10. Confirm from the SNMP client that the parameter {TestTransmission} is set to
Failed after 10 seconds.
11. Confirm from the SNMP client that also the parameter {EndToEnd} is set to
Failed when {TestTransmission} indicates Failed.
12. Wait until an ASTERIX Category 023 report is issued. Confirm that NOGO bit is
set to one.
13. Verify that the time of the Log File Message when the loss of test transmission
occurred is within the accuracy of 1 s.
14. Confirm that all the user access activity, all the warning and failure messages
and all the control instructions during this test procedure are logged. Confirm
that the timestamp of the failure log message in scenario 2 is with a resolution
of 1 s of the time when the failure occurred.

5.9.4 Control Functions

5.9.4.1 Objectives

This test procedure verifies that the 1090 ES Ground Station can be controlled in
accordance with the requirements specified in Section 3.9.4.
The requirements 3.9.4 b), c), d), e), and f) are covered. The requirement 3.9.4 a) is
tested elsewhere in Section 5.9.3.1 (the test procedure for Status Reporting).
This test procedure also verifies the requirements 3.9.6 a) capability to log the user
access activity and 3.9.6 c) capability to log control instructions.

© EUROCAE, 2010
 88

5.9.4.2 Test Equipment Setup

The test equipment setup shall be the same as the standard setup described in
Section 5.1.1 with the following exceptions:
• an external electronic media for storing the 1090 ES Ground Station
configuration parameters.

5.9.4.3 Scenario Design

The control functions are tested only on the following 1090 ES Ground Station
Configuration Parameters:
• GSIPAddr (Internet Protocol Address of the 1090 ES Ground Station)
• GSIPNetmask (Internet Protocol Netmask of the 1090 ES Ground Station)
• GSIPDefGW (Internet Protocol default gateway for the 1090 ES Ground
Station)
• ASTERIXTTL (Internet Protocol Time-To-Live for transmitted ASTERIX reports)
The other 1090 ES Ground Station required configuration parameters are tested in
other test procedures. All the required configuration parameters and the test
procedures, in which the parameters are tested, are listed in Table 23.

TABLE 23: TESTING OF REQUIRED CONFIGURATION PARAMETERS

Configuration Parameter Test Procedure

System Mode
5.9.3.1 - Status Reporting
{SystemMode}
System Identification Code
5.10.3 - Data Item Inclusion
{SIC*}
System Area Code
5.10.3- Data Item Inclusion
{SAC*}
GS IP Address
5.9.4.3 – (This procedure)
{GSIPAddr*}
GS IP Default Gateway
5.9.4.3 – (This procedure)
{GSIPDefGW*}
GS IP Netmask
5.9.4.3 – (This procedure)
{GSIPNetmask*}
ASTERIX Report Destination IP Address
Tested Implicitly
{ASTERIXDestIPAddr*}
ASTERIX Report Destination UDP port
Tested Implicitly
{ASTERIXDestPort*}
ASTERIX Report IP TTL
5.9.4.3 – (This procedure)
{ASTERIXTTL*}
Maximum Ground Interface Bit Rate 5.3.3 - Communications
{MaxCommBitRate*} Overloads
ASTERIX State Vector Reporting Mode 5.10.2.3.1 - Periodic State
{ASTERIXReportMode*} Vector Reports
Periodic Reporting Interval 5.10.2.3.1- Periodic State
{PeriodicReportInterval*} Vector Reports

© EUROCAE, 2010
 89

Configuration Parameter Test Procedure

CPR Airborne Maximum Range
5.10.2.4.1 - Range Check
{CPRAirborneMaxRange}
ASTERIX Category 023 Ground Station Status
Reporting Interval 5.10.3.2 - Status Reports
{GSReportInterval*}
ASTERIX Category 023 Service Status
Reporting Interval 5.10.3.2- Status Reports
{ServiceReportInterval*}
ASTERIX Category 247 Reporting Interval 5.10.3.3 - ASTERIX Version
{VersionReportInterval*} Reports
GS Latitude
5.10.2.4.1 - Range Check
{GSLatitude}
GS Longitude
5.10.2.4.1 - Range Check
{GSLongitude}
Test Target Alert Power Threshold 5.9.3.9 - End to End System
{TestTargetAlertPower} Test
Test Target Fail Power Threshold 5.9.3.9- End to End System
{TestTargetFailPower} Test
Capacity Threshold
5.3.1 - Overall Capacity
{CapacityThreshold}

In the first part of the test, installing of alternate 1090 ES Ground Station software is
tested. In the second part, saving, restoring and modifying of the configuration
parameters are tested.

5.9.4.4 Test Procedure

Test Steps - installing software via the control and monitoring interface:
1. Put the 1090 ES Ground Station in the default configuration.
2. Note the current version of the 1090 ES Ground Station software.
3. Install an alternate version of the software.
4. Verify by checking the version number of the installed software that the software
has been changed.
5. Revert to the original version and verify that it is operating under that original
version.
Test Steps - saving, changing and restoring all the configuration parameters:
6. Save all the configuration parameters of the 1090 ES Ground Station to an
external electronic media. Confirm from the saved file that all the required
configuration parameters are implemented.
7. Change the following parameters:
GSIPAddr
GSIPDefGW
GSIPNetMask
ASTERIXTTL

© EUROCAE, 2010
 90

8. Verify that these configuration parameters are changed in the 1090 ES Ground
Station.
9. Restart the 1090 ES Ground Station. Confirm that the configuration parameters
have not changed during the restart and the initialisation state of the 1090 ES
Ground Station.
10. Restore the configuration parameters from the data saved to the external
electronic media. Confirm that all the configuration parameters are restored
back to those before the modification.
11. Confirm that all the user access activity and all the control instructions during
this test procedure are logged.

5.9.5 Security

5.9.5.1 Objectives

This test procedure verifies that the 1090 ES Ground Station can be commanded and
configured by authorised users only, in accordance with the requirements specified in
Section 3.9.5.

5.9.5.2 Test Equipment Setup

The test equipment setup shall be the same as the standard setup described in
Section 5.1.

5.9.5.3 Scenario Design

No 1090 ES message scenario design is needed for this test.

5.9.5.4 Test Procedure

Test Steps:
1. Put the 1090 ES Ground Station in the default configuration. Set the current
mode to Maintenance.
2. Try to change the configuration as an unauthorised user. For example set
CPRAirborneMaxRange different from the current value. Confirm that the 1090
ES Ground Station does not allow this change.
3. Change the mode of the 1090 ES Ground Station to Operational as an
unauthorised user. Confirm the 1090 ES Ground Station does not allow this
change.

5.9.6 Data Logging

5.9.6.1 Objectives

This test procedure verifies that the 1090 ES Ground Station is able to handle log files
in accordance with the requirements specified in Section 3.9.6 e) and f).
The requirements 3.9.6 a), b), c) and d) are tested as parts of the test procedures
listed in Table 24.

© EUROCAE, 2010
 91

TABLE 24: REQUIREMENTS TESTED IN OTHER TEST PROCEDURES

Requirement Test procedure

0 a) 0, 0, 0
0 b) 0, 0,
0 c) 0, 0, 0
0 d) 0

5.9.6.2 Test Equipment Setup

The test equipment setup shall be the same as the standard setup described in
Section 5.1 with the following exceptions:
An external storage device shall be included.

5.9.6.3 Scenario Design

No 1090 ES message scenario design is needed for this test.

5.9.6.4 Test Procedure

1. Save the existing log file into an external storage device.

2. Confirm that the log file was successfully stored by comparison with the online
log file in the 1090 ES Ground Station.
3. Disconnect the power supply.
4. Connect back the power supply.
5. Confirm by comparison with the previous online log file of the 1090 ES Ground
Station or the saved log file in the external storage device that the Ground
Station is able to retain the log file in the event of loss of power.

5.10 MESSAGE PROCESSING AND REPORT ASSEMBLY

5.10.1 General Message Processing Requirements

5.10.1.1 Message Type Filtering

5.10.1.1.1 Objectives

Verify that the 1090 ES Ground Station processes the following 1090 MHz Extended
Squitter messages in accordance with section 3.10.1.1:
• Any message with DF = 17 from an airborne participant;
• Messages with DF = 18 and CF = 0 or 1 from an airborne participant;
• Messages with DF = 19 and AF = 0.
As an option, the 1090 ES Ground Station may process non-ADS-B Mode S
messages, TIS-B messages, surface participant messages or other message types.
This test procedure verifies that such messages do not generate ASTERIX Category
021 reports by default.

5.10.1.1.2 Test Equipment Setup

The test equipment setup shall be the same as the standard setup described in
Section 5.1.1.

© EUROCAE, 2010
 92

5.10.1.1.3 Scenario Design

The scenario consists of the Mode S messages shown in Table 25.

TABLE 25: ES MESSAGES FOR MESSAGE TYPE FILTERING TEST

ASTERIX
Msg Inject Category
DF CA/CF/AF FTC CPR Notes
No Time (s) 021
Report
1 0.5 17 0 9-18 0 No
2 1.0 17 4 9-18 1 No
3 1.1 0 NA No
4 1.2 4 NA No
5 1.3 5 NA No
6 1.4 11 NA No
7 1.5 16 NA No
8 1.6 20 NA No
9 1.7 21 NA No
10 2.0 18 2 9-18 0 No Use position > 4.5 NM from
Msg No 2.
11 2.5 18 3 9-18 1 No Use position > 4.5 NM from
Msg No 2.
12 3.0 18 4 9-18 0 No Use position > 4.5 NM from
Msg No 2.
13 3.5 18 5 9-18 1 No Use position > 4.5 NM from
Msg No 2.
14 4.0 18 6 9-18 0 No Use position > 4.5 NM from
Msg No 2.
15 4.5 18 2 5-8 1 No Use position > 4.5 NM from
Msg No 2.
16 5.0 18 3 5-8 0 No Use position > 4.5 NM from
Msg No 2.
17 5.5 18 4 5-8 1 No Use position > 4.5 NM from
Msg No 2.
18 6.0 18 5 5-8 0 No Use position > 4.5 NM from
Msg No 2.
19 6.5 18 6 5-8 1 No Use position > 4.5 NM from
Msg No 2.
20 7.0 17 7 5-8 0 No Use position < 1 NM from
Msg No 2
21 7.5 17 5 9-18 0 No Use position < 1 NM from
Msg No 2
22 8.0 17 6 9-18 1 Yes Use position < 1 NM from
Msg No 2
23 8.5 18 0 9-18 0 Yes Use position < 4 NM from
Msg No 22
24 9.0 18 1 9-18 1 Yes Use position < 4 NM from
Msg No 22
25 9.1 0 NA No
26 9.2 4 NA No
27 9.3 5 NA No
28 9.4 11 NA No
29 9.5 16 NA No

© EUROCAE, 2010
 93

ASTERIX
Msg Inject Category
DF CA/CF/AF FTC CPR Notes
No Time (s) 021
Report
30 9.6 20 NA No
31 9.7 21 NA No
32 10.0 18 2 9-18 0 No Use position < 4NM from
Msg No 22
33 10.5 18 3 9-18 1 No Use position < 4NM from
Msg No 22
34 11.0 18 4 9-18 0 No Use position < 4NM from
Msg No 22
35 11.5 18 5 9-18 1 No Use position < 4NM from
Msg No 22
36 12.0 18 6 9-18 0 No Use position < 4NM from
Msg No 22
37 12.5 18 2 5-8 1 No Use position < 4NM from
Msg No 22
38 13.0 18 3 5-8 0 No Use position < 4NM from
Msg No 22
39 13.5 18 4 5-8 1 No Use position < 4NM from
Msg No 22
40 14.0 18 5 5-8 0 No Use position < 4NM from
Msg No 22
41 14.5 18 6 5-8 1 No Use position < 4NM from
Msg No 22
42 15.0 17 0 5-8 1 No Use position < 4NM from
Msg No 22
43 15.5 17 4 5-8 0 No Use position < 4NM from
Msg No 22
44 16.0 17 5 5-8 1 No Use position < 4NM from
Msg No 22
45 16,5 17 6 5-8 0 No Use position < 4NM from
Msg No 22
46 17.0 17 7 5-8 1 No Use position < 4NM from
Msg No 22
47 17.5 17 5 9-18 0 Yes Use position < 4NM from
Msg No 22
48 18.0 17 6 9-18 1 Yes Use position < 4NM from
Msg No 22
49 18.5 18 0 9-18 0 Yes Use position < 4NM from
Msg No 22
50 19.0 18 1 9-18 1 Yes Use position < 4NM from
Msg No 22
51 19.5 19 0 9-18 1 Yes Use position < 4NM from
Msg No 22
52 20.0 19 1 NA No Randomise bits 9 through
112

All messages except Msg No 52 should have the same announced address (AA) or
should use the same address for determining the AP field, depending on the DF type.

© EUROCAE, 2010
 94

5.10.1.1.4 Test Procedure

Test Steps:
1. Play the scenario.
2. When the scenario is complete, stop recording ASTERIX reports.
3. Analyze the recorded data and verify that reports are produced as shown in the
table. Verify that the contents of the ASTERIX reports are consistent with the
input data in the ES messages (e.g. correct lat/lon, altitude etc.)

5.10.1.2 Extended Squitter Version Processing

5.10.1.2.1 Objectives

The aim of this test procedure is to check that the system detects the version of the
1090 ES MOPS of messages received, decodes the messages according to the
detected version, and reports the parameters contained therein accordingly. During
the test, all the transitions between version states are tested.

5.10.1.2.2 Test Equipment Setup

The test equipment setup shall be the same as the standard setup described in
Section 5.1.1 with the following exceptions:
• Emitter category item 20 shall be active in ASTERIX Category 021 reports.

5.10.1.2.3 Scenario Design

The following scenario has been designed to cover all possible version state
transitions [see also Table 26 below]:
Step 1: Target acquisition and version 0 assumed. VNS=0, VN=0.
Step 2: Change from version 0 assumed to version 0 confirmed.
Step 3: Change from version 0 confirmed to version 1.
Step 4: Change from version 1 confirmed to version 0 confirmed.
Step 5: Change from version 0 confirmed to unrecognised version. Note: VNS is
1 for unrecognised version.
Step 6: Change from unrecognised version to version 0 confirmed.
Step 7: 92 Seconds of position messages only. Version information should
expire, resulting in assumed version 0. VNS=0, VN=0.
Step 8: Change from version 0 assumed to version 1.
Step 9: Change from version 1 confirmed to unrecognised version. Note: VNS is
1 for unrecognised version.
Step 10: Change from unrecognised version to version 1 confirmed.
Step 11: 92 Seconds of position messages only. Version information should
expire, resulting in assumed version 0. VNS=0, VN=0.
Step 12: Change from version 0 assumed to unrecognised version. Note: VNS is 1
for unrecognised version.
Step 13: 92 Seconds of position messages only. Version information should
expire, resulting in assumed version 0. VNS=0, VN=0.
Once these steps are completed, all possible version state transitions are covered.
NOTE: The target in this scenario may be stationary. Velocity messages and
emitter category / callsign messages may be present but are not required

© EUROCAE, 2010
 95

TABLE 26: ES VERSION STATE PROCESSING TEST

Expected ASTERIX Category 021
ES Input
Output
Step Inject
MOPS
Msg ID Time FTC CPR Rpt VNS VN
VN
(s)
PO1 0.5 18 0
PE2 1 18 1
1 PO3 1.5 18 0
PE4 2 18 1 R1 0 0 (assumed)
PO5 2.5 18 0 R2 0 0 (assumed)
AOS1 2.6 31 0
2
PE6 3 18 1 R3 0 0 (confirmed)
AOS2 3.1 31 1
3
PO7 3.5 18 0 R4 0 1
AOS3 3.6 31 0
4
PE8 4 18 1 R5 0 0 (confirmed)
PO9 4.5 18 1 R6 0 0 (confirmed)
5 AOS4 4.8 31 3
PE10 5 18 1 R7 1 3 (unrecognised)
AOS5 5.4 31 0
6
PO11 5.5 18 0 R8 0 0 (confirmed)
PE12 6 18 1 R9 0 0 (confirmed)
PO13 6.5 18 0 R10 0 0 (confirmed)
Position messages (PE14 through PO197) are continued at half-second
intervals for the next 92 seconds. No AOS messages are to be injected during
this period.
PE198 99 18 1 R195 0 (assumed)
7 PO199 99.5 18 0 R196 0 0 (assumed)
AOS6 99.6 31 1
8 PE200 100 18 1 R197 0 1
PO201 100.5 18 0 R198 0 1
9 AOS7 138.3 31 3
PE202 101 18 1 R199 1 3 (unrecognised)
AOS8 138.6 31 1
10 PO203 101.5 18 0 R200 0 1
PE204 102 18 1 R201 0 1
PO205 102.5 18 0 R202 0 1
Position messages (PE206 through PO389) are continued at half-second
intervals for the next 92 seconds. No AOS messages are to be injected during
this period.
PE390 195 18 1 R387 0 0 (assumed)
11 PO391 195.5 18 0 R388 0 0 (assumed)
12 PE392 196 18 1 R389 0 0 (assumed)
AOS9 196.3 31 3

© EUROCAE, 2010
 96

Expected ASTERIX Category 021

ES Input
Output
Step Inject
MOPS
Msg ID Time FTC CPR Rpt VNS VN
VN
(s)
PO393 196.5 18 0 R390 1 3 (unrecognised)
PE394 197 18 1 R391 1 3 (unrecognised)
PO395 197.5 18 0 R392 1 3 (unrecognised)
Position messages (PE396 through PO580) are continued at half-second
13 intervals for the next 92 seconds. No AOS messages are to be injected during
this period.
PE581 290 18 1 R578 0 0 (assumed)
PO582 290.5 18 0 R579 0 0 (assumed)

5.10.1.2.4 Test Procedure

Test Steps:
1. Put the GS in the default configuration.
2. Make the following configuration:
Activate Emitter category item I021/020 in ASTERIX Category 021 reports.
3. Prepare the report capture tool to capture ASTERIX reports.
4. Prepare the message source to play the scenario.
5. Play the scenario.
6. When the scenario is complete, stop recording ASTERIX reports.
7. Analyse the recorded data and verify that the expected outputs are present as
per Table 26.

5.10.1.3 Duplicate Mode S Address Processing

5.10.1.3.1 Objectives

This test procedure verifies that the 1090 ES Ground Station is able to produce
separate ASTERIX Category 021 reports for two targets with the same Mode S
address in accordance with the requirements specified in Section 3.10.1.3.

5.10.1.3.2 Test Equipment Setup

The test equipment setup shall be the same as the standard setup described in
Section 5.1.

5.10.1.3.3 Scenario Design

In order to test the ability to detect a target with duplicate Mode S address in any point
in the lifecycle (i.e. acquisition, maintenance) of the other target three different
scenarios are tested. In these scenarios the two targets with the same Mode S
address and with 6 - 6.1 NM of horizontal separation are simulated. Altitudes of the
targets should be the same. Testing with other altitude combinations is recommended
but not required.

© EUROCAE, 2010
 97

5.10.1.3.4 Scenario 1

In this scenario the first target is simulated through the acquisition life cycle. When the
target passes the range check and CPR validation and enters the maintenance life
cycle, ASTERIX Category 021 Output starts to be issued with CL and RC flags of data
item I021/040 set to zero. Two more position messages of this target are injected in
order to verify that these positions are reported as new updates of the position of this
target.
Injection of the second target is then started. After the second target passes the range
check and the CPR validation, both targets shall be flagged as duplicates in ASTERIX
Category 021 output (ATP is set to one). The scenario 1 is listed in Table 27.
NOTE: The later target is the first target with ATP flag of data item I021/040 set to
one.

TABLE 27: SIMULATING OF TWO DUPLICATE TARGETS IN SCENARIO 1

ES Input Expected ASTERIX Category 021

Output
Injec Targe CPR Lat Lon Alt Lat Lon CL RC ATP
tTim t [notes [notes [notes [note [note
e (s) 1,3] 1,3] 2,4] s 5,6, s 5,6,
7] 7]

0 0 YZ01 XZ01 H1 No Output

0.5 1 YZ11 XZ11 H1 No Output

1 1 0 YZ01 XZ01 H1 No Output

1.5 1 YZ11 XZ11 H1 Rlat11 Rlon11 0 0 0

2.0 0 YZ01 XZ01 H1 Rlat01 Rlon01 0 0 0

2.25 2 0 YZ02 XZ02 H2 No Output

2.5 1 1 YZ11 XZ11 H1 Rlat11 Rlon11 0 0 0

2.75 2 1 YZ12 XZ12 H2 No Output

3.0 1 0 YZ01 XZ01 H1 Rlat01 Rlon01 0 0 0

3.25 2 0 YZ02 XZ02 H2 No Output

3.5 1 1 YZ11 XZ11 H1 Rlat11 Rlon11 0 0 0

3.75 2 1 YZ12 XZ12 H2 Rlat12 Rlon12 0 0 1

4.0 1 0 YZ01 XZ01 H1 Rlat01 Rlon01 0 0 1

© EUROCAE, 2010
 98

NOTES:
1. An arbitrary chosen position of target 1 (Lat1,Lon1) within the range of the
1090 ES Ground Station is encoded into a pair YZ01, XZ01 or YZ11, XZ11
using the CPR Encoding process with even or odd format, respectively.
2. H1 is an arbitrary chosen altitude of target 1.
3. An arbitrary chosen position of target 2 (Lat2,Lon2) within the range of the
1090 ES Ground Station is encoded into a pair YZ02, XZ02 or YZ12, XZ12
using the CPR Encoding process with even or odd format, respectively.
The distance between the positions of target 1 and 2 shall be 6 - 6.1 NM.
4. H2 is an arbitrary chosen altitude of target 2. The Ground Station must
pass the test when H2 = H1. Testing with other altitude combinations is
recommended but not required.
5. A pair Rlat01, Rlon01 or Rlat11, Rlon11 is a position of target 1 reported in
ASTERIX Category 021 reports. The position is a decoded position using
Locally Unambiguous CPR Decoding with even or odd format,
respectively.
6. 6. A pair Rlat02, Rlon02 or Rlat12, Rlon12 is a position of target 2 reported
in ASTERIX Category 021 reports. The position is a decoded position
using Locally Unambiguous CPR Decoding with even or odd format,
respectively.
7. Latitude and longitude in ASTERIX Category 021 reports must match the
corresponding latitude and longitude used to create the ES messages to
within one-half of the sum of the CPR resolution (Dlati/2Nb and Dloni/2Nb,
see A.1.7 of DO-260A) and the ASTERIX Category 021 resolution
(180/223 for I021/130 or 180/230 for I021/131).

5.10.1.3.5 Scenario 2

In this scenario the first target is simulated through the range check. When the target
passes the range check and is currently in the CPR validation the second target is
started to be simulated. The simulation of both the targets continues until both of them
enter the maintenance point of their life cycle. Both the targets shall then be flagged
as duplicates in ASTERIX Category 021 output (ATP is set to one). The scenario 2 is
listed in Table 28.
NOTE: The later target is the first target with ATP flag of data item I021/040 set to
one.

© EUROCAE, 2010
 99

TABLE 28: SIMULATING OF TWO DUPLICATE TARGETS IN SCENARIO 2

ES Input Expected ASTERIX Category 021

Output
Inject Targe CP Lat Lon Alt Lat Lon CL RC ATP
Time t R [notes [notes [notes [notes [notes
(s) 1,3] 1,3] 2,4] 5,6,7] 5,6,7]
0 1 0 YZ01 XZ01 H1 No Output
1 1
0.5 1 1 YZ1 XZ1 H1 No Output
0.75 2 0 YZ02 XZ02 H2 No Output
1 1
1 1 0 YZ0 XZ0 H1 No Output
1.25 2 1 YZ12 XZ12 H2 No Output
1 1 1
1.5 1 1 YZ1 XZ1 H1 Rlat1 Rlon11 0 0 0
1.75 2 0 YZ12 XZ12 H2 No Output
1 1 1
2.0 1 0 YZ0 XZ0 H1 Rlat0 Rlon01 0 0 0
2.25 2 0 YZ02 XZ02 H2 Rlat02 Rlon02 0 0 1
1 1 1 1
2.5 1 1 YZ1 XZ1 H1 Rlat1 Rlon1 0 0 1
2.75 2 1 YZ12 XZ12 H2 Rlat12 Rlon12 0 0 1
1 1 1 1
3.0 1 0 YZ0 XZ0 H1 Rlat0 Rlon0 0 0 1
NOTES: see Notes of Table 27.

5.10.1.3.6 Scenario 3

In this scenario both the targets are simulated simultaneously through their life cycle
until both of them reach the maintenance point of their life cycle. Both the targets shall
then be flagged as duplicates in ASTERIX Category 021 output (ATP is set to one).
The scenario 3 is listed in Table 29.
NOTE: The later target is the first target with ATP flag of data item I021/040 set to
one.

© EUROCAE, 2010
 100

TABLE 29: SIMULATING OF TWO DUPLICATE TARGETS IN SCENARIO 3

ES Input Expected ASTERIX Category 021

Output
Inject Targe CP Lat Lon Alt Lat Lon CL RC ATP
Time t R [notes [notes [notes [notes [notes
(s) 1,3] 1,3] 2,4] 5,6,7] 5,6,7]
0 1 0 YZ01 XZ01 H1 No Output
2 2
0.25 2 0 YZ0 XZ0 H2 No Output
0.5 1 1 YZ11 XZ11 H1 No Output
2 2
0.75 2 1 YZ1 XZ1 H2 No Output
1 1 0 YZ01 XZ01 H1 No Output
2 2
1.25 2 0 YZ0 XZ0 H2 No Output
1.5 1 1 YZ11 XZ11 H1 Rlat11 Rlon11 0 0 0
2 2 2 2
1.75 2 1 YZ1 XZ1 H2 Rlat1 Rlon1 0 0 1
2.0 1 0 YZ01 XZ01 H1 Rlat11 Rlon11 0 0 1
2 2 2 2
2.25 2 0 YZ0 XZ0 H2 Rlat1 Rlon1 0 0 1
NOTES: see Notes of Table 27

5.10.1.3.7 Test Procedure

Preconditions:
Equipment is setup as described above
Test Steps:
1. Put the 1090 ES Ground Station in the default configuration.
2. Prepare the report capture tool to capture ASTERIX reports.
3. Prepare the message source to play scenario 1.
4. Play scenario 1.
5. When the scenario 1 is complete, stop recording ASTERIX reports.
6. Analyze the recorded data and verify that the expected outputs are present.
7. Prepare the report capture tool to capture ASTERIX reports.
8. Prepare the message source to play scenario 2 and ensure that the 1090 ES
Ground Station does not contain information on any targets.
9. Play scenario 2.
10. When scenario 2 is complete, stop recording ASTERIX reports.
11. Analyze the recorded data and verify that the expected outputs are present.
12. Prepare the message source to play scenario 3 and ensure that the 1090 ES
Ground Station does not contain information on any targets.
13. Play scenario 3.
14. When scenario 3 is complete, stop recording ASTERIX reports.
15. Analyze the recorded data and verify that the expected outputs are present.

© EUROCAE, 2010
 101

5.10.2 Report Triggering

5.10.2.1 Report Types

There are no specific tests for Section 3.10.2.1.

5.10.2.2 Data Driven Transmission Mode

5.10.2.2.1 ASTERIX Category 021 Data Driven Reports

There are no specific tests for Section 3.10.2.2.1. The requirements are tested in
section 5.10.3.1.2.

5.10.2.2.2 ASTERIX Category 023 Event Driven Reports

There are no specific tests for Section 3.10.2.2.2. The requirements are instead
verified during the tests in sections 5.3, 5.9.3.1 and 5.9.3.9.

5.10.2.3 Periodic Transmission Mode

5.10.2.3.1 ASTERIX Category 021 Periodic Reports

Objectives
This procedure tests the following requirements in section 3.10.2.3.1 for ASTERIX
Category 021 Periodic Reports.
The data content of the minimum fields is not tested here as the test procedure for this
is described under the tests in section 5.10.3.1.2.
Test Equipment Setup
The test equipment setup shall be the same as the standard setup described in
Section 5.1.1.
Scenario Design
The following scenario tests that data driven reports are produced following a change
in the Emergency/Priority status or Surveillance Status. It uses messages from one
target only.

© EUROCAE, 2010
 102

TABLE 30: ASTERIX CATEGORY 021 PERIODIC REPORT TEST SCENARIO

Expected ASTERIX Category 021

ES Input
Output
FTC/ Inject Emerg/ Emerg/
Msg
Sub- Time Priority SS Rpt Priority SS
ID
type (s) Status Status

PE1 0
PO2 0.5
PE3 1.0
PO4 1.5
PO5 5.0 1 P1 0 1
TS1 28/1 6.0 1 P2 1 1
OS1 31/0 7.0 2 P3 2 1
TS2 28/1 8.0 3 P4 3 1
OS2 31/0 9.0 4 P5 4 1
TS3 28/1 10.0 5 P6 5 1
OS3 31/0 11.0 6 P7 6 1
TS1 28/1 12.0 7 P8 7 1
OS1 31/0 13.0 0 P9 0 1
PO6 14.0 2 P10 0 2
PO7 15.0 3 P11 0 3
PO8 16.0 0 P12 0 0

Test Procedure
Test Steps:
1. Set the test generator to inject alternate odd and even position squitter
messages for the same aircraft address, all having FTC ≠ 0, initially at a rate of
3 messages per second. Note – this ensures that a report is triggered on each
0.5 s interval in step 2.
2. Set the ASTERIX Category 021 periodic report interval to 0.5 s.
3. Verify that ASTERIX Category 021 position reports are produced for the test
aircraft address at intervals of 0.5 s.
4. Reduce the message rate lower than the reciprocal of the report interval, i.e.
below 2 Hz.
5. Verify that ASTERIX Category 021 periodic reports are now produced only at
the same overall rate as the input messages.
6. Repeat steps 4 to 8 but setting the ASTERIX Category 021 periodic report
interval to 1.0, 1.5, 14.5 and 15.0 seconds.
7. Change the generator to set FTC = 0 in the input messages and verify that no
ASTERIX Category 021 reports are generated.
8. Analyze the recorded data and verify that the expected minimum fields as
defined in section 3.10.3.1.1 are present.

© EUROCAE, 2010
 103

9. Play the test scenario in the table above.

10. Check that the expected ASTERIX Category 021 reports were generated. Verify
that any changes in the Surveillance Status or Emergency/Priority Status in the
ES Input are reflected in the Category 021 output within 5 seconds. With the
report interval still set to 15 seconds from step 6, one Position State Vector
report, in addition to those in the table above, may be issued during this step.

5.10.2.3.2 ASTERIX Category 023 Periodic Reports

Objectives
Verify that ASTERIX Category 023 Ground Station Status and Service Status reports
are transmitted in periodic mode with an independently configurable period, according
to section 3.10.3.2.
Note – the presence and data content of the minimum fields for ASTERIX Category
023 reports are tested in section 5.10.3.2.
Test Equipment Setup
The test equipment setup shall be the same as the standard setup described in
Section 5.1.1.
Scenario Design
There is no requirement to inject ADS-B messages for this test, since reporting of
status is independent of target processing.
Test Procedure
Test Steps:
1. Set the ASTERIX Category 023 Ground Station Status report interval to 1
second.
2. Verify that ASTERIX Category 023 Ground Station Status reports are produced
at intervals of 1 second. Verify that ASTERIX Category 023 Service Status
reports are produced at the default interval of 10 seconds.
3. Set the ASTERIX Category 023 Ground Station Status report interval to 2
seconds.
4. Verify that ASTERIX Category 023 Ground Station Status reports are produced
at intervals of 2 seconds.
5. Set the ASTERIX Category 023 Ground Station Status report interval to 127
seconds.
6. Verify that ASTERIX Category 023 Ground Station Status reports are produced
at intervals of 127 seconds.
7. Set the ASTERIX Category 023 Service Status report interval to 1 second.
8. Verify that ASTERIX Category 023 Service Status reports are produced at
intervals of 1 second. Verify that ASTERIX Category 023 Ground Station Status
reports are produced at intervals of 127 seconds.
9. Set the ASTERIX Category 023 Service Status report interval to 2 seconds.
10. Verify that ASTERIX Category 023 Service Status reports are produced at
intervals of 2 seconds.
11. Set the ASTERIX Category 023 Service Status report interval to 127 seconds.
12. Verify that ASTERIX Category 023 Service Status reports are produced at
intervals of 127 seconds.

© EUROCAE, 2010
 104

5.10.2.3.3 ASTERIX Category 247 Periodic Reports

There are no specific tests for Section 3.10.2.3.3. The requirements are tested under
section 5.10.3.3.

5.10.2.4 Target Acquisition

5.10.2.4.1 Range Check

Objectives
This test procedure verifies that the 1090 ES Ground Station checks that the position
of a newly acquired target lies within a credible area [or volume] relative to the ground
station, ensuring that no ASTERIX position report is generated for new targets with
unreasonable position values.
A target is considered as new when the 1090ES Ground Station has no previous
position information for it.
This procedure does not verify the range check operation under periodic reporting
mode operation since the range check function is assumed to be the same as under
the data driven mode.
Test Equipment Setup
The test equipment setup shall be the same as the standard setup described in
Section 5.1.1.
Scenario Design
The 1090 ES Ground Station will be injected with a sequence of four even/odd pairs of
position squitters as shown in the diagram below where the first two pairs refer to
airborne target A1 while the last two pairs are for airborne target A2 which must be
distinct from A1. The locations of A1 and A2 shall be such that the first is within the
acceptance range of the station and the second outside.
It has to be shown that position reports are generated only for A1 as shown in the
table below.

Expected ASTERIX Category 021

ES Input
Output
Inject 24-
Msg
Time bit CPR Lat Lon Rpt Lat Lon CL RC
ID
(s) Addr
PE1 0 A1 0 Y1 X1 No Output
PO2 0.5 A1 1 Y1 X1 No Output
PE3 1.0 A1 0 Y1 X1 No Output
PO4 2.5 A1 1 Y1 X1 R1 Y21 X1 0 0
PE5 3.0 A2 0 Y2 X2 No Output
PO6 3.5 A2 1 Y2 X2 No Output
PE7 4.0 A2 0 Y2 X2 No Output
PO8 4.5 A2 1 Y2 X2 No Output

2
The expected latitude and longitude may vary from the input latitude and longitude by the combined quantisation
errors of the CPR algorithm and the ASTERIX Category 021 latitude/longitude encoding.

© EUROCAE, 2010
 105

A1 and A2 can be any two distinct legal 24-bit Mode Addresses.

[Y1, X1] can be any lat/long position whose distance from the Ground Station location
is less than CPRAirborneMaxRange and greater than
CPRAirborneMaxRange – 0.5 NM.
[Y2, X2] can be any lat/long position whose distance from the Ground Station location
is greater than CPRAirborneMaxRange but less than
CPRAirborneMaxRange + 0.5 NM.
The timing of the messages for A2 (PE5 to PO8) may be shifted with regard to those
for A1 (PE1 to PO4).
The above scenario will be repeated for additional targets at same ranges as A1 and
A2 but displaced from them to bearings of +12, +22 and +45 degrees to ensure that
the area being checked is round. More points may be included in scenario. Messages
for each target may be interleaved or separated in time.
Test Procedure
Test Steps:
1. Play the scenario described above and log the output ASTERIX reports
2. Analyze the logged reports and verify that position reports are present for all the
injected targets that are located within the configured range of the station and
only those.

5.10.2.4.2 CPR Validation

Objectives
Verify the requirements of section 3.10.2.4.2.
This test needs to verify only those aspects of the CPR validation requirements that
are necessary for ED-126 compliance. As a consequence, the test does not verify the
processing of surface position messages or the creation of reports prior to the
completion of the CPR validation test (e.g. for monitoring applications). This test
procedure is applicable to Ground Station implementations that implement CPR
decoding in accordance with DO-260A. Alternative CPR decoding implementations
may require different procedures and scenarios to ensure compliance with section
3.10.2.4.2. Alternative tests must exercise the decoding algorithm at vulnerable points
and should include two categories of test cases: normal range test cases and
robustness (abnormal range) test cases.
Test Equipment Setup
The test equipment setup shall be the same as the standard setup described in
Section 5.1.1.
Scenario Design
The position messages used in each scenario must be airborne position messages
(FTC = 9-18). The positions used in the first two messages must result in a global
decode that passes the range check. To maximise test efficiency, the single target
scenarios described below may be combined by giving each target a different
announced address (AA) and interleaving the messages. The messages for each
target in the combined scenario must have the same spacing in time as the
corresponding messages in the individual scenarios.
The following definitions apply to this section
The latitude zone offset (in degrees) is:

⎛ 360° ⎞
ZOLAT = ⎜⎜ ⎟⎟
⎝ (59)(60) ⎠

© EUROCAE, 2010
 106

The longitude zone offset is:

⎛ 360° ⎞
ZOLON = ⎜⎜ ⎟⎟
⎝ ( NL )(NL − 1) ⎠
Where NL is as defined in section A.1.7.2d of DO-260A.
The CPR bin width for latitude is:
360°
BWLAT =
2 (60 − i )
17

Where i=0 for even encoding and i=1 for odd encoding.
The CPR bin width for longitude is:
360°
BWLON =
2 ( NL − i )
17

Where i and NL are as defined above.

First, create a one target scenario to verify that the messages used for CPR validation
are different than the ones used for the range check and that messages close to but
less than 10 seconds apart are accepted.

Scenario 1
Expected ASTERIX Category
ES Input
021 Output
Inject
Msg
Time CPR Lat Lon Lat Lon CL RC
ID
(s)
PE1 0 0 Y X No Output
PO2 0.5 1 Y X No Output
PE3 1.0 0 Z T No Output
PO4 10.9 1 Z T Z T 0 0

The change in position between PO2 and PE3 must be less than 6NM to preclude
failing the local decoding reasonableness test, if implemented.
Next, create a one target scenario to verify that even and odd messages more than 10
seconds apart are not used for CPR validation. Include an additional message to
demonstrate that the system is operational and capable of producing target reports.

Scenario 2
Expected ASTERIX Category
ES Input
021 Output
Inject
Msg
Time CPR Lat Lon Lat Lon CL RC
ID
(s)
PE1 0 0 Y X No Output
PO2 0.5 1 Y X No Output
PE3 1.0 0 Z T No Output
PO4 11.1 1 Z T No Output
PE5 11.6 0 R S R S 0 0

© EUROCAE, 2010
 107

The difference between latitudes Z and R and between longitudes T and S must be
less than ½ of the zone offset minus one bin width (½ZO – BW) for the global decode
of PO4 and PE5 to be successful.
Create a one target scenario to verify that all position data used in a failed validation
attempt is not used in a subsequent attempt

Scenario 3
Expected ASTERIX Category
ES Input
021 Output
Inject
Msg
Time CPR Lat Lon Lat Lon CL RC
ID
(s)
PE1 0 0 Y X No Output
PO2 0.5 1 Y X No Output
PE3 1.0 0 Y X No Output
PO4 1.5 1 Y+c1 X No Output
PE5 2.0 0 Y X No Output
PO6 2.5 1 Y X No Output
PE7 3.0 0 Y X No Output
PO8 3.5 1 Y X Y X 0 0

The latitude differences between Y and Z and between Y and R, and the longitude
difference between X and T and between X and S must be greater than 6.2 NM to
ensure that the global decode of PO8 is not using data from any of the first four
messages. The change in position between PO6 and PE7 must be less than 6 NM. c1
is defined by the following expression
1
c1 = ZOLAT + BWLAT
2
Test Procedure
Test Steps:
a. Play each scenario and record the outputs
b. Analyze the recorded data and verify that the expected outputs are present.

5.10.2.5 Target Data Maintenance

Objectives
Verify the following that the 1090 ES Ground Station meets the minimum requirements
for Target Data Maintenance. This includes verifying that:
ƒ local decoding is used
ƒ positions that fail the Local Decoding Reasonableness Test are not used as a
reference position for subsequent local decodes
ƒ the Local Decoding Reasonableness Test works
This test only needs to verify those aspects of the target data maintenance
requirements that are necessary for ED-126 compliance. As a consequence, the test
does not verify the processing of surface position messages or the creation of reports
for positions that fail the local decoding reasonableness test (e.g. for monitoring
applications).

© EUROCAE, 2010
 108

Test Equipment Setup

The test equipment setup shall be the same as the standard setup described in
Section 5.1.1.
Scenario Design
The position messages used in each scenario must be airborne position messages
(FTC = 9-18) located within the configured range of the Ground Station. The positions
used in the first two messages must result in a global decode that passes the range
check. To maximise test efficiency, the single target scenarios described below may
be combined by giving each target a different announced address (AA) and
interleaving the messages. The messages for each target in the combined scenario
must have the same spacing in time as the corresponding messages in the individual
scenarios.
The first scenario verifies the use of local decoding during participant data
maintenance. Create a scenario with ES messages scheduled as follows:

Scenario 1
Expected ASTERIX Category
ES Input
021 Output
Inject
Msg
Time CPR Lat Lon Lat Lon CL RC
ID
(s)
PE1 0 0 Y X No Output
PO2 0.5 1 Y X No Output
PE3 1.0 0 Y X No Output
PO4 1.5 1 Y X Y X 0 0
PE5 2.0 0 Y+.075° X Y+.075° X 0 0

The first report from PO4 demonstrates that the GS has completed CPR validation.
The fifth message has a latitude change of 4.5NM, If the fifth message were combined
with any of the first four in a global decode, the resulting position would not match the
expected latitude output for the fifth message The 4.5NM change exceeds the 3NM
limit for correct global decoding.

© EUROCAE, 2010
 109

The second scenario verifies the local decoding reasonableness test. The scenario
should comply with the following table:

Scenario 2
Expected ASTERIX
ES Input Category 021
Output
Inject
Msg ID Time CPR Lat Lon Lat Lon
(s)
PE1 0 0 Y X No Output
PO2 0.5 1 Y X No Output
PE3 1.0 0 Y X No Output
PO4 1.5 1 Y X Y X
PE5 31.4 0 Y+a1° X+b1° Y+a1° X+b1°
PO6 31.9 1 Y X Y X
PO7 62.0 1 Y+a1° X+b1° Y+a1° X+b1°
PE8 62.5 0 Y X Y X
PE9 92.6 0 Y+a2° X+b2° Y+a2° X+b2°
PO10 93.1 1 Y X Y X
PO11 123.0 1 Y+a2° X+b2° No output
PE12 123.5 0 Y X Y X

NOTES:
o a1 and b1 shall be values that define a point between 5.90 and 5.99
nautical miles from Y, X.
o a2 and b2 shall be values that define a point between 6.01 and 6.10
nautical miles from Y, X.
The first four messages get the target through the range check and CPR validation.
PE5 represents a position jump of less than 6NM in just under 30 seconds. PO6 and
PO7 produce a position jump of less than 6NM in just over 30 seconds. PE8 and PE9
have a position jump of just over 6NM in just over 30 seconds. PO10 and PO11 have
a position jump of just over 6NM in just under 30 seconds.
The third scenario verifies that position updates that fail the Local Decoding
Reasonableness Test are not used as reference positions for subsequent local
decodes. Scenario 3 is described in the table below.

Scenario 3
Expected ASTERIX
ES Input Category 021
Output
Inject
Msg ID Time CPR Lat Lon Lat Lon
(s)
PE1 0 0 Y X No Output
PO2 0.5 1 Y X No Output
PE3 1.0 0 Y X No Output
PO4 1.5 1 Y X Y X
PO5 2.0 1 Y+3.025° X No Output
PE6 2.5 0 Y X Y X

© EUROCAE, 2010
 110

If the position update from PO5 was used as the reference position for PE6, the
latitude in PE6 would not decode correctly. Even CPR latitude zones are 6° wide and
odd zones are approximately 6.1° wide. Local decoding requires the distance from the
reference position to the target to be less than ½ zone, or 3° for even zones and
approx 3.05° for odd zones. If the position obtained for PO5 was used as the
reference position in the decode of PE6, the distance between the reference point (i.e.
PO5) and the reported target position (i.e. PO6) would be 3.025°. A 3.025° change
should result in no output because it would exceed the 6NM in 30 seconds criterion for
local decoding. If there were an output, the latitude would not match Y because 3.025°
exceeds the ½ zone limit (i.e. 3°) for even local decoding.
Test Procedures
Test Steps:
1. Play each scenario and record the outputs.
2. Analyze the recorded data and verify that the expected outputs are present.

5.10.2.6 Target Termination (Re-initialisation)

Objectives
Verify the following:
Participants shall be reinitialised after no more than 120 seconds without a position
update. Messages received after the 120-second timeout shall be treated as
messages from a new participant (i.e., the requirements for participant acquisition in
section 3.10.2.3.2 apply).
Test Equipment Setup
The test equipment setup shall be the same as the standard setup described in
Section 5.1.1.
Scenario Design
The position messages used in each scenario must be airborne position messages
(FTC = 9-18 or FTC = 20-22). The positions used in the first two messages must result
in a global decode that passes the range check. To maximise test efficiency, the
single target scenarios described below may be combined by giving each target a
different announced address (AA) and interleaving the messages. The messages for
each target in the combined scenario must have the same spacing in time as the
corresponding messages in the individual scenarios.
The first scenario verifies that the target is not reinitialised before 120 seconds without
a position update.
Scenario 1
Expected ASTERIX
ES Input Category 021
Output
Inject
Msg ID Time CPR Lat Lon Lat Lon
(s)
PE1 0 0 Y X No Output
PO2 0.5 1 Y X No Output
PE3 1.0 0 Y X No Output
PO4 1.5 1 Y X Y X
PO5 121.4 0 Y X Y X
PO6 121.9 1 Y X Y X

© EUROCAE, 2010
 111

The target is shown as stationary in the table above but may be moving as long as the
requirements for local decoding, specified in Appendix A of DO-260A, are met.
The second scenario verifies that the target is reinitialised if no updates are received
within a 120 second interval.

Scenario 2
Expected Cat21
ES Input
Output
Inject
Msg ID Time CPR Lat Lon Lat Lon
(s)
PE1 0 0 Y X No Output
PO2 0.5 1 Y X No Output
PE3 1.0 0 Y X No Output
PO4 1.5 1 Y X Y X
PO5 121.6 1 Z T No Output
PE6 122.1 0 Z T No Output
PO7 122.6 1 Z T No Output
PE8 123.1 0 Z T Z T

The locations of (Y,X) and (Z,T) must be more than 3NM apart in latitude and must be
close enough together to satisfy the requirements for a local decode as specified in
DO-260A, Appendix A.
If the GS retains target data longer than 120 seconds, PO5, PE6 and PO7 will trigger
ASTERIX reports.
Test Procedure
Test Steps:
1. Play each scenario and record the outputs.
2. Analyze the recorded data and verify that the expected outputs are present.

5.10.3 Data Item Inclusion

5.10.3.1 State Vector Reports

This section contains tests relating to ASTERIX Category 021 reports. It is noted that
no tests are currently defined for ASTERIX Category 021 Edition 0.23 format reports.
Support for ASTERIX Category 021 Edition 0.23 is optional.

5.10.3.1.1 Periodic State Vector Reports

The requirements of section 3.10.3.1.1 are covered by the tests in sections 5.10.2.3.1
and 5.10.3.1.2.

© EUROCAE, 2010
 112

5.10.3.1.2 Data Driven State Vector Reports

a. Data Driven Position Reports

Objectives
The aim of this test is to check that the system state vector reports contain all of the
minimum data items listed in Table 5. The following fields of these data items are
tested:
TOMT, DCR, Position WGS-84, FL, T.Ident, PS, SS, VNS, VN, LTT, SIC, SAC, GBS,
ARC, TOA, TOMR and Target Address.
Fields only for Version 1 ES: NACV, NICBARO, SIL, NACP, NIC
Fields only for Version 0 ES: NUCR, NUCP
The following fields are not tested here as they are tested elsewhere: ATP (duplicate
address).
RC, CL, NOGO, RCF, CPR, LDPJ, RCF, RAB, SIM, TST and SAA are optional fields
and if present they have to be zero.
Test Equipment setup
The test equipment setup shall be the same as the standard setup described in
Section 5.1.1.
Scenario design
Due to the number of parameters to test, the scenario will consist of several different
targets (different addresses).
GS coordinates shall be set to 0º latitude, 0º longitude to enable correct CPR
decoding to be tested for all possible combinations of positive and negative values for
target latitude and longitude.
To avoid jumps on position, data item “Position WGS-84” will be tested in four different
targets. Each target will test one of the North, South, East, West combinations.
Target 1:
This target will provide tests for NICBARO, NACV and position in WGS-84.
Target 1
ES Input Expected Category 021 Output
Inject Time

Position in
MOPS VN

WGS-84
Step

NICBARO

NICBARO
Lat/Lon
Msg ID

NACV

NACV
FTC

Rpt
(s)

PO1 18 0.5 S/W

PE2 18 1 S/W
PO3 18 1.5 S/W
1
PE4 18 2 S/W R1 0 S/W 0
AOS1 31 2.1 1
PO5 18 2.5 S/W R2 0 S/W 0
2 VEL1 19 2.6 0 R3 0 0
PE6 18 3 S/W R4 0 0
VEL2 19 3.1 1 R5 0
PO7 18 3.5 S/W R6 0 1
VEL3 19 3.6 2 R7 0

© EUROCAE, 2010
 113

Target 1
ES Input Expected Category 021 Output

Inject Time

Position in
MOPS VN

WGS-84
Step

NICBARO

NICBARO
Lat/Lon
Msg ID

NACV

NACV
FTC

Rpt
(s)
PE8 18 4 S/W R8 0 2
VEL4 19 4.1 3 R9 0
PO9 18 4.5 S/W R10 0 3
VEL5 19 4.6 4 R11 0
PE10 18 5 S/W R12 0 4
VEL6 19 5.1 4 R13 0
PO11 18 5.5 S/W R14 0 5
VEL7 19 5.6 4 R15 0
PE12 18 6 S/W R16 0 6
VEL8 19 6.1 4 R17 0
PO13 18 6.5 S/W R18 0 7
PE14 18 7 S/W R19 0
AOS2 31 7.3 0 0
TSS1 29 7.4 0 0
PO15 18 7.5 S/W R20 0
AOS3 31 7.8 0
TSS2 29 7.9 1
PE16 18 8 S/W R21 1
AOS4 31 8.3 1
TSS3 29 8.4 0
PO17 18 8.5 S/W R22 0
AOS5 31 8.8 1
TSS4 29 8.9 1
3 PE18 18 9 S/W R23 1
TSS5 29 9.3 0
AOS6 31 9.4 0
PO19 18 9.5 S/W R24 0
TSS6 29 9.8 0
AOS7 31 9.9 1
PE20 18 10 S/W R25 1
TSS7 29 10.3 1
AOS8 31 10.4 0
PO21 18 10.5 S/W R26 0
TSS8 29 10.8 1
AOS9 31 10.9 1
PE22 18 11 S/W R27 1

© EUROCAE, 2010
 114

Target 1: The evolution of the states of this target is as follows:

Step 1: Target acquisition and version 1 confirmed. S/W position is tested.
Step 2: All possible values for NACV are tested.
Step 3: All possible combinations of values for NICBARO are tested.
Target 2:
This target will provide tests for SIL.
Target 2
Expected Category
ES Input
021 Output
Step
Msg Inject MOPS
FTC SIL Rpt SIL
ID Time (s) Version
PO1 18 0.5
PE2 18 1
PO3 18 1.5
1
PE4 18 2 R1 0
AOS1 31 2.1 1
PO5 18 2.5 R2 0
AOS2 31 2.8 (random) value 0 to 3
2 TSS1 29 2.9 0
PE6 18 3 R3 0
AOS3 31 3.3 (random) value 0 to 3
3 TSS2 29 3.4 1
PO7 18 3.5 R4 1
AOS4 31 3.8 (random) value 0 to 3
4 TSS3 29 3.9 2
PE8 18 4 R5 2
AOS5 31 4.3 (random) value 0 to 3
5 TSS4 29 4.4 3
PO9 18 4.5 R6 3
TSS6 29 4.8 (random) value 0 to 3
6 AOS7 31 4.9 0
PE10 18 5 R7 0
TSS7 29 5.3 (random) value 0 to 3
7 AOS8 31 5.4 1
PO11 18 5.5 R8 1
TSS8 29 5.8 (random) value 0 to 3
8 AOS9 31 5.9 2
PE12 18 6 R9 2
TSS9 29 6.3 (random) value 0 to 3
9 AOS10 31 6.4 3
PO13 18 6.5 R10 3

© EUROCAE, 2010
 115

Target 2: The evolution of the states of this target is as follows:

Step 1: acquisition and version 1 confirmed.
Steps 2 to 9: all possible values for SIL are tested
Target 3:
This target will provide tests for NACP.
Target 3
Expected Category 021
ES Input
Output
Step

MOPS VN
Time (s)
Msg ID

Inject

NACP

NACP
FTC

Rpt
PO1 18 0.5
PE2 18 1
PO3 18 1.5
1
PE4 18 2 R1 0
AOS1 31 2.1 1
PO5 18 2.5 R2 0
AOS2 31 2.8 (random) value 0 to 15
2 TSS1 29 2.9 0
PE6 18 3 R3 0
AOS3 31 3.3 (random) value 0 to 15
3 TSS2 29 3.4 1
PO7 18 3.5 R4 1
AOS4 31 3.8 (random) value 0 to 15
4 TSS3 29 3.9 2
PE8 18 4 R5 2
AOS5 31 4.3 (random) value 0 to 15
5 TSS4 29 4.4 3
PO9 18 4.5 R6 3
AOS6 31 4.8 (random) value 0 to 15
6 TSS5 29 4.9 4
PE10 18 5 R7 4
AOS7 31 5.3 (random) value 0 to 15
7 TSS6 29 5.4 5
PO11 18 5.5 R8 5
AOS8 31 5.8 (random) value 0 to 15
8 TSS7 29 5.9 6
PE12 18 6 R9 6
AOS9 31 6.3 (random) value 0 to 15
9 TSS8 29 6.4 7
PO13 18 6.5 R10 7
10 AOS10 31 6.8 (random) value 0 to 15
TSS9 29 6.9 8

© EUROCAE, 2010
 116

Target 3
Expected Category 021
ES Input
Step Output

MOPS VN
Time (s)
Msg ID

Inject

NACP

NACP
FTC

Rpt
PE14 18 7 R11 8
AOS11 31 7.3 (random) value 0 to 15
11 TSS10 29 7.4 9
PO15 18 7.5 R12 9
AOS12 31 7.8 (random) value 0 to 15
12 TSS11 29 7.9 10
PE16 18 8 R13 10
AOS13 31 8.3 (random) value 0 to 15
13 TSS12 29 8.4 11
PO17 18 8.5 R14 11
AOS14 31 8.8 (random) value 0 to 15
14 TSS13 29 8.9 12
PE18 18 9 R15 12
AOS15 31 9.3 (random) value 0 to 15
15 TSS14 29 9.4 13
PO19 18 9.5 R16 13
AOS16 31 9.8 (random) value 0 to 15
16 TSS15 29 9.9 14
PE20 18 10 R17 14
AOS17 31 10.3 (random) value 0 to 15
17 TSS16 29 10.4 15
PO21 18 10.5 R18 15
TSS17 29 10.8 (random) value 0 to 15
18 AOS18 31 10.9 0
PE22 18 11 R19 0
TSS18 29 11.3 (random) value 0 to 15
19 AOS19 31 11.4 1
PO23 18 11.5 R20 1
TSS19 29 11.8 (random) value 0 to 15
20 AOS20 31 11.9 2
PE24 18 12 R21 2
TSS20 29 12.3 (random) value 0 to 15
21 AOS21 31 12.4 3
PO25 18 12.5 R22 3
TSS21 29 12.8 (random) value 0 to 15
22 AOS22 31 12.9 4
PE26 18 13 R23 4

© EUROCAE, 2010
 117

Target 3
Expected Category 021
ES Input
Step Output

MOPS VN
Time (s)
Msg ID

Inject

NACP

NACP
FTC

Rpt
TSS22 29 13.3 (random) value 0 to 15
23 AOS23 31 13.4 5
PO27 18 13.5 R24 5
TSS23 29 13.8 (random) value 0 to 15
24 AOS24 31 13.9 6
PE28 18 14 R25 6
TSS24 29 14.3 (random) value 0 to 15
25 AOS25 31 14.4 7
PO29 18 14.5 R26 7
TSS25 29 14.8 (random) value 0 to 15
26 AOS26 31 14.9 8
PE30 18 15 R27 8
TSS26 29 15.3 (random) value 0 to 15
27 AOS27 31 15.4 9
PO31 18 15.5 R28 9
TSS27 29 15.8 (random) value 0 to 15
28 AOS28 31 15.9 10
PE32 18 16 R29 10
TSS28 29 16.3 (random) value 0 to 15
29 AOS29 31 16.4 11
PO33 18 16.5 R30 11
TSS29 29 16.8 (random) value 0 to 15
30 AOS30 31 16.9 12
PE34 18 17 R31 12
TSS30 29 17.3 (random) value 0 to 15
31 AOS31 31 17.4 13
PO35 18 17.5 R32 13
TSS31 29 17.8 (random) value 0 to 15
32 AOS32 31 17.9 14
PE36 18 18 R33 14
TSS32 29 18.3 (random) value 0 to 15
33 AOS33 31 18.4 15
PO37 18 18.5 R34 15

© EUROCAE, 2010
 118

Target 3: The evolution of the states of this target is as follows:

Step 1: acquisition and version 1 confirmed.
Steps 2 to 33: all possible values for NACP are tested.
Target 4:
This target will provide tests for NIC and position WGS-84.
Target 4
ES Input Expected Category 021 Output

Supplement
Inject Time

Position in
MOPS VN

WGS-84
Step

Lat/Lon
Msg ID

FTC

NIC

NIC
Rpt
(s)

PO1 0.5 22 N/W

PE2 1 22 N/W
PO3 1.5 22 N/W
1
PE4 2 22 N/W R1 N/W 0
AOS1 2.1 31 1 1
PO5 2.5 22 N/W 0 R2 N/W 0
2 PE6 3 21 N/W 0 R3 10
3 PO7 3.5 20 N/W 0 R4 11
4 PE8 4 18 N/W 0 R5 0
5 PO9 4.5 17 N/W 0 R6 1
AOS2 4.8 31 0
AOS3 4.9 31 1
PE10 5 16 N/W R7 3
6
AOS4 5.3 31 1
AOS5 5.4 31 0
PO11 5.5 16 N/W R8 2
7 PE12 6 15 N/W 0 R9 4
8 PO13 6.5 14 N/W 0 R10 5
AOS6 6.8 31 0
AOS7 6.9 31 1
PE14 7 13 N/W R11 6
9
AOS8 7.3 31 1
AOS9 7.4 31 0
PO15 7.5 13 N/W R12 6
10 PE16 8 12 N/W 0 R13 7
AOS10 8.3 31 0
AOS11 8.4 31 1
PO17 8.5 11 N/W R14 9
11
AOS12 8.8 31 1
AOS13 8.9 31 0
PE18 9 11 N/W R15 8
12 PO19 9.5 10 N/W 0 R16 10

© EUROCAE, 2010
 119

Target 4
ES Input Expected Category 021 Output

Supplement
Inject Time

Position in
MOPS VN

WGS-84
Step

Lat/Lon
Msg ID

FTC

NIC

NIC
Rpt
13 PE20 10(s) 9 N/W 0 R17 11
14 PO21 10.5 8 N/W 0 R18 0
AOS14 10.8 31 0
AOS15 10.9 31 1
PE22 11 7 N/W R19 9
15
AOS16 11.3 31 1
AOS17 11.4 31 0
PO23 11.5 7 N/W R20 8
16 PE24 12 6 N/W 0 R21 10
17 PO25 12.5 5 N/W 0 R22 11
18 PE26 13 0 N/W

The evolution of the states of this target is as follows:

Step 1: acquisition and version 1 confirmed. N/W Position is tested.
Steps 2 to 18: all possible values for NIC are tested.
Target 5:
This target provides tests for NUCR and NUCP for version 0 participants.
Target 5
Expected Category 021
ES Input
Output
Step

Time (s)
Msg ID

MOPS
NUCR

NUCR
Inject

NUCP
FTC

Rpt
VN

PO1 0.5 18
PE2 1 18
PO3 1.5 18
1
PE4 2 18 R1 0 0
AOS1 2.1 31 0
PO5 2.5 18 R2 0 0
2 VEL1 2.6 19 0 R3 0 0
PE6 3 18 R4 0 0
VEL2 3.1 19 1 R5 1 0
PO7 3.5 18 R6 1 0
VEL3 3.6 19 2 R7 2 0
PE8 4 18 R8 2 0
VEL4 4.1 19 3 R9 3 0
PO9 4.5 18 R10 3 0

© EUROCAE, 2010
 120

Target 5
Expected Category 021
ES Input
Output

Step

Time (s)
Msg ID

MOPS
NUCR

NUCR
Inject

NUCP
FTC

Rpt
VN
VEL5 4.6 19 4 R11 4 0
PE10 5 18 R12 4 0
VEL6 5.1 19 5 R13 5 0
PO11 5.5 18 R14 5 0
VEL7 5.6 19 6 R15 6 0
PE12 6 18 R16 6 0
VEL8 6.1 19 7 R17 7 0
PO13 6.5 18 R18 7 0
PE14 7 0
PO15 7.5 5 R19 9
PE16 8 6 R20 8
PO17 8.5 7 R21 7
PE18 9 8 R22 6
PO19 9.5 9 R23 9
PE20 10 10 R24 8
PO21 10.5 11 R25 7
3 PE22 11 12 R26 6
PO23 11.5 13 R27 5
PE24 12 14 R28 4
PO25 12,5 15 R29 3
PE26 13 16 R30 2
PO27 13.5 17 R31 1
PE28 14 18 R32 0
PO29 14.5 20 R33 9
PE30 15 21 R34 8

Target 5: The evolution of the states of this target is as follows:

Step 1: acquisition and version 0 confirmed.
Step 2: all possible values for NUCR are tested
Step 3: all possible values for NUCP are tested

© EUROCAE, 2010
 121

Target 6
This target will provide tests for Time of Report Transmission (TORT), DCR, position
WGS-84, FL, T.IDENT, PS, SS, VNS, VN, LTT.
Target 6
ES Input Expected Category 021 Output
Inject Time (s)

Altitude (feet)

Position in
MOPS VN

WGS-84
T. Ident.

T. Ident.
Lat/Lon
Msg ID

TORT

DCR

VNS
FTC

LTT
Rpt

VN
PS

SS

PS

SS
FL
Q

PO1 0.5 20 S/E 30025

AOS1 0.6 31
PE2 1 20 S/E 30025 0
PO3 1.5 20 S/E 30025 0
AAA362

ID1 1.6 2

AAA362
PE4 2 20 S/E 30025 0 R1 TR1 0 S/E 300.25 0 0 2

AOS1 0.6 31 0

AAA362
PO5 2.5 18 S/E 30025 0 R2 TR2 0 S/E 300.25 0 0 2

AOS2 2.6 31 1
AAA362

PE6 3 18 S/E 30025 0 0 R3 TR3 0 S/E 300.25 0 0 1 2

AS1 3.1 28 0
PO7 3.5 18 S/E 25025 0 R4 250.25 0
PE8 4 18 S/E 25025 0 1 R5 250.25 1
AS2 4.1 28 1
PO9 4.5 18 S/E 20025 0 R6 200.25 1
PE10 5 18 S/E 17525 1 2 R7 175 2
AS3 5.1 28 2
PO11 5.5 18 S/E 15025 1 R8 150 2
PE12 6 18 S/E 12525 1 3 R9 125 3
AS4 6.1 28 3
PO13 6.5 18 S/E 10025 1 R10 100 3
PE14 7 18 S/E 50 1 R11 50
AS5 7.1 28 4

© EUROCAE, 2010
 122

Target 6
ES Input Expected Category 021 Output
Inject Time (s)

Altitude (feet)

Position in
MOPS VN

WGS-84
T. Ident.

T. Ident.
Lat/Lon
Msg ID

TORT

DCR

VNS
FTC

LTT
Rpt

VN
PS

SS

PS

SS
FL
Q
PO15 7.5 18 S/E 25 1 R12 25 4
PE16 8 18 S/E 0 1 R13 0
AS6 8.1 28 5
PO17 8.5 5 S/E 1 R14 5
PE18 9 5 S/E 1 R15
AS7 9.1 28 6
PO19 9.5 5 S/E 1 R16 6

TOMT is tested on reports 1, 2 and 3 shall be completed with the time of delivery of
the ASTERIX Category 021 reports.
DCR is tested on reports 1, 2 and 3, and shall always be set to zero.
N/E WGS-84 position is tested on reports 1, 2 and 3.
FL is tested on reports 1 to 13. Reports 1 to 6 have 25ft resolution due to Q bit in
position message set to zero. Reports 7 to 13 have 100ft resolution due to Q bit in
position message set to one.
T.IDENT is tested on reports 1, 2 and 3.
PS is tested on reports 3, 5, 7, 9.
SS is tested on reports 4, 6, 8, 10, 12, 14 and 16.
VNS, VN and LTT are tested on reports 1, 2 and 3.

© EUROCAE, 2010
 123

Target 7
This target will provide tests for position WGS-84 (N/E), SIC-SAC, GBS, ARC,
TARGET ADDRESS.
Target 7
ES Input Expected Category 021 Output

Target Address

Target Address
Inject Time (s)

Position in
MOPS VN

WGS-84
Lat/Lon
Msg ID

GBS

ARC
SAC
FTC

SIC
Rpt
Q
PO1 0.5 5 N/E BBBBBB
PE2 1 5 N/E BBBBBB
PO3 1.5 5 N/E BBBBBB
PE4 2 5 N/E BBBBBB R1 N/E A B 1 2 BBBBBB
AOS1 2.1 31 1
PO5 2.5 0 N/E BBBBBB
PE6 3 5 N/E R2 1 2
PO7 3.5 6 N/E R3 1 2
PE8 4 7 N/E R4 1 2
PO9 4.5 8 N/E R5 1 2
PE10 5 9 N/E 1 R6 0 0
PO11 5.5 10 N/E 1 R7 0 0
PE12 6 11 N/E 1 R8 0 0
PO13 6.5 12 N/E 1 R9 0 0
PE14 7 13 N/E 1 R10 0 0
PO15 7.5 14 N/E 1 R11 0 0
PE16 8 15 N/E 0 R12 0 1
PO17 8.5 16 N/E 0 R13 0 1
PE18 9 17 N/E 0 R14 0 1
PO19 9.5 18 N/E 0 R15 0 1
PE20 10 20 N/E 0 R16 0 1
PO21 10.5 21 N/E 0 R17 0 1
PE22 11 22 N/E 0 R18 0 1

WGS-84 N/E position, SIC, SAC and TARGET ADDRESS are tested on reports 1 and
2.
All possible GBS values are tested on reports 1 to 18. GBS is derived from the FTC of
the received position messages.
All possible ARC values are tested on reports 1 to 18. ARC is derived from the Q bit of
the position message.

© EUROCAE, 2010
 124

Target 8
This target will provide tests for TOA for position and TOMR for position.
Target 8
ES Input Expected Category 021 Output

Inject Time

Position
Step

TOA for
Msg ID

TOMR
FTC

Rpt
VN
(s)

T
PO1 0.5 5
PE2 1 5
1 PO3 1.5 5
PE4 2 5 1 R1 2
AOS1 2.1 31 1
PO5 2.5 5 1 R2 2.6015625
PE6 3 6 1 R3 2.796875
PO7 3.5 7 1 R4 3.40625
PE8 4.01 8 1 R5 4.007813
PO9 4.51 9 1 R6 4.515625
PE10 5 10 1 R7 4.796875
PO11 5.53 11 1 R8 5.53125
PE12 5.99 12 1 R9 5.9921875
2 PO13 6.4 13 1 R10 6.3984375
PE14 6.9 14 1 R11 6.8984375
PO15 7.45 15 1 R12 7.453125
PE16 8 16 1 R13 8
PO17 8.55 17 1 R14 8.546875
PE18 9.1 18 1 R15 9.1015625
PO19 9.5 20 1 R16 9.40625
PE20 10 21 1 R17 10
PO21 10.51 22 1 R18 10.515625
3 PE22 10.99 5 0 R19 10.9921875
PO23 11.47 6 0 R20 11.46875
PE24 12.03 7 0 R21 12.03125
PO25 12.52 8 0 R22 12.5234375
PE26 13 9 0 R23 13
PO27 13.5 10 0 R24 13.5
PE28 14 11 0 R25 14
PO29 14.5 12 0 R26 14.5
PE30 15 13 0 R27 15
PO31 15.5 14 0 R28 15.5
PE32 16 15 0 R29 16
PO33 16.5 16 0 R30 16.5
PE34 17 17 0 R31 17

© EUROCAE, 2010
 125

Target 8
ES Input Expected Category 021 Output

Inject Time

Position
Step

TOA for
Msg ID

TOMR
FTC

Rpt
VN
(s)

T
PO35 17.5 18 0 R32 17.5
PE36 18 20 0 R33 18
PO37 18.5 21 0 R34 18.5
PE38 19 22 0 R35 19
Target 8: The evolution of the states of this target is as follows:
Step 1: acquisition and version 1 confirmed.
Step 2: values for TOA and TOMR are tested with T bit = 1. TOA values are
calculated according to section 3.10.4.8. TOMR values are calculated according to
section 3.10.4.10.
Step 3: values for TOA and TOMR are tested with T bit = 0. TOA values shall not
appear with T = 0. TOMR values are calculated according to section 3.10.4.10.
Test procedure
Test Steps:
1. Play the scenario for all targets.
2. When the scenario is complete, stop recording ASTERIX reports.
3. Analyze the recorded data and verify that the expected outputs are present.
4. Test for target 7 shall be repeated with a different SIC SAC configuration.
5. When the scenario is complete, stop recording ASTERIX reports.
6. Analyze the recorded data and verify that the expected outputs are present.
b. Data Driven Velocity Reports
Objectives
This test verifies the data encoding rules for the minimum fields for ASTERIX
Category 021 data driven velocity reports, listed inTable 7.
These fields are:
I021/010 Data Source Identification
I021/040 Target Report Descriptor
I021/075 Time of Message Reception of Velocity
I021/077 Time of Report Transmission
I021/080 Target Address
I021/090 Quality Indicators
I021/150 Air Speed
I021/151 True Air Speed
I021/160 Ground Vector
I021/170 Target Identification
I021/200 Target Status
I021/210 MOPS Version

© EUROCAE, 2010
 126

Test Equipment Setup

The test equipment setup shall be the same as the standard setup described in
Section 5.1.1.
Scenario Design
All messages shall have the same 24-bit aircraft address.
The velocity (FTC = 19) messages shall have all fields set to zero unless otherwise
specified.
The identification messages shall have FTC = 4, category 0, aircraft ID = “TEST0001”.
Scenario 1 – ES messages containing velocity over ground
The scenario tests that various permutations of EW and NS velocity values and their
associated direction bits for FTC = 19 subtype 1 and 2 velocity messages are reported
correctly.

ES Input Expected ASTERIX

Category 021 Output
Msg FTC/ Inject EW NS EW NS NUCR Rpt GS TA NACV
ID Sub- Time Vel. Vel. Dir. Dir. or
type (s) NACV
PE1 0
PO2 0.5
PE3 1.0
PO4 1.5
ID1 4/0 1.6
ES1 28/1 1.7
V1 19/1 2.0 0 0 0 0 0 V1 DNP DNP 0
V2 19/1 2.5 1 0 0 0 1 V2 DNP DNP 1
V3 19/1 3.0 0 1 0 0 2 V3 DNP DNP 2
V4 19/1 3.5 1 1 0 0 3 V4 0 0 3
V5 19/1 4.0 2 1 0 0 4 V5 4 16384 4
V6 19/1 4.5 1 2 0 0 5 V6 4 0 5
V7 19/1 5.0 2 2 0 0 6 V7 6 8192 6
V8 19/1 5.5 2 2 0 1 7 V8 6 24576 7
V9 19/1 6.0 2 2 1 0 0 V9 6 40960 0
V10 19/1 6.5 2 2 1 1 1 V10 6 57344 1
V11 19/1 7.0 1022 1022 1 1 2 V11 6570 57344 2
V12 19/1 7.5 1023 1022 1 1 3 V12 DNP DNP 3
V13 19/1 8.0 1022 1023 1 1 4 V13 DNP DNP 4
V14 19/2 8.5 0 0 0 0 5 V14 DNP DNP 5
V15 19/2 9.0 1 0 0 0 6 V15 DNP DNP 6
V16 19/2 9.5 0 1 0 0 7 V16 DNP DNP 7
V17 19/2 10.0 1 1 0 0 0 V17 0 0 0
V18 19/2 10.5 2 1 0 0 1 V18 18 16384 1
V19 19/2 11.0 1 2 0 0 2 V19 18 0 2
V20 19/2 11.5 2 2 0 0 3 V20 25 8192 3

© EUROCAE, 2010
 127

V21 19/2 12.0 2 2 0 1 4 V21 25 24576 4

V22 19/2 12.5 2 2 1 0 5 V22 25 40960 5
V23 19/2 13.0 2 2 1 1 6 V23 25 57344 6
V24 19/2 13.5 1022 1022 1 1 7 V24 26281 57344 7
V25 19/2 14.0 1023 1022 1 1 0 V25 DNP DNP 0
V26 19/2 14.5 1022 1023 1 1 1 V26 DNP DNP 1

Scenario 2 – Airspeed and NACV

This scenario tests the various permutations of Airspeed and the Airspeed Available
bit for FTC = 19 subtype 3 and 4 velocity messages.

Expected ASTERIX Category 021

ES Input
Output
FTC/ Inject NUCR True TAS
Msg AS Air Air
Sub- Time or Rpt Air RE NACV
ID Type speed Speed
type (s) NACV Speed bit
PE1 0
PO2 0.5
PE3 1.0
PO4 1.5
ID1 4/0 1.6
ES1 28/1 1.7
V1 19/3 2.0 0 0 0 V1 DNP DNP - 0
V2 19/3 2.5 0 1 1 V2 0 DNP - 1
V3 19/3 3.0 0 2 2 V3 4 DNP - 2
V4 19/3 3.5 0 3 3 V4 9 DNP - 3
V5 19/3 4.0 0 512 4 V5 2325 DNP - 4
V6 19/3 4.5 0 1022 5 V6 4646 DNP - 5
V7 19/3 5.0 0 1023 6 V7 DNP DNP - 6
V8 19/3 5.5 1 0 7 V8 DNP DNP - 7
V9 19/3 6.0 1 1 0 V9 DNP 0 0 0
V10 19/3 6.5 1 2 1 V10 DNP 1 0 1
V11 19/3 7.0 1 3 2 V11 DNP 2 0 2
V12 19/3 7.5 1 512 3 V12 DNP 511 0 3
V13 19/3 8.0 1 1022 4 V13 DNP 1021 0 4
V14 19/3 8.5 1 1023 5 V14 DNP 1022 1 5
V15 19/4 9.0 0 0 6 V15 DNP DNP - 6
V16 19/4 9.5 0 1 7 V16 0 DNP - 7
V17 19/4 10.0 0 2 0 V17 18 DNP - 0
V18 19/4 10.5 0 3 1 V18 36 DNP - 1
V19 19/4 11.0 0 512 2 V19 9302 DNP - 2
V20 19/4 11.5 0 1022 3 V20 18586 DNP - 3
V21 19/4 12.0 0 1023 4 V21 DNP DNP - 4
V22 19/4 12.5 1 0 5 V22 DNP DNP - 5

© EUROCAE, 2010
 128

V23 19/4 13.0 1 1 6 V23 DNP 0 0 6

V24 19/4 13.5 1 2 7 V24 DNP 4 0 7
V25 19/4 14.0 1 3 0 V25 DNP 8 0 0
V26 19/4 14.5 1 512 1 V26 DNP 2044 0 1
V27 19/4 15.0 1 1022 2 V27 DNP 4084 0 2
V28 19/4 15.5 1 1023 3 V28 DNP 4085 1 3

Scenario 3 – Magnetic Heading and MOPS version

This scenario tests the various permutations of Heading, and the Heading Available bit
for FTC = 19 subtype 3 and 4 velocity messages and the Horizontal Reference
Direction (HRD) and MOPS version in FTC = 31 Subtype 0 Operational Status
messages.

Expected ASTERIX
ES Input
Category 021 Output
FTC/ Inject
Msg MOPS Magnetic
Sub- Time HA Heading HRD Rpt VN
ID VN Hdg
type (s)
PE1 0
PO2 0.5
PE3 1.0
PO4 1.5
ID1 4/0 1.6
ES1 28/1 1.7
V1 19/3 2.0 0 0 V1 DNP 0
V2 19/3 2.5 0 1023 V2 DNP 0
V3 19/3 3.0 1 0 V3 0 0
V4 19/3 3.5 1 512 V4 512 0
V5 19/3 4.0 1 1023 V5 1023 0
OS1 31/0 4.4 0 1
V6 19/3 4.5 0 0 V6 DNP 1
V7 19/3 5.0 0 1023 V7 DNP 1
V8 19/3 5.5 1 0 V8 DNP 1
V9 19/3 6.0 1 1023 V9 DNP 1
OS2 31/0 6.4 1 1
V10 19/3 6.5 0 0 V10 DNP 1
V11 19/3 7.0 0 1023 V11 DNP 1
V12 19/3 7.5 1 0 V12 0 1
V13 19/3 8.0 1 512 V13 512 1
V14 19/3 8.5 1 1023 V14 1023 1
OS3 31/0 8.9 0 0
V15 19/4 9.0 0 0 V15 DNP 0
V16 19/4 9.5 0 1023 V16 DNP 0
V17 19/4 10.0 1 0 V17 0 0

© EUROCAE, 2010
 129

V18 19/4 10.5 1 512 V18 512 0

V19 19/4 11.0 1 1023 V19 1023 0
OS4 31/0 11.4 0 1
V20 19/4 11.5 0 0 V20 DNP 1
V21 19/4 12.0 0 1023 V21 DNP 1
V22 19/4 12.5 1 0 V22 DNP 1
V23 19/4 13.0 1 1023 V23 DNP 1
OS5 31/0 13.4 1 1
V24 19/4 13.5 0 0 V24 DNP 1
V25 19/4 14.0 0 1023 V25 DNP 1
V26 19/4 14.5 1 0 V26 0 1
V27 19/4 15.0 1 512 V27 512 1
V28 19/4 15.5 1 1023 V28 1023 1
Test Procedure
Test Steps:
1. Play the scenario
2. When the scenario is complete, stop recording ASTERIX reports
3. Analyze the recorded data and verify that the expected outputs are present.
4. For all velocity reports, verify that:
I021/010 Data Source Identification contains the configured SIC and SAC
I021/040 Target Report Descriptor contains the expected values
I021/075 Time of Message Reception of Velocity contains the UTC time that the
velocity message was injected
I021/077 Time of Report Transmission contains the expected time
I021/080 Target Address contains the 24-bit address used for the test target
I021/090 Quality Indicators contains zeros apart from NACr
I021/150 Air Speed is present for scenario 2 and 3 only
I021/151 True Air Speed is present for scenario 2 and 3 only
I021/160 Ground Vector is not present for scenarios 2 and 3
I021/170 Target Identification contains the 8 character identification used in the
injected identification squitter.
I021/200 Target Status. Verify that this contains the correct status as sent in the last
Emergency/Priority status or Target State and Status squitter.
I021/210 MOPS Version. Verify that this contains the correct version. Verify that the
Link Technology Type field is set to 2 for 1090 ES

5.10.3.2 Status Reports

5.10.3.2.1 Objectives

This test procedure verifies that the 1090 ES Ground Station reports periodically the
status of the system and its components through ASTERIX Category 023 reports in
accordance with the requirements specified in Section 3.10.3.2 and Table 9.

© EUROCAE, 2010
 130

5.10.3.2.2 Test Equipment Setup

The test equipment setup shall be the same as the standard setup described in
Section 5.1.1.

5.10.3.2.3 Scenario Design

The 1090 ES Ground Station is configured to report Ground Station and Service
Status with non default periods and its output is recorded to verify that these reports
are generated with the configured frequencies and have the correct content under
nominal conditions.

5.10.3.2.4 Test Procedure

Test Steps:
1. Put the 1090 ES Ground Station in the default configuration per Section 5.1.1
and switch it to Maintenance Mode.
2. Make the following configuration or mode changes:
GSReportInterval = 30 s
ServiceReportInterval = 20 s
3. Return the 1090 ES Ground Station to the default configuration [Operational
Mode, UTC Coupled, and On-Line State].
4. Record the outgoing ASTERIX Category 023 reports for a period of 5 minutes.
5. Verify that at least 15 ASTERIX Category 023 Service Status reports (per active
service) and 10 ASTERIX Category 023 Ground Station Status reports have
been produced during this period.
6. Verify that each of the Ground Station Status reports recorded in step 4
contains the following valid ASTERIX Category 023 data items:
• Message Type (I023/000) set to 1;
• Data Source Identifier (I023/010) set to the Ground Station SAC and
SIC;
• Time of Day (I023/070) set to a UTC time corresponding to the
transmission of the report;
• Ground Station Status (I023/100) is reported as indicated in the table
below:
• 1st Octet
Bit 8 7 6 5 4 3 2 1
Flag NOGO ODP OXT MSC TSV SPO RN FX
Value 0 0 0 0 0 0 0 1
• 2 Octet (GSSP = 30s)
nd

Bit 8 7 6 5 4 3 2 1
Flag GSSP FX
Value 0 0 1 1 1 1 0 0

© EUROCAE, 2010
 131

7. Verify that each of the Service Status reports recorded in step 4 contains the
following valid ASTERIX Category 023 data items:
• Message Type (I023/000) set to 2;
• Data Source Identifier (I023/010) set to the Ground Station SAC and
SIC;
• Service Type and Identification (I023/015) set to the SID allocated for
the service and STYP = 2 (ADS-B Ext. Squitter);
• Time of Day (I023/070) set to a UTC time corresponding to the
transmission of the report;
• Service Configuration (I023/101) reported as indicated below:
• 1st octet (RP = 0 s indicates data-driven mode)

Bit 8 7 6 5 4 3 2 1
Flag RP
Value 0 0 0 0 0 0 0 0
• 2nd octet (SC = 1 indicates NRA class):

Bit 8 7 6 5 4 3 2 1
Flag SC 0 0 0 0 FX
Value 0 0 1 0 0 0 0 1
rd
• 3 octet (SSRP = 20s):

Bit 8 7 6 5 4 3 2 1
Flag SSRP FX
Value 0 0 1 0 1 0 0 0
8. Service Status (I023/110) reported as indicated below (STAT = 4 indicates
Normal Service):

Bit 8 7 6 5 4 3 2 1
Flag 0 0 0 0 STAT FX
Value 0 0 0 0 1 0 0 0

5.10.3.3 ASTERIX Version Reports

5.10.3.3.1 Objectives

Verify that the requirements from section 3.10.3.3 are met.

5.10.3.3.2 Test Equipment Setup

The test equipment setup shall be the same as the standard setup described in
Section 5.1.1.

5.10.3.3.3 Scenario Design

Create a scenario with at least position messages for one target. The message
content should be such that ASTERIX State Vector reports are produced for the
target. The scenario will need to run continuously for the duration of the test. The
purpose of this scenario is to demonstrate that the 1090 ES Ground Station is capable
of producing ASTERIX reports during the periods of the test when it is not supposed to
produce ASTERIX Version Reports.

© EUROCAE, 2010
 132

5.10.3.3.4 Test Procedure

Test Steps:
1. Configure the ASTERIX Version Report period to 0 and ensure that this setting
will be used after a restart of the GS. Play the scenario into the GS and verify
that ASTERIX target reports are produced. While target messages are being
injected, restart the GS. Verify that no ASTERIX Version Report is produced
after the restart. Continue with ES messages being injected for at least 10
minutes and verify that no ASTERIX version reports are produced during this
period.
2. Change the ASTERIX Version Report period to 10 minutes and ensure that this
setting will be used after the GS is restarted. While injecting target reports,
restart the GS. Verify that one ASTERIX version report is produced after the
restart prior to any target reports. Continue for at least 10 minutes with target
reports being injected and verify that only 1 ASTERIX version report, in addition
to the initial ASTERIX version report, is sent by the GS.
3. Configure the ASTERIX Version Report period to 60 minutes. If the GS
supports more than one version of ASTERIX Category 021, change the
ASTERIX Category 021 version. Ensure that these values will be used after a
restart. While injecting target reports, restart the GS. Verify that one ASTERIX
version report is produced after the restart prior to any target reports. Verify that
only 1 ASTERIX version report is received every 60 minutes.
4. Examine the contents of the ASTERIX version reports produced in the
preceding steps and verify that the reported versions for ASTERIX Category
021 and Category 023 are consistent with the 1090 ES Ground Station
configuration settings and specifications. Verify that the reported version for
ASTERIX Category 247 is Edition 1.2 or greater and that the report construction
is compliant with the version reported, and contains the minimum fields
specified in section 3.10.3.3.

5.10.3.4 Data Validity Periods

5.10.3.4.1 Objectives

The aim of this test is to check that the system correctly applies the default validity
periods for the mandatory data items contained in ASTERIX Category 021 reports, as
specified in section 3.10.3.4 and summarised in the table below:
ASTERIX
Report Parameter Category Default Validity Period(s)
021 Item
Call Sign I021/170 100
Emergency/ Priority Status I021/200 100
SV Quality - NACP I021/090 24
SV Quality - NIC supplement I021/090 ± 5 from position message
Reported only with the associated position
SV Quality – NIC or NUCP I021/090
contained in the same message
Reported only with the associated velocity
SV Quality - NACV or NUCR I021/090
contained in the same message
SV Quality - SIL I021/090 24
SV Quality - NICBARO I021/090 100
10,
I021/140
Altitude per associated position contained in the
or 145
same message
10,
Position I021/130
per ED126 SPR19 and 23

© EUROCAE, 2010
 133

Position, altitude, velocity, heading, NIC/NUCP, and NACV/ NUCR shall never be
reported more than once.

5.10.3.4.2 Test Equipment Setup

The test equipment setup shall be the same as the standard setup described in
Section 5.1.1 with the following exceptions:
Periodic report mode shall be used for target 6 in order to test the position and flight
level validity periods.

5.10.3.4.3 Scenario Design

The methodology used is to send the initial target messages (at least 4 position
messages) to establish a track, then send the message containing the item under test
at time t=X, followed by a position message to trigger a report immediately afterwards
and again 0.9 seconds before and after the expected data expiry time (assuming a 1
second tolerance is to be allowed on the timeout).
The scenario has been designed to test all of the required validity periods. Empty cells
in the tables mean that the result of that cell is not necessary for the test. Due to the
number of parameters to test, the scenario will use several different targets (different
addresses).
TARGET 1
This target is used to test the validity period of 100s for the Callsign (I021/170). An
identification squitter is injected into the 1090 ES Ground Station and just before and
after this a report is triggered by new position squitters.
Target 1
Expected ASTERIX
ES Input
Category 021 Output
MOPS VN
Call SIign

Call SIign
Time (s)
Msg ID

Inject
Step

FTC

Rpt

PO1 0.5 18
PE2 1 18
1 PO3 1.5 18
PE4 2 18 R1
AOS1 2.1 31 1
2 ID1 2.5 1 AAAAAA
PO5 101.6 18 R2 AAAAAA
3
PE6 103.4 18 R3 DNP

Step 1: Target acquisition and version 1 confirmed.

Step 2: Callsign input
Step 3: Verification of Callsign validity period. Callsign is available in report 2 but not in
report 3.

© EUROCAE, 2010
 134

TARGET 2
This target is used to test the validity period for NACP and SIL. Input for these two data
item can be from both FTC = 29 and FTC = 31. The scenario tests first with FTC = 29
input and then with FTC = 31 input.
Target 2
Expected ASTERIX
ES Input
Category 021 Output

MOPS VN
Time (s)
Msg ID

Inject

NACP

NACP
Step

FTC

Rpt
SIL

SIL
PO1 0.5 18
PE2 1 18
1 PO3 1.5 18
PE4 2 18 R1
AOS1 2.1 31 1
TSS1 3 29 1 2
2
PO5 3.01 18 R2 1 2
3 PE6 26.1 18 R3 1 2
4 PO7 27.9 18 R4 DNP DNP
AOS2 29 31 1 2 1
5
PE8 29.01 18 R5 1 2
PO9 52.1 18 R6 1 2
6
PE10 53.9 18 R7 DNP DNP

Step 1: Target acquisition and version 1 confirmed.

Step 2: NACP and SIL input for FTC = 29.
Step 3 and 4: Verification of NACP and SIL validity period. Both values are valid at
report 3 but not at report 4.
Step 5: NACP and SIL input for FTC = 31.
Step 6: Verification of NACP and SIL validity period obtained from FTC = 31. Both
values are valid at report 6 but not at report 7.

© EUROCAE, 2010
 135

TARGET 3
This target is used to test the validity period for NIC supplement. This is done by
examining the reported NIC as it is required to be determined from both the FTC of the
latest position squitter message and the NIC supplement in the FTC = 31 Aircraft
Operational Status squitter message closest in time to the position message.
Target 3
Expected ASTERIX
ES Input
Category 021 Output

Inject Time

NIC suppl.

MOPS VN
Msg ID
Step

FTC

NIC
Rpt
(s)
PO1 0.5 18
PE2 1 18
1 PO3 1.5 18
PE4 2 18 R1
AOS1 3 31 1 1
PO5 7.9 16 R2 3
2
PE6 8.9 16 R3 2
Step 1: Target acquisition and version 1 confirmed.
Step 2: Input of NIC supplement and verification of NIC supplement validity period.
NIC is available on report 2 with value of 3 and with value of 2 on report 3 due to NIC
supplement expiration.

TARGET 4
This target is used to test the validity period for Emergency/Priority Status. Input for
this data item can be from both FTC = 29 and FTC = 28. The scenario tests first with
FTC = 29 input and then with FTC = 28 input.
Target 4
Expected ASTERIX
ES Input
Category 021 Output
Inject Time

MOPS VN
Msg ID

Em/Pri
status
Step

FTC

Rpt

PS
(s)

PO1 0.5 18
PE2 1 18
1 PO3 1.5 18
PE4 2 18 R1
AOS1 2.1 31 1
TSS1 3 29 3
2
PO5 3.01 18 R2 3
PE6 102.1 18 R3 3
3
PO7 103.9 18 R4 0
AS1 105 28 3
4
PE8 106 18 R5 3
PO9 204.1 18 R6 3
5
PE10 205.9 18 R7 0

© EUROCAE, 2010
 136

Step 1: Target acquisition and version 1 confirmed.

Step 2: Emergency priority status input for FTC = 29.
Step 3: Verification of PS FTC = 29. PS is available at report 3 but not at report 4 (PS
is encoded as a zero value).
Step 4: Emergency priority status input from FTC = 28.
Step 5: Verification of PS obtained from FTC = 28. PS is available at report 6 but not
at report 7 (encoded as a zero value).

TARGET 5
This target is used to test the validity period for NICBARO. Input for this data item can be
from both FTC = 29 and FTC = 31. The scenario tests first with FTC = 29 input and
then with FTC = 31 input.
Target 5
Expected ASTERIX
ES Input
Category 021 Output
MOPS VN
Time (s)

NICBARO

NICBARO
Msg ID

Inject
Step

FTC

Rpt
PO1 0.5 18
PE2 1 18
1 PO3 1.5 18
PE4 2 18 R1
AOS1 2.1 31 1
TSS1 3 29 1
2
PO5 3.01 18 R2 1
PE6 102.1 18 R3 1
3
PO7 103.9 18 R4 DNP
AOS2 110 31 1 1
4
PE8 110.5 18 R5 1
PO9 209.1 18 R6 1
5
PE10 210.9 18 R7 DNP

Step 1: Target acquisition and version 1 confirmed.

Step 2: NICBARO input for FTC = 29.
Step 3: Verification of NICBARO validity period obtained from FTC = 29. NICBARO values
are available at report 3 but not at report 4.
Step 4: NICBARO input for FTC = 31.
Step 5: Verification of NICBARO validity period obtained from FTC = 31. NICBARO values
are available at report 3 but not at report 4.

© EUROCAE, 2010
 137

TARGET 6
This target is used to test the validity period for, WGS-84, FL and NUCP. As they can
only be sent once, the test is performed in periodic mode. Initially, the report period is
set to the minimum value of 0.5 seconds in order to give the best resolution for
checking the timing of the data. To test the validity period for WGS-84 position and FL,
the test is repeated with a second reporting period of 15s.
Target 6
Expected ASTERIX
ES Input
Category 021 Output

Positiion in
Inject Time

Longitude

MOPS VN
Latitude

WGS-84
Altitude
Msg ID

NUCP
Step

FTC

Rpt
(s)

FL
PO1 0.5 18
PE2 1 18
1 PO3 1.5 18
PE4 2 18 R1
AOS1 2.1 31 0
PO5 2.4 18 Z Y X
21
2.5 R21 X-Y Z 0
3 No Report Generated
1
3 3.5 No Report Generated
4 No Report Generated
2
4 17 No Report Generated
Step 1: On step 1 we have target acquisition, and version 0 confirmation.
Step 2: On this step we have input and the first and only report containing WGS-84
Position, FL and NUCP (if the reporting period is set to 0.5 s).
Step 3: Verification of the requirement that WGS-84 Position, FL and NUCP shall be
never sent more than once.
Step 4: Verification of validity period of 10 seconds for WGS-84 Position and FL.

1
This step will apply only when the reporting period is equal to 0.5 s.
2
This step will apply only when the reporting period is equal to 15 s.

5.10.3.4.4 Test Procedure

Test Steps:
1. Play the scenario for targets 1-5
2. When the scenario is complete, stop recording ASTERIX reports
3. Wait at least 120s for target data re-initialisation.
4. Change GS configuration to “periodic reporting mode” and select report period
equal to 0.5s.
5. Prepare the message source to play the scenario with target 6
6. Play the scenario.
7. When the scenario is complete, stop recording ASTERIX reports
8. Wait at least 120s for target data re-initialisation.

© EUROCAE, 2010
 138

9. Change GS configuration to “periodic reporting mode” and select report period

equal to 15s.
10. Prepare the message source to play the scenario with target 6
11. Play the scenario.
12. When the scenario is complete, stop recording ASTERIX reports.
13. Analyze the recorded data and verify that the expected outputs are present.

5.10.4 ASTERIX Category 021 Report Assembly

There are no specific tests for section 3.10.4. The minimum requirements of this
section are covered by the tests for Position and Velocity reports in section 5.10.3.1.

5.11 RECEIVER CHARACTERISTICS

NOTE: the signal power levels measured in these tests may need to be adjusted
to take into account any differences between the antenna system with
which the Ground Station is designed to operate, and the Reference
Antenna described in section 3.1.2. Further guidance is given in
APPENDIX G.

5.11.1 Receiver Sensitivity

5.11.1.1 Objectives

Test the sensitivity requirements in section 3.11.1.

5.11.1.2 Test Equipment Setup

The test equipment setup shall be the same as the standard setup described in
Section 5.1.1.

5.11.1.3 Scenario Design

The test uses a repeated sequence of 1090 ES messages injected at a convenient

repetition rate for RF testing.

5.11.1.4 Test Procedure

Test Steps:
1. Establish 1090 ES Ground Station Receiver MTL as follows:
2. Decrease the input power level and determine the minimum RF signal level
required to produce a 90 percent ADS-B message reception rate by the 1090
ES Ground Station receiver measured over at least 1000 messages.
3. This value minus the cable loss value represents the measured MTL of the
1090 ES Ground Station ADS-B receiver.
4. Verify that the measured MTL is in compliance with the limits specified in
section 3.11.1.
5. Vary the RF signal frequency over the range of 1089 to 1091 MHz and
determine the variation in RF signal level required to produce 90 percent ADS-B
message reception rate by the 1090 ES Ground Station receiver measured over
at least 1000 messages. Verify that the measured MTL continues to comply
with the limits specified in section 3.11.1.
6. Set the power level to the minimum level specified in section 3.11.1.
7. Inject at least 1000 messages and verify that the successful message reception
rate is 15% or greater.

© EUROCAE, 2010
 139

5.11.2 Receiver Desired Signal Dynamic Range

5.11.2.1 Objectives

This test verifies that the ADS-B receiver can detect and decode valid ADS-B
messages over the equipment’s specified dynamic range, as specified in section
3.11.2.

5.11.2.2 Test Equipment Setup

The test equipment setup shall be the same as the standard setup described in
Section 5.1.1.

5.11.2.3 Scenario Design

The test uses a repeated sequence of 1090 ES messages injected at a convenient

repetition rate for RF testing.

5.11.2.4 Test Procedure

Test Steps:
1. Set the input signal power level to the minimum value specified in section
3.11.2.
2. Inject at least 1000 messages and verify that the receiver properly detects and
decodes at least 99% of all ADS-B Messages injected.
3. Increase the input signal power level in 10 dB steps up to the maximum value
specified in section 3.11.2.
4. At each signal level, inject at least 1000 messages and verify that the receiver
properly detects and decodes at least 99% of all ADS-B Messages injected.

© EUROCAE, 2010
 140

CHAPTER 6

INSTALLED EQUIPMENT PERFORMANCE

6.1 INTRODUCTION

This Section specifies the minimum acceptable level of performance, and test
procedures for verifying that performance, for the equipment when installed. The
previous Sections defined 1090 ES ADS-B Ground Station equipment requirements.
This Section addresses system related requirements that are not necessarily to be
tested by equipment manufacturers as “type approval tests”, but which need to be
verified by implementers claiming ED-126 compliant services.
Installed performance criteria are generally the same as those contained in Section 3,
which were verified through bench and environmental tests. However, certain
performance parameters may be affected by the physical installation (e.g. antenna
patterns, receiver sensitivity, etc.) and can only be verified after installation. The
installed performance limits specified below take these situations into consideration.

6.2 EQUIPMENT INSTALLATION

6.2.1 Environment

Installed equipment shall be compatible with the environmental conditions present in

the specific location where the equipment is installed.

6.2.2 Failure Protection

Any probable failure of the equipment shall not degrade the normal operation of any
other equipment or systems connected to it. The failure of interfaced equipment or
systems shall not degrade normal operation of the subject equipment.

6.2.3 Interference Effects

The equipment shall not be the source of harmful conducted or radiated interference,
and shall not be adversely affected by conducted or radiated interference from other
equipment or systems installed in the vicinity.
NOTE: Electromagnetic compatibility problems observed after installation of the
equipment may result from such factors as the design characteristics of
previously installed systems or equipment and the physical installation
itself. It is not intended that the equipment manufacturer design for all
installation environments. The installer will be responsible for resolving any
incompatibility between the equipment and previously installed equipment.
The various factors contributing to the incompatibility shall be considered.

6.2.4 Inadvertent Turnoff

Protection shall be provided to prevent the inadvertent turnoff of the equipment.

6.2.5 Power Source

The installation shall ensure that the appropriate voltage and voltage characteristics
required by the equipment are continuously applied to the equipment at all times that
the equipment is required to be operational. The power source installation should be
commensurate with the overall availability requirements for the system.

6.2.6 Transmission Lines

The transmission line(s) connecting antennas to receivers shall have impedance and
loss characteristics in accordance with the equipment manufacturer’s specifications.

© EUROCAE, 2010
 141

6.2.7 Antenna Type

Antennas used shall be compatible with the 1090 ES Ground Station equipment
manufacturer’s specifications, and the intended coverage volume.

6.2.8 Antenna Location

The location of antennas shall be compatible with the intended coverage volume. Care
should be taken to avoid physical obstructions that may impact required coverage
performance. As far as is practical, antennas should be located such that interference
from other nearby antennas and equipment is kept to a minimum, particularly if that
equipment is transmitting on adjacent frequency bands as may occur with DME.
Guidance on DME interference considerations is included in Appendix J.

6.2.9 Time Source

Where an external time source such as a GPS receiver or antenna is required to be

connected to the 1090 ES Ground Station equipment, it shall conform to the Ground
Station manufacturer’s specifications.

6.2.10 Lightning Protection

The system shall be protected against lightning in accordance with IEC/EN 62305.
This has been jointly developed with the IEC and is published in Europe through
CENELEC member organisations in the following parts.
EN 62305-1 Protection against lightning – Part 1 General principles;
EN 62305-2 Protection against lightning – Part 2 Risk management;
EN 62305-3 Protection against lightning – Part 3 Physical damage to structures
and life hazard;
EN 62305-4 Protection against lightning – Part 4 Electrical and electronic
systems within structures;
EN 62305-5 Protection against lightning – Part 5 Services.

6.2.11 Communications

The characteristics of the communications links shall be verified, including bit rate,
latency and packet loss.

6.2.12 Remote Control and Monitoring

Correct operation of the remote control and monitoring procedures shall be verified.

6.2.13 End to End System Testing

End to end system tests shall be performed to verify interoperability with client
systems.

6.3 EXTERNAL EQUIPMENT

The installed ADS-B System shall include a site monitor or equivalent method to allow
an end-to-end system test including RF reception, to confirm the total system
operation against a known target. As well as testing against a known source, this
provides the user with confidence that the system is operating correctly in the absence
of any traffic, for example during night time periods.

6.4 INSTALLED EQUIPMENT PERFORMANCE

The installed equipment shall achieve the levels of performance specified in ED-126
for the ADS-B ground domain, such as the latency, update rate and the probability of
detection.

© EUROCAE, 2010
 142

6.5 CONDITIONS OF TEST

The following subparagraphs define the conditions under which the tests specified in
Section 6.6 shall be conducted.

6.5.1 Power Input

Unless otherwise specified, tests should be conducted with the equipment powered by
the installed equipment electrical power system.

6.5.2 Associated Equipment or Systems

Unless otherwise specified, all electrically operated equipment and systems should be
turned on before carrying out interference tests.

6.5.3 Environment

During the tests, the equipment should not be subjected to environmental conditions
that exceed those specified by the equipment manufacturer.

6.5.4 Adjustment of Equipment

The equipment under test should be properly configured in accordance with the
manufacturer's recommended practices before the application of the specified tests.

6.5.5 Warm-up Period

Unless otherwise specified, tests should be conducted after a warm-up (stabilisation)

period of not more than fifteen minutes, but not less than any minimum warm-up
period specified by the manufacturer.

6.6 TEST PROCEDURES FOR INSTALLED EQUIPMENT PERFORMANCE

The following test procedures provide one means of determining installed equipment
performance.
Although specific test procedures are prescribed, it is recognised that other methods
may be preferred by the installer/manufacturer. Such alternative procedures may be
used if they provide at least equivalent information, in which case, the procedures
described in this Section should be used as one criterion in evaluating the
acceptability of the alternative procedures.
The equipment shall be tested to demonstrate compliance with the performance
criteria specified in Section 3.
Test results, or other proof of conformity, supplied by the equipment manufacturer,
may be accepted in lieu of bench tests performed by the installer.

6.6.1 Ground Test Procedures

6.6.1.1 Conformity Inspection

Visually inspect the installed equipment to determine the use of acceptable

workmanship and engineering practices.
Verify that proper mechanical and electrical connections have been made and that the
equipment has been located and installed in accordance with the manufacturer's
recommendations.

6.6.1.2 Equipment Function

Proper functioning of the installed system should be verified according to the

documented system operating procedures.

© EUROCAE, 2010
 143

6.6.1.3 Equipment Accessibility

Determine that the equipment can be accessed and removed in accordance with the
prescribed maintenance practices.

6.6.1.4 Probability of Detection and Coverage Volume

Verify that the probability of detection of 1090 ES targets reaches the specified levels
at the required range and throughout the intended coverage volume. The following
steps are recommended:
1. Perform coverage predictions using a proprietary software package. This tool
should include configurable site location, line-of-sight coverage, use of the 4/3
earth model for coverage predictions, power budget on the downlink given the
Mode S transponder output level and minimum received power level at the 1090
ES Ground Station receiver, link load calculations and the impact of interference
on system performance.
2. Perform Commissioning tests, which fully characterise the installed 1090 ES
Ground Station and thereby gain sufficient confidence that the system will meet
the Site Acceptance Test performance requirements. These tests also initiate
the process to demonstrate that the measured surveillance performance meets
its coverage predictions.
3. The 1090 ES Ground Station undergoes a Site Acceptance Test (SAT), which
fully tests the equipment specification in terms of measured surveillance
performance and the correct operation of the Ground Station interfaces with
ancillary equipment. Targets Of Opportunity (TOO) should be used to verify the
coverage volume, and to measure performance of the surveillance system
within that volume.
4. A flight trial is performed to confirm that the operational coverage requirements
are met for aircraft operating at the limit of the minimum ICAO Annex 10
specification. As such the flight trial aircraft should be equipped with a minimum
ICAO Annex 10 specification transponder.

6.6.1.5 RF Environment

It is recommended that a check should be made for possible sources of RF

interference at the installation site, for example by connecting a spectrum analyzer to
the output of the antenna.

© EUROCAE, 2010
 144

APPENDIX A

GROUND STATION CONFIGURATION AND MONITORING PARAMETERS

NOTE: In order to promote standardisation of the SNMP control interface,

recommended names for the configuration and monitoring parameters are
given. These are shown within braces {…}.
For parameters that are configurable on a per service basis, indicated by the symbol *
at the end of the name, the service ID is added to the parameter name as a three digit
decimal suffix, for example SIC001 for service 1.

A.1 REQUIRED CONFIGURATION PARAMETERS

Parameter Name Purpose Allowed Values Default Value Reference
System Mode System operating One of: Operational 3.9.2.1
{SystemMode} mode Operational
Maintenance
System Identification Code System Integer [0..255] 0 3.10.4.2
{SIC*} identification
code
System Area Code System area Integer [0..255] 0 3.10.4.2
{SAC*} code
GS IP Address Internet Protocol As appropriate
{GSIPAddr*} address of GS
GS IP Default Gateway Internet Protocol As appropriate
{GSIPDefGW*} default gateway
for GS
GS IP Netmask Internet Protocol As appropriate
{GSIPNetmask*} netmask for GS
ASTERIX Report Internet Protocol As appropriate 2.2
Destination IP Address destination
{ASTERIXDestIPAddr*} address for
ASTERIX reports
ASTERIX Report Destination UDP As appropriate 2.2
Destination UDP port port for ASTERIX
{ASTERIXDestPort*} reports
ASTERIX Report IP TTL Internet Protocol As appropriate 2.2
{ASTERIXTTL*} Time-To-Live for
transmitted
ASTERIX reports
Maximum Ground Interface Maximum bit rate As appropriate – 2.2, 3.3.3
Bit Rate available for System dependent 3.9.3.5
{MaxCommBitRate*} communications 3.10.2.1.2
via the ground
interface.
ASTERIX State Vector ASTERIX State One of: Data Driven 2.2
Reporting Mode Vector Report - Data-Driven 3.10.2.1.3
{ASTERIXReportMode*} reporting mode - Periodic

© EUROCAE, 2010
 145

Parameter Name Purpose Allowed Values Default Value Reference

Periodic Reporting Interval Nominal time At a minimum 0.5 2.2
{PeriodicReportInterval*} between to 15 seconds in 3.10.2.3.1
ASTERIX State 0.5 second
Vector Reports increments
when the
Reporting Mode
is periodic
ASTERIX Category 023 Nominal time At a minimum 1 to 60 seconds 3.10.3.2
Ground Station Status between 127 seconds in 1 3.10.2.3.2
Reporting Interval ASTERIX Ground second increments
{GSReportInterval*} Station Status
Reports
ASTERIX Category 023 Nominal time At a minimum 1 to 60 seconds 3.10.3.2
Service Status Reporting between 127 seconds in 1 3.10.2.3.2
Interval ASTERIX Service second increments
{ServiceReportInterval*} Status Reports
ASTERIX Category 247 Nominal time At a minimum 0 to 10 minutes 3.10.3.3
Reporting Interval between 60 minutes in 10
{VersionReportInterval*} ASTERIX Version minute increments
Reports
GS Latitude Latitude of the Per GS location
{GSLatitude} GS RF antenna
GS Longitude Longitude of the Per GS location
{GSLongitude} GS RF antenna
Test Target Alert Power Power level As appropriate – 3.9.3.9
Threshold below which an manufacturer
{TestTargetAlertPower} alert will be specific
triggered
Test Target Fail Power Power level As appropriate – 3.9.3.9
Threshold below which GS manufacturer
{TestTargetFailPower} Failed state will specific
be triggered
Capacity Threshold Number of Integer 300 3.3.2
{CapacityThreshold} detected targets
above which an
alert will be
triggered

© EUROCAE, 2010
 146

A.2 OPTIONAL CONFIGURATION PARAMETERS

Parameter Name Purpose Allowed Values Default Value Reference
ASTERIX Category 021 ASTERIX 1.4 1.4 2.2
Version Category 21 0.23
{ASTERIXVersion*} version number
used for
formatting state
vector reports
CPR Airborne Maximum Maximum 300 NM 2.2
Range expected range
{CPRAirborneMaxRange} of GS for
airborne targets.
Targets outside
this range will not
be reported.
This range may
be implemented
as a polygon for
non-circular GS
coverage
volumes.
GS Time State Coasting Integer 30 minutes 2.3.3
Timeout 3.7
{CoastingTimeout}
Reporting of Non-Validated Enables Enabled Not enabled 3.10.2.4
Targets ASTERIX Not enabled
{ReportNonValidated*} Category 021
reports when
target has yet
passed validation
checks
Site Monitor Mode S Address 24 bit Mode S Any 24 bit value As appropriate 3.10.4.6
{SiteMonitorAddress} Address of site except 000000 or 3.9.3.9
monitor(s) FFFFFF hex
Report Non ADS-B Data Enables Enabled Not enabled 3.10.1.1
{ReportNonADSB*} reporting of non- Not enabled
ADS-B Mode S
data
Call Sign Validity Period Integer (seconds) 100 seconds 3.10.3.4
{CallSignValidity}
Emitter Category Validity Integer (seconds) 200 seconds 3.10.3.4
Period
{EmitterCategoryValidity}
Emergency/ Priority Status Integer (seconds) 100 seconds 3.10.3.4
Validity Period
{EmergencyValidity}
Capability Class Codes Integer (seconds) 24 seconds 3.10.3.4
Validity Period
{ CapabilityClassValidity}
Operational Mode Validity Integer (seconds) 24 seconds 3.10.3.4
Period
{OperationalModeValidity}
SV Quality - NACP Validity Integer (seconds) 24 seconds 3.10.3.4
Period
{NACpValidity}

© EUROCAE, 2010
 147

Parameter Name Purpose Allowed Values Default Value Reference

SV Quality - NIC Supplement Maximum time Integer (seconds) 5 seconds 3.10.3.4
Validity Period before or after
{ NICSupplementValidity} position message
SV Quality - SIL Validity Integer (seconds) 24 seconds 3.10.3.4
Period
{SILValidity}
SV Quality - NICBARO Validity Integer (seconds) 100 seconds 3.10.3.4
Period
{NICBaroValidity}
Horizontal Reference Integer (seconds) 100 seconds 3.10.3.4
Direction (HRD) Validity
Period
{HRDValidity}
Mode A Code Validity Period Integer (seconds) 100 seconds 3.10.3.4
{ModeAValidity}
Airborne Velocity Validity Velocity, Vertical Integer (seconds) 10 seconds 3.10.3.4
Period Rate, Airspeed,
Heading, NACV
{AirborneVelocityValidity} or NUCR
Selected Altitude Validity Integer (seconds) 24 seconds 3.10.3.4
Period
{ SelectedAltitudeValidity}
Airborne Position Validity Position, Altitude, Integer (seconds) 10 seconds 3.10.3.4
Period NIC or NUCP
{AirbornePositionValidity}
Time to enter Integer (seconds) 10 seconds 3.9.3.9.c
Test Transmission Timeout failed state on
{TestTransmissionTimeout} loss of test
transmissions

A.3 REQUIRED SNMP MONITORING PARAMETERS

SNMP Monitored Recommended Name Possible Values Reference
Parameter
Ground Station State {GSState Initialisation/On-line/Failed 2.3.2,
3.9.3.1
Time Source State {TimeSourceState} UTC Coupled/Not Coupled/ 2.3.3,
Coasting 3.9.3.7
Target Overload {TargetOverload} Passed/Warning 3.9.3.4
Communications Overload {CommunicationsOverload} Passed/Warning 3.9.3.5
Communications Loss {CommunicationsLoss} Passed/Failed 3.9.3.6
Receiver Sensitivity {ReceiverSensitivity} Passed/Failed/Warning 3.9.3.9.f
Test Transmission Loss {TestTransmission} Passed/Failed 3.9.3.9.d
Decoder Test {Decoder} Passed/Failed 3.9.3.9.h
Status of Individual LRUs Manufacturer Dependent Manufacturer Dependent 3.9.3.1.c
(see Note 1)

NOTE 1: The‘Status of Individual LRUs’ parameter is ‘Required’ if the GS

incorporates redundant LRUs to meet the Availability requirement defined
in section 3.8. (See section 3.9.3.1c). If the GS does not make use of
redundant LRUs to meet the Availability requirement then this parameter
may be considered as ‘Optional’.

© EUROCAE, 2010
 148

A.4 OPTIONAL SNMP MONITORING PARAMETERS

SNMP Monitored Recommended Name Possible Values Reference
Parameter
Buffer Overflow Test {BufferOverflow} Passed/Failed 3.9.3.2
Processor Overload {ProcessorOverload} Passed/Failed 3.9.3.3
Temperature Range {TemperatureRange} Passed/Warning 3.9.3.8

© EUROCAE, 2010
 149

APPENDIX B

BITE TEST SUMMARY

B.1 BITE TESTS

BITE Test Result Ground SNMP ASTERIX ASTERIX
Station Status I023/110 I023/100
State
Buffer overflows§ Passed On Line* Passed Normal*
Failed Failed Failed Failed NOGO = 1
Processor overload§ Passed On Line* Passed Normal*
Failed Failed Failed Failed NOGO = 1
ODP = 1
Target overload Passed On Line* Passed Normal*
Warning On Line* Warning Normal* ODP = 1
Communications Loss Passed On Line* Passed Normal*
Failed Failed Failed Failed NOGO = 1
Communications overload Passed On Line* Passed Normal*
Warning On Line* Warning Normal* OXT = 1
Time Synchronisation Passed On Line* Passed Normal*
Warning (TS On Line* Warning Normal* TSV = 0
Coasting)
Failed (TS Failed Failed Failed NOGO = 1
Not TSV = 1
Coupled)
Temperature Range§ Passed On Line* Passed Normal*
Warning On Line* Warning Normal*
End to End Passed On Line* Passed Normal*
Warning On Line* Warning Normal*
(Low
sensitivity)
Failed Failed Failed Failed NOGO = 1
* Assuming that no other failure conditions exist and initialisation of the 1090ES
Ground Station has been completed.
§ Denotes an optional BITE test.

NOTES:
ASTERIX Category 023 NOGO, TSV, ODP and OXT bits are zero except
where specified.
The NOGO bit is also set if the 1090 ES Ground Station is in Maintenance
mode.
During initialisation the 1090 ES Ground Station state is “Initialisation” and
the STAT field in I023/110 is set to “Initialisation”.

© EUROCAE, 2010
 150

APPENDIX C

1090 ES GROUND STATION INTEGRITY REQUIREMENT

C.1 OVERVIEW

This Appendix provides an overview of the rationale behind the integrity requirement
defined for the 1090 ES Ground Station in Sec. 3.6.
The 1090 ES Ground Station supports the reception, processing and delivery
functions for a 1090 ES ADS-B message, from airborne domain output or Ground
Station domain input (interface D) to Ground Station output (interface E2) according to
Figure C-1

FIGURE C-1: HIGH-LEVEL VIEW OF 1090 ES GROUND STATION AND AIRBORNE SEGMENTS
PER ED-126

External Data Sources

(e.g., GNSS)

Receive Aircraft Domain

D A2 B2
ADS-B
Messages Aircraft sensors
Transmit Aircraft Domain (e.g., GNSS Aircraft Processing Functions
receiver)
A1 B1 C
Ownship
Surveillance
Aircraft sensors Aircraft systems Transmit
(e.g., GNSS (e.g., FMS) Processing
Receiver) Ownship (STP) of
Surveillance ADS-B SSR
Nav. Data
Transmit Transmit Replies
Processing Function
Aircraft systems (STP)
Cockpit
(e.g., FMS) Aircraft
Display of
Surveillance
ADS-B/ Traffic
ADS-B, and
TIS-B Information Flight
TIS-B Separation
Receive and Crew
Reports Assistance
Function Control
Data Sources on SSR Processing
Interrogation Panel
(ASSAP)
Transmitting Reply (CDTI)
Aircraft
ADS-B &
TIS-B
Messages E1 F1 G1
ADS-B messages and
SSR replies
TIS-B Messages

G2 F2 E2

ADS-B
Receive
Air ATC ADS-B, Subsystem TIS-B Processing
ATC
Traffic Processing Surv and other and Transmit
Display Reports Surveillance Subsystem
Co. System
Inputs
(e.g. radar)

Ground Domain

C.2 REQUIREMENT

To be able to support ADS-B-NRA services in line with ED-126 an ADS-B Ground

Station is required, as a minimum, to provide data according to the following integrity
requirement:
ED-126: “The likelihood that the ADS-B receive subsystem corrupts ADS-B
information through the reception, processing or delivery of data (E2) shall be no
more than 5×10-6 per ATSU hour.”
NOTE 1:
This integrity requirement represents the probability that the ADS-B
Receive subsystem introduces systematic errors into the data transmitted
via ADS-B Messages to the extent that the errors become operationally
relevant to the Controller.

© EUROCAE, 2010
 151

The integrity requirement is stated from aircraft transmission (interface D) to Ground

Station output (interface E2), according to Figure C-1. The required integrity is derived
based on corruption of position or position quality indicator information. Further, the
requirement is derived from the most stringent operational environment identified, the
TMA environment.

C.3 ANALYSIS

The ED-126 analysis was made assuming that integrity errors that propagate to the
Controller Work Position (CWP) either are detected or undetected. The required
integrity level was derived from the analysis case where integrity errors at the CWP
cannot be detected. The consequence of this is that any error in the Ground Station
output data, induced after interface D, has to be regarded as an undetected integrity
error at the CWP and therefore meet the ED-126 required integrity level.
The integrity requirement “represents the probability that the ADS-B Receive
subsystem introduces systematic errors into the data transmitted via ADS-B
Messages to the extent that the errors become operationally relevant to the
Controller”. In assessing systematic and operational relevant to the controller the
following assumption has been made:
Assumption 1: For a systematic error to become operationally relevant to the
controller, it is assumed that the error has to occur in at least two subsequent update
intervals for the same aircraft.
The 1090 ES ADS-B link provides a CRC protection encoded per aircraft message (or
squitter). To enable a comparison between the CRC provided integrity on a per
message basis, and the operational required integrity per ATSU hour it is assumed
that:
Assumption 2: in line with the ED-126 TMA environment definition, one Ground
Station is serving one sector, i.e. 1 GSh = 1 ATSUh.
To simplify the analysis and avoid assessing the probability of having a corruption in
the position information or the probability that an error introduced in the aircraft
transmitted message is causing a systematic error in the output the following
assumptions are made:
Assumption 3: All airborne position or position quality indicator messages are
corrupted.
This means that the analysis does not take advantage of the fact that a message error
beyond the CRC integrity actually could contain a valid message with respect to
position or position quality indicator. Further, it is conservatively assumed that:
Assumption 4: Any subsequent link integrity error will result in a systematic error to
the position or position quality indicator on the CWP screen.
Assumption 5: If the CRC integrity check fails for one airborne position report that
report propagates to the CWP display in the next update (see Figure C-2).

© EUROCAE, 2010
 152

FIGURE C-2: ASSUMED RELATION BETWEEN AIRBORNE POSITION REPORTS AND CWP
SCREEN UPDATES

5 seconds Airborne
position
reports

CWP
position
updates
Position report displayed on the CWP (also assumed to propagate due to failed CRC integrity)
Position report not displayed on the CWP
Undetected position report

In this scenario the probability that a corrupt single airborne position report propagates
through the CRC integrity protection to the CWP has the same probability as the
probability of the CRC failure.
Thus, the probability of having false position information (position or position quality
indicator) displayed on the CWP display due to CRC integrity failure is equal to the
probability of having a CRC integrity failure.
The integrity provided by the CRC is dependent on the extent to which the CRC is
used to recover a message by employing error correction and the environment noise.
The ADS-B MOPS [REF21] considers that the 1090 ES CRC provides integrity of 1-
10-7 per ADS-B message. It is up to the system designer to select an appropriate error
correction strategy to meet the integrity requirement.
The Ground Station implementation of ADS-B message error correction must not
impact the ADS-B message integrity provided by the 1090 ES CRC in such a way that
the ADS-B message integrity falls below 10-5. Based on the required minimum
message integrity, the probability for an error that is operationally relevant to the
controller to occur at any instant is:
P (≥ 2 subsequent) = 10-5 × 10-5 = 10-10
NOTE: The calculation is ignoring terms for more than 2 errors in sequence.
The fact that the event could occur at any instance during an ATSU hour results in 720
permutations of the event to occur. The probability that the event occurs, for 2
subsequent update intervals or more, during 1 ATSUh can be expressed as:
P (≥ 2 subsequent) = 720 × 10-10 = 7.2 × 10-8
Or expressed as integrity in the order of 10-7.

© EUROCAE, 2010
 153

APPENDIX D

PROCESSING OF DUPLICATE ADDRESSES

D.1 INTRODUCTION

Every Mode S message sent on 1090 MHz identifies the sender by the use of a 24-bit
“unique” address. These addresses are assigned by a regulatory authority, and are
allocated to a particular aircraft such that there should never be more than one aircraft
operating with any given address.
By modern standards Mode S messages are short in length, comprising 56 or 112 bits
depending on the type of message. Information such as the type of message, CRC
checksum, and aircraft address must be included in these bits. Extended squitter
ADS-B messages are all 112 bits in length but only half of the data bits are available
for the ADS-B data content. It is therefore unsurprising that the required ADS-B
information, such as position in Latitude, Longitude and Altitude, call-sign, velocity
vector, aircraft category, etc. cannot be sent in a single message, and must be
communicated using several messages. Since all transmitted messages contain the
aircraft address, any receiving station should be able to correlate all received
messages with a given address to reassemble the complete set of data.
In theory the receiving process is simple since all aircraft addresses are supposed to
be unique. In practice however duplication of addresses is commonplace. The most
likely scenario is that a new aircraft has the same address as a mature target, but
provision must be made to recognise the existence of two aircraft with the same
address when the receiver is powered up, in which case they are likely to enter the
target acquisition process at roughly the same time.

D.2 CAUSES OF DUPLICATED ADDRESSES

Duplicated addresses can be classified into three main groups:

D.2.1 Accidental re-use of an address

The majority of duplicate address occurrences are the result of inadvertent operation
of a transponder with an incorrect address. This may occur when a new transponder is
fitted to an aircraft without entering the allocated address. A similar problem can be
caused when a transponder is moved between aircraft without setting the new
address. Additionally wiring errors or poor connections in the aircraft wiring itself have
been found to cause the problem.

D.2.2 Incorrect Decoding of a Garbled Message

Each Extended Squitter message contains a 24-bit checksum which allows the
detection, and to some extent the correction, of a message that has become corrupted
by interference. The CRC error syndrome is calculated and the message is deemed to
be correct if the syndrome is zero. Occasionally an error syndrome may equate to
zero when the message contains errors. The probability of this depends largely on the
error correction algorithm employed in the receiver, but in order to have a syndrome of
zero in the presence of errors there must be at least six incorrect bits in the decoded
message. One or more of these six bits may be in the address field causing an
incorrect address to be decoded for the message. Of course, the chance that a
corrupted address matches an aircraft already being tracked by the receiver is very
unlikely.

© EUROCAE, 2010
 154

D.2.3 Deliberate Transmission of Incorrect Messages

Much work has been done on ways to mitigate the effects of deliberate transmission of
false data, and it is not within the scope of this document to provide details. However
when developing an algorithm to discriminate duplicate addresses thought must be
given to intentional duplicates.

D.3 DESIRABLE BEHAVIOUR IN THE EVENT OF DUPLICATE ADDRESSES

The ideal behaviour for a receiver when presented with duplicate addresses is to
output two separate tracks as if the addresses were different. Both such tracks would
be flagged as duplicates.
The minimum requirement is to identify one or more targets as duplicates, since there
is a real chance that some of the information reported for that target may in fact
belong to a different aircraft. Targets that are flagged as duplicates are required to be
reported as such to downstream clients by the 1090 ES Ground Station (section
3.10.1.3).

© EUROCAE, 2010
 155

APPENDIX E

THROTTLED REPORTING MODE

E.1 INTRODUCTION

This Appendix describes throttled reporting mode, a hybrid of the data-driven and
periodic reporting modes described in Section 3.10. Throttled reporting mode
conserves communications bandwidth while minimising data age. Throttled reporting
mode is not a minimum requirement for 1090 ES Ground Stations compliant with this
specification but it is described here so that manufacturers who choose to implement it
may do so in a consistent manner.

E.2 DATA-DRIVEN REPORTING MODE

In data driven mode, ASTERIX Category 021 state vector reports are generated and
sent immediately upon receipt of position and velocity Extended Squitter messages.
Figure E-1 depicts the processing of ES messages and the delivery of ASTERIX
Category 021 reports in data-driven reporting mode.

FIGURE E-1: PROCESSING TIMELINE FOR DATA-DRIVEN REPORTING MODE

Extended Squitter Position # and Velocity a Messages

3 4 5 6 8 10 11 12 13
A B C D E G I

t0 t0 + 1s t0 + 2s t0 + 3s t0 + 4s

Cat 021
State B C D E G I
Vector 4 5 6 8 10 11 12 13
Reports

GS Processing Latency

Data driven reporting could result in up to 5 ASTERIX reports per second (2 position,
2 velocity and 1 emergency) for each ADS-B target within range of a Ground Station.
The high data rate resulting from data-driven reporting has been a concern in areas
with limited communications bandwidth.

E.3 PERIODIC REPORTING MODE

In periodic mode, reports are generated at a configurable time interval asynchronously

from the receipt of Extended Squitter messages. Periodic reporting was envisioned as
a way to reduce communications load while maintaining an adequate update rate.
One consequence of periodic reporting is that the age of the data reported can vary by
up to the duration of the periodic reporting interval (typically 1-5 seconds). Figure E-2
is a processing timeline for periodic reporting mode.

© EUROCAE, 2010
 156

FIGURE E-2: PROCESSING TIMELINE FOR PERIODIC MODE SHOWING POTENTIAL DATA AGE
VARIATION

Extended Squitter Position # and Velocity a Messages

3 4 5 6 8 10 11 12
A B C D E G I

t0 t0 + 1s t0 + 2s t0 + 3s t0 + 4s
PRI PRI PRI PRI

Cat 021
State 4 A 6 C 8 G 12 I
Vector Data age
Reports variation

GS Processing Latency Velocity is optional in periodic reports

PRI - Periodic Reporting Interval

E.4 THROTTLED REPORTING MODE

The US Federal Aviation Administration (FAA) determined that the data age variation
in periodic mode could cause problems for some ATC systems. The FAA proposed
throttled mode as a solution that would yield constant data age at the expense of
greater variation in the time between reports. Throttled mode is essentially the same
as data driven mode except there is a wait period after each ASTERIX state vector
report. No reports are sent during the wait period. The first triggering ES message to
arrive after the end of the wait period initiates an ASTERIX report and a new wait
period. Separate wait period timers are maintained for position and velocity messages
from each target. The durations of the wait periods are configurable. Figure E-3
depicts the operation of throttled mode.

© EUROCAE, 2010
 157

FIGURE E-3: PROCESSING TIMELINE FOR THROTTLED REPORTING MODE

Extended Squitter Position # and Velocity a Messages

3 4 5 6 8 10 11 12 13
A B C D E G I M

t0 t 0 + 1s t 0 + 2s t 0 + 3s t 0 + 4s
PWP PWP PWP

VWP VWP VWP

Cat 021
State
4 B D 8 G 10 I 13
Vector
Reports

GS Processing Latency = Data Age

PWP – Position Wait Period
VWP – Velocity Wait Period

The position and velocity wait period durations are usually the same but they are not
required to be so.

E.5 RECOMMENDED REQUIREMENTS FOR THROTTLED REPORTING MODE

The following requirements are recommended for products that include throttled
reporting mode. These requirements are not mandatory for the 1090 ES Ground
Station described in this specification.
The 1090 ES Ground Station shall provide separate, configurable wait periods for
position and velocity reports.
The wait period shall be configurable over a range of at least 0.7 to 6 seconds.
The resolution of the wait period configuration parameter shall be 1 second or less.
Position and velocity wait periods shall be maintained for each target independently of
the wait periods for all other targets.
Wait periods shall commence at the time of receipt of the ES message that triggers an
ASTERIX state vector report.
Position and velocity ES messages received during wait periods shall not trigger
ASTERIX state vector reports.
The first position or velocity ES message received after the expiration of the applicable
wait period shall trigger an ASTERIX state vector report.
ASTERIX state vector reports generated in throttled reporting mode shall be populated
as specified in section 0 for data-driven state vector reports.

© EUROCAE, 2010
 158

APPENDIX F

REFERENCE 1090 ES SIGNAL POWER BUDGET

This Appendix specifies the power budget applicable to the reception of signals
received on a 1090 ES Ground Station.

F.1 1090 ES SYSTEM CHARACTERISTICS

The carrier frequency, modulation, and other characteristics of the Extended Squitter
waveform are defined by the Mode S standards as follows:
Carrier Frequency : 1090 MHz +/- 1 MHz.
Modulation : Pulse position modulation. For each bit period, a pulse is transmitted
either in the first half of the period (indicating a 1) or the second half of the period
(indicating a 0).
Data Rate : 1 Mbps, within a message.
Message Synchronisation : A transmitted message includes a preamble so that a
receiver can detect the beginning of the message and can synchronise on the data in
the message. The preamble consists of 4 pulses.
Message Size : A message consists of 112 bits.
Coding : Each message contains 24 parity bits, which can be used for error detection
or correction. This is the standard Mode S code, which is currently used by
transponders, SSRs, and TCAS.
Message Types and Broadcast Rates : The term “message” is used to refer to
individual Extended Squitters of 112 bits, and the term “report”3 is used to refer to a
block of information generated as an output by the ADS-B receiver for use as an input
to “applications.” These reports typically contain information extracted from multiple
messages depending on the Ground Station reporting mode.
Channel Access: ADS-B messages are transmitted with a pseudo random pattern
that is nominally periodic with a standard rate and the transmission times are deviated
slightly using a pseudo random process. Specifically, a timing jitter uniformly
distributed over a range of +/-100 ms is applied to each transmission. This jitter is
much larger than the duration of each message, so that synchronous interference
effects are avoided.
1090 ES Transmitter Power: The transmitter power levels for transmitted Extended
Squitter signals are specified in the RTCA DO-260 and DO-260A to be the same as
the existing standards for Mode S transponders. Specifically:

Equipment Class4 Transmitter Power5

Class A1, A2, A3, B1 51 to 57 dBm
Class A0, B0, B2, B3 48.5 to 57 dBm

3
This specification assumes ASTERIX Category 021 as the report format.
4
Class A equipment refers to interactive aircraft/vehicles while class B refers to broadcast only systems (aircraft,
vehicles, fixed obstacles).
5
These values refer to the antenna end of the cable between the antenna and the transmitter.

© EUROCAE, 2010
 159

F.2 SIGNAL DYNAMIC RANGE ON GROUND 1090 ES RECEIVER

The power level (in dBm) of the 1090 MHz signal received at the RF input connector
of the 1090 ES receiver is given by the following equation:
Prx_dBm = 10*log(Pout) + Loss_TX + Gtx + Path_Loss + Lat +Grx + Loss_RX
= 10*log(Pout) + Loss_TX + Gtx – 98.543 -20*log( R)
- 0.009*R + Grx + Loss_RX
where
Prx_dBm = Power (in dBm) received at the RF input of the receiver.
Pout = Transmitted Power (in mW) measured at the transponder RF output connector.
R = distance between the transmitting and receiving antennas in nautical miles.
λ = wavelength (m) at 1090 MHz = 300/1090.
Loss_TX = attenuation (in dB) provided by the connection between the transponder
and the transmit antenna. This includes the cable and connectors.
Gtx = gain (in dB) of the transmitting antenna.
Grx = gain (in dB) of the receiving antenna.
Loss_RX = attenuation (in dB) provided by the connection of the receiving antenna
to the receiver. This includes the cable, connectors, and pre-amplifier (if any).
Lat = Loss due to atmospheric attenuation = -0.009*R dB.
Path_Loss = attenuation (in dB) of a 1090 MHz signal in free space for a distance
equal to R, calculated through the formula:
Path_Loss = 10 log (λ / (4 * π * R ))2
Since the transmitted power Pout depends on the transponder class, the signal level
received at the antenna end of the cable between receiver and RX antenna is
between the following:
a. Minimum power
A0 transponder
Prx_dBm = -50.043 + Gtx + Grx - 0.009*R -20*log( R)
A1-A3 transponder
Prx_dBm = -47.543 + Gtx + Grx - 0.009*R -20*log( R)
b. Maximum power
Prx_dBm = -41.543 + Gtx + Grx - 0.009*R -20*log( R)
The antenna gain on the aircraft is assumed to be 0 dB since this specification has
postulated a reference zero gain isotropic ground antenna. Consequently the resulting
received signal strength dynamic ranges (in dBm) will be:

© EUROCAE, 2010
 160

TABLE F-1: RECEIVED SIGNAL STRENGTH

Target Range Maximum Signal Level Minimum Signal Level (dBm)

(NM) (dBm) A1-A3 A0
0.2 -27.6 -33.6 -36.1
10 -61.6 -67.6 -70.1
20 -67.7 -73.7 -76.2
50 -76.0 -82.0 -84.5
100 -82.4 -88.4 -90.9
150 -86.4 -92.4 -94.9
180 -88.3 -94.3 -96.8
200 -89.4 -95.4 -97.9
250 -91.8 -97.8 -100.3
300 -93.8 -99.8 -102.3

FIGURE F-1: DESIRED SIGNAL LEVELS VERSUS TARGET DISTANCE FROM 1090 ES
RECEIVER

-20

Maximum Signal Level

-30
Minimum Signal Level A1-1A3
-40
Minimum Signal Level A0
-50
Signal Level, dBm

-60

-70

-80

-90

-100

-110
0 50 100 150 200 250 300
Range, NM

© EUROCAE, 2010
 161

APPENDIX G

REFERENCE ANTENNA

It is necessary as part of this Technical Specification to specify the minimum RF

performance of the 1090 ES Ground Station receiver, to ensure for example that it can
receive messages adequately from aircraft at the edge of the intended coverage area.
It is preferable to measure this performance using laboratory test equipment, under
conditions that can be controlled experimentally, rather than by employing actual
aircraft flying at long range, under environmental atmospheric and FRUIT conditions
that will be difficult to control. Further it is more convenient, and less expensive in
terms of test equipment, to inject RF test signals directly into the 1090 ES Ground
Station using a 50-ohm cable, rather than transmitting them over free space to the
antenna of the 1090 ES Ground Station.
Power measurements are defined at the "antenna end of the antenna to receiver
transmission line" so that installations with long cables are taken into account, and
pre-amplifiers can be used as part of the overall design.
The antenna forms an important part of the ground system, affecting its performance.
It is recognised that antenna characteristics will vary between manufacturers. It is also
recognised that different types of antenna may be used for different applications, for
example sectaries versus omni-directional antennas.
The performance specifications assume that the 1090 ES Ground Station is installed
with a theoretical Reference Antenna conforming to the minimum specifications
described in section 3.1.2. If the actual antenna to be used differs in characteristics
from the assumed Reference Antenna, then it shall be demonstrated that the overall
performance of the 1090 ES Ground Station with the actual antenna to be used is
equivalent to or better than that of a 1090 ES Ground Station conforming to the
performance specifications in this section, connected to a Reference Antenna. Such a
demonstration is likely to take the form of a theoretical analysis. For example, if the
gain of the actual antenna to be used with the Ground Station is 3 dB higher than the
Reference Antenna, the requirement for the measured MTL of the Ground Station will
also be 3 dB higher.
If an external pre-amplifier is used then this may be counted as part of the antenna for
the purposes of this analysis, if it was not included as part of the 1090 ES Ground
Station when conducting the performance tests in Section 5. This also applies to the
transmission lines connecting the antenna, the pre-amplifier (if used) and the Ground
Station.

© EUROCAE, 2010
 162

APPENDIX H

NRA 1090 MHZ FRUIT LEVELS ASSESSMENT

H.1 BACKGROUND

The EUROCONTROL CASCADE Programme organised a study to assess the 1090

MHz FRUIT levels expected to occur in European non-radar airspaces towards 2015.
Its aim was to determine the worst case interference environments that ADS-B
Ground Stations would have to cope with in these airspaces. This work was done as
an input into the requirements for future ADS-B Ground Stations in ED-129, which
were being developed by EUROCAE Working Group 51 / Subgroup 4.
The outcome of this work was a report [REF31] whose results are summarised in this
Appendix.

H.2 NON-RADAR AIRSPACES (NRA) CASE STUDIES

FRUIT simulations were completed for eight areas of non-radar airspace around
Europe selected on the basis of information from the CRISTAL projects of the
EUROCONTROL CASCADE Programme. The selected NRA areas are shown in
Figure below.

FIGURE H-1: EVALUATED NRAs

© EUROCAE, 2010
 163

H.3 AIR AND GROUND SCENARIOS

Air traffic scenarios were based on present EUROCONTROL Central Flow

Management Unit [CFMU] traffic data extrapolated to 2015 levels using
EUROCONTROL Air Traffic Statistics and Forecasts Service [STATFOR] traffic
growth figures for each area. Ground radar scenarios were created using knowledge
of the present radar infrastructure and national plans for upgrading from Mode A/C to
Mode S.
It was assumed that:
• all civil radars and at least 75% of the military ones will have been upgraded to
Mode S by 2015.
• All aircraft will be equipped with Mode S transponders capable of Extended
Squitter transmission.
• 80% of all aircraft will be TCAS equipped.
• CFMU traffic needs to be augmented by 40% to account for General Aviation,
military flights and aircraft taxiing on the airport surface.
• A single test point location would be sufficient for FRUIT measurement per
NRA. LoS constraints due to earth curvature were accounted for but not terrain
profiles.

H.4 FRUIT MODEL

1090 MHz FRUIT was estimated using a model previously created by Helios
Technology Ltd for EUROCONTROL. This model takes as input a static air traffic
situation and a radar infrastructure scenario and estimates the amount of FRUIT that
would be produced at a given location. The calculated FRUIT includes Mode A/C and
Mode S replies (due to TCAS/ACAS and SSR/Mode S radar interrogations) as well as
Extended Squitters broadcasted for ADS-B purposes.
FRUIT rates were calculated per NRA area for a baseline historic scenario based on
2004-2006 air traffic and radar situation data as well as three scenarios for 2015
(assuming STATFOR predictions for low, medium, and high air traffic growth rates).

H.5 CONCLUSIONS

FRUIT was estimated for each of the eight NRA areas. It was found (see Table H1
below) that Short Squitter (Mode S) FRUIT should become the dominant interference
in these areas towards 2015. This is a consequence of the assumption that most
radars will have been upgraded by 2015 to Elementary Mode S. As the local SSR to
Mode S upgrade programmes advance, Mode A/C FRUIT will progressively decline in
the coming years while SS and ES FRUIT will increase.

© EUROCAE, 2010
 164

TABLE H-1: WORST CASE CUMULATIVE FRUIT RATES AT -92 dBm PER NRA IN 2015
SCENARIO6

Mode A/C
SS FRUIT ES FRUIT
NRA FRUIT
(msg/s) (msg/s)
(msg/s)
Spain, Girona 1299-1489 3216-4104 893-1042
Italy, Sardinia 1425-1516 2032-2268 477-508
Greece, Lamia 2-10 631-910 310-465
Scotland 30-124 185-425 81-130
UK, North Atlantic 16-47 159-272 50-99
Sweden, Kiruna 0 176-237 112-136
Portugal, Madeira 0 28-57 81-130
Portugal, Santa Maria 0 1-3 6-19

Based on the results of Table H-1, at least two NRA categories can be distinguished
with regard to FRUIT rate levels7:
a) “High Interference” NRA areas (e.g. Girona, Sardinia, Greece ) with cumulative:
• SS FRUIT rising towards the range 1- 4 kmsg/s by 2015;
• ES FRUIT rising towards the range 0.5 - 1 kmsg/s by 2015;
• A/C FRUIT in the range 7.5 - 12 kmsg/s today, and dropping to less than
1.5 kmsg/s by 2015.
b) “Low Interference” NRA areas (e.g. Scotland, North Atlantic, Sweden, Madeira
and Santa Maria) with cumulative
• SS FRUIT rising to below 0.5 kmsg/s until 2015;
• ES FRUIT rising to below 0.2 kmsg/s until 2015;
• A/C FRUIT up to 1.5 kmsg/s today, and dropping to less than 0.15
kmsg/s towards 2015.
The highest interference environment was found to be Girona in Spain. In that case a
more realistic estimate of the FRUIT rate profile versus signal level is shown in Figure
H-2 below.

6
Worst case FRUIT levels correspond to transmissions at the maximum power (57 dBm) allowed by the 1090
MOPS. In practice transmission powers would be in the range 49.5 to 57 dBm.
7
FRUIT levels were measured at -92 dBm (assuming 0 dB gain isotropic antenna on the Ground Station) and
maximum transmission power (=57 dBm).

© EUROCAE, 2010
 165

FIGURE H-2: FRUIT RATE VERSUS SIGNAL LEVEL AT GIRONA, SPAIN, 20158

4,500

(Var) Cumulative Mode A/C

4,000
(Var) Cumulative SS

(Var) Cumulative ES
3,500

3,000
FRUIT rate, msg/sec

2,500

2,000

1,500

1,000

500

0
-98 -96 -94 -92 -90 -88 -86 -84 -82 -80 -78 -76 -74 -72
Rx Signal Level, dBm

The desired Extended Squitter signal levels should be in the range -27 to -94 dBm as
explained in [REF31 Appendix B].

8
FRUIT signal levels calculated assuming TX powers in the range 50 to 57 dBm in accordance with 1090 MOPS.

© EUROCAE, 2010
 166

APPENDIX I

ADS-B PERFORMANCE IN NRA 1090 MHZ FRUIT ENVIRONMENT

I.1 INTRODUCTION

This appendix details the analysis into the required ADS-B decoding performance in
the simulated worst case environment as predicted by the EUROCONTROL 1090
MHz NRA Interference Study [REF31], (summarised in APPENDIX H). Girona was
chosen from several European sites that were modelled in the EUROCONTROL study
since the FRUIT rates were predicted to be the highest of any environment in the
study.
This study investigated the probability that an ADS-B signal from an aircraft was
received without being overlapped by an unwanted Mode S transmission.

I.2 REQUIRED SURVEILLANCE PERFORMANCE

I.2.1 En-Route Surveillance

En-route surveillance is defined by ED-126 [REF16] as a service allowing the lateral

separation of aircraft at the same altitude by at least 5 Nautical Miles (NM).
The required aircraft position update interval for en-route surveillance is defined in
ED-126 as a 95% probability of at least one position update every 10 seconds.
There is no universal requirement for the required coverage range at which an aircraft
can be detected with the required performance. For the purposes of this study
performance will be analyzed for aircraft at 150, 180, 200 and 250 NM.

I.2.2 Terminal Surveillance

Terminal surveillance is defined within ED-126 as a service allowing the lateral

separation of aircraft at the same altitude by at least 3 Nautical Miles (NM). In order to
allow closer spacing than the en-route case it follows that a faster position update rate
is required. The required aircraft position update interval for terminal surveillance is
defined in ED-126 as a 95% probability of at least one position update every 5
seconds.
There is no universal requirement for the required coverage range for a terminal
surveillance system either. For the purposes of this study performance will be
analyzed for aircraft at 60 NM.

I.3 ADS-B POSITION UPDATE RATE

ADS-B equipped aircraft transmit two position messages per second. In order to
satisfy the update rate for the terminal surveillance of at least one every five seconds it
follows that at least one in ten of the transmitted position messages must be
successfully received and processed by the Ground Station.
Similarly for the ten-second update rate required for en-route surveillance, it follows
that one in twenty transmitted position messages must be successfully received.

I.4 WANTED SIGNAL AMPLITUDE

When considering the effects of interference on 1090 MHz signal decoding the worst
case scenario occurs when a transponder transmitting the minimum allowed power
level exists at the maximum required range. This situation produces the lowest signal
to FRUIT amplitude ratio.

© EUROCAE, 2010
 167

For most commercial applications the required output power from a transponder is 21
dBW (125 Watts); however aircraft incapable of operating above 15,000ft are
permitted to transmit as little as 18.5 dBW (70 Watts). This lower power class of
transponder is not considered applicable to the en-route scenario, since the low
altitude of such aircraft will prevent them from being detected at maximum range
because they will be below the horizon.

I.4.1 Terminal Airspace Power Budget Calculation

The worst case scenario, i.e. the weakest wanted signal relative to the FRUIT levels in
a terminal environment would be a 70 W transponder at maximum range, which in this
case is 60 NM.
The power budget for the ADS-B aircraft at maximum range (60 NM) is calculated as
follows:
received_power = transmitter_power + system_gains – system_losses
Where:
system_gains = transmitter_antenna_gain + receiver_antenna_gain
and:
system_losses = transmitter_cable_loss + range_loss +
atmospheric_loss + lens_loss + receiver_cable_loss

In the case of the aircraft the ICAO minimum power limit (18.5 dBW or 48.5 dBm) is
specified at the aircraft antenna, so the transmitter cable loss is zero in this case. The
aircraft antenna gain is 0 dB, and the receiver antenna is assumed to be a reference
isotropic antenna, with no cable loss. An elevation angle of +1° is assumed for the
atmospheric and lens loss values [REF32].

Range_loss = 98.550 + 20 log d

= 98.550 + 20 log 60
= 98.550 + 20 * 1.778
= 98.550 + 35.56
= 134.1 dB

The receiver cable loss as stated previously is 0 dB, so the total system loss can be
found:
system_losses = transmitter_cable_loss + range_loss + atmospheric_loss +
lens_loss + receiver_cable_loss
= 0 + 134.1 + 0.5 + 0.1 + 0
= 134.7 dB

The received power at the input to the ADS-B receiver can now be calculated:
received_power = transmitter_power + system_gains – system_losses
= 48.5 + 0 – 134.7
= -86.2 dBm

© EUROCAE, 2010
 168

I.4.2 En-Route Application

The power budget for the ADS-B aircraft at 180 NM is calculated as follows:
received_power = transmitter_power + system_gains – system_losses
Where:
system_gains = transmitter_antenna_gain + receiver_antenna_gain
and:
system_losses = transmitter_cable_loss + range_loss +
atmospheric_loss + lens_loss + receiver_cable_loss

In the case of the aircraft the ICAO minimum power limit (21 dBW or 51 dBm) is
specified at the aircraft antenna, so the transmitter cable loss is zero in this case. The
aircraft antenna gain is 0 dB, and the receiver antenna is assumed to be a reference
isotropic antenna, with no cable loss. An elevation angle of +1° is assumed for the
atmospheric and lens loss values [REF32].

Range_loss = 98.550 + 20 log d

= 98.550 + 20 log 180
= 98.550 + 20 * 2.255
= 98.550 + 45.1
= 143.7 dB

The receiver cable loss as stated previously is 0 dB, so the total system loss can be
found:
system_losses = transmitter_cable_loss + range_loss + atmospheric_loss +
lens_loss + receiver_cable_loss
= 0 + 143.7 + 1.0 + 0.3 + 0
= 145.0 dB

The received power at the input to the ADS-B receiver can now be calculated:
received_power = transmitter_power + system_gains – system_losses
= 51 + 0 – 145
= -94.0 dBm

Since there is no universally accepted figure for the maximum range of an en-route
surveillance system, the power budget calculation was repeated using several
common range values. The results are shown in Table I-1.

© EUROCAE, 2010
 169

TABLE I-1: RECEIVED SIGNAL POWER FOR SEVERAL COMMON RANGE VALUES

Range Range Loss Atmospheric Loss Lens Loss Received

(NM) (dB) (dB) (dB) Power (dBm)
150 142.1 0.9 0.2 -92.2
180 143.7 1.0 0.3 -94.0
200 144.6 1.1 0.3 -95.0
250 146.5 1.1 0.4 -97.0

I.5 FRUIT MODELLING

I.5.1 The EUROCONTROL NRA Study

The rate and amplitude distribution of the Girona FRUIT is detailed in APPENDIX H
[summary of REF31]. Four scenarios were modelled:
• Baseline 2004;
• 2015 with expected FRUIT rates;
• 2015 with lower than expected FRUIT rates;
• 2015 with higher than expected FRUIT rates.
Each scenario modelled three kinds of 1090 MHz transmission; Mode A/C SSR
replies, short Mode S replies including acquisition squitter transmissions, and long
Mode S replies including Extended Squitter transmissions.

I.5.2 ADS-B Interference Model

For this study, in order to calculate the probability that a wanted ADS-B message with
given amplitude would be overlapped (garbled) by another transmission the
environment was simulated using Matlab models. Mode S FRUIT and Mode A/C
FRUIT were modelled separately since they produce different effects when
overlapping a wanted ADS-B signal.

I.5.3 Mode A/C FRUIT

Mode A/C FRUIT comprises replies to Mode A, C, and occasionally Mode 2

interrogations. The replies consist of a pair of framing pulses (denoted F1 and F2)
which are always present with additional code pulses to represent the reply data.
Normally only a few code pulses are used, with the most common reply being 7000
(1200 in the USA) which use five pulses for the entire reply.

FIGURE I-1: MODE A / C / 2 REPLY FORMAT

F1 C1 A1 C2 A2 C4 A4 X B1 D1 B2 D2 B4 D4 F2 SPI

© EUROCAE, 2010
 170

The pulses themselves each represent a single data bit and are 0.45 µs wide and 1.45
µs apart. Mode S messages, of which ADS-B messages are an example, use a
different method of data representation. Each data bit is represented by a 0.5 µs pulse
which occupies either the first or second half of a 1 µs window. A binary one is
represented by the pulse in the first half, and a binary zero by the pulse being in the
second half as illustrated in Figure I-2.

FIGURE I-2: MODE S MODULATION FORMAT

1 µs 1 µs

Binary 1 Binary 0

When a Mode S message is overlapped by a Mode A/C reply, the 0.45 µs pulses of
the Mode A/C reply will corrupt part of the Mode S data sequence. However, as the
Mode S data bits are effectively 1 µs wide, less than half of the Mode S bit is rendered
unreadable. There is therefore a good chance that the ADS-B decoder can still
recognise the data being transmitted, even if the Mode A/C transmission has greater
amplitude. Only when an ADS-B data bit is overlapped by more than one Mode A/C
pulse is it likely that the data bit will become unreadable. Even then, the error
detection / correction process may be able to correct any corrupted data.

I.5.3.1 Mode A/C FRUIT Model

Mode S messages have an inherent resistance to corruption by Mode A/C FRUIT. As

different decoding techniques differ in their susceptibility to FRUIT it is not possible to
state which messages would be successfully decoded or not. For this reason the
Mode A/C FRUIT model simply counts the number of replies expected to occur over
the 120 µs duration of an ADS-B message.
The model took as its input the cumulative Mode A/C FRUIT transmissions per second
calculated as part of the EUROCONTROL study. Random start times between 0 and 1
second were assigned to each one of the replies. A random start time was then
assigned to a single ADS-B message during the same second. The model then
counted the number of Mode A/C replies that started less than 21 µs before or up to
120 µs after the start of the ADS-B message.
In order that the results were statistically significant this process was repeated one
million times each for FRUIT amplitudes between 0 and -135 dBm in 1 dBm steps.
This entire process was performed for each of the four Girona FRUIT scenarios.

I.5.3.2 Mode A/C FRUIT Results

The results of the Mode A/C FRUIT models are shown in Figure I-3 through Figure I-6.

© EUROCAE, 2010
 171

FIGURE I-3: GIRONA BASELINE 2004 SCENARIO RESULTS FOR MODE A/C FRUIT

Average Number of Mode A/C FRUIT Replies Overlapping Each Wanted ADS-B Message
Girona 2004 Baseline Scenario

1.8 14000

1.6
12000
Average number of Overlapping mode AC replies

1.4

Mode A/C FRUIT Replies per Second

10000
1.2

1 8000
AC FRUIT Rate
Overlapping Replies
0.8
6000

0.6
4000

0.4

2000
0.2

0 0
10
08
06
04
02
00

8
6
4
2
0
8
6
4
2
0
8
6
4
2
0
8
6
4
2
0
-9
-9
-9
-9
-9
-8
-8
-8
-8
-8
-7
-7
-7
-7
-7
-6
-6
-6
-6
-6
-1
-1
-1
-1
-1
-1

Wanted Signal Amplitude (dBm)

FIGURE I-4: GIRONA BASELINE 2015 SCENARIO RESULTS FOR MODE A/C FRUIT

Average Number of Mode A/C FRUIT Replies Overlapping Each Wanted ADS-B Message
Girona 2015 Baseline Scenario

0.25 1600

1400
Average number of Overlapping mode AC replies

0.2
Mode A/C FRUIT Replies per Second

1200

1000
0.15

AC FRUIT Rate
800
Overlapping Replies

0.1
600

400
0.05

200

0 0
02
00

8
6
4
2
0
8
6
4
2
0

2
8
6
4
2
0
8
6
4

0
10
08
06
04

-9
-9
-9
-9
-9
-8
-8
-8
-8
-8
-7
-7
-7
-7
-7
-6
-6
-6
-6
-6
-1
-1
-1
-1
-1
-1

Wanted Signal Amplitude (dBm)

© EUROCAE, 2010
 172

FIGURE I-5: GIRONA LOW LEVEL 2015 SCENARIO RESULTS FOR MODE A/C FRUIT

Average Number of Mode A/C FRUIT Replies Overlapping Each Wanted ADS-B Message
Girona 2015 Low Scenario

0.25 1600

1400
Average number of Overlapping mode AC replies

0.2

Mode A/C FRUIT Replies per Second

1200

1000
0.15

AC FRUIT Rate
800
Overlapping Replies

0.1
600

400
0.05

200

0 0
10
08
06
04
02
00

8
6
4
2
0
8
6
4
2
0
8
6
4
2
0
8
6
4
2
0
-9
-9
-9
-9
-9
-8
-8
-8
-8
-8
-7
-7
-7
-7
-7
-6
-6
-6
-6
-6
-1
-1
-1
-1
-1
-1

Wanted Signal Amplitude (dBm)

FIGURE I-6: GIRONA HIGH LEVEL 2015 SCENARIO RESULTS FOR MODE A/C FRUIT

Average Number of Mode A/C FRUIT Replies Overlapping Each Wanted ADS-B Message
Girona 2015 High Scenario

0.25 1600

1400
Average number of Overlapping mode AC replies

0.2
Mode A/C FRUIT Replies per Second

1200

1000
0.15

AC FRUIT Rate
800
Overlapping Replies

0.1
600

400
0.05

200

0 0
10
08
06
04
02
00

8
6
4
2
0
8
6
4
2
0
8
6
4
2
0
8
6
4
2
0
-9
-9
-9
-9
-9
-8
-8
-8
-8
-8
-7
-7
-7
-7
-7
-6
-6
-6
-6
-6
-1
-1
-1
-1
-1
-1

Wanted Signal Amplitude (dBm)

© EUROCAE, 2010
 173

I.5.4 Mode S FRUIT

In terms of overlapping messages Mode S FRUIT is significantly more destructive

than Mode A/C FRUIT. It is highly unlikely that any Mode S message will be
successfully decoded if overlapped by another Mode S message of similar amplitude.
For this reason the Mode S FRUIT model simply evaluated whether a message was
overlapped or not, rather than counting the number of overlapping messages as was
modelled for the Mode A/C FRUIT.

I.5.4.1 Mode S FRUIT Model

The Mode S FRUIT model also used the FRUIT characteristics data from the
EUROCONTROL study [REF31] as its input. Each FRUIT transmission and the
wanted ADS-B message were assigned a random start time. The ADS-B message
was deemed to have been overlapped by a long Mode S message if any one of the
messages started less than 120 µs before or less than 120 µs after the ADS-B
message. Similarly, an overlap with a short Mode S transmission was deemed to have
occurred if any one of the short transmissions started less than 64 µs before or less
than 120 µs after the start of the ADS-B message.
As with the Mode A/C FRUIT model this process was repeated one million times each
for FRUIT amplitudes between 0 and -135 dBm in 1 dBm steps. This entire process
was performed for each of the four Girona FRUIT scenarios.

I.5.4.2 Mode S FRUIT Results

The results of the four Mode S FRUIT models are shown in Figure I-7 through
Figure I-10.

FIGURE I-7: GIRONA BASELINE 2004 SCENARIO RESULTS FOR MODE S FRUIT

Probability that an Extended Squitter Message is Received with No Overlapping FRUIT

Girona 2004 Baseline

1 4500

0.9 4000

0.8
3500

0.7
FRUIT Replies per Second

3000
Probability of no overlap

0.6
2500 Short S
0.5 Long S
2000 P(no overlap
0.4

1500
0.3

1000
0.2

0.1 500

0 0
10

08

06

04

02
00

0
-9

-9

-9

-9

-9

-8

-8

-8

-8

-8

-7

-7

-7

-7

-7

-6

-6

-6

-6

-6
-1

-1

-1

-1

-1
-1

Wanted Signal Amplitude (dBm)

© EUROCAE, 2010
 174

FIGURE I-8: GIRONA 2015 SCENARIO RESULTS FOR BASELINE MODE S FRUIT

Probability that an Extended Squitter Message is Received with No Overlapping FRUIT

Girona 2015 Baseline

1 4500

0.9 4000

0.8
3500

0.7

FRUIT Replies per Second

3000
Probability of no overlap

0.6
2500 Short S
0.5 Long S
2000 P(no overlap
0.4

1500
0.3

1000
0.2

0.1 500

0 0
6

0
02

00

6
4

8
10

08

06

04

-7

-6

-6

-6

-6

-6
-9

-9

-9

-9

-9

-8

-8
-8

-8

-8

-7

-7

-7

-7
-1

-1

-1
-1

-1

-1

Wanted Signal Amplitude (dBm)

FIGURE I-9: GIRONA 2015 SCENARIO RESULTS FOR LOW FRUIT LEVEL

Probability that an Extended Squitter Message is Received with No Overlapping FRUIT

Girona 2015 Low Scenario

1 4500

0.9 4000

0.8
3500

0.7
FRUIT Replies per Second

3000
Probability of no overlap

0.6
2500 Short S
0.5 Long S
2000 P(no overlap
0.4

1500
0.3

1000
0.2

0.1 500

0 0
10

08

06

04

02
00

0
2

0
8

2
8

6
4

-6
-8

-7

-7

-7

-7

-7

-6

-6

-6

-6
-9

-9

-9

-9

-9

-8

-8

-8

-8
-1

-1

-1

-1

-1

-1

Wanted Signal Amplitude (dBm)

© EUROCAE, 2010
 175

FIGURE I-10: GIRONA 2015 SCENARIO RESULTS FOR HIGH FRUIT LEVEL

Probability that an Extended Squitter Message is Received with No Overlapping FRUIT

Girona 2015 High Scenario

1 4500

0.9 4000

0.8
3500

0.7

FRUIT Replies per Second

3000
Probability of no overlap

0.6
2500 Short S
0.5 Long S
2000 P(no overlap
0.4

1500
0.3

1000
0.2

0.1 500

0 0
8
6

2
10
08

06

04

02
00

8
6
4

2
0

2
0
8

6
4

0
-9
-9

-9

-9

-9
-8

-8
-8
-8

-8

-7

-7

-7
-7

-7
-6
-6

-6

-6

-6
-1

-1

-1

-1

-1
-1

Wanted Signal Amplitude (dBm)

I.6 CONCLUSIONS

The predicted worst case FRUIT environment is unlikely to prevent ADS-B receivers
from meeting the required target update rate.
The modelling results indicate that even the weakest received ADS-B signals have a
greater than 1-in-3 chance of not being overlapped by any FRUIT signals at all.
Whilst more advanced decoding techniques will inevitably produce a higher update
rate than basic decoders, even the most basic decoder will be able to meet the
performance requirements for NRA.
There are no Ground Station decoding performance requirements resulting from this
study, since sufficient numbers of ADS-B messages will be received with no garbling.

© EUROCAE, 2010
 176

APPENDIX J

DME INTERFERENCE EFFECTS

J.1 INTRODUCTION

This appendix presents the results of a study into the effects of Distance Measuring
Equipment (DME) signal interference on ground-based ADS-B receiving equipment. It
is not the intent of this study to present a set of hard-and-fast rules for siting 1090 ES
Ground Stations, but to examine the effects that must be considered when choosing a
site near a DME Ground Station.

J.2 CHARACTERISTICS OF DME SIGNALS AND SYSTEMS

J.2.1 Principle of Operation

DME is a navigational radio system that allows an aircraft to measure its range from a
radio beacon. The principle of DME is that an aircraft transmits a pair of pulses that
are received by the ground equipment and re-transmitted back to the aircraft on a
different frequency. The distance to the ground equipment is found by measuring the
round trip time of the signals.

J.2.2 Modulation Scheme

Unlike SSR, DME does not use a single pair of frequencies. Each ground-based
transponder has its own assigned air-to-ground and ground-to-air channels. The
frequency range defined for DME is 962 to 1167 MHz, and most are paired with VHF
navigational radio frequencies, such that a VOR beacon on a given frequency will
have a co-located DME on a known frequency.
The transmitted pulses are Gaussian in shape with a pulse width of 3.5 µs (measured
at the 50% power points). An example of a (modelled) DME pulse is shown in Figure
J-1.

FIGURE J-1: STANDARD DME PULSE SHAPE (LINEAR AMPLITUDE SCALE)

© EUROCAE, 2010
 177

J.2.3 Frequency Allocation

Table J-1 shows the DME channels with ground-to-air frequencies within 30 MHz of
1090 MHz. Each DME channel is paired with a VHF navaid frequency, so that when a
pilot tunes to a VHF navaid the DME system can automatically tune to the same
beacon. Although frequencies between 1088 MHz and 1092 MHz are defined as
ground-to-air channels, they are not paired with VHF channels and are not used.
Table J-2 shows a list of DME channels whose air-to-ground frequencies are within 30
MHz of 1090 MHz.

TABLE J-1: LIST OF DME CHANNELS WITH GROUND-TO-AIR FREQUENCIES WITHIN 30 MHz
OF 1090 MHz

G to A Typical
Paired Air to Ground to
DME difference attenuation in
VHF freq Ground Air freq
Channel from 1090 receivers filter
(MHz) freq (MHz) (MHz)
(MHz) (dB)
126 Y 117.95 1150 1087 3 0
125 Y 117.85 1149 1086 4 1
124 Y 117.75 1148 1085 5 3
123 Y 117.65 1147 1084 6 7
122 Y 117.55 1146 1083 7 12
121 Y 117.45 1145 1082 8 16
120 Y 117.35 1144 1081 9 22
119 Y 117.25 1143 1080 10 25
118 Y 117.15 1142 1079 11 29
117 Y 117.05 1141 1078 12 31
116 Y 116.95 1140 1077 13 35
115 Y 116.85 1139 1076 14 39
17 Y 108.05 1041 1104 14 39
114 Y 116.75 1138 1075 15 41
18 Y 108.15 1042 1105 15 41
113 Y 116.65 1137 1074 16 43
19 Y 108.25 1043 1106 16 43
112 Y 116.55 1136 1073 17 47
20 Y 108.35 1044 1107 17 47
111 Y 116.45 1135 1072 18 49
21 Y 108.45 1045 1108 18 49
110 Y 116.35 1134 1071 19 52
22 Y 108.55 1046 1109 19 52
109 Y 116.25 1133 1070 20 54
23 Y 108.65 1047 1110 20 54
108 Y 116.15 1132 1069 21 55
24 Y 108.75 1048 1111 21 55
107 Y 116.05 1131 1068 22 57
25 Y 108.85 1049 1112 22 57
106 Y 115.95 1130 1067 23 60

© EUROCAE, 2010
 178

G to A Typical
Paired Air to Ground to
DME difference attenuation in
VHF freq Ground Air freq
Channel from 1090 receivers filter
(MHz) freq (MHz) (MHz)
(MHz) (dB)
26 Y 108.95 1050 1113 23 60
105 Y 115.85 1129 1066 24 62
27 Y 109.05 1051 1114 24 62
104 Y 115.75 1128 1065 25 64
28 Y 109.15 1052 1115 25 64
103 Y 115.65 1127 1064 26 65
29 Y 109.25 1053 1116 26 65
102 Y 115.55 1126 1063 27 67
30 Y 109.35 1054 1117 27 67
101 Y 115.45 1125 1062 28 69
31 Y 109.45 1055 1118 28 69
100 Y 115.35 1124 1061 29 72
32 Y 109.55 1056 1119 29 72
33 Y 109.65 1057 1120 30 74
99 Y 115.25 1123 1060 30 74

TABLE J-2: LIST OF DME CHANNELS WITH AIR-TO-GROUND FREQUENCIES WITHIN 30 MHz
OF 1090 MHz

G to A Typical
Paired Air to Ground to
DME difference attenuation in
VHF freq Ground Air freq
Channel from 1090 receivers filter
(MHz) freq (MHz) (MHz)
(MHz) (dB)
70 X 112.3 1094 1157 4 1
70 Y 112.35 1094 1031 4 1
71 X 112.4 1095 1158 5 3
71 Y 112.45 1095 1032 5 3
72 X 112.5 1096 1159 6 7
72 Y 112.55 1096 1033 6 7
59 X 112.2 1083 1020 7 12
59 Y 112.25 1083 1146 7 12
73 X 112.6 1097 1160 7 12
73 Y 112.65 1097 1034 7 12
58 X 112.1 1082 1019 8 16
58 Y 112.15 1082 1145 8 16
74 X 112.7 1098 1161 8 16
74 Y 112.75 1098 1035 8 16
57 X 112 1081 1018 9 22
57 Y 112.05 1081 1144 9 22
75 X 112.8 1099 1162 9 22

© EUROCAE, 2010
 179

G to A Typical
Paired Air to Ground to
DME difference attenuation in
VHF freq Ground Air freq
Channel from 1090 receivers filter
(MHz) freq (MHz) (MHz)
(MHz) (dB)
75 Y 112.85 1099 1036 9 22
56 X 111.9 1080 1017 10 25
56 Y 111.95 1080 1143 10 25
76 X 112.9 1100 1163 10 25
76 Y 112.95 1100 1037 10 25
55 X 111.8 1079 1016 11 29
55 Y 111.85 1079 1142 11 29
77 X 113 1101 1164 11 29
77 Y 113.05 1101 1038 11 29
54 X 111.7 1078 1015 12 31
54 Y 111.75 1078 1141 12 31
78 X 113.1 1102 1165 12 31
78 Y 113.15 1102 1039 12 31
53 X 111.6 1077 1014 13 35
53 Y 111.65 1077 1140 13 35
79 X 113.2 1103 1166 13 35
79 Y 113.25 1103 1040 13 35
52 X 111.5 1076 1013 14 39
52 Y 111.55 1076 1139 14 39
80 X 113.3 1104 1167 14 39
80 Y 113.35 1104 1041 14 39
51 X 111.4 1075 1012 15 41
51 Y 111.45 1075 1138 15 41
81 X 113.4 1105 1168 15 41
81 Y 113.45 1105 1042 15 41
50 X 111.3 1074 1011 16 43
50 Y 111.35 1074 1137 16 43
82 X 113.5 1106 1169 16 43
82 Y 113.55 1106 1043 16 43
49 X 111.2 1073 1010 17 47
49 Y 111.25 1073 1136 17 47
83 X 113.6 1107 1170 17 47
83 Y 113.65 1107 1044 17 47
48 X 111.1 1072 1009 18 49
48 Y 111.15 1072 1135 18 49
84 X 113.7 1108 1171 18 49
84 Y 113.75 1108 1045 18 49
47 X 111 1071 1008 19 52
47 Y 111.05 1071 1134 19 52

© EUROCAE, 2010
 180

G to A Typical
Paired Air to Ground to
DME difference attenuation in
VHF freq Ground Air freq
Channel from 1090 receivers filter
(MHz) freq (MHz) (MHz)
(MHz) (dB)
85 X 113.8 1109 1172 19 52
85 Y 113.85 1109 1046 19 52
46 X 110.9 1070 1007 20 54
46 Y 110.95 1070 1133 20 54
86 X 113.9 1110 1173 20 54
86 Y 113.95 1110 1047 20 54
45 X 110.8 1069 1006 21 55
45 Y 110.85 1069 1132 21 55
87 X 114 1111 1174 21 55
87 Y 114.05 1111 1048 21 55
44 X 110.7 1068 1005 22 57
44 Y 110.75 1068 1131 22 57
88 X 114.1 1112 1175 22 57
88 Y 114.15 1112 1049 22 57
43 X 110.6 1067 1004 23 60
43 Y 110.65 1067 1130 23 60
89 X 114.2 1113 1176 23 60
89 Y 114.25 1113 1050 23 60
42 X 110.5 1066 1003 24 62
42 Y 110.55 1066 1129 24 62
90 X 114.3 1114 1177 24 62
90 Y 114.35 1114 1051 24 62
41 X 110.4 1065 1002 25 64
41 Y 110.45 1065 1128 25 64
91 X 114.4 1115 1178 25 64
91 Y 114.45 1115 1052 25 64
40 X 110.3 1064 1001 26 65
40 Y 110.35 1064 1127 26 65
92 X 114.5 1116 1179 26 65
92 Y 114.55 1116 1053 26 65
39 X 110.2 1063 1000 27 67
39 Y 110.25 1063 1126 27 67
93 X 114.6 1117 1180 27 67
93 Y 114.65 1117 1054 27 67
38 X 110.1 1062 999 28 69
38 Y 110.15 1062 1125 28 69
94 X 114.7 1118 1181 28 69
94 Y 114.75 1118 1055 28 69
37 X 110 1061 998 29 72

© EUROCAE, 2010
 181

G to A Typical
Paired Air to Ground to
DME difference attenuation in
VHF freq Ground Air freq
Channel from 1090 receivers filter
(MHz) freq (MHz) (MHz)
(MHz) (dB)
37 Y 110.05 1061 1124 29 72
95 X 114.8 1119 1182 29 72
95 Y 114.85 1119 1056 29 72
36 X 109.9 1060 997 30 74
36 Y 109.95 1060 1123 30 74
96 X 114.9 1120 1183 30 74
96 Y 114.95 1120 1057 30 74

J.2.4 DME Transponder Antenna Pattern

DME transponders, like SSR transponders, may be interrogated from any direction
and will transmit an omnidirectional reply. A typical DME antenna, the dB Systems
inc. 5100A, comprises an end-fed stacked dipole array and is shown in Figure J-2.

FIGURE J-2: A TYPICAL DME ANTENNA (dB SYSTEMS INC. TYPE 5100A)

The required vertical antenna pattern is similar in shape to the vertical pattern of a
ground-based SSR interrogator antenna. Most of the gain is concentrated just above
the horizon, since it is at these low elevation angles that the most distant aircraft are to
be found. As is the case with SSR antennas there is an intentionally steep reduction in
gain below the horizon, since RF energy transmitted towards the ground is not only
wasteful, it can also lead to gaps in coverage caused by multipath nulls.
The vertical gain profile for the 5100A antenna is shown in Figure J-3.

© EUROCAE, 2010
 182

FIGURE J-3: DME ANTENNA VERTICAL GAIN PROFILE (dB SYSTEMS INC. TYPE 5100A)

dBs 5100A Vertical Pattern, 1090 MHz, Typical

10

-5

-10

-15

-20
-90 -80 -70 -60 -50 -40 -30 -20 -10 0 10 20 30 40 50 60 70 80 90
Vertical Angle (Deg)

J.2.5 DME Transponder Transmitted Power Levels

DME transponders normally exist in either en-route or terminal configuration. The en-
route systems have a nominal transmitter power of one kilowatt and are intended to be
usable by aircraft at ranges of over two hundred miles. Terminal systems on the other
hand are usually paired with a short range navaids such as ILS installations. It is
common to install a single DME transponder equidistant between the glide slope
transmitters with a negative range correction to make the measured range correct
relative to the glide slope transmitters. This configuration allows the same transponder
to be used regardless of the active runway direction.

J.2.6 DME Transmission Rates

Airborne DME interrogators transmit pulse pairs at two distinct rates, according to
whether they are operating in the search or track mode. In the search mode the
aircraft is attempting to identify DME transponders on the ground and transmits at a
rate of 124 pulse pairs per second. Once the transponder has been acquired the
interrogator enters the track mode, in which the interrogation rate falls to an average
of 22 pulse pairs per second.

J.3 CHARACTERISTICS OF 1090 MHZ RECEIVERS

Receivers in SSR or ADS-B systems naturally have their greatest sensitivity at 1090
MHz with a 3 dB bandwidth of around 8 MHz. The precise frequency response
requirement is defined in DO-260A [section 2.2.4.3.2 of REF21], and is repeated in
Table J-3. It is assumed in this study that all ADS-B receivers meet this mandatory
requirement.

© EUROCAE, 2010
 183

TABLE J-3: REQUIRED ADS-B RECEIVER FREQUENCY RESPONSE

Frequency Difference Triggering Level

(MHz from 1090 MHz) (dB above MTL)
± 5.5 >= 3 dB
± 10 >= 20 dB
± 15 >= 40 dB
± 25 >= 60 dB

Many DME channels are sufficiently close to 1090 MHz for some of the RF energy to
pass through the receiver’s filter, and hence the DME pulses will be visible in the
baseband output. The amplitude of these pulses will depend on the received signal
strength and the frequency difference from 1090 MHz.
A DME signal source and a typical 1090 MHz receiver were modelled using Matlab.
The noise floor of the receiver is approximately -94 dBm, and the frequency response
below 1090 MHz is shown in Figure J-4.

FIGURE J-4: FREQUENCY RESPONSE OF MODELLED ADS-B RECEIVER (HALF SHOWN)

© EUROCAE, 2010
 184

Figure J-5 shows the modelled output of the receiver for two DME pulses at 1090
MHz. The Y scale shows the baseband output amplitude calibrated to show the
received signal power on a logarithmic scale. It can be seen that the input pulses have
peak amplitude of -70 dBm, and the logarithmic amplifier in the receiver has changed
the apparent pulse shape.

FIGURE J-5: PAIR OF 1090 MHz DME PULSES AS DETECTED IN AN ADS-B RECEIVER

Figure J-6 shows similar pulses, as were modelled in Figure J-5, but this time the
DME frequency has been changed to 1085 MHz. The amplitude of these pulses is
also -70 dBm, but they are attenuated by 3 dB due to the receiver’s filter.

FIGURE J-6: PAIR OF 1085 MHz DME PULSES AS DETECTED IN AN ADS-B RECEIVER

© EUROCAE, 2010
 185

J.4 EFFECTS OF DME PULSES ON 1090 MHZ RECEPTION

Two series of simulated tests were performed using the Matlab model. The timing of
the DME pulses was identical to that shown inFigure J-5 and Figure J-6.

J.4.1 Effects of DME Pulse Amplitude on ADS-B Reception

The amplitude test had a 1090 MHz ADS-B transmission at fixed amplitude (-70 dBm)
overlapped by DME pulses of fixed frequency and steadily increasing amplitude. The
amplitude of the DME pulses was varied from 14 dB below the ADS-B signal to 5 dB
above it. The resulting effects on the received 1090 MHz signals are shown in Figure
J-7 through Figure J-26. Only the first 38 µs of the ADS-B transmission is shown in
order to illustrate the effects on individual pulses.
In a general study such as this it is not possible to state the amplitude level at which
the ADS-B message becomes unreadable, since ADS-B decoding algorithms vary
widely in their ability to decode garbled signals.

FIGURE J-7: -84 dBM

FIGURE J-8: -83 dBM

© EUROCAE, 2010
 186

FIGURE J-9: -82 dBM

FIGURE J-10: -81 dBM

FIGURE J-11: -80 dBM

© EUROCAE, 2010
 187

FIGURE J-12: -79 dBM

FIGURE J-13: -78 dBM

FIGURE J-14: -77 dBM

© EUROCAE, 2010
 188

FIGURE J-15: -76 dBM

FIGURE J-16: -75 dBM

FIGURE J-17: -74 dBM

© EUROCAE, 2010
 189

FIGURE J-18: -73 dBM

FIGURE J-19: -72 dBM

FIGURE J-20: -71 dBM

© EUROCAE, 2010
 190

FIGURE J-21: -70 dBM

FIGURE J-22: -69 dBM

FIGURE J-23: -68 dBM

© EUROCAE, 2010
 191

FIGURE J-24: -67 dBM

FIGURE J-25: -66 dBM

FIGURE J-26: -65 dBM

If the DME pulse were the only source of interference, the message would probably be
correctable in most decoders whilst the DME pulse amplitude was at least 3 dB below
that of the ADS-B signal. Above this level the signal amplitude between the pulses (i.e.
when no pulse is being transmitted) becomes closer to the reference amplitude than
the level of the real pulses. In this case the decoded message will contain errors,
although some decoders may be able to correct them. Messages that are garbled by
both DME pulses would almost certainly not be decoded correctly.

© EUROCAE, 2010
 192

J.4.2 Effects of DME Pulse Frequency on ADS-B Reception

The frequency test had an ADS-B transmission at fixed frequency and amplitude (-70
dBm at 1090 MHz) overlapped by DME pulses of fixed amplitude and increasing
frequency. The frequency of the DME pulses was varied from 1065 MHz to 1090 MHz.
The resulting effects on the received 1090 MHz signals are shown in Figure J-27
through Figure J-35.

FIGURE J-27: 1075 MHz, 42 dB FILTER ATTENUATION; DME PULSES ARE NOT DETECTABLE
IN THE RECEIVER

FIGURE J-28: 1080 MHz, 25 dB FILTER ATTENUATION

FIGURE J-29: 1081 MHz, 22 dB FILTER ATTENUATION

© EUROCAE, 2010
 193

FIGURE J-30: 1082 MHz, 16 dB FILTER ATTENUATION

FIGURE J-31: 1083 MHz, 12 dB FILTER ATTENUATION

FIGURE J-32: 1084 MHz, 7 dB FILTER ATTENUATION

© EUROCAE, 2010
 194

FIGURE J-33: 1085 MHz, 3 dB FILTER ATTENUATION

FIGURE J-34: 1086 MHz, 1 dB FILTER ATTENUATION

FIGURE J-35: 1087 MHz, 0 dB FILTER ATTENUATION

It can be seen from these results that the closer the DME frequency gets to 1090 MHz
the higher the received DME amplitude appears. There is also a visible beat effect on
the pulse tops that is particularly visible in Figure J-31 and Figure J-32.
From this simulation it appears that the decoded message would be decoded correctly
whilst the effective amplitude of the DME signal remains at least 3 dB below the
wanted signal amplitude. For the -65 dBm DME signal in this simulation (which was 5
dB stronger then the ADS-B signal) it was necessary for the DME frequency to be at
least 7 MHz away from 1090 for the message to be decoded without errors. Again,
some decoders may be able to correct the errors if there were few other garbled
pulses in the message.

© EUROCAE, 2010
 195

J.5 RECEIVED DME SIGNAL AMPLITUDES

J.5.1 Power Budget Calculation

The received amplitude is given by the following formula, where all gains and losses
are specified in dB units:
received_power = transmitter_power + system_gains – system_losses
Where:
system_gains = transmitter_antenna_gain + receiver_antenna_gain
and:
system_losses = transmitter_cable_loss + range_loss + atmospheric_loss +
lens_loss + receiver_cable_loss
In the case of an en-route DME the transmitted power is 1 kW, and for a terminal DME
it is 100 W (10 dB less). Typical cable losses of 1 dB have been used for both the
transmitter and receiver, and due to the short range the atmospheric absorption and
lens losses are negligible as shown in [REF32].
From [REF32], the range loss is given as:
Range_loss = 98.550 + 20 log d
where d is the distance between antennas in nautical miles.
The resulting received signal amplitude will be in the same units as was used for the
transmitter_power value (i.e. if 30 dBW was used the result is in dBW, if 60 dBm was
used the result is in dBm).

J.5.2 Effects of Range and Relative Elevation on DME Signal Amplitude

Using the above power budget, calculations were performed of the received DME
signal amplitude at the 1090 MHz receiver for various range and elevation values.
For the antenna gains the values, which vary with elevation angle, have been taken
from the dB Systems Inc. 5100A antenna pattern plot in Figure J-3. It is of no
significance which antenna is the higher, since a positive elevation angle for one of the
antennas results in an equal and opposite negative elevation angle for the other
antenna as shown in Figure J-36.

FIGURE J-36: RELATIVE POSITIONS OF DME AND ADS-B ANTENNAS

© EUROCAE, 2010
 196

The link power budget between DME and ADS-B antennas was calculated for range
values between 10 meters and 4000 meters. At each range elevation angles from -20°
to +20° were used. The resulting values were displayed as contour plots with the
received signal amplitude indicated by colour. The plot for the en-route DME
transponder is shown in Figure J-37, and the equivalent plot for the terminal
transponder is shown in Figure J-38.
It can be seen in these plots that relative elevation angle has a significant effect on the
received signal strength.

FIGURE J-37: RECEIVED DME SIGNAL AMPLITUDE FOR AN EN-ROUTE DME TRANSPONDER

Unsurprisingly, the terminal case gives exactly the same pattern but the signal
amplitudes are 10 dB less.

FIGURE J-38: RECEIVED DME SIGNAL AMPLITUDE FOR A TERMINAL TRANSPONDER

© EUROCAE, 2010
 197

J.6 EXPECTED ADS-B SIGNAL AMPLITUDES

The final report of the CASCADE 1090 MHz Capacity Study [REF31] gives the
example of a spatial distribution of aircraft reproduced in Figure J-39.

FIGURE J-39: ASSUMED AIRCRAFT DISTRIBUTION WITH RANGE FROM A GROUND

RECEIVER

In Figure J-39 the number of aircraft increases steadily with range until the peak value
between 140 and 150NM, after which an increasing proportion of aircraft fall below the
horizon. At the maximum range only the highest aircraft are detectable, resulting in
very few of the weakest signals being observed.
The CASCADE 1090 MHz Capacity Study [REF31] also gives an example of the
expected distribution of amplitude, but that analysis used assumed a higher gain
antenna than the standard DME type used here.
The expected amplitude distribution has therefore been recalculated and is shown in
Figure J-40. The modal amplitude in this case is -81 dBm.

© EUROCAE, 2010
 198

FIGURE J-40: PROBABILITY OF A SIGNAL AT THE ADS-B RECEIVER HAVING A SPECIFIC

AMPLITUDE

J.7 AN EXAMPLE CALCULATION

J.7.1 The Scenario

An airport owner wishes to install an ADS-B receiver to provide terminal surveillance

covering a radius of 40 nautical miles around the airport. The airport already has an
ILS operating on 116.85 MHz with co-located 100 W terminal DME, and several local
sites are under consideration.
One such site is located on a hill 2 kilometres away from the centre of the airfield
where the DME is located, with an unobstructed line of sight. The airport already owns
a communications tower on the hill and an analysis must be performed to determine
whether the airport DME would interfere with the ADS-B receiver if that site were
chosen. The elevation of the communications tower is 175 meters above the DME on
the airfield.
The following example illustrates how such an analysis would be performed.
To begin with some basic assumptions are made:
• A worst-case ICAO compliant transponder (51 dBm) must be detected at
maximum range.
• The DME feeder cable loss is 1 dB.
• The ADS-B receiver cable loss is 1 dB.
• Both the DME and the ADS-B antennas will have equivalent performance to
that shown in Figure J-3.
• A 3 dB link margin is desired for the long range aircraft.

© EUROCAE, 2010
 199

J.7.2 The DME Received Power Calculation

The relative elevation angle is calculated as shown in Figure J-41.

FIGURE J-41: ELEVATION ANGLE CALCULATION

175m
a
2000m

The elevation angle a is calculated by:

tan a = 175 / 2000
= 0.875
∴a = arctan 0.875
= 5°

The slant range is found by Pythagoras. In this case it is 2008 meters, or 1.084 NM.
The power budget for the DME is then calculated:
received_power = transmitter_power + system_gains – system_losses
Where:
system_gains = transmitter_antenna_gain + receiver_antenna_gain
and:
system_losses = transmitter_cable_loss + range_loss + atmospheric_loss +
lens_loss + receiver_cable_loss
The transmitter power is 100 W (50 dBm)
In this case the transmitter and receiver antenna gains can be found from the vertical
pattern plot in Figure J-3. The transmitter antenna gain at +5° is 9 dB and the receiver
antenna gain at -5° is -5 dB. The total system gain is therefore 4 dB.
The range loss can now be calculated
Range_loss = 98.550 + 20 log d
= 98.550 + 20 log 1.084
= 98.550 + 20 * 0.035
= 98.550 + 0.700
= 99.250 dB

The total system losses can now be found:

system_losses = 1 + 99.25 + 0 + 0 +1
= 101.25 dB
The received power at the input to the ADS-B receiver can now be calculated:
received_power = transmitter_power + system_gains – system_losses
= 50 + 4 – 101.25
= -47.25 dBm

© EUROCAE, 2010
 200

This value agrees with the contour plot shown in Figure J-38.
To calculate the DME signal power detected by the receiver we need to calculate the
attenuation caused by the 1090 MHz band pass filter. The ILS used a frequency of
116.85 MHz, which can be found from Table J-1 to be paired with DME channel 115Y.
This DME channel has a ground-to-air frequency of 1076 MHz, which from the graph
in Figure J-4 would be attenuated by 39 dB.
The total DME power observed by the receiver is found
observed_power = power_at_receiver_input – bandpass_filter_loss
= -47.25 – 39
= -86.25 dBm

J.7.3 The ADS-B Power Budget Calculation

The power budget for the ADS-B aircraft at maximum range (40 NM) is then
calculated:
received_power = transmitter_power + system_gains – system_losses
Where:
system_gains = transmitter_antenna_gain + receiver_antenna_gain
and:
system_losses = transmitter_cable_loss + range_loss + atmospheric_loss +
lens_loss + receiver_cable_loss
In the case of the aircraft the ICAO minimum power limit (51 dBm) is specified at the
aircraft antenna, so the transmitter cable loss is zero in this case. The aircraft antenna
gain is 0 dB, and from [1] we can assume that the minimum practical elevation angle
is 0.25°, which from Figure J-3 gives a receiver antenna gain of 7 dB. The system gain
total is therefore 7 dB.
An additional 2 km (1.08 NM) must be added to the maximum range since the receiver
is now not at the airport, which gives a new required range of 41.08 nautical miles.
Range_loss = 98.550 + 20 log d
= 98.550 + 20 log 41.08
= 98.550 + 20 * 1.614
= 98.550 + 32.04
= 130.8 dB

The receiver cable loss as stated previously is 1 dB, so the total system loss can be
found:
system_losses = transmitter_cable_loss + range_loss + atmospheric_loss +
lens_loss + receiver_cable_loss
= 0 + 130.6 + 0 + 0 + 1
= 131.8 dB

The received power at the input to the ADS-B receiver can now be calculated:
received_power = transmitter_power + system_gains – system_losses
= 51 + 7 – 131.8
= -73.8 dBm

© EUROCAE, 2010
 201

It is good practice to allow a link margin, and in this case a value of 3 dB is used. We
should therefore assume that the minimum power received from a minimum spec
transponder at 41 miles is -76.8 dBm.

J.7.4 The Analysis Result

The power budget calculations showed that the minimum signal amplitude allowing for
the 3 dB link margin is -76.8 dBm, and the effective DME signal power is -86.25 dBm.
The ADS-B signal is therefore 9.45 dB stronger than the DME interference, and Figure
J-12 shows that for a relative amplitude of -9 dB the ADS-B message should be
decoded without errors.
It is therefore concluded that the site on the hill would be suitable for the ADS-B
receiver.

J.8 CONCLUSIONS

1. The received amplitude of ground-to-air DME transmissions will depend on the

frequency, power, and location of the DME Ground Station relative to the ADS-
B receiver. The amplitude of these DME signals will be constant.
2. From the simulation results it is concluded that most decoders would be able to
successfully decode ADS-B messages where the effective amplitude of the
DME signal is at least 3 dB below that of the ADS-B signal, providing no other
interference exists.
3. The precise amplitude at which ADS-B Ground Stations will fail to decode
received messages correctly is a function of the capability of the decoding
algorithm.
4. Interference to ADS-B systems from ground-based DME transponders will be
evident in a reduction in probability of detection beyond a certain range. This
range will depend on the altitude of the aircraft, and will correspond to an
amplitude level of 3 dB above the received DME amplitude.
5. If the effective received DME amplitude at the ADS-B receiver is -95 dBm or
less, there will be no noticeable effect on the ADS-B performance at all.
6. It is not possible to control the effects of airborne DME transmissions, since the
ADS-B antenna has to be placed where there is good coverage of the required
surveillance volume.

J.9 RECOMMENDATIONS

In the rare event that a DME frequency for a ground transponder can be chosen, it is
advisable to choose a channel that has ground-to-air and air-to-ground frequencies as
far from 1090 MHz as possible.
When considering possible sites for an ADS-B Ground Station near a DME
transponder, the following steps should be taken for each candidate site:
• Determine the ground-to-air and air-to-ground frequencies of the DME
transponder, together with the transmitted power level.
• Perform a power budget calculation based on range and elevation angle
between the two antennas (such as the example shown in Figure J-37) taking
into account the vertical pattern of each antenna.
• Refer to a frequency response chart (such as the example shown in Figure J-4)
to estimate the additional attenuation provided by the filter in the ADS-B
receiver.
• The filter attenuation value, when subtracted from the power budget result, will
indicate the effective DME signal amplitude in the receiver.
• If possible choose a location that will provide an effective received amplitude of
-95 dBm or less.

© EUROCAE, 2010
 202

APPENDIX K

SOFTWARE ASSURANCE LEVEL (SWAL) REQUIREMENTS

K.1 SUMMARY

This paper uses a method based on severity and likelihood to determine the
appropriate Software Assurance Level (SWAL) for a 1090ES Ground Station
supporting NRA services in line with ED-126. The assessment is based on a ‘typical’
ground system, incorporating functionality as described in ED-126. Means for
detecting loss of target, e.g. a coasting function as described in ED-126 Annex D, is
assumed to be independent from or external to the Ground Station functionality. In the
event that the target system differs from the typical ground system (e.g. additional
functionality is included in the Ground Station), a complementing SWAL assessment is
necessary. This analysis shows that SWAL 3 (AL4) is required for a 1090 ES Ground
Station supporting NRA services as defined in ED-126.

K.2 INTRODUCTION

This paper briefly introduces the SWAL analysis method as described in the Safety
Assessment Methodology (SAM) guidance material Software Assurance Level. It
applies the method and makes assumptions on a typical ground system as described
in ED-126. Finally it concludes on the appropriate SWAL for the 1090 ES Ground
Station.
SWAL is based upon the contribution of software to potential consequences of its
anomalous behaviour as determined by the system safety assessment process. The
assignment of a Software Assurance Level does not imply calculating a failure rate for
that software. Software assurance levels or software reliability rates based on
software assurance levels cannot be used by the system safety assessment process
as can hardware failure rates.

K.3 REFERENCES

Air Navigation System Safety Assessment Methodology, SAF.ET1.ST03.1000-MAN-

01, Edition 2.1, 2006
Software Assurance Level, SAF.ET1.ST03.1000-GUI-01-02
Safety, Performance and Interoperability Requirements Document for ADS-B NRA
Application, ED-126, 2006
Draft Technical Specification for a 1090 MHz Extended Squitter ADS-B Ground
Station, ED-129
Guidelines for Communication, Navigation, Surveillance and Air Traffic Management
(CNS/ATM) Systems Software Integrity Assurance, ED-109, 2002

K.4 OBJECTIVE

Identify the appropriate software assurance level (SWAL) for an ED-126 compliant
1090 ES Ground Station.

K.5 METHOD

The method used in this document to identify the appropriate SWAL is based on the
Software Assurance Level guidance material, provided in the ANS Safety Assessment
Methodology.
The Software Assurance Level guidance material recommends to identify the
appropriate SWAL using a method based on the probability that a software failure
causes a certain effect (Ph x Pe), as described in Figure K-1.

© EUROCAE, 2010
 203

FIGURE K-1: DETERMINATION OF THE LIKELIHOOD OF A SOFTWARE FAILURE LEADING TO

AN EFFECT

SWAL

“Pivotal”
HAZARD
Event S Effect1

S
Effect2
F
S Effect3

Ph Pe F
SW Effect4
F
FTA ETA
Causes Consequences

15

The approach can be summarised in three steps:

1. Identify the likelihood (Pe x Ph) that, once software fails, this software failure
can generate an end effect which has a certain severity (do that for each effect
of a hazard);
2. Identify the SWAL for that couple (severity, likelihood) using the matrix in Table
K-1;
3. This has to be done for all the hazards due to the software.
NOTE: This has to be done for all effects only if Methods 1 & 3 of setting Safety
Objectives is used. If Methods 2 & 4 are used then only the worst credible
effect will be taken into consideration. (See SAM-FHA Chapter 3 Guidance
Material G “Methods for setting Safety Objectives).

TABLE K-1: SWAL BASED ON SEVERITY AND LIKELIHOOD

EFFECT SEV
1 2 3 4
Probability (Ph x Pe)
Very possible SWAL1 SWAL2 SWAL3 SWAL4
Possible SWAL2 SWAL3 SWAL3 SWAL4
Very Unlikely SWAL3 SWAL3 SWAL4 SWAL4
Extremely Unlikely SWAL4 SWAL4 SWAL4 SWAL4

© EUROCAE, 2010
 204

Where the probabilities are described as follows:

• Very Possible: This effect will certainly occur due to software failure.
• Possible: This effect may happen due to software failure.
• Very Unlikely: It is not expected to have such an effect due to software failure
more than exceptionally and in some specific circumstances throughout the
system lifetime.
• Extremely Unlikely: Such an effect is not expected to happen due to software
failure throughout the system lifetime.

K.6 ANALYSIS

The method described above has been used in this analysis, assessing severity and
likelihood for the worst credible effect of software components failure in the 1090 ES
Ground Station. The identification of software components that are included in the
Ground Station functionality has been based on ED-126, and draft Ground Station
specification. The assessment addressed relevant components that are able to cause
the hazards as identified in ED-126. Some examples of failures that may be caused by
a software component failure leading to the hazards are listed below, for a complete
list refer to ED-126:
• Corruption of ADS-B quality indicator (GND-E03, GND-10)
• Corruption of position information (GND-E8, GND-E01)
• Loss of target (GND-L03)
ASSUMPTION: Software components that have been assumed independent of the
Ground Station functionality are software components supporting the functions listed
below:
• Detection of loss of target function, e.g. a coasting function (IM1-F01)
Determination of probability for a software component failure propagating to an effect
was done by first identifying basic causes corresponding to Ground Station software
functionality. Then, assuming a failure of this component, the probability of this failure
to be able to propagate to the effect was assessed by analyzing the fault trees and
event trees for the specific failure. The result of this analysis is shown in Table K-2,
where the column ‘SW prob causing OH (Ph)’ corresponds to the combined
mitigations identified in the fault tree preventing the software failure from propagating
to a hazard and the column ‘Probability (Pe)’ corresponds to the combined
effectiveness of the barriers identified to prevent the propagation of the hazard to the
effect. The column ‘Ph x Pe’ is the combined effect of the fault tree barriers (also
known as internal mitigation means) and the event three barriers (also known as
external mitigation means).
Based on this, each failure could be assessed for the worst credible effect (severity)
and then combined with the likelihood of the failure to lead to the effect, as shown in
Table K-2. The appropriate SWAL corresponds to the most stringent level in the
SWAL column. The overview is seen when studying the three columns ‘Severity’, ‘Ph
x Pe’ and ‘SWAL’.

© EUROCAE, 2010
 205

TABLE K-2: SWAL DETERMINATION BASED ON SEVERITY

NRA
OH Severity SW prob causing OH (Ph) Probability (Pe) Ph x Pe SWAL
OH1d 4 1,00E+00 5,00E-01 5,00E-01 4
OH1u 1 1,00E-05 1,00E-01 1,00E-06 3
OH2d 3 1,00E+00 1,00E-01 1,00E-01 3
OH3d1 3 1,00E+00 1,00E+00 1,00E+00 3
OH3u1 1 1,00E+00 1,00E-07 1,00E-07 4
OH3d2 3 1,00E+00 1,00E-01 1,00E-01 3
OH3u2 1 2,50E-04 5,00E-03 1,25E-06 3
OH3d3 3 1,00E+00 1,00E+00 1,00E+00 3
OH3u3 1 1,00E-05 5,00E-03 5,00E-08 4
OH4d1 4 1,00E+00 1,00E+00 1,00E+00 4
OH4u1 1 1,00E+00 1,00E-07 1,00E-07 4
OH4d2 4 1,00E+00 1,00E+00 1,00E+00 4
OH4u2 1 2,50E-04 5,00E-03 1,25E-06 3
OH4d3 4 1,00E+00 1,00E+00 1,00E+00 4
OH4u3 1 1,00E-04 5,00E-03 5,00E-07 3

NOTE: A grey field in the Ph column indicates that detailed fault tree analysis has
not been carried out to determine the Ph for the failure to propagate,
instead the probability has been set to 1.
ASSUMPTION: To be able to interpret the subjective likelihood as defined in the ANS
SAM guidance material, and restated in the method section, a quantitative
measurement of the likelihood was assumed, as shown in Table K-3.

TABLE K-3: ASSUMED PROBABILITIES FOR THE LIKELIHOOD A FAILURE TO PROPAGATE

TO THE EFFECT

Very Possible
Possible < 1,00E-03
Very Unlikely < 1,00E-05
Extremely unlikely < 1,00E-07

K.7 CONCLUSION

Determination of the appropriate SWAL for a specific system component is dependent

on the total system design. This analysis has focused on a typical (minimal) ground
system design, as used for the ED-126 analysis in conjunction with the in this
document stated assumptions. In the event that the target system differs from the
typical ground system or the stated assumptions a complementing assessment is
necessary. For example if critical functions for detection of loss of target have
common software causes as those causing loss of target, a higher SWAL may be
needed.
This analysis shows that SWAL 3 (AL4) is required for a 1090 ES Ground Station
supporting NRA services as defined in ED-126.

© EUROCAE, 2010
 206

APPENDIX L

ED-129 TRACEABILITY MATRIX TO ED-126 REQUIREMENTS

L.1 INTRODUCTION

This specification (ED-129) defines the minimum technical specification for a 1090
MHz Extended Squitter ADS-B Ground Station used to provide surveillance data for
air traffic control in Non Radar Airspaces (ADS-B-NRA application) in accordance with
the minimum operational, safety, and performance requirements (SPR-*) and
interoperability requirements (IR-*) stated in ED-126.
This Appendix provides a matrix indicating the coverage of the ED-126 and SPR and
INTEROP requirements in ED-129. It is noted that ED-126 allocates the set of
minimum SPR and INTEROP requirements at aircraft and ground domain level. The
1090 ES Ground Station is considered part of the ground domain level.
The traceability matrix refers only to the ASTERIX Category 021 output of the 1090
ES Ground Station as it is the only mandatory one.

L.2 ED-126 SAFETY AND PERFORMANCE REQUIREMENTS

Id ED-126 Requirement ED-129 Provision9
SPR-1 to
Airborne segment requirements N/A
SPR-12
The likelihood that the ADS-B receive subsystem corrupts ADS-B
SPR-13 information through the reception, processing or delivery of data Sec. 3.6 and APPENDIX K
(E2) shall be no more than 5e-6 per ATSU hour
The likelihood that ADS-B Receive subsystem does not provide
updated ADS-B surveillance reports for more than one aircraft
SPR-14 Sec. 3.5
from which ADS-B messages are being received shall be no
more than 5e-6 per ATSU hour
The likelihood that the ADS-B receive subsystem does not
provide updated ADS-B surveillance reports for one aircraft from
SPR-15 Sec. 3.5 and 3.6
which ADS-B messages are being received shall be no more
than 1e-04 per ATSU-hour.
The 95% latency for ADS-B Surveillance Reports (measured
SPR-16 Sec. 3.4
between points D and E2) shall be no greater than 0.5s
The time of applicability conveyed in the ADS-B Surveillance
SPR-17 Report shall have an absolute accuracy relative to UTC of +/- 0.2 Sec. 3.7.1
seconds or less.
Each type of ADS-B Surveillance Report (i.e. containing position,
Table Table 5 and Sec.
SPR-18 identity and/or Emergency/SPI data) shall contain a time of
3.10.4.8
applicability (Interface E2).
The update interval (as defined in ED-126 section 3.2) for
Surveillance Reports containing any new ADS-B Position data
SPR-19 Sec. 3.2.2 and 3.10.2.1.3
associated with any single aircraft shall be no longer than 10s
with a probability of 95% for 5 NM en route separation
Additional surveillance requirements for 5 NM en route separation
SPR-20 N/A
are subject to local implementation

9
N/A indicates airborne domain requirements with no impact on the ADS-B ground station. Such requirements
may still have an impact on downstream ground systems, for example ED-126 SPR-1 on position accuracy
should affect a surveillance tracking system.

© EUROCAE, 2010
 207

Id ED-126 Requirement ED-129 Provision9

The update interval (as defined in ED-126 section 3.2) for
Surveillance Reports containing any new aircraft identification Sec. 3.10.3.4 and Table
SPR-21
associated with any single aircraft shall be no longer than 100s Table 11
with a probability of 95% for 5 NM en route separation
The time to alert for a change in Surveillance Emergency/SPI
Sec. 3.10.2.3.1, 3.10.3.4
SPR-22 Reports measured at point E2 shall be no longer than 10s for
and 3.10.4.30
En-route with a probability of 95% for 5 NM en route separation
The update interval (as defined in section 3.2) for Surveillance
Reports containing any new ADS-B Position data associated
SPR-23 Sec. 3.2.2 and 3.10.2.1.3
with any single aircraft shall be less than 5s with a probability of
95% for 3NM terminal separation
Additional surveillance requirements for 3NM terminal separation
SPR-24 N/A
are subject to local implementation
The update interval (as defined in section 3.2) for Surveillance
Reports containing only ADS-B Identity data associated with any
SPR-25 Sec. 3.10.3.4 and Table 11
single aircraft shall be less than 100s with a probability of 95% for
3NM terminal separation
The time to alert for a change in surveillance Emergency/SPI
Sec. 3.10.2.3.1, 3.10.3.4
SPR-26 reports measured at point E2 shall be no longer than 5s for 3NM
and 3.10.4.30
terminal separation

L.3 ED-126 INTEROPERABILITY REQUIREMENTS

Id ED-126 Requirement ED-129 Provision9
The Transmit Aircraft Domain shall provide ADS-B messages Reception and reporting of all
containing at least the elements which enable the ground system to ED-126 mandatory elements is
IR-1
format the required ADS-B Surveillance reports for the ADS-B-NRA supported, see Table Table 5
application and Table 6
Unique Mode S address
The Transmit Aircraft Domain shall provide in each ADS-B
IR-2 expected per target, see Sec.
message a unique identification of the flight and/or aircraft
3.10.4.6 and Table 5
The ADS-B Receive Subsystem shall provide a time field in each
IR-3 ADS-B Surveillance report, which is translatable to the time of Table 5Table
applicability of the data contained in the report
For ADS-B Surveillance reports containing position information, the
IR-4 report shall also contain the time of applicability of that position Table Table 5
data
Mandatory requirement for
The Transmit Aircraft Domain shall provide the 24 bit aircraft
IR-5 reception, Sec. 3.10.4.6 and
address within each ADS-B message
Table 5
The Transmit Aircraft Domain shall provide an ADS-B message Information received and
IR-6
containing the aircraft identification reported per Sec.3.10.4.29
As per ICAO Doc. 4444, PANS/ATM the following definitions shall
be applied by the Transmit Aircraft Domain:
(Chapter 1, Definitions) Aircraft Identification is ‘A group of letters,
figures or a combination thereof which is either identical to, or the
coded equivalent of, the aircraft call sign to be used in air-ground
communications, and which is used to identify the aircraft in
ground-ground air traffic services communications’,
Information received and
IR-7 (Appendix 2, 2.2) one of the following aircraft identifications, not reported per Sec. 3.10.4.29.
exceeding 7 characters:
o the registration marking of the aircraft, or
o the ICAO designator for the aircraft operating agency followed
by the flight identification when in radiotelephony the call sign to be
used by the aircraft will consist of the ICAO telephony designator
for the operating agency followed by the flight identification

© EUROCAE, 2010
 208

Id ED-126 Requirement ED-129 Provision9

The Transmit Aircraft Domain shall transmit horizontal position Information received and
IR-8 information (i.e. latitude, longitude) consistent with the associated reported per Sec. 3.10.4.17
quality indicator and 3.10.4.16.
The Transmit Aircraft Domain and the ADS-B Receive Subsystem
IR-9 shall reference all geometric position elements to the WGS-84 Sec. 3.10.4.17
ellipsoid
The Transmit Aircraft Domain shall transmit barometric altitude Information received and
IR-10
whenever it is available reported per Sec. 3.10.4.21
The Transmit Aircraft Domain shall formulate altitude
IR-11 measurements as barometric altitude relative to a standard Sec. 3.10.4.21
pressure of 1013.25 hectopascals (29.92in Hg)
The ADS-B Receive Subsystem shall distinctly mark in the
Surveillance Report containing altitude/height whether this
IR-12 information is derived from a barometric or geometric source. This Sec. 3.10.4.20 and 3.10.4.21
will allow the end user to distinguish between the different
parameter indicators
The Ground Domain shall interpret barometric altitude as altitude
IR-13 relative to a standard pressure of 1013.25 hectopascals (29.92in Sec. 3.10.4.21
Hg)
The Transmit Aircraft Domain shall provide the appropriate Information received and
IR-14
indication of quality for the position information reported per Sec. 3.10.4.16
The indicators used shall be either NUCp as specified in DO-242 or
IR-15 Sec. 3.10.4.16
NIC, NACP and SIL as specified in DO-242A
When NUCp is used, the aircraft installation and design shall
IR-16 Sec. 3.10.4.16
provide HPL to the ADS-B transmit function
When HPL and HFOM are provided, the ADS-B transmit function
IR-17 Sec. 3.10.4.16
shall base quality indicators on HPL
A distinction between NUCP and NIC/NACP/SIL airborne
IR-18 implementations shall be provided by the Transmit Aircraft Domain Sec. 3.10.4.16
(e.g. a link-specific defined version number)
The Transmit Aircraft Domain shall transmit an indicator when the
IR-19 pilot has selected an emergency mode or if otherwise determined Sec. 3.10.4.30
to exist within the Aircraft Domain
The Transmit Aircraft Domain shall transmit the appropriate
discrete indicator(s) whenever the capability for the pilot to select
special purpose codes is available in the airborne system as
IR-20 Sec. 3.10.4.30
defined in the Emergency procedures of ICAO Amendment 77,
Annex 10, VOL IV, § 2.1.4.2 and 2.1.4.3 (Mode A code 7500, 7600,
or 7700)
The Transmit Aircraft Domain shall transmit the Emergency
IR-21 Sec. 3.10.4.30
indicator(s) for as long as the emergency mode is selected
When the aircraft system provides this functionality, the Transmit
IR-22 Aircraft Domain shall send an indicator when the special position Sec. 3.10.4.30
identification (SPI) is set
When provided by the Transmit Aircraft Domain, the Ground
IR-23 Domain shall use the SPI information provided in ADS Surveillance Sec. 3.10.4.30
reports to indicate the state to the end user (controller)
When required for a particular implementation of ADS-B-NRA, the
Transmit Aircraft Domain shall transmit both velocity and its Table 6 and Sec. 3.10.4.28 and
IR-24
associated quality indicator (i.e. NUCR or NACV as specified in DO- 3.10.4.16.
242 and DO-242A, respectively)
The Transmit Aircraft Domain and the ADS-B Receive Subsystem
IR-25 Sec. 3.10.4.28
shall reference all velocity elements to the WGS-84 ellipsoid

© EUROCAE, 2010
 209

L.4 ED-126 INTEROPERABILITY RECOMMENDATIONS

Id ED-126 Requirement ED-129 Provision9

When the ADS-B message definitions permit and when the
information is available in the airborne system, the Transmit Aircraft Information optionally received
IRec-1
Domain should transmit an ADS-B message containing the Mode A and reported per Sec. 3.10.4.7.
code
The Transmit Aircraft Domain should be capable of manually
IRec-2 N/A
deselecting barometric altitude
Gilham altitude encoders should not be used by aircraft
IRec-3 N/A
implementations
As opposed to a single quality parameter, the ADS-B Transmit
IRec-4 function should send accuracy and integrity as independent items Sec. 3.10.4.16
(as defined per DO-242A)
When the data source is GPS, then use of DO-208 RAIM
calculations to determine HPL is acceptable as a minimum.
IRec-5 However, NUCp/NIC values should be determined using HPL N/A
values based on DO-229C RAIM methodology or equivalent when
feasible
The NACP values should be determined using the HFOM value of a
IRec-6 Sec. 3.10.4.16
DO-208 or a DO-229C GNSS receiver or equivalent
IRec-7 Avionics providers should implement distinct Emergency indicators Sec. 3.10.4.30

L.5 ED-126 1090 SPECIFIC INTEROPERABILITY REQUIREMENTS

Id ED-126 Requirement ED-129 Provision9

Broadcast Message Characteristics: Data formats and control
H.1.1 parameters that shall be used for communications using Mode S Sec. 3.10
specific services on 1090 MHz media
Minimum set of surveillance parameters required for NRA
H.1.2 Table Table 5
application
Minimum set of parameters that shall be provided to support the
H.1.3.1 Table 5
NRA application
Recommendation: The following parameters should be
H.1.3.2 Table 6
transmitted to support ADS-B-NRA
Recommendation: The following parameter should be
H.1.3.3 Sec. 3.10.4.7
transmitted to support ADS-B-NRA in airspace that requires it
When the flight identification (ICAO designation of operating
H.1.4.1.1 Sec. 3.10.4.29
agency + flight identification) is available, it shall be transmitted
Recommendation: When the flight identification is not available,
H.1.4.1.2 Sec. 3.10.4.29
the aircraft registration should be transmitted
The aircraft shall encode the flight identification (flight
identification or aircraft registration) in BDS 0.8 as defined in
H.1.4.1.3 Sec. 3.10.4.29
ICAO Annex 10, Amendment 79, VOL III, Appendix to chapter 5,
table 2-8
Characters used for flight identification or aircraft registration
H.1.4.1.4 shall be encoded as defined in ICAO Annex 10, Amendment 77, Sec. 3.10.4.29
VOL IV, § 3.1.2.9
The transmission rate of the Aircraft identification shall be as
H.1.4.1.5 Table 11
defined in DO-260/ED-102 or DO-260A, § 2.2.3.3.2.4
The Mode A code shall be encoded in BDS type 23, subtype 7,
H.1.4.2.1 Sec. 3.10.4.7
as defined in DO-260A, § 2.2.3.2.7.3
The transmission rate of the Mode A code shall be as defined in
H.1.4.2.2 Table 11
DO-260A, § 2.2.3.3.1.4.4

© EUROCAE, 2010
 210

Id ED-126 Requirement ED-129 Provision9

A special position identification shall be transmitted when the
crew presses the IDENT button on ATC control panel, as defined
H.1.4.3.1 Sec. 3.10.4.30
in SPI procedures of ICAO Annex 10, Amendment 77, VOL IV, §
3.1.1.6.3
The activation of the SPI shall change the encoding of the
surveillance status field in the airborne position message (BDS
H.1.4.3.2 Sec. 3.10.4.30
0.5), as defined in ICAO Amendment 79, VOL III, appendix to
chapter 5, § 2.3.2.6, and table 2-5
The SPI transmission rate shall be as defined in DO-260/ED-102
H.1.4.3.3 Table Table 11
or DO-260A §2.2.3.3.2.2
The surveillance status field shall indicate the special
Sec. 3.10.4.30 and Table
H.1.4.3.4 identification during a period between 15 to 30 seconds, as
Table 11.
defined in ICAO Annex 10, Amendment 77, VOL IV, § 3.1.1.7.13
Airborne position shall be encoded as per ICAO, Annex 10,
H.1.4.4.1 Sec. 3.10.4.17
Amendment 79, VOL III, Appendix to chapter 5, § 2.3.2
H.1.4.4.2 Airborne position shall be referenced to WGS-84 Sec. 3.10.4.17
The transmission rate of airborne position shall be as defined in
H.1.4.4.3 Sec. 3.10.1
DO-260/ED-102 or DO-260A §2.2.3.3.2.2
For implementations following DO-260/ ICAO Annex 10 VOL III,
the Quality of information data is called NUCp and is encoded in
H.1.4.5.1 Sec. 3.10.4.16
the Type code of the DF17/18 messages (see ICAO Annex 10,
Amendment 79, VOL III, Appendix to chapter 5, §2.3.1)
When NUCp is used, the aircraft installation and design shall
H.1.4.5.2 N/A
provide HPL to the ADS-B transmit function
For implementations following DO-260A, the Quality of
H.1.4.5.3 Sec. 3.10.4.16
information data shall be determined from NIC, NACP & SIL
H.1.4.5.4 NIC & SIL shall be encoded as defined in DO260A §2.2.3.2.3.1.1 Sec. 3.10.4.16
H.1.4.5.5 NAC shall be encoded as defined in DO-260A §2.2.3.2.7.2.7 Sec. 3.10.4.16
The aircraft shall send an indicator when it is in emergency mode
H.1.4.6.1.1 Sec. 3.10.4.30
in BDS 0.5
Selection of code 7500, 7600 or 7700 on ATC control panel shall
H.1.4.6.1.2 N/A
change the encoding of surveillance status
The transmission rate of emergency indicators shall be defined
H.1.4.6.2 Sec. 3.10.4.30
as in DO-260 and DO-260A
Recommendation: Specific emergency type should be
H.1.4.6.3.1 Sec. 3.10.4.30
transmitted in BDS 6.1 subtype 1
The specific emergency indicator shall be encoded as defined in
H.1.4.6.3.2 ICAO Annex 10 Amendment 79, VOL III, Appendix to chapter 5, Sec. 3.10.4.30
§ 2.3.8, and table 2-97
The transmission rate of BDS 6.1 shall be as defined in DO-260A
H.1.4.6.3.3 Sec. 3.10.4.30
§2.2.3.3.2.6.3
Barometric altitude shall be encoded as per ICAO Annex 10,
H.1.4.7.1 Sec. 3.10.4.21
Amendment 79, VOL III, § 2.3.2.4
The transmission rate for barometric altitude shall be as defined
H.1.4.7.2 Sec. 3.10.4.21
in DO-260/ED-102 or DO-260A §2.2.3.3.2.2
When provided, the Geometric height difference from barometric
H.1.4.8.1 altitude shall be encoded as per ICAO Annex 10, Amendment 79, Sec. 3.10.4.20
VOL III, Appendix to chapter 5, § 2.3.5.7
When provided, the transmission rate for geometric height
H1.4.8.2 difference from barometric altitude shall be as defined in DO-260 Sec. 3.10.4.20
or DO-260A § 2.2.3.3.2.5
Ground velocity shall be encoded as per ICAO, Annex 10,
Amendment 79, VOL III, Appendix to chapter 5, § 2.3.5, subtype
H.1.4.9.1 1 and 2 Sec. 3.10.4.28

© EUROCAE, 2010
 211

Id ED-126 Requirement ED-129 Provision9

The transmission rate for ground velocity shall be as defined in
H.1.4.9.2 Sec. 3.10.4.28
DO-260/ED-102 or DO-260A §2.2.3.3.2.5
For implementations following DO-260/ ICAO Annex 10 VOL III,
the Quality of information data is called NUCR and shall be
H.1.4.10.1 Sec. 3.10.4.16
encoded as per ICAO Annex 10, Amendment 79, VOL III,
Appendix to ch. 5, Table 2-9a
For implementations following DO-260A, the Quality of
information is called NACV and shall be encoded as defined in
H.1.4.10.2 Sec. 3.10.4.16
DO260A §2.2.3.2.6.1.5 for Subtype 1 and §2.2.3.2.6.2.5 for
Subtype 2
The indication that the installation is compliant with DO-260A
H.1.4.11.1 shall be provided in the field “version number” in BDS 6.5, as Sec. 3.10.1.2
defined in DO-260A §A.1.4.10.5
The transmission rate for BDS 6.5 shall be as defined in DO-
H.1.4.11.2 Sec. 3.10.1.2
260A §A.1.4.10.1
The ADS-B Receive Subsystem shall use the value of version
number field in BDS 6.5 to distinguish a DO-260/Annex 10 Am.
H.1.4.11.3 Sec. 3.10.1.2
79 VOL III, Appendix to chapter 5 from a DO-260A compliant
installation

© EUROCAE, 2010
 212

APPENDIX M

ASTERIX CATEGORY 021 EDITION 0.23

M.1 INTRODUCTION

For compatibility with existing equipment, the 1090 ES Ground Station may optionally
support ASTERIX Category 021 Edition 0.23 output. This appendix highlights the
differences from Edition 1.4 (detailed in section M.3) and provides guidelines for
generating the reports.

M.2 DATA ITEM INCLUSION

M.2.1 POSITION REPORTS

It is recommended that each State Vector report should contain at least the minimum
data set shown in Table M-1A.
Reports for targets with duplicate addresses should contain the data items specified in
Table M-1A except for I021/170 Target Identification.
The 1090 ES Ground Station may additionally include in periodic reports the optional
ASTERIX Category 021 Edition 0.23 items shown in Table M-1B (provided that they
are configurable).
In the case of targets with duplicate addresses, items or sub-fields should be included
in the report only if the Ground Station is able to associate the data they contain
unambiguously with the target whose position is transmitted in the ASTERIX Category
021 message.

TABLE M-1A: ASTERIX CATEGORY 021 EDITION 0.23 PERIODIC OR DATA DRIVEN POSITION
REPORT: MINIMUM ITEMS

Item Content Notes

I021/010 Data Source 1090 ES Ground Station SIC and 1090 ES GS configuration
Identification SAC
I021/030 Time of Day Time of Applicability of the reported Latest Position squitter [note 1]
position
I021/040 Target Report Type and characteristics of data Per the provisions in section
Descriptor transmitted M.4.4
I021/080 Target Address Target identifier 24 bit ICAO address
I021/090 Figure of Merit ADS Figure of Merit (FOM) Per the provisions in section
provided by the aircraft avionics M.4.6
I021/130 WGS-84 Position Position in WGS-84 Co-ordinates. Latest Position squitter and
previous track information [note 1]
I021/145 Flight Level Flight Level from barometric Latest Position squitter [note 2]
measurements, not QNH corrected
I021/170 Target Target (aircraft or vehicle) Latest Identification squitter. This
Identification identification in 8 characters (if field is not included in the report
available) when no Identification squitter has
been received [note 2]
I021/200 Target Status Status of the target Latest Position, Target State, and
Aircraft Status squitters
I021/210 Link Technology Link Technology used Link Technology Type = 2 for
Indicator 1090 ES

© EUROCAE, 2010
 213

NOTE:
1. State Vector report should not be transmitted if no new position
squitter has been received since the previous State Vector report.
2. This item should be included only if it contains new information
received in an extended squitter message since the previous State
Vector report. If the value of newly received information is equal to
the value conveyed in the last State Vector Report, the information is
still considered “new” and reported.

TABLE M-1B: ASTERIX CATEGORY 021 EDITION 0.23 PERIODIC OR DATA DRIVEN POSITION
REPORT: OPTIONAL ITEMS

Item Content Notes

I021/020 Emitter Category Characteristics of the originating Latest identification squitter
ADS-B unit
I021/095 Velocity Accuracy Velocity uncertainty category of the Latest velocity squitter [note 1]
least accurate velocity component
I021/140 Geometric Minimum altitude from a plane Latest Position squitter [note 1]
Altitude tangent to the earth’s ellipsoid,
defined by WGS-84
I021/146 Intermediate The short-term vertical intent as Latest Target State squitter
State Selected Altitude described by either the FMS selected [note 1]
altitude, the Altitude Control Panel
Selected Altitude, or the current
aircraft altitude according to the
aircraft's mode of flight
I021/150 Air Speed Calculated Air Speed Latest Velocity Squitter [note 1]
I021/151 True Air Speed True Air Speed Latest Velocity Squitter [note 1]
I021/152 Magnetic Heading Magnetic Heading Latest Velocity Squitter [note 1]
I021/155 Barometric Barometric Vertical Rate Latest Velocity Squitter [note 1]
Vertical Rate
I021/157 Geometric Geometric Vertical Rate Latest Velocity Squitter [note 1]
Vertical Rate
I021/160 Ground Vector Ground Speed and Track Angle Latest Velocity Squitter [note 1]

NOTE: This information should be included only if it represents new information

since the previous State Vector report.

M.2.2 DATA DRIVEN VELOCITY REPORTS

Data driven velocity reports are issued on the reception of a new velocity squitter
provided at least one position report has been transmitted for the target since its last
track (re)initialisation.
These reports should contain at a minimum the items listed in Table M-2.
Data driven velocity reports may also contain any of the optional items listed in Table
M-1B for which new information has been received since the previous state vector
(position or velocity) report.
Data-driven velocity reports should not be issued for targets with duplicate addresses.

© EUROCAE, 2010
 214

TABLE M-2: ASTERIX CATEGORY 021 EDITION 0.23 DATA DRIVEN VELOCITY REPORT:
MINIMUM ITEMS

Item Content Notes

I021/010 Data Source 1090 ES Ground Station SIC and Set by 1090 GS configuration
Identification SAC
I021/030 Time of Day Time of applicability of the reported Time of message reception of the
velocity velocity squitter
I021/040 Target Report Type and characteristics of data Per the provisions in section M.4.4
Descriptor transmitted
I021/080 Target Address Target identifier 24 bit ICAO address specified in
the velocity squitter
I021/095 Velocity Velocity uncertainty category Equal to the Navigation
Accuracy encoded per the NACV provisions in Uncertainty Category (NUCR) or
DO-242A, section 2.1.2.14 and Navigation Accuracy Category for
Appendix R Velocity (NACV as reported in the
velocity squitter
I021/150 Airspeed Target velocity as reported in the Reporting of airspeeds may be
OR squitter disabled as a Ground Station
configuration option
I021/151 True Airspeed
OR
I021/160 Ground Vector
I021/170 Target Target (aircraft or vehicle) Latest received Identification
Identification identification in 8 characters (if squitter
available)
I021/200 Target Status Status of the target Per the provisions of section
M.4.19
I021/210 Link Technology Link Technology used Link Technology Type = 2 for
1090 ES

© EUROCAE, 2010
 215

M.3 DIFFERENCES BEWTEEN EDITION 0.23 AND EDITION 1.4

TABLE M-3: CHANGES FROM ASTERIX CATEGORY 021 EDITION 0.23 TO 1.4

ASTERIX Category 021 Edition ASTERIX Category 021 Edition 1.4 Changes from Edition
0.23 0.23 to 1.4
I021/008 Aircraft Operational New
Status
I021/010 Data Source I021/010 Data Source Same
Identification Identification
I021/015 Service Identifier New
I021/016 Service Management New
I021/020 Emitter Category I021/020 Emitter Category Same
I021/030 Time of Day Deleted. Replaced by
I021/071 – I021/077
I021/032 Time of Day Deleted
Accuracy
I021/040 Target Report I021/040 Target Report Replaced bit 10 (SPI) and
Descriptor Descriptor bit 9 (unassigned) with
conf level, added one
extend for error conditions
I021/070 Mode 3/A Code New
I021/071 Time of Applicability New
for Position
I021/072 Time of Applicability New, but not applicable
for Velocity for 1090 ES
I021/073 Time of Message New
Reception for Position
I021/074 Time of Message New
Reception for Position
– High Precision
I021/075 Time of Message New
Reception for Velocity
I021/076 Time of Message New
Reception for Velocity
– High Precision
I021/077 Time of Message New
Transmission
I021/080 Target Address I021/080 Target Address Same
I021/090 Figure of Merit I021/090 Quality Indicators Completely reformatted
I021/095 Velocity Accuracy Included in I021/090
Quality Indicators
I021/110 Trajectory Intent I021/110 Trajectory Intent Same, not used
I021/130 Position in WGS-84 I021/130 Position in WGS-84 Same
co-ordinates co-ordinates
I021/131 Position in WGS-84 New
co-ordinates, high
resolution
I021/132 Message Amplitude New

© EUROCAE, 2010
 216

ASTERIX Category 021 Edition ASTERIX Category 021 Edition 1.4 Changes from Edition
0.23 0.23 to 1.4
I021/140 Geometric Altitude I021/140 Geometric Altitude Added "greater than"
encoding
I021/145 Flight Level I021/145 Flight Level Same
I021/146 Intermediate State I021/146 Intermediate State Same
Selected Altitude Selected Altitude
I021/148 Final State I021/148 Final State Selected Same, not used
Selected Altitude Altitude
I021/150 Air Speed I021/150 Air Speed Same
I021/151 True Air Speed I021/151 True Air Speed Added "greater than"
encoding
I021/152 Magnetic Heading I021/152 Magnetic Heading Same
I021/155 Barometric Vertical I021/155 Barometric Vertical Added "greater than"
Rate Rate encoding
I021/157 Geometric Vertical I021/157 Geometric Vertical Added "greater than"
Rate Rate encoding
I021/160 Ground Vector I021/160 Ground Vector Added "greater than"
encoding and direction
reference for track angle
I021/161 Track ID New, not used by GS
I021/165 Rate of Turn I021/165 Track Angle Rate Same, not used
I021/170 Target Identification I021/170 Target Identification Same
I021/200 Target Status I021/200 Target Status Added surveillance status
and "downed aircraft" for
emergency status
I021/210 Link Technology I021/210 MOPS Version Completely reformatted,
Indicator added MOPS version
number and a "version not
supported" flag
I021/220 Met Report I021/220 Met Report Same, not used
I021/230 Roll Angle I021/230 Roll Angle Same, not used
I021/250 Mode S MB Data New, not used by GS

I021/260 ACAS Resolution New, not used by GS

Advisory Report
I021/271 Surface Capabilities New
and Characteristics
I021/295 Data Ages New, not used by GS

I021/400 Receiver ID New, not used by GS

© EUROCAE, 2010
 217

M.4 ASTERIX CATEGORY 021 EDITION 0.23 REPORT ASSEMBLY

This section defines the data mapping between Extended Squitter messages and
ASTERIX Category 021 Edition 0.23 reports. Table M-4 summarises the 1090 ES
Ground Station support for ASTERIX Category 021 Edition 0.23 data items.

TABLE M-4: SUMMARY OF ASTERIX CATEGORY 021 EDITION 0.23 DATA ITEMS

Supported
Data by
Description Notes
Item Ground
Station?
I021/010 Data Source Identification Yes
(SAC/SIC)
I021/020 Emitter Category Yes
I021/030 Time of Day (TOA) Yes
I021/032 Time of Day Accuracy No Not required
I021/040 Target Report Descriptor Yes
I021/080 Target Address Yes
I021/090 Figure of Merit Yes
I021/095 Velocity Accuracy Yes
I021/110 Trajectory Intent No Never implemented
in the field
I021/130 Position in WGS-84 co- Yes
ordinates
I021/140 Geometric Altitude Yes
I021/145 Flight Level Yes
I021/146 Intermediate State Selected Yes
Altitude
I021/148 Final State Selected Altitude No No data available in
1090 ES
I021/150 Air Speed Yes
I021/151 True Air Speed Yes
I021/152 Magnetic Heading Yes
I021/155 Barometric Vertical Rate Yes
I021/157 Geometric Vertical Rate Yes
I021/160 Ground Vector Yes
I021/165 Rate of Turn No Never implemented
in 1090 ES
I021/170 Target Identification Yes
I021/200 Target Status Yes
I021/210 Link Technology Indicator Yes
I021/220 Met Report No No support in DO-
260/260A
I021/230 Roll Angle No DO-260 only

© EUROCAE, 2010
 218

M.4.1 I021/010 Data Source Identification (SAC/SIC)

Same as ASTERIX Category 021 Edition 1.4. See 3.10.4.2.

M.4.2 I021/020 Emitter Category

Emitter Category (I021/020) should be assigned as shown in Table M-5.

TABLE M-5: EMITTER CATEGORY FIELD MAPPING REQUIREMENTS FOR ASTERIX

CATEGORY 021 EDITION 0.23

Aircraft Identification and

I021/020 ECAT
Type Message
Emitter Category Version State = Version State = Assumed or
FTC (SET)
Code Confirmed Version 1 Confirmed Version 0
1 (D) 0 DNP DNP
1 (D) 1-7 DNP DNP
2 (C) 0 DNP DNP
2 (C) 1 20 20
2 (C) 2 21 21
2 (C) 3 22 22
2 (C) 4 22 DNP
2 (C) 5 22 DNP
2 (C) 6-7 DNP DNP
3 (B) 0 DNP DNP
3 (B) 1 11 11
3 (B) 2 12 12
3 (B) 3 16 16
3 (B) 4 15 15
3 (B) 5 DNP DNP
3 (B) 6 13 13
3 (B) 7 14 14
4 (A) 0 DNP DNP
4 (A) 1 1 1
4 (A) 2 3 3
4 (A) 3 3 3
4 (A) 4 5 5
4 (A) 5 5 5
4 (A) 6 6 6
4 (A) 7 10 10

NOTE: “DNP” means do not populate (i.e. do not include) I021/020 in reports.

The Emitter Category data item should not be included in the report if the data in the
ADS-B Emitter Category subfield of the ADS-B Aircraft Identification and Type
Message has not been received or has expired.

© EUROCAE, 2010
 219

M.4.3 I021/030 Time of Day

For ASTERIX Category 021 Edition 0.23, Time of Day is the same as Time of
Applicability (TOA).
Time of Day values should be rounded to the nearest 1/128th second.
If the ASTERIX Category 021 report contains the Ground Vector item (I021/160) and
not the WGS-84 position item (I021/130), Time of Day should be the time of message
receipt (TOMR) of the airborne velocity message from which the velocity reported in
I021/160 was derived.
If the ASTERIX Category 021 report contains the WGS-84 position item and the T bit
(ME bit 21, message bit 53) of the last position message equals 0, Time of Day should
be the TOMR of the last position message.
If the ASTERIX Category 021 report contains the WGS-84 position item, the T bit (ME
bit 21, message bit 53) of the last position message equals 1 and the FTC of the last
position message is 7, 8, 11-18 or 22, Time of Day should be the TOMR of the last
position message.
If the ASTERIX Category 021 report contains the WGS-84 position item, the T bit (ME
bit 21, message bit 53) of the last position message equals 1, the FTC of the last
position message is 5, 6, 9, 10, 20 or 21, and the Ground Station is in either the UTC
Coupled or the Coasting time state, Time of Day should be determined as follows:
if (TOMR - tFprevious) < 200 ms then
Time of Day = tFprevious
else
Time of Day = tFnext
endif
Where:
• TOMR is the time of message receipt of the position message used in the
current report;
• Time of Day is the time of applicability reported in I021/030, rounded to 1/128th
of a second;
• tFprevious and tFnext are defined as in section 3.10.4.8.
NOTE: The Ground Station does not emit ASTERIX Category 021 reports by
default when in the Not Coupled time state.

M.4.4 I021/040 Target Report Descriptor

DCR (Differential Correction, bit 16) should be 0.

GBS (Ground Bit Set, bit 15) should be 0 for targets broadcasting airborne position
messages.
SIM (Simulated Target, bit 14) should be 0 when the Ground Station is reporting
actual targets detected from Extended Squitter messages received over the RF
interface in real time. If the Ground Station supports an optional reprocessing
capability, SIM should be 1 when the GS is reprocessing recorded or simulated target
data.
TST (Test Target, bit 13) should be 1 if the target corresponds to a configured internal
test target address for the Ground Station, otherwise it should be 0.
RAB (bit 12) should be 1 if the target address corresponds to a configured Site
Monitor for the Ground Station, otherwise it should be 0.
SAA (Selected Altitude, bit 11) should be 1 if the target transponder version has been
confirmed as version 1 (DO-260A, and the last Target State and Status message
(FTC = 29, subtype 0) received for this target has not expired and has the Target
Altitude Capability field set to either 1 or 2. In all other cases the SAA bit should be 0.

© EUROCAE, 2010
 220

SPI (Special Position Identification, bit 10) should be 1 if the last airborne position
message (FTC = 9 to 18 or 20-22) has not expired and has a surveillance status (SS)
field equal to 3. In all other cases the SPI bit should be 0.
ATP (Address Type, bits 8, 7, 6) should be 0 (non-unique address) if the Ground
Station determines that this target may have the same 24-bit address as another
target. If the Extended Squitter messages received from the target have DF = 18 with
CF set to 1, ATP should be 3 (anonymous address). Otherwise the ATP field should
be 1 (24 bit ICAO address), indicating either DF = 17, or DF = 18 and CF = 0, or DF =
19 and AF = 0.
ARC (Altitude Reporting Capability, bits 5, 4). If an airborne position message with Q
(ME bit 16, message bit 48) equals 1 has been received from the target and has not
expired, the ARC field should be 1. The ARC field should be 2 if the Q bit in the
airborne position message equals 0. If no airborne position message has been
received, or if it has expired, then the ARC field should be 0.
Bits 1, 2 and 3 of I021/040 should be zero.
NOTE: I021/040 in Category 021 Edition 0.23 does not have an extend with error
conditions.

M.4.5 I021/080 Target Address

I021/080 bits 24 through 1 should be equal to message bits 9 through 32 of the first
position report received from a target.

M.4.6 I021/090 Figure of Merit (FOM)

The FOM field should be included in the ASTERIX Category 021 Edition 0.23 report
only when the WGS-84 position field (I021/130) is included.
AC, MN and DC should always be 0.
For version 0 targets, or targets with a duplicate address, PA should be determined
from Table M-6.

TABLE M-6: PA FOR VERSION 0 TARGETS

Extended Squitter I021/090 Edition 0.23

Format Type Code Position Accuracy
0, 8, 18, 22 0
5, 9, 20 9
6, 10, 21 8
7, 11 7
12 6
13 5
14 4
15 3
16 2
17 1

For version 1 targets, PA should be determined from Table M-7.

© EUROCAE, 2010
 221

TABLE M-7: PA FOR VERSION 1 TARGETS

I021/090 Ed 0.23
DO-260A NIC
Position Squitter Position
Supplement
Format Type Code Accuracy (PA)
from FTC = 31
(DO-242 NUC_P)
0, 8, 18, 22 0 0
5, 9, 20 0 9
6, 10, 21 0 8
1
7, 11 7
0
12 0 6
0 5
13
1
4
14 0
15 0 3
1
16 2
0
17 0 1

The NIC supplement value used to determine PA should be the value received closest
in time to the position squitter used in the state vector report. For version 1 targets, PA
should be based on the larger of the two containment radii defined for FTC = 7, 11, 13
and 16 if the NIC supplement is unavailable, invalid or expired.

M.4.7 I021/095 Velocity Accuracy

The Velocity Accuracy field should contain the latest NUCR or NACV value received
from the target. The last 3 bits of this field should be identical to ME bits 11-13
(message bits 43-45) of the most recently received airborne velocity message, FTC =
19, subtypes 1 to 4. The most significant 5 bits should be zero. If no airborne velocity
message has been received from the target, or if the velocity accuracy information has
expired, then the Velocity Accuracy field should be 0 to indicate unknown accuracy.

M.4.8 I021/130 Position in WGS-84 Coordinates

Same as ASTERIX Category 021 Edition 1.4. See 3.10.417.

M.4.9 I021/140 Geometric Altitude

Same as ASTERIX Category 021 Edition 1.4 except I021/140 should not be included
in the report if “Difference from Baro Altitude” is all ones (127 decimal). See 3.10.4.20.

M.4.10 I021/145 Flight Level

Same as ASTERIX Category 021 Edition 1.4. See 3.10.4.21.

M.4.11 I021/146 Intermediate State Selected Altitude

Same as ASTERIX Category 021 Edition 1.4. See 3.10.4.22.

M.4.12 I021/150 Air Speed

Same as ASTERIX Category 021 Edition 1.4. See 3.10.4.23.

© EUROCAE, 2010
 222

M.4.13 I021/151 True Air Speed

Same as ASTERIX Category 021 Edition 1.4 as defined in 3.10.4.24 except I021/151
should not be included if the value in the airspeed field of the airborne velocity
message is equal to 1023.

M.4.14 I021/152 Magnetic Heading

Same as ASTERIX Category 021 Edition 1.4. See 3.10.4.25.

M.4.15 I021/155 Barometric Vertical Rate

Same as ASTERIX Category 021 Edition 1.4 as described in 3.10.4.26 except when
the value in the Vertical Rate field equals 511, I021/155 should be omitted.

M.4.16 I021/157 Geometric Vertical Rate

Same as ASTERIX Category 021 Edition 1.4 as described in 3.10.4.27, except that
when the value in the Vertical Rate field equals 511, I021/157 should be omitted.

M.4.17 I021/160 Ground Vector

Same as ASTERIX Category 021 Edition 1.4 as described in 3.10.4.28 except when
either the N/S Velocity or the E/W Velocity is 1023, the Ground Vector field should not
be included.

M.4.18 I021/170 Target Identification

Same as ASTERIX Category 021 Edition 1.4. See Section 3.10.4.29.

M.4.19 I021/200 Target Status

The data sources for the Target Status data item are the following:
1. SS subfield from the Airborne Position Message (FTC = 9-18 and 20-22);
2. Emergency/Priority Status subfield from the Extended Squitter Aircraft Status
Message (FTC = 28), subtype = 1;
3. Emergency/Priority Status subfield from the Target State and Status Message
(FTC = 29), subtype = 0 (Version 1 targets only).
The value of Target Status should be determined from the latest value of the
Surveillance Status subfield, the latest value of the Emergency/Priority Status subfield
and Table M-8.

TABLE M-8: SURVEILLANCE STATUS TO TARGET STATUS MAPPING

Surveillance ES FTC = 28 or 29
Target Status
Status Emergency/Priority Status
0 Ignored 0: No Emergency/Not Reported
1 Expired or = 0, 1, 6 or 7 1: General Emergency
1 Not expired and = 2 to 5 Use value from Table M-9
2 Ignored 0: No Emergency/Not Reported
3 Ignored 0: No Emergency/Not Reported

© EUROCAE, 2010
 223

TABLE M-9: EMERGENCY/PRIORITY STATUS TO TARGET STATUS MAPPING FOR

SURVEILLANCE STATUS = 1

ES FTC = 28 or 29
Target Status
Emergency/Priority Status
2 2: Lifeguard/Medical
3 3: Minimum Fuel
4 4: No Communications
5 5: Unlawful Interference

If all of the source message data expires, the Target Status value should be 0.
If the Emergency/Priority Status data expires or has not been received, and if the
Surveillance Status Data is valid, Target Status should be 1 if the Surveillance Status
is 1 and should be 0 otherwise.
If the State Vector report is for a target with a duplicate address, Target Status should
be 1 if the Surveillance Status is 1 and should be 0 otherwise.

M.4.20 I021/210 Link Technology Indicator

The I021/210 UAT, VDL and OTR subfields should be 0.

The I021/210 MDS subfield should be 1.
The value in the I021/210 DTI subfield should be in accordance with Table M-10

TABLE M-10: I021/210 CDTI DETERMINATION

Received Extended Squitter Information

Transmitted
Assumed and Confirmed Confirmed Version 1 ASTERIXI021/210 Link
Version 0 targetsAircraft targetsAircraft Technology Indicator, DTI
Operational Status Operational Status bit
Message (FTC = 31) Message (FTC = 31)
CDTI = 0 CDTI = 0 or 0: Unknown
Service Level ≠ 00
CDTI = 1 CDTI = 1 and 1: Aircraft Equipped with CDTI
Service Level = 00

DTI should be 0 if the Aircraft Operational Status Message (FTC = 31) is not received
or expires or if the report is for a target with a duplicate address.

© EUROCAE, 2010
 224

LIST OF MEMBERS OF EUROCAE WORKING GROUP 51 SUB-GROUP 4

Chairman TAMVACLIS Constantin EUROCONTROL

Secretary FREWIN Keith KINETIC Avionics
STEVENS Martin Cantor International Ltd.
Members
ATKINSON Simon ROKE MANOR RESEARCH
BUSBRIDGE Neville QINETIQ
DOUKAS Dimitris EUROCONTROL
ENGEL Alex EUROCONTROL
MARSHAL Al SENSIS
MARTENSSON Johan EUROCONTROL
MILLS Damian NATS UK
MUNOZ-MARTINEZ Miguel INDRA
KOPECKY Rudolf ERA
NEUFELDT Holger THALES ATM
OUANES Eric DTI France
PICI Manuel SELEX SI
PUPILLO Enrico SELEX Comms
QUILTER Timothy ERA
SZLEZAK Andrzej BECKER Avionics

© EUROCAE, 2010
 225

ED-129 MODIFICATION SUGGESTION FORM

Name: __________________________________ Company Name: _______________________

Address: ______________________________________________________________________

City: __________________________ Postal code: _________ Country: ____________________

Phone: __________________________________ Date: ________________________________

Fax: ____________________________________ E-mail: _______________________________

DOCUMENT: ED-129 Paragraph: _________ Page: ___________ Line: ___________

… Editorial error (format, punctuation, spelling)

… Content error

… Enhancement or refinement

Rationale (Describe the error or justification for enhancement): ____________________________

______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________

Proposed change (attach marked-up text or proposed rewrite): ____________________________

______________________________________________________________________________
______________________________________________________________________________

Please provide any general comments for improvement of this document: ____________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________

Return completed form to:

EUROCAE
102 Rue Etienne Dolet
92240 MALAKOFF
Email: [email protected]

© EUROCAE, 2010