2024年3月12日发(作者：)
ADS-B地面站数据标准asterix cat021版
本介绍
中国第一家航空设备网上销售平台——航店
“航店”（）成立于2011年，主要是代理国外的航
电产品，包括航电、机场、空管等领域的产品。我们也能根据您的需
要找到您想要的产品，并为您量身定做您满意的航空领域解决方案以
及提供技术支持等。
我们的产品包括ACARS、ADS-B、GPS等专业产品，涵盖航空电子、航
空仪表、WiNRADiO接收机、实验室测试台等产品线，也有专门用于
无人机的相关产品。
更多产品信息访问：
APANPIRG/23
Appendix H to the Report on Agenda Item 3.4
GUIDANCE MATERIAL ON
GENERATION, PROCESSING & SHARING of ASTERIX
CATEGORY 21 ADS-B MESSAGES
(Including Attachments A, B, C & D)
1.
INTRODUCTION
1.1 The “All Purpose Structured Eurocontrol Surveillance Information Exchange”
(ASTERIX) Category 21 is a data format standard globally accepted by the Air Traffic Management
(ATM) system manufacturing industry for sharing of ADS-B data with ATM automation system.
Asterix Category 21 data is used to convey ADS-B data from ADS-B ground stations to ATC
processing and display system. This guidance material discusses various aspects of this process.
Since the ASTERIX Category 21 version 0.23 was issued in November 2003, it has undergone
continuous revisions with some 14 subsequent versions. The focus of this guidance material is to
concentrate on 1090ES ADS-B data using:
a) DO260;
b) DO260A; and
c) DO260B
1.2 The ASTERIX Category 21 version 1.0 issued in August 2008 has fully incorporated
the DO260A standard while the latest version 2.1 issued in May 2011 has fully incorporated the latest
DO260B standard.
2.
ASTERIX CAT 21 IN ASIA AND PACIFIC REGIONS
2.1 To ensure interoperability of ADS-B ground stations in the Asia Pacific (ASIA/PAC)
Regions, during the 16th APANPIRG Meeting held in August 2005, the ASTERIX Category 21 version
0.23 which had incorporated DO260 standard was adopted as the baselined ADS-B data format for
deployment of ADS-B ground stations and sharing of ADS-B data in the ASIA/PAC Regions. At this
time DO260A and DO260B standards were not defined.
3.
CHOICE OF ASTERIX VERSION NUMBER
3.1 The Asterix standard has been developed over many years. Stability in the standard is
desirable so that ADS-B ground station designers and ATM automation designers and manufacturers
can build interoperable systems with confidence. Because ADS-B technology has been evolving over
the years, and will continue to do so, it is not surprising that the Asterix standard has also developed
along with the ADS-B link technology standards to grasp the best benefits of its intended design.
3.4H - 1
APANPIRG/23
Appendix H to the Report on Agenda Item 3.4
3.2 During 2005, Asia Pacific decided to use V0.23 as the version for sharing ADS-B data
between states. This version provides adequate information so that useful ATC operational services can
be provided including ATC 3 nautical mile and 5 nautical mile separation services. V0.23 can be used
with DO260, DO260A and DO260B ADS-B avionics/ground stations to provide basic ATC operational
services. However, V0.23 cannot fully support all the capabilities offered by DO260A and DO260B.
3.3 Nearly all V0.23 data items can be “re-constructed” from a received V2.1 data stream.
However, most of the special DO260A/B data items cannot be “re-constructed” from a V0.23 data
stream. In terms of domestic use and data sharing with other ANSPs concerning ADS-B data,
several options exist for ANSPs as follows:
Option Domestic use
1
2
V0.23
V2.1
Data sharing
V0.23. This is the default and basic standard.
V0.23. This will require some conversions to occur, probably
through an ADS-B format conversion and filter system (see
Paragraph 11), between a domestic system and a foreign system.
Difficulties may exist if the domestic system requires special
DO260A/B data items, since they cannot all be re-constructed from
the external foreign V0.23 data stream.
3 V2.1 V2.1. Must negotiate bilaterally with data sharing partner regarding
exact version to be used to achieve the intended functions.
Note: In this table, V2.1, the latest Asterix Cat 21 version, is chosen as a representation of an Asterix
Cat 21 version after V0.23. There exists other Asterix CAT 21 versions (e.g. 0.26, 1.3. and etc.) after
V0.23 that could be used by ANSPs for domestic and data sharing use.
4.
SPECIFICATION OF ASTERIX MESSAGE PROCESSING
4.1 Care is needed to understand the difference in specifications :
4.2 Asterix Cat 21: Defines the characteristics of the data ON the interface including
fields that are mandatory on the interface.
4.3 ADS-B ground station specifications: To define the Asterix standard, must also
define which optional Asterix data items are required to be delivered on the Asterix interface, when
the appropriate data is received from the aircraft. It is desirable that suppliers be required to :
3.4H - 2
a)
b)
APANPIRG/23
Appendix H to the Report on Agenda Item 3.4
indicate how the ground station processes and outputs every received DO260,
DO260A and DO260B data element into an Asterix data element/field; and
indicate which and how each Asterix data element and field presented at the
output are populated.
4.4 ATM automation system specifications: Defines which received Asterix data
element and fields are processed and how they are processed. Also defines which Asterix optional
data fields are required by the ATM automation systems (if any). ANSPs that specify ADS-B ground
stations and ATM automation systems need to consider carefully and clearly about what they desire to
achieve. Specifications which simply require compliance with a particular Asterix standard will be
inadequate in most circumstances. In particular ANSPs, together with their suppliers should :
a) Specify the Asterix standard version to be used. This defines the message
formats that are placed on the link between ADS-B ground station and
downstream systems like ATM automation, recording & analysis systems,
bypass ATC systems and foreign ANSPs. The standard will define which
messages elements are mandatory in each message (very few fields) and a
large number of optional fields. The optional fields can only be filled if
relevant data is received from the aircraft. The optional fields will only be
filled if the ground station specification requires them to be filled.
b) Specify the ADS-B ground station behaviour so that when data is received
from the aircraft, the ground station is required to fill appropriate optional
Asterix data fields.
c) Specify the ATM automation system behaviour including appropriate
semantic and syntax checks applied to the Asterix data, including any triggers
for the system to discard data. The processing applied to each received
Asterix data field.
5.
MANDATORY FIELDS : ASTERIX AND 1090ES ADS-B
5.1 Asterix Cat 21 has been designed to support multiple datalinks. It has been defined to
support data fields which are not available in the 1090ES standards. Therefore some data items and
fields are not relevant when 1090ES is used.
5.2 The standard itself defines various items as optional or mandatory. This is defining
what is ON the interface. It does NOT specify the behaviour of the transmitting ground station nor the
behaviour of the receiving ATM automation system.
3.4H - 3
APANPIRG/23
Appendix H to the Report on Agenda Item 3.4
5.3 When a single link technology has been chosen it may be sensible to diverge from the
formal V0.23 standard to reduce the required Asterix datalink bandwidth. E.g.: in an environment with
only 1090ES, it is unnecessary to transmit “Link Technology Indicator”. Asterix Cat 21 Version 2.1
allows this selection.
Mandatory (M) or Optional (O) items as
per ASTERIX Category 21
Version 0.23 Version 2.1
SpecificationSpecification
I021/010 Data Source Identification M M
I021/030 Time of Day M N/A
I021/071 Time of Applicability of N/A One of these is must
or Position or be transmitted
I021/073 Time of Message
reception for position
I021/040 Target Report M M
Descriptor
I021/080 Target Address M M
I021/210 Link Technology M O
Indicator/ MOPS version
Data
Items
Description
6.
GENERATION OF ASTERIX AT AN ADS-B GROUND STATION
6.1
The following general principles should be adopted:
6.2 Commensurate with link bandwidth availability transmit all mandatory Asterix data
items and also transmit those Asterix data items that are operationally desirable. That is, when the
appropriate aircraft transmission is received by the ADS-B ground station, the data should be
transmitted to the ATC system for operational use or for technical recording and analysis use. If no
aircraft transmission data is received to fill an Asterix data item during any update cycle, the data item
should not be included in the Asterix data stream to reduce bandwidth requirements.
6.3 Group 1 (Mandatory Data Items): An Asterix Cat21 message should not be
transmitted unless the mandatory data items defined in Appendix A are all present.
6.4 Group 2 (Desirable Data Items) : The data items defined in Appendix B are
operationally desirable which should always be transmitted in the Asterix Cat 21 messages whenever
the data are received by the 1090ES ground station from aircraft (if allowed by the relevant Asterix
standard chosen).
6.5 Group 3 (Optional Data Items) : The data items defined in Appendix C are
considered optional and may or may not need to be transmitted depending on availability of such data
from aircraft and/or other specific operational needs.
3.4H - 4
APANPIRG/23
Appendix H to the Report on Agenda Item 3.4
6.6. Group 4 (Future Data Items): The following data are defined in the DO260A and
DO260B standards but are not yet defined in the Asterix standard. This group is provided for
information only. It illustrates the need for system designers to provide for future adaptability when
possible and when cost effective to do so. Not only will the Asterix standard continue to evolve, but
changes to DO260 can also be anticipated within the decade.
a) Target heading: Information from DO260A/B Target state and status
messages (On condition messages). These could be used for detection of pilot
errors in selection of heading/altitude; and
b) GPS Offset: Could be used to more accurately display aircraft position on an
airport surface, or better detect that an aircraft has passed an airport hold
point.
6.7 When developing a specification for an ADS-B ground station, it is considered
necessary that the specification requires the transmission of all data items that are operationally
desirable (Group 2), when such data are received from the aircraft, in addition to the data items that
are mandatory (Group 1) in Asterix messages. Whether Group 3 optional data items will need to be
transmitted or not should be configurable on item-by-item basis within the ADS-B ground station
depending on specific operational needs.
PROCESSING OF ASTERIX ADS-B DATA AT ATC SYSTEM
7.
7.1 An Asterix Cat21 message should not be accepted by the ATC system for processing
unless it includes at least all the Group 1 data items.
7.2
The ATC system should process all received Asterix Cat21 message data items that
bring operational benefits (i.e. Group 2 data items). An ATM automation specification should require
that the system appropriately process those Group 2 data items depending on specific operational need.
Whether the ATC system will process Group 3 optional data items will depend on specific operational
needs.
8.
DATA SHARING OF ASTERIX ADS-B DATA
8.1 In principle, all data receiving from the shared ADS-B ground station should be delivered to
the receiving party as far as practicable without filtering unless owing to technical reasons such as the
need to convert the data from one ASTERIX format to another or it is requested by the receiving party
of the data.
3.4H - 5
APANPIRG/23
Appendix H to the Report on Agenda Item 3.4
8.2 It is considered necessary that all data items that are mandatory in Asterix messages (i.e.
Group 1 data items) and operationally desirable (i.e. Group 2 data items) when such data are received
from aircraft, should be included in data sharing. In the event that the data have to be filtered, the list of
optional data items (i.e. Group 3 data items) needs to be shared will be subject to mutual agreement
between the two data sharing parties concerned.
9.
9.1
ISSUE RELATED TO DO260A
Support of DO260A using Asterix Cat 21 V0.23
a) DO260A was developed after V0.23 of Asterix was defined. Therefore,
V0.23 does not directly support DO260A. However, ground station software
can generate useful V0.23 Asterix data from DO260A reports through use of
the following techniques;
A useful I021/090 Figure of Merit can be generated from DO260A messages.
Some implementations have a table, which defines the FOM/PA to be
generated for each combination of SIL, NIC and NAC. The contents of the
table can be offline defined to generate the appropriate FOM/PA values. The
downstream ATC system can then process DO260A reports as if they were
DO260 reports; and
If there is a particular need for the ATC system to have access to the
NIC/NAC or SIL or other data item that exist in DO260A (but not in DO260),
then users may need to consider a more recent version of Cat 21.
b)
c)
9.2
Support of DO260A using Asterix Cat 21 V2.1
a)
b)
If DO260A is used, then the ANSP could decide to use Asterix Cat 21 V1.0
(or later versions) or V2.1; and
Readers are invited to carefully examine the DO260A fields (see Appendix D)
to determine if the benefits of additional DO260A fields are large enough to
warrant adoption of Asterix Cat 21 V1.0 (or later versions) or V2.1.
10.
10.1
ISSUE RELATED TO DO260B
Support of DO260B using Asterix Cat 21 V0.23
a)
3.4H - 6
DO260B was developed some years after DO260A. Therefore, Asterix Cat
21, V0.23 does not directly support DO260B;
b)
APANPIRG/23
Appendix H to the Report on Agenda Item 3.4
The same techniques used for processing DO260A can be used for processing
DO260B, however, the table used must account for NIC supplement B &
NIC supplement C; and
If there is a particular need for the ATC system to have access to the new data
items offered by DO260B, then users may need to consider a more recent
version of Cat 21 (e.g. V2.1).
c)
10.2
Support of DO260B using Asterix Cat 21 V2.1
a)
b)
If DO260B is used, then the ANSP could decide to use Asterix Cat 21 V2.1;
and
Readers are invited to carefully examine the DO260B data items (see
Appendix D) to determine if the benefits of additional DO260B data items
are large enough to warrant adoption of Asterix Cat 21 Version 2.1.
11.
ADS-B FORMAT CONVERSION AND FILTER SYSTEM
11.1 It is clear that the evolution of 1090ES ADS-B transmission will continue. Avionics
software will be upgraded to provide additional or changed functionality. As a result Asterix standards
will also continue to evolve, and ATC systems will need to be adaptable to be able to cope with new
functionality requirements and new message standards.
11.2 The use of an ADS-B format conversion & filter (ADS-B FC&F) system between
domestic ADS-B systems and data shared with other states is a cost-effective way to provide the
necessary protection and flexibility in this evolution. Such a system provides ADS-B format
conversion between domestic and foreign ADS-B systems. While decoupling one ADS-B Asterix
environment from another, the system allows information that meets specific sharing criteria to be
passed through for data sharing. By doing so, loading on the ATM automation systems to process
ADS-B data and bandwidth requires to transmit the ADS-B data could then be reduced. The system
also allows independent domestic format changes without disruption to the foreign environment. A
typical structure could be as shown below:
3.4H - 7
APANPIRG/23
Appendix H to the Report on Agenda Item 3.4
3.4H - 8
APANPIRG/23
Appendix H to the Report on Agenda Item 3.4
Attachment A - Group 1 (Mandatory Data Items)
V V
Data Items Description Remarks
0.23 2.1
I021/010 Data Source
Identification
X X Identifies source of data. Important if
validity checks are performed as an anti
spoofing capability. Validation that the data
is received from an approved ADS-B
ground station. Data received from a ground
station should not be processed if the
position of the reported aircraft is an
unreasonable distance away from the
known location of the ADS-B ground
station
X Necessary to extrapolate the ADS-B data to
time of display. Data received with a Time
of Day too far in the past should be
discarded. This data is too old.
X Necessary to extrapolate the ADS-B data to
time of display. Data received with a Time
of Day too far in the past should be
discarded. This data is too old.
X X Indicates if report is a duplicate, on the
ground, is a simulated target, is a test target.
This needs to be checked by ATC system
prior to processing. If the data indicates that
the report is a test target or a simulated
target, it is normally processed differently
to “real” targets.
X X Included in all 1090ES downlink messages,
so always available. Used for report/report
linkage in ATC tracking.
X X Position cannot be used without quality
indicator. If the quality of the positional
data does not meet the requirements the data
should be discarded.
X X Report cannot be used without position
I021/030
Time of Day
Time of Applicability
of Position or
Time of Message
reception for position
Target Report
Descriptor
I021/071
or
I021/073
I021/040
I021/080 Target Address
I021/090 Figure of
Merit/Quality
Indicators
Position in WGS-84
co-ordinates
I021/130
3.4H - 9
APANPIRG/23
Appendix H to the Report on Agenda Item 3.4
Attachment B - Group 2 (Desirable Data Items)
Data Items Description
V
0.23
V
2.1
Remarks
I021/008 Aircraft operational status X TCAS capability, Target state reporting
capability, CDTI capability, Single/dual
aircraft antenna.
It is desirable to have immediate
knowledge of RA event.
I021/020 Emitter Category X X Aircraft or vehicle type
I021/140 Geometric Altitude/Height X X Useful for RVSM monitoring. Not
normally used for ATC application.
Could perhaps be used as an indicator of
correct QNH setting in aircraft.
I021/145 Flight Level X X Flight level is an important information
to ATC
I021/155 Barometric Vertical Rate X X Used for predictive tools and safety nets.
I021/157 Geometric Vertical Rate X X
Either Barometric vertical rate or
Geometric vertical rate is provided by
the aircraft – not both.
However, the ATC system can calculate
vertical rate from multiple flight level
reports if these data items are not
available.
I021/160 Ground Vector X X Provides excellent vector to support
extrapolation of positional data to time
of display.
However, the ATC system can calculate
the velocity vector (ground vector) from
multiple position reports. I021/160
however, is normally far superior that
ATC system calculation.
3.4H - 10
Data Items
I021/170
APANPIRG/23
Appendix H to the Report on Agenda Item 3.4
V V
Description Remarks
0.23 2.1
Target Identification X X This is the callsign/Flight ID is
extremely useful for ATC and matching
to the flight plan (if any).
Target identification is only sent once
per 5 seconds. Some ground stations
designs attach the target identification (if
known from previous recent downlinks)
even if not received in the last 5 seconds.
The field can be missing at the edge of
ADS-B coverage – for flights inbound to
coverage.
This is the emergency type and is highly
desirable.
I021/200 Target Status X X
3.4H - 11
APANPIRG/23
Appendix H to the Report on Agenda Item 3.4
Attachment C - Group 3 (Optional Data Items)
Data Items
I021/077
Description
Time of report transmission
V
0.23
V
2.1
Remarks
I021/032 Time of Day Accuracy
I021/095 Velocity Accuracy
I021/072
I021/075
Time of applicability of
velocity
Time of message reception of
velocity
Track number I021/161
I021/110 Trajectory Intent
I021/146
I021/148
(Intermediate) Selected
Altitude
Final State Selected Altitude
I021/015 Service identification
I021/016 Service management
Time of applicability is relevant for
ATC system processing. Time of
transmission is less relevant.
X Maximum error in Time of day.
Normally the maximum value is
known by the ANSP because of
station design.
X If using GPS, velocity accuracy will
be adequate if the Position quality is
accurate.
X Can be managed by a velocity data
time out in Ground station.
X Normally velocity is in the same
Asterix message as position. Velocity
data time out in Ground station.
X Tracking can be performed by ATC
system. Also the 24 bit code (aircraft
address) could be used as a pseudo
track number.
X X Defined in DO260 but not transmitted
by any known product. Not defined in
DO260A or DO260B
X X Target altitude :
Information from DO260A/B Target
X X
state and status messages (On
condition messages). These could be
used for detection of pilot errors in
selection of heading/altitude.
X Type of Service (VDL4, Ext Squitter,
UAT, TIS-B VDL4, TIS-B Ext
Squitter, TIS-B UAT, FIS-B VDL4,
GRAS VDL4, MLT). Not useful to
most ATC systems.
X Update rate or whether data driven
output from GS. Normally known by
receiver.
X
3.4H - 12
Data Items
I021/074
APANPIRG/23
Appendix H to the Report on Agenda Item 3.4
V V
Description
0.23 2.1
Remarks
Time of message reception of
position – high resolution
Time of message reception of
velocity – high resolution
MOPS version/ Link
Technology Indicator
Mode 3/A code
Rate of Turn/Track Angle rate
Surface capabilities and
characteristics
Message amplitude
I021/076
I021/210
I021/070
I021/165
I021/271
I021/132
I021/250
I021/260
High resolution is designed to support
MLAT system processing by receiver.
Not required for pure ADS-B.
X High resolution is designed to support
MLAT system processing by receiver.
Not required for pure ADS-B.
X X Maybe useful for statistics about
equipage.
Not operationally relevant
X Could be used for legacy ATC system
that do not use Flight ID
X X Not transmitted in DO260, DO260A
or DO260B messages
X
Useful for technical analysis. Not
operationally relevant
X
X
X
X
X Defined in standards but only sent in
X
absence Ground vector information.
Can’t be used for extrapolation unless
wind speed known.
X X Defined in standards but only sent in
absence Ground vector information.
X X Not transmitted in DO260, DO260A
or DO260B messages
X X Not transmitted in DO260, DO260A
or DO260B messages
X
X
X
X
X
Mode S MB data
ACAS resolution advisory
report
I021/400 Receiver ID
I021/295 Data ages
I021/150 Air Speed
I021/151 True Air Speed
I021/152
I021/220
I021/230
Magnetic Heading
Met Report
Roll Angle
I021/131 Position in WGS-84
coordinates, high resolution
3.4H - 13
APANPIRG/23
Appendix H to the Report on Agenda Item 3.4
Attachment D - Differences among DO260, DO260A, DO260B
Introduction of
Navigation Integrity
Category (NIC) to
replace Navigation
Uncertainty Category
(NUC
P
)
DO-260
NUC
P
is used.
DO-260A
NIC is used to
replace NUC
P
.
DO-260B
More level of
NIC available.
Vertical
component
removed.
Availability of data in
Asterix CAT 21
NIC is shown in v1.0
and above. More level
of NIC (shown as PIC)
is available in v2.1.
Potential uses of additional information
The additional quantum levels of NIC would
allow the ANSP more flexibility in deciding
whether the NIC is considered as ‘good’ (if
required)
However, for 3 NM & 5 NM separation with
HPL 1Nm and 2 Nm respectively, this additional
quantum is not useful.
Vertical component is not available for DO260B.
Quality Indicator for
Velocity (NUC
R
and
NAC
V
)
Surveillance Integrity
Level and Source
Integrity Level (SIL)
NUC
R
is used.
Not available.
Replaced with
NAC
V
.
Definition
remains the
same.
Surveillance
Integrity Level
is used.
Vertical
component
removed.
Renamed as
Source Integrity
Level. Definition
is changed to
exclude avionics
fault.
To address
probability of
avionics fault.
Available in v0.23 and
above.
Available in v1.0 and
above.
System Design
Assurance (SDA)
Not available. Not available. Available in v2.1.
The SIL will allow the user to further assess the
integrity of the reported position (if required).
NB: An implied SIL exists for DO260 aircraft if
they always use GPS. However DO260 aircraft
do not provide SIL.
The SDA will indicate the robustness of the
system. ANSPs may decide on a minimum SDA
for ADS-B services.
If this action is taken then DO260 aircraft will be
unable to meet the criteria.
K - 14
Navigation Accuracy
Category (NAC
P
)
Geometric Vertical
Accuracy (GVA)
Barometric Altitude
Integrity Code
(NIC
BARO
)
Length / Width of
Aircraft
APANPIRG/23
Appendix H to the Report on Agenda Item 3.4
DO-260 DO-260A DO-260B Availability of data in Potential uses of additional information
Asterix CAT 21
Not available. Derived from Relies only on Available in v1.0 and A reported accuracy is not provided by DO260.
HFOM and HFOM. above. However, an estimated accuracy can be derived
VFOM. from NUC – assuming that NUC is HPL based.
Not available. Not available. Derived from Available in v2.1. Geometric altitude accuracy is not normally
VFOM. required for operational purposes.
Not available. To indicate Same as Available in v1.0 and The NIC
BARO
indicates the integrity of the
integrity of DO-260A above. barometric height.
barometric
ANSPs could indicate to the controller that
altitude.
Barometric data has not been verified, however,
aircraft without dual barometric systems/air data
computers may be unable to provide a non zero
NIC
BARO
as data could be unnecessarily
discarded.
Not available. Provide an Same as Available in v1.0 and The width / length indicate the size of the
indication of DO-260A above. aircraft. This information may be used as an
aircraft size. input for generating alerts on airport surface
movement control.
3.4H - 15
APANPIRG/23
Appendix H to the Report on Agenda Item 3.4
Indication of
capabilities
DO-260
Only show
status of
TCAS and
CDTI.
DO-260A
More
information
available
including
capability to
send Air
Reference
Velocity, Target
State and
Trajectory
Change reports.
Status of
Identity
Switch.
Information on
whether
Resolution
Advisory is
active.
Indication on
whether GPS
offset is
applied.
Availability of data in
Asterix CAT 21
Available in v1.0 and
Additional
above, except
information on
type of ADS-B in
availability of
(i.e. 1090ES in or
1090ES/UAT in and
information on GPS
UAT in).
antenna offset.
DO-260B Potential uses of additional information
Indication on the availability of 1090ES in /
UAT in may allow the controller to anticipate a
potential request for in-trail procedure clearance.
NB: ITP requires decision support aids which are
more complex than ADS-B IN alone.
Status of Resolution
Advisory
Not available.
Same as
DO-260A
Available in v1.0 and
above,
Indication of the resolution advisory status
allows the controller to know whether the pilots
were alerted about the potential conflict.
Indication on GPS offset may be one of the
inputs for generating alerts on airport surface
movement control.
The intended heading and flight level can be
used as an input to the trajectory prediction
algorithm in the Short-Term Conflict Alert.
GPS offset Not available. Information on
GPS antenna
offset is
provided.
Same as
Intention Not available. Able to
DO-260A
indicate
intended
altitude and
heading.
GPS offset status is
available in v1.0 and
above. Information on
GPS offset is not
available in ASTERIX
Intended altitude is
available in v0.23.
Intended heading is not
available in ASTERIX.
3.4H - 16
Target Status
Resolution Advisory
APANPIRG/23
Appendix H to the Report on Agenda Item 3.4
DO-260 DO-260A DO-260B Availability of data in
Asterix CAT 21
Vertical Navigation
Not available. Not available. Indication of
Autopilot mode,
mode, Altitude Hold
mode and Approach
Vertical
Navigation mode,
Mode are available in v
0.23 and above
Altitude Hold
mode, Approach
Mode and LNAV
LNAV Mode is
available in v2.1
Mode.
Not available. Not available. Availability of
Available in v1.0 and
above.
Active
Resolution
Advisories;
Resolution
Advisory
complement
record,
Resolution
Terminated;
Multiple Threat
encounter; Threat
Type indicator;
and Threat
Identity data.
Potential uses of additional information
The target status allows the controller to know
the mode that the aircraft is in. i.e.: It could be
presented to ATC.
The Resolution Advisory will help the controller
know the advisories that are provided to the
pilots by the ACAS. This helps prevent the
controller from giving instructions that are in
conflict with the ACAS.
3.4H - 17
APANPIRG/23
Appendix H to the Report on Agenda Item 3.4
Mode A
DO-260
DO260A
change 1,
allows this
using test
message in
USA only.
This was not
implemented
in actual
products.
DO-260A
Broadcasted
using test
message in
USA only.
DO-260B
Broadcasted
worldwide as a
regular message.
Availability of data in Potential uses of additional information
Asterix CAT 21
Available in v0.26 and The Mode A allows flight plans to be coupled
above. with the ADS-B tracks (supports legacy ATM
automation system).
_ _ _ _ _ _ _ _ _ _ _ _ _
3.4H - 18
发布评论