MCP/gr-mcp-docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
gr-mcp-docs/reference/cospas-sarsat/a-series/a002.md
Ryan Malloy 4ed92efd69 refactor: move spec references out of published site 
Cospas-Sarsat specification summaries moved to reference/ for internal
use only. Links updated to point to official cospas-sarsat.int site.

The extracted images remain in public/ for use in other pages.
2026-02-13 05:03:09 -07:00

8791 lines
206 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
title: "A002: C/S A.002 Issue 8 - Rev.5"
description: "Official Cospas-Sarsat A-series document A002"
sidebar:
badge:
text: "A"
variant: "note"
# Extended Cospas-Sarsat metadata
documentId: "A002"
series: "A"
seriesName: "Operational"
documentType: "operational"
isLatest: true
issue: 8
revision: 5
documentDate: "October 2025"
originalTitle: "C/S A.002 Issue 8 - Rev.5"
---
> **📋 Document Information**
>
> **Series:** A-Series (Operational)
> **Version:** Issue 8 - Revision 5
> **Date:** October 2025
> **Source:** [Cospas-Sarsat Official Documents](https://www.cospas-sarsat.int/en/documents-pro/system-documents)
---
COSPAS-SARSAT
MISSION CONTROL CENTRES
STANDARD INTERFACE
DESCRIPTION
C/S A.002
Issue 8 – Revision 5
![Image 1 from page 1](/images/cospas-sarsat/A-series/A002/A002_page_1_img_1.png)
COSPAS-SARSAT MISSION CONTROL CENTRES STANDARD INTERFACE
DESCRIPTION
History
Issue
Revision
Date
Comments
Original issue approved by CSSC
Approved by Council (CSC-1)
Approved by Council (CSC-7)
Approved by Council (CSC-19)
Approved by Council (CSC-43)
Approved by Council (CSC-45)
Approved by Council (CSC-47)
Approved by Council (CSC-49)
Approved by Council (CSC-51)
Approved by Council (CSC-53)
Approved by Council (CSC-55)
Approved by Council (CSC-57)
Approved by Council (CSC-59)
Approved by Council (CSC-61)
Approved by Council (CSC-62)
Approved by Council (CSC-63)
Approved by Council (CSC-64)
Approved by Council (CSC-65)
Approved by Council (CSC-66)
Approved by Council (CSC-67)
Approved by Council (CSC-69)
Approved by Council (CSC-70)
Approved by Council (CSC-71)
Approved by Council (CSC-73)
TABLE OF CONTENTS
Page
1.
INTRODUCTION ............................................................................................................ 1-1
1.1 Overview ................................................................................................................... 1-1
1.2
Document Objective ................................................................................................. 1-1
1.3
Required Implementation Data ................................................................................. 1-1
1.4
Reference Documents ............................................................................................... 1-2
2.
COMMUNICATION CHANNEL INTERFACES ....................................................... 2-1
2.1
Voice Communication Facilities ............................................................................... 2-1
2.2
Data Communication Facilities .................................................................. 2-1
2.2.1
Subject Indicator Types (SITs) ................................................................... 2-1
2.2.2
Cospas-Sarsat Message Text ...................................................................... 2-2
2.2.3
Character Text ............................................................................................. 2-2
3.
COMMUNICATION STANDARDS .............................................................................. 3-1
3.1
File Transfer Protocol (FTP) Communications ........................................................ 3-1
3.2
AFTN/AMHS Communications ............................................................................... 3-1
3.3
Email Communications ............................................................................................. 3-2
3.4
Web Service Communications .................................................................................. 3-2
4.
MESSAGE FORMAT ...................................................................................................... 4-1
4.1
Format Requirements ................................................................................................ 4-1
4.2
Character Set ............................................................................................................. 4-2
LIST OF ANNEXES
ANNEX A
Subject Indicator Types (SITs) ........................................................................... A-1
ANNEX B
Message Field Description ...................................................................................... B-1
ANNEX C
Message Content by SIT......................................................................................... C-1
ANNEX D
Useful Information for Standard Message Formats between MCC and RCC .............. D-1
ANNEX E
Cospas-Sarsat Standard for the Transmission of SIT Messages via FTP ...................... E-1
ANNEX F
Cospas-Sarsat Standard for the Transmission of SIT Messages via Hardware VPN ..... F-1
ANNEX G
Cospas-Sarsat Standard for the Transmission of SIT Messages via AFTN ................. G-1
ANNEX H
Implementation Plan for New Communication Links ............................................... H-1
ANNEX I
Protocol for the Transmission of SIT Messages via Electronic Mail (Email) ................ I-1
LIST OF TABLES
Table 4-1:
International Alphabet No.5 (IA5) ....................................................................... 4-3
Table 4-2:
International Telegraph Alphabet No.2 (ITA2) ................................................... 4-4
Table 4-3:
Equivalents for Translation between International Telegraph Alphabet .................
No.2 and International Alphabet No.5 ................................................................. 4-5
Table A-1:
Subject Indicator Types for Alert Messages ....................................................... A-2
Table A-2:
Subject Indicator Types for System Information and Narrative Messages ......... A-6
Table A-3:
SIT Number Assignment ..................................................................................... A-8
Table B-1:
Message Field Description .................................................................................. B-3
Table C-1:
Message Content for Alert Messages .................................................................. C-2
Table C-2:
Message Content for System Information and Narrative Messages ................... C-9
Table C-3:
Message Content for SIT 185 Messages ........................................................... C-14
Table C-4:
Message Content for SIT 985 Messages ........................................................... C-15
Table C-5:
LADR Message Field Descriptions ................................................................... C-16
Table E-1:
FTP Password Special Characters ........................................................................ E-4
Table F-1:
Template for VPN Concentrator Parameters ....................................................... F-3
Table F-2:
Template for FTP Server Logon Information ...................................................... F-4
Table F-3:
Example of Template of VPN Concentrator Parameters ..................................... F-4
Table F-4:
Example of Template of FTP Server Logon Information .................................... F-5
Table G-1:
Suggested AFTN Priority for SIT Messages ....................................................... G-5
LIST OF FIGURES
Figure 4.1:
General Message Structure ............................................................................. 4-1
Figure B.1:
Using Unlocated Alerts to Determine and Flag the Image Position ............ B-46
Figure B.2:
Algorithm to Determine if Computed Position is Inside Satellite .......................
Footprint ....................................................................................................... B-47
Figure B.3:
Message Sequence Checking Flowchart ...................................................... B-49
Figure B.4:
Missed Message List Monitoring Flowchart ................................................ B-50
Figure C.1:
XML Schema for the Transfer of TOA/FOA Data Between MEOLUTs .... C-11
Figure G.1:
Message Format International Telegraph Alphabet No.2 (ITA2) .................. G-6
Figure G.2:
Message Format International Alphabet No.5 (IA5) ..................................... G-7
1-1
1.
INTRODUCTION
1.1
Overview
The purpose of the Cospas-Sarsat System is to provide distress alert and location data for the
support of search and rescue (SAR) and other emergency services using spacecraft and ground
facilities to detect and locate distress signals.
Distress beacons transmit 406 MHz signals that are relayed through SAR instruments on Cospas-
Sarsat low-altitude polar-orbit (LEOSAR) spacecraft, medium-altitude Earth orbit (MEOSAR)
GNSS spacecraft, or geostationary (GEOSAR) spacecraft. These signals are relayed to Cospas-
Sarsat ground facilities termed Local User Terminals (LUTs), which process the signals to
determine the beacon location. Alerts are then relayed, together with location data, via a Mission
Control Centre (MCC), either to another MCC or to the Distress authorities responsible for
managing the response to the beacon alerts.
Each MCC distributes Cospas-Sarsat messages according to the System document C/S A.001,
“Cospas-Sarsat Data Distribution Plan”, which defines the Cospas-Sarsat ground communication
network. Most Cospas-Sarsat messages are sent in formats which permit the data to be
automatically processed and transmitted. These message formats are described in this document
C/S A.002, “Cospas-Sarsat Mission Control Centres Standard Interface Description”.
1.2
Document Objective
The Cospas-Sarsat System is operated in accordance with the 1988 International Cospas-Sarsat
Programme Agreement (document C/S P.001) and other related documents. The purpose of this
document C/S A.002 (SID) is to describe the message formats and communication standards that
are used to transmit data between Cospas-Sarsat MCCs. It is designed to facilitate information
exchange between Cospas-Sarsat MCCs and between those MCCs and Distress authorities.
This document specifies the structure and content of the information portion of Cospas-Sarsat
messages, regardless of the communication network to be used. For an operational
implementation, the information portion will of necessity be framed with the addressing, header
and trailer data required by the specific network protocol.
1.3
Required Implementation Data
The following information must be agreed upon between two agencies establishing a
communications interface:
•
network and protocols to be used,
•
data rate,
•
addressing/routing,
1-2
•
packet size constraints,
•
security (e.g., password, call identification and caller user data).
1.4
Reference Documents
a.
C/S A.001
Cospas-Sarsat Data Distribution Plan,
b.
C/S A.003
Cospas-Sarsat System Monitoring and Reporting,
c.
C/S A.005
Cospas-Sarsat Mission Control Centre (MCC) Performance Specification
and Design Guidelines,
d.
C/S T.001
Specification for Cospas-Sarsat [First-Generation] 406 MHz Distress
Beacons,
e.
C/S T.002
Cospas-Sarsat
[LEOLUT]
Local
User
Terminal
Performance
Specification and Design Guidelines,
f.
C/S T.009
Cospas-Sarsat GEOLUT Performance Specification and Design
Guidelines,
g.
C/S T.015
Cospas-Sarsat Specification and Type Approval Standard for 406 MHz
Ship Security Alert (SSAS) Beacons,
h.
C/S T.018
Specification for Second-Generation Cospas-Sarsat 406-MHz Distress
Beacons,
i.
C/S T.019
Cospas-Sarsat MEOLUT Performance Specification and Design
Guidelines,
j.
C/S P.001
International Cospas-Sarsat Programme Agreement,
k.
ICAO
Convention on International Civil Aviation, [the Chicago Convention,]
Annex 10 “Communication Procedures”, Volume II;
l.
C/S R.025
Cospas-Sarsat Two-Way Communication Operational Concept and High-
Level Requirements.
Other information that is used in this document is contained on the Cospas-Sarsat website,
available at http://www.cospas-sarsat.int/en/pro.
The acronyms used in this document are contained in the Cospas-Sarsat Glossary, document
C/S S.011.
– END OF SECTION 1 –
2-1
2.
COMMUNICATION CHANNEL INTERFACES
Two types of communications are required among the Cospas-Sarsat MCCs. Voice
communication is required for general coordination and follow-up/confirmation of certain
automated message transmissions. Data communication using formatted messages are required for
the transfer of Cospas-Sarsat alert data and System information.
2.1
Voice Communication Facilities
Voice communications are made over the public dial-up telephone network or other available
facilities. Voice communication will not be discussed further in this document.
2.2
Data Communication Facilities
Except when otherwise noted, the following specifications (including Annexes) apply to all data
communication involving Cospas-Sarsat Ground segment equipment (i.e., LUTs and MCCs) and
external message destinations, including:
a)
messages sent by an MCC to another MCC;
b)
messages sent by an MCC to a foreign SPOC; and
c)
TOA/FOA (network) data sent by a MEOLUT to a MEOLUT associated with a different
MCC.
These specifications do not apply to messages exchanged within an administration, e.g., alert
messages sent by a LUT to its associated MCC, alert messages sent by an MCC to an RCC within
the administration, or TOA/FOA data exchanged by LUTs controlled by a single administration.
All text and data transmissions to external destinations, including alert messages and System
information messages, shall be made in character text format only and sent in accordance with
Table 4-3. Each respective Ground Segment Provider shall:
a)
make the necessary provisions for connecting to the appropriate communication networks;
and
b)
implement communications to external destinations, on the selected communication
networks in accordance with the standards described in the annexes to this document.
Ground Segment Providers may bilaterally choose to implement primary and alternate
communications systems.
2.2.1
Subject Indicator Types (SITs)
Annex A lists messages sent by MCCs, where each type of message is identified by a Subject
Indicator Type (SIT). The SIT is used to facilitate automatic message handling. Annex A lists the
2-2
SIT code numbers and their assigned use. Annex C defines the content of each of the SIT
messages.
2.2.2
Cospas-Sarsat Message Text
All Cospas-Sarsat messages contain specified types of information. Each one of these information
types, called a Message Field (MF), is described in greater detail in Annex B. These message fields
are then grouped as shown in Annex C to produce the messages for the various SITs listed in
Annex A.
Fields indicated by the letter "A" and letter “X” shall not be omitted. Originators of operational
messages shall provide actual values in all fields indicated by the letter “A” in Tables C-1 and C-
2, as available. Fields indicated by the letter “X” may use default values if actual data is not
available.
Originators of SIT 185 messages destined to RCCs and SPOCs shall populate all the fields
indicated by the letter “M” in Table C-3. Fields indicated by the letter “O” in Table C-3 may be
omitted if their value is NIL in order to minimize the overall length of the SIT 185 message.
2.2.3
Character Text
This specification is based on a text format using International Alphabet No.5 representation. To
provide for use on networks using the International Telegraph Alphabet No.2 (ITA2) characters, a
table of equivalence between the International Alphabet No.5 character representation and ITA2
is provided in Table 4-3.
– END OF SECTION 2 –
3-1
3.
COMMUNICATION STANDARDS
The message formats presented in this document provide flexibility, efficiency, and compatibility
among MCCs. They are independent of the communication network and protocol employed.
All MCC messages are formed as a series of octets (one octet is 8 bits, or one byte, which contains
one character and is commonly referred to as a “character”). A message may be made up of any
number of octets, subject to the restriction in section 4.
The communication networks accepted for communications with destinations are introduced
below and the standards to which each MCC must adhere for their use in the Cospas-Sarsat Ground
Segment are described in the annexes to this document. Some of these networks provide an error
detection and/or error correction capability for detecting and correcting data errors introduced by
the communications system, in order to prevent corrupt messages from being transmitted.
Ground Segment Providers shall implement adequate security to protect their automated means of
communications, including MCCs firewall technology to protect each of their Internet
connections.
3.1
File Transfer Protocol (FTP) Communications
FTP is an Internet-based protocol that can be used to exchange messages. It is highly reliable due
to its inherent error detection and correction capability. Communicating via FTP shall comply with
the applicable standards described in the Internet Engineering Task Group document RFC 959 -
File Transfer Protocol and the Cospas-Sarsat standards contained in Annex E.
All FTP servers used for the exchange of SIT messages should be linked exclusively using Internet
virtual private networks (VPNs) that meet the Cospas-Sarsat standard provided at Annex F. This
is referred to as FTPV communication.
3.2
AFTN/AMHS Communications
The Aeronautical Fixed Telecommunications Network (AFTN) is a worldwide system that
provides point-to-point communications for text messages. Access to the AFTN network is
restricted to terminals that are operated in controlled locations, such as Air Traffic Control Centres
and MCCs. This network may operate at fairly low data rates (i.e., 300 or 9600 baud).
Communications procedures for the AFTN are controlled by ICAO and are detailed in Annex 10
to the Convention on International Civil Aviation, Volume II, Communication Procedures.
Guidance for using AFTN is provided at Annex G to this document.
AFTN is being upgraded by ICAO to the Aeronautical Message Handling System (AMHS). The
transition from AFTN to AMHS will be implemented gradually to meet the requirements of
Administrations. This transition is expected to enhance communication services in several regions
of the world and should not negatively impact the use of AFTN communications by Cospas-Sarsat.
3-2
3.3
Email Communications
Electronic mail is a store-and-forward communication method over the Internet or other networks.
It is an optional mode of communications between MCCs and destinations which may be
undertaken on a bilateral contingency basis. Guidance on using email is provided at Annex I to
this document.
3.4
Web Service Communications
Nodal MCCs shall provide ELT(DT) alert data to the Location of an Aircraft in Distress Repository
(LADR) using Web Services, per Annex C, section “MESSAGE CONTENT FOR MESSAGES
SENT TO THE LADR”. The use of Web Services shall comply with SWIM T1-Yellow Profile
binding requirements, per Appendix 3 of the LADR Functional Specifications (draft version 3.1).
– END OF SECTION 3 –
4-1
4.
MESSAGE FORMAT
4.1
Format Requirements
All Cospas-Sarsat messages shall be framed as shown in Figure 4.1. The structure of the frames is
specified by the host network and does not impact the Cospas-Sarsat information transmitted.
For the entire message, including the required network framing, the number of characters on any
one line shall not exceed 69. This does not include the New Line (NL) sequence described below.
Each line shall end with a new line (NL) sequence that is defined as CRCRLF or CRLF where:
CR means Carriage Return
- Hex 0D (i.e., zero D)
LF means Line Feed
- Hex 0A (i.e., zero A)
The entire message, including any network required framing, shall not exceed 25,000 characters.
However, message originators may need to further limit message size depending on specific
network constraints.
Format Frame
Contents
HEADER
(network dependent)
Made available to satisfy the host network requirements (if
any).
These contents must be designed into the application
software of the agency using the network.
INFORMATION
(SIT message)
Cospas-Sarsat message text as defined in this document,
irrespective of the network in use.
TRAILER
(network dependent)
As per HEADER above.
1Figure 4.1: General Message Structure
All MCC-to-MCC SIT messages shall contain a “SIT header” and a “SIT footer”. All SIT
messages sent from an MCC to an RCC/SPOC can have a “SIT header” and/or a “SIT footer”. The
“SIT header” is defined as line 1, containing Message Fields \#1, \#2, and \#3, and line 2, containing
Message Fields \#4 and \#5. Depending on the SIT format, additional MFs (which are not a part of
the message header) may be present after MF \#5 on line 2. The “SIT footer” is defined as MF \#42
on the second to last line, and MF \#43 on the last line.
4-2
Since some communication networks may add a header that precedes the SIT message, MCCs
must be able to identify the beginning of a SIT message. The presence of SIT Message Fields 1 -
3 shall be used to identify the beginning of the SIT message text. That is, Message Fields 1 - 3
shall have the format “/nnnnn nnnnn/nnnn/nnn nn nnnn”, where n is a numeral between 0 - 9.
4.2
Character Set
The set of International Alphabet No.5 characters that have an equivalent ITA2 character is the set
of allowable characters for the INFORMATION frame of Figure 4.1.
To ensure compatibility, Tables 4-1, 4-2 and 4-3 provide details of those characters. Table 4-1
defines the International Alphabet No.5 characters while Table 4-2 illustrates ITA2 characters.
Table 4-3 details the conversions between the two character sets.
Characters not found in Table 4-3 are not permitted.
The octothorpe (\#) character shall not be used in the information frame of Cospas-Sarsat messages
as it is a command character for some networks.
The “@” (AT sign), “%” (percentage sign), and “\_” (underscore sign) are not listed in Table 4-3,
but are required for some messages.
The “@” (AT sign) should be replaced by “(AT)”, the “%” (percentage sign) should be replaced
by “PERCENT”, and the “\_” (underscore sign) should be replaced by “(UNDERSCORE)”.
For consistency, this format should apply to all messages that are sent by MCCs through all
communication modes
4-3
Table 4-1: International Alphabet No.5 (IA5)
b7 -> 0
BITS
b6 -> 0
b5 -> 0
b4
b3
b2
b1
Column
Row
NUL
DLE
SP
@
P
\
p
SOH
DC1
!
A
Q
a
q
STX
DC2
"
B
R
b
r
ETX
DC3
\#
C
S
c
s
EOT
DC4
$
D
T
d
t
ENQ
NAK
%
E
U
e
u
ACK
SYN
&
F
V
f
BEL
ETB
'
G
W
g
w
BS
CAN
(
H
X
h
HT
EM
)
I
Y
y
LF
SUB
\*
:
J
Z
j
z
VT
ESC
+
;
K
[
k
{
FF
FS
,
<
L
/
l
|
CR
GS
-
=
M
]
m
}
SO
RS
.
>
N
^
n
~
SI
US
/
?
O
___
o
DEL
4-4
Table 4-2: International Telegraph Alphabet No.2 (ITA2)
Combination
Number
Code Element
Character / Allocations
A
B
?
C
:
D
WHO R U
E
F
G
H
\#
I
J
BELL
K
(
L
)
M
.
N
,
O
P
Q
R
S
'
T
U
V
=
W
X
/
Y
Z
+
Carriage Return
Line Feed
Letters Shift
Figures Shift
Space
Not Used
4-5
Table 4-3: Equivalents for Translation between International Telegraph Alphabet
No.2 and International Alphabet No.5
ITA2 Combination No.
(Table 4-2 refers)
IA5 Column/Row (Table 4-1 refers)
Conversion at Interface
ITA2 Letters Case
ITA2 Figures Case
A
4/1, 6/1
-
2/13
B
4/2, 6/2
?
3/15
C
4/3, 6/3
:
3/10
D
4/4, 6/4
ENQ
0/5
E
4/5, 6/5
3/3
F
4/6, 6/6
G
4/7, 6/7
H
4/8, 6/8
\#
2/3
I
4/9, 6/9
3/8
J
4/10, 6/10
BEL
0/7
K
4/11, 6/11
(
2/8
L
4/12, 6/12
)
2/9
M
4/13, 6/13
.
2/14
N
4/14, 6/14
,
2/12
O
4/15, 6/15
3/9
P
5/0, 7/0
3/0
Q
5/1, 7/1
3/1
R
5/2, 7/2
3/4
S
5/3, 7/3
.
2/7
T
5/4, 7/4
3/5
U
5/5, 7/5
3/7
V
5/6, 7/6
=
3/13
W
5/7, 7/7
3/2
X
5/8, 7/8
/
2/15
Y
5/9, 7/9
3/6
Z
5/10, 7/10
+
2/11
CR
0/13
LF
0/10
SI
0/15
SO
0/14
SP
2/0
NUL
0/0
– END OF SECTION 4 –
A-1
ANNEX A
SUBJECT INDICATOR TYPES (SITs)
1.
GENERAL
All Cospas-Sarsat messages are identified by a Subject Indicator Type (SIT) number according to
the subject matter being transmitted.
Descriptions of the Subject Indicator Types are included in Tables A-1 and A-2.
2.
SIT BLOCK ASSIGNMENT
To maintain uniqueness between the SIT numbers for all Cospas-Sarsat agencies, Table A-3
subdivides the range of possible numbers, from 000 to 999 by subject and application.
The proper application of this table will ensure standardization in numbers and usage to facilitate
automatic message handling by the MCCs.
A-2
4Table A-1:
Subject Indicator Types for Alert Messages
SIT
Title
Meaning
Page
FGB LEOSAR and GEOSAR Incident Alert Messages
DOPPLER
INTERFERER
NOTIFICATION
(FGB)
These messages are used for notification of 406 MHz interferer
signals from a LEOLUT.
C-19
LEOSAR/GEOSAR
INCIDENT
(NO DOPPLER) (FGB)
406 MHz alert message from an FGB with no Doppler positions.
An encoded (i.e., GNSS) position may or may not be available.
C-20
POSITION CONFLICT
(LEOSAR/GEOSAR;
ENCODED ONLY)
(FGB)
406 MHz alert message from an FGB with no Doppler positions for
which the encoded (i.e., GNSS) position differs by more than the
match criteria from one or more previous positions.
C-20
POSITION
CONFIRMATION
(LEOSAR;
ENCODED ONLY)
(FGB)
406 MHz alert message from an FGB with no Doppler positions that
identifies the confirmed position of a 406 MHz alert.
C-20
INCIDENT (LEOSAR)
(FGB)
Beacon alert message computed using 406 MHz incident data from
an FGB. The message contains Doppler positions.
C-21
POSITION CONFLICT
(LEOSAR) (FGB)
Beacon alert message computed using 406 MHz incident data from
an FGB. The message contains Doppler and/or encoded (i.e., GNSS)
position(s) which may differ from previous position(s) by the match
criteria.
C-21
POSITION
CONFIRMATION
(LEOSAR) (FGB)
406 MHz alert message from an FGB with Doppler positions that
identifies the confirmed position of a 406 MHz alert. It may or may
not contain an encoded (i.e., GNSS) position.
C-21
NOTIFICATION
OF COUNTRY OF
REGISTRATION
(LEOSAR/GEOSAR
ENCODED ONLY)
(FGB)
Message used between MCCs to notify the country of registration of
an FGB 406 MHz beacon (NOCR). This message does not contain
independent position data (Doppler position data). It may or may not
contain an encoded (i.e., GNSS) position.
C-21
NOTIFICATION
OF COUNTRY OF
REGISTRATION
(LEOSAR) (FGB)
Message used between MCCs to notify the country of registration of
an FGB 406 MHz beacon (NOCR). This message contains Doppler
position data. It may or may not contain an encoded (i.e., GNSS)
position.
C-21
NOTIFICATION OF
RETURN LINK
SERVICE PROVIDER
(LEOSAR/GEOSAR;
ENCODED ONLY)
(FGB)
Message used between MCCs to notify the responsible MCC (see
note 1) of an FGB 406 MHz beacon with RLS capability. This
message only contains an encoded (i.e., GNSS) position (i.e., it does
not contain Doppler positions). This message may or may not
contain an encoded (i.e., GNSS) position when an updated alert is
sent to the RLSP after position confirmation.
C-20
NOTIFICATION OF
RETURN LINK
SERVICE PROVIDER
(LEOSAR/GEOSAR)
(FGB)
Message used between MCCs to notify the responsible MCC (see
note 1) of an FGB 406 MHz beacon with RLS capability. This
message contains Doppler position data. It may or may not contain
an encoded (i.e., GNSS) position.
C-21
A-3
SIT
Title
Meaning
Page
FGB MEOSAR Incident Alert Messages
NOTIFICATION OF
COUNTRY OF
REGISTRATION
(MEOSAR;
ENCODED ONLY)
(FGB)
Message used between MCCs to notify the country of registration of
an FGB 406 MHz beacon (NOCR). This message does not contain
independent position data (DOA position data). It contains an
encoded (i.e., GNSS) position.
C-23
NOTIFICATION OF
COUNTRY OF
REGISTRATION
(MEOSAR) (FGB)
Message used between MCCs to notify the country of registration of
an FGB 406 MHz beacon (NOCR). This message contains DOA
position data. It may or may not contain an encoded (i.e., GNSS)
position.
C-22
NOTIFICATION OF
RETURN LINK
SERVICE PROVIDER
(MEOSAR;
ENCODED ONLY)
(FGB)
Message used between MCCs to notify the responsible MCC (see
note 1) of an FGB 406 MHz beacon with RLS capability. This
message only contains an encoded (i.e., GNSS) position (i.e., it does
not contain a DOA position). This message may or may not contain
encoded (i.e., GNSS) position when an updated alert is sent to the
RLSP after position confirmation.
C-23
NOTIFICATION OF
RETURN LINK
SERVICE PROVIDER
(MEOSAR) (FGB)
Message used between MCCs to notify the responsible MCC (see
note 1) of an FGB 406 MHz beacon with RLS capability. This
message contains DOA position data. It may or may not contain an
encoded (i.e., GNSS) position.
C-22
DOA INTERFERER
NOTIFICATION
(FGB)
These messages are used for notification of 406 MHz interferer
signals from a MEOLUT.
C-22
MEOSAR INCIDENT
(NO DOA) (FGB)
406 MHz alert message from an FGB with no DOA position.
An encoded (i.e., GNSS) position may or may not be available.
C-23
POSITION CONFLICT
(MEOSAR;
ENCODED ONLY)
(FGB)
406 MHz alert message from an FGB with no DOA position for
which the encoded (i.e., GNSS) position differs by more than the
match criteria from one or more previous positions.
C-23
POSITION
CONFIRMATION
(MEOSAR;
ENCODED ONLY)
(FGB)
406 MHz alert message from an FGB with no DOA position that
identifies the confirmed position of a 406 MHz alert.
C-23
INCIDENT
(MEOSAR) (FGB)
Beacon alert message computed using 406 MHz incident data from
an FGB. The message contains a DOA position.
C-22
POSITION
CONFLICT
(MEOSAR) (FGB)
Beacon alert message computed using 406 MHz incident data from
an FGB. The message contains DOA and/or encoded (i.e., GNSS)
position(s) which may differ from previous position(s) by the match
criteria.
C-22
POSITION
CONFIRMATION
(MEOSAR) (FGB)
406 MHz alert message from an FGB with a DOA position that
identifies the confirmed position of a 406 MHz alert. It may or may
not contain an encoded (i.e., GNSS) position.
C-22
COSPAS-SARSAT
ALERTS
(FGB & SGB)
Message used for alert and NOCR messages from MCCs to SPOCs
(FGBs and SGBs).
C-28
to
C-46
A-4
SIT
Title
Meaning
Page
SGB Incident Alert Messages
GEOSAR INCIDENT
(SGB)
406 MHz alert message from an SGB, which does not contain
independent position data (Doppler or DOA position data). It may or
may not contain an encoded (i.e., GNSS) position.
C-24
POSITION CONFLICT
(GEOSAR;
ENCODED ONLY)
(SGB)
406 MHz alert message from an SGB with no Doppler nor DOA
positions for which the encoded (i.e., GNSS) position differs by
more than the match criteria from one or more previous positions.
C-24
POSITION
CONFIRMATION
(GEOSAR;
ENCODED ONLY)
(SGB)
406 MHz alert message from an SGB with no Doppler nor DOA
positions that identifies the confirmed position of a 406 MHz alert.
C-24
NOTIFICATION
OF COUNTRY OF
REGISTRATION
(GEOSAR
ENCODED ONLY)
(SGB)
Message used between MCCs to notify the country of registration of
an SGB 406 MHz beacon (NOCR). This message contains only an
encoded (i.e., GNSS) position.
C-24
NOTIFICATION OF
RETURN LINK OR
TWO WAY
COMMUNICATION
SERVICE PROVIDER
(GEOSAR;
ENCODED ONLY)
(SGB)
Message used between MCCs to notify the responsible MCC (see
note 1) of an SGB 406 MHz beacon with RLS or TWC capability.
This message only contains an encoded (i.e., GNSS) position (i.e., it
contains no independent position). This message may or may not
contain encoded (i.e., GNSS) position when an updated alert is sent
to the RLSP after position confirmation, or to the TWC-SP after a
position is determined.
C-24
NOTIFICATION OF
COUNTRY OF
REGISTRATION
(MEOSAR ENCODED
ONLY) (SGB)
Message used between MCCs to notify the country of registration of
an SGB 406 MHz beacon (NOCR). This message does not contain
independent position data (DOA position data). It contains an
encoded (i.e., GNSS) position.
C-25
NOTIFICATION OF
COUNTRY OF
REGISTRATION
(MEOSAR) (SGB)
Message used between MCCs to notify the country of registration of
an SGB 406 MHz beacon (NOCR). This message contains DOA
position data. It may or may not contain an encoded (i.e., GNSS)
position.
C-25
NOTIFICATION OF
RETURN LINK OR
TWO WAY
COMMUNICATION
SERVICE PROVIDER
(MEOSAR;
ENCODED ONLY)
(SGB)
Message used between MCCs to notify the responsible MCC (see
note 1) of an SGB 406 MHz beacon with RLS or TWC capability.
This message only contains an encoded (i.e., GNSS) position (i.e., it
contains no independent position). This message may or may not
contain encoded (i.e., GNSS) position when an updated alert is sent
to the RLSP after position confirmation, or to the TWC-SP after a
position is determined.
C-26
NOTIFICATION OF
RETURN LINK OR
TWO WAY
COMMUNCATION
SERVICE PROVIDER
(MEOSAR) (SGB)
Message used between MCCs to notify the responsible MCC (see
note 1) of an SGB 406 MHz beacon with RLS or TWC capability.
This message contains DOA position data. It may or may not contain
an encoded (i.e., GNSS) position.
C-25
MEOSAR INCIDENT
(NO DOA) (SGB)
406 MHz alert message from an SGB with no DOA position. An
encoded (i.e., GNSS) position may or may not be available.
C-26
A-5
SIT
Title
Meaning
Page
POSITION CONFLICT
(MEOSAR;
ENCODED ONLY)
(SGB)
406 MHz alert message from an SGB with no DOA position for
which the encoded (i.e., GNSS) position differs by more than the
match criteria from one or more previous positions.
C-26
POSITION
CONFIRMATION
(MEOSAR;
ENCODED ONLY)
(SGB)
406 MHz alert message from an SGB with no DOA position that
identifies the confirmed position of a 406 MHz alert.
C-26
INCIDENT
(MEOSAR) (SGB)
Beacon alert message computed using 406 MHz incident data from
an SGB. The message contains a DOA position.
C-25
POSITION
CONFLICT
(MEOSAR) (SGB)
Beacon alert message computed using 406 MHz incident data from
an SGB. The message contains a DOA position and possibly an
encoded (i.e., GNSS) position which may differ from previous
position(s) by the match criteria.
C-25
POSITION
CONFIRMATION
(MEOSAR) (SGB)
406 MHz alert message from an SGB with a DOA position that
identifies the confirmed position of a 406 MHz alert. It may or may
not contain an encoded (i.e., GNSS) position.
C-25
Note 1: The responsible MCC for the various GNSS providers is stated in the Table “Associated MCCs for Return
Link Service Providers” and in Table “Associated MCCs for TWC Service Providers” in document
C/S A.001; e.g., for the SAR/Galileo system it is the FMCC.
A-6
5Table A-2:
Subject Indicator Types for System Information and Narrative Messages
SIT
Title
Meaning
Page
System Messages
ORBIT VECTORS
Sarsat or Cospas spacecraft orbit position and time message.
C-47
ORBIT VECTORS
Sarsat or Cospas spacecraft orbit position and time message.
Used in special conditions (e.g., after a satellite manoeuvre)
when it is required that orbit vectors at the MCC and its
associated LUTs be initialized. See document C/S A.001,
section entitled “Scheduled Satellite Manoeuvres”.
C-47
ORBIT VECTORS
MEOSAR spacecraft two-line orbital elements (TLE)
message.
C-48
SARP CALIBRATION
Time and frequency calibration for a SARP.
C-49
SARP-3 CALIBRATION
Time and frequency calibration for a SARP-3.
C-51
406 MHz SARR
FREQUENCY
CALIBRATION OFFSET
Offset between actual and 406 MHz SARR-provided beacon
frequencies.
C-53
SYSTEM STATUS AND
INTERNATIONAL
EXERCISE
NOTIFICATION TO ALL
MCCs
Narrative message transmitted to all MCCs to indicate
changes in System status and provide beacon test notification
for Cospas-Sarsat approved international exercises (as
specified in section “Co-Ordination of Beacon Tests” of
document C/S A.001) . System status messages include
System element and System function failures, scheduled
maintenance, integration or testing of new System elements,
and the commissioning of new equipment or new capabilities
of existing equipment.
C-50
&
C-54
to
C-58
For MCC information
transmission to a
single MCC
Narrative message for MCC to MCC operator. This is a free
format message, except when a specific format is defined
(Note 1). Includes notification to affected MCCs about
operational beacon tests under the control of a national
administration, as specified in section “Co-Ordination of
Beacon Tests” of document C/S A.001.
C-50
406 BEACON
REGISTRATION
INFORMATION (15 HEX ID)
This message is used between MCCs to provide 406 MHz
beacon registration information (for 15 Hex ID).
C-59
406 BEACON
REGISTRATION
INFORMATION (23 HEX ID)
This message is used between MCCs to provide 406 MHz
beacon registration information (for 23 Hex ID).
[TBD]
BEACON OPERATIONAL
CHARACTERISTICS
INFORMATION FOR MCCs
Narrative message transmitted to all MCCs to provide
information on the operational characteristics for C/S Type
Approved Second Generation Beacons (SGBs).
C-60
BEACON OPERATIONAL
CHARACTERISTICS
INFORMATION FOR SPOCs
Narrative message transmitted to Distress authorities
(including SPOCs) and FGB-only capable MCCs to provide
information on the operational characteristics for a C/S Type
Approved Second Generation Beacon (SGBs).
C-61
A-7
SIT
Title
Meaning
Page
System Messages for Space Segment Providers
SARP TELEMETRY
SARP telemetry from a Sarsat spacecraft.
C-50
SARP OUT OF LIMIT
Warning message to indicate abnormal performance of the SARP.
C-50
SARP COMMAND
Command request for the SARP.
C-52
SARP COMMAND
VERIFICATION
Verification of the execution (or non-execution) of a SARP
command as requested by command message.
C-50
SARR TELEMETRY
SARR telemetry from a Sarsat spacecraft.
C-50
SARR OUT OF LIMIT
Warning message to indicate abnormal performance of the SARR.
C-50
SARR COMMAND
Command request for the SARR.
C-52
SARR COMMAND
VERIFICATION
Verification of the execution (or non-execution) of a SARR
command as requested by a SARR command message.
C-50
Note 1:
Free format applies only to the message text. The complete message must still be formatted as per the
host communication networks procedures.
A-8
6Table A-3:
SIT Number Assignment
Subject Matter
Between Cospas-
Sarsat MCCs
Internally by
each Cospas-
Sarsat Participant
Between Cospas-
Sarsat MCCs and
non Cospas-Sarsat
Agencies
Future Growth
000 - 099
INCIDENTS
(FGB)
100 - 149
150 - 179
180 - 1991
ORBIT
200 - 249
250 - 279
280 - 299
INCIDENTS
(SGB)
300 - 349
350 - 379
380 - 3991
SARP
400 - 449
450 - 479
480 - 499
SARR
500 - 549
550 - 579
580 - 599
STATUS
600 - 649
650 - 679
680 - 699
LUT
700 - 749
750 - 779
780 - 799
800 - 899
NARRATIVE
900 - 949
950 - 979
980 - 999
Note:
SIT for new messages other than those used internally by each Cospas-Sarsat participant shall be
coordinated with all Cospas-Sarsat MCCs before being implemented.
1- SIT 185 messages shall be used with either FGB or SGB alerts.
– END OF ANNEX A –
B-1
ANNEX B
MESSAGE FIELD DESCRIPTION
1.
GENERAL
Every Cospas-Sarsat SIT message is divided into a series of fields, each field containing unique
information. Each Message Field (MF) is described in this Annex in terms of possible characters
and range of numbers.
All fields must be present when required for a specific SIT message
Message formats and examples by SIT numbers are given in Annex C.
2.
MESSAGE FIELD LIST
A detailed description of each Message Field is given in this Annex. Once it is known which MFs
form a particular SIT, their corresponding formats are concatenated to form the information frame
of the message.
The list in Table B-1 is composed of four columns:
•
Message Field Number (MF \#),
•
Message Field Name (Name),
•
Content,
•
Character Text.
2.1
MF \#
The numbers in this column are for simplicity of reference in Annex C.
2.2
Name
This column contains the name of the message field.
2.3
Content
This column contains the value ranges and meanings of the numbers of each MF.
The listed default values are inserted in the field only when the MCC has no proper value to insert.
2.4
Character Text
This column contains the format for each MF. Note that for MF #1 to MF #44, MF # 64 to #84
and MF \#87 to \#97, fields are separated by a "/" inserted at the beginning of the field, while the
elements within a field are separated by a space (indicated as "b"). For all other message fields, all
B-2
required "/" and spaces (b) are indicated where they are needed. Where multiple spaces are
indicated in a field in the SIT 185 message, the number of spaces may be reduced, if at least one
space is provided.
The following legend applies:
•
all upper case = the actual transmitted character,
•
a = all transmittable characters,
•
h = hexadecimal characters (0-9, A-F),
•
s = sign symbol, plus (+) or minus (-),
•
n = numerals 0 to 9,
•
b = blank space character.
Ensure the 25,000-character transmission limit is not exceeded.
B-3
7Table B-1: Message Field Description
See details of message field description provided in Appendix B.1
MF \#
NAME
CONTENT
CHARACTER TEXT
MESSAGE NUMBER
Current message
Original message
00001 to 99999
If the outgoing message is not a
retransmission, "00000" will be inserted
as the original message number.
nnnnn
nnnnn
REPORTING FACILITY
See (www.cospas-sarsat.int)
nnnn
MESSAGE
TRANSMIT
TIME
Year = 00 -> 99
Day Julian = 001-> 366
UTC - Hours= 00 -> 23
Minutes = 00 -> 59
nn
nnn
nnnn
SIT
(See Table A-1 and A.2)
000 to 999
nnn
DESTINATION MCC
(See www.cospas-sarsat.int)
nnnn
SPACECRAFT ID
Sarsat =
001 to 099
Cospas =
101 to 199
GOES =
201 to 220
Electro-L / Louch-5 / [Arktika-M] =
221 to 240
INSAT / GSAT =
241 to 260
MSG / MTG =
261 to 280
GPS =
300 to 399
Galileo =
400 to 499
Glonass =
500 to 599
BDS = 600 to 699
Per
spacecraft
status
information
provided at www.cospas-sarsat.int and
System Status information provided in
SIT 605 messages.
For MEOSAR satellites the sequence
within the range corresponds to the
Pseudo Random Noise (PRN) number
for the spacecraft (e.g., GPS PRN 23
would be 323)
nnn
ORBIT NUMBER
00000 to 99999
nnnnn
NUMBER OF ALERTS WITH
DOPPLER/DOA POSITIONS
01 to 99
nn
B-4
MF \#
NAME
CONTENT
CHARACTER TEXT
Not Used
(Previously Number of Images
Reported)
NUMBER OF ALERTS
WITHOUT DOPPLER or DOA
POSITIONS
01 to 99
nn
SOURCE ID
Per LUT status information provided at
www.cospas-sarsat.int
and
System
Status information provided in SIT 605
messages.
nnnn
LOCAL or
GLOBAL FLAG
FREQUENCY BAND
Local = “+”
Global or Local and Global = “-”
1 =
not used
2 =
not used
3 =
not used
4 =
406 SARP\*
5 =
406 combined LEO/GEO with
SARP
6 =
406 combined LEO/GEO with
SARR
7 =
406 combined LEO/GEO with
SARP and SARR
8 =
406 SARR
9 =
406 combined SARP and SARR
* Value to be used for SIT 121
messages (406 MHz interferer
notification).
sn
BIAS
BSDEV
DRIFT
-30000.0 to +75000.0 (Hz)
Default value = +99999.9
000.0 to 900.0 (Hz)
Default value = 999.9
-99.00 to +99.00 (Hz/min)
Default value = +99.99
snnnnn.n
nnn.n
snn.nn
TCA
(TIME OF CLOSEST
APPROACH)
Year = 00 to 99
Day (Julian) = 001 to 366
Hours = 00 to 23 (UTC)
Minutes = 00 to 59
Seconds = 00.00 to 59.99
nn
nnn
nnnn
nn.nn
14a
TIME OF FIRST BURST
(AVERAGE TOA)
(Same as MF \#14)
(Same as MF \#14)
14b
TIME OF LAST BURST
(AVERAGE TOA)
(Same as MF \#14)
(Same as MF \#14)
B-5
MF \#
NAME
CONTENT
CHARACTER TEXT
WINDOW FACTOR (WF)
0 = in Window
1 to 9 = outside Window
WF = Integer of the Quotient:
(TCA – ½ (Tf + Tl)) / (½ (Tf – Tl))
where:
TCA =
Time of Closest
Approach
Tf =
Time of first data point
Tl =
Time of last data point
All times are in absolute time reference
(i.e., seconds since 1980).
n
NUMBER OF ITERATIONS
1 to 9
Default value = 0
n
CROSS TRACK ANGLE
00.000 to 33.000 (degrees)
nn.nnn
SECONDARY SOURCE ID
(See www.cospas-sarsat.int)
Default value = 0000
nnnn
NUMBER OF SIDEBANDS
00 to 99
Default value = 00
nn
SWEEP PERIOD
SPSDEV
SPERIOD = 0001 to 9999 (mSec)
Default value = 0000
SPSDEV = 01 to 90 (mSec)
Default value = 00
nnnn
nn
NUMBER OF POINTS or
BURSTS
01 to 99
Default value = 00
(Set to 99 if value exceeds 99.)
nn
BEACON ID
15 Hex characters
Per section “Beacon Identification” of
document C/S A.001
hhhhhhhhhhhhhhh
FGB 406 MESSAGE
(See document C/S T.001)
30 Hex Characters (Bits 25-144)
h....[30]....h
DDR/SERVICE AREA
PS FLAG
MCC Country Code = 100 to 999
Position Status (PS) Flag:
“+” in A and B = No Confirmed
Position,
“+” = Confirmed A, B, or DOA or
Non-Image Unconfirmed A or B
Position,
snnn
B-6
MF \#
NAME
CONTENT
CHARACTER TEXT
“-” = Incorrect A, B or DOA, or
Unconfirmed DOA position
LATITUDE
LAT: + 00.000 to + 90.000 (Degrees)
where:
“+” = North
“-” = South
snn.nnn
LONGITUDE
LONG: + 000.000 to +180.000
(Degrees)
where:
“+” = East
“-” = West
snnn.nnn
ERROR ELLIPSE:
ANGLE
MAJ AXIS
MIN AXIS
000 to 359 (Degrees)
000.1 to 999.9 (km)
000.1 to 999.9 (km)
nnn
nnn.n
nnn.n
PROBABILITY
01 to 99 (%)
nn
NEXT TIME OF VISIBILITY
(Same as MF \#3)
Default value = all zeroes (0)
(Same as MF \#3)
CONFIDENCE FACTOR
1 to 5
Default value = 9
n
DATA RESIDUAL:
SDEV
TREND
000.0 to 250.0 (Hz)
Default value = 255.0
000.0 to 250.0 (Hz)
Default value = 255.0
nnn.n
nnn.n
NUMBER OF ORBIT
VECTORS
nn
NUMBER OF PROCEDURE
NAMES
01 to 99
nn
ORBIT TIME
Year = 00 to 99
Day (Julian) = 001 to 366
Hours = 00 to 23 (UTC)
Minutes = 00 to 59
Seconds = 00.000 to 59.999
nn
nnn
nnnn
nn.nnn
B-7
MF \#
NAME
CONTENT
CHARACTER TEXT
ORBIT POSITION
X = + 0000.0000 to + 9999.9999 (km)
Y = + 0000.0000 to + 9999.9999 (km)
Z = + 0000.0000 to + 9999.9999 (km)
snnnn.nnnn
snnnn.nnnn
snnnn.nnnn
ORBIT VELOCITY
X' = +000.00000 to +999.99999
(km/sec)
Y' = +000.00000 to +999.99999
(km/sec)
Z' = +000.00000 to +999.99999
(km/sec)
snnn.nnnnn
snnn.nnnnn
snnn.nnnnn
CALIBRATION TIME
(Same as MF \#34)
(Same as MF \#34)
USO FREQUENCY
0000000.000 to 9999999.999 (Hz)
nnnnnnn.nnn
38a
USO FREQUENCY
00000000.000 to 99999999.999 (Hz)
nnnnnnnn.nnn
COMMAND PROCEDURE
NAME
PRIORITY
Defined by MCC/MCC requirement
R = Routine
E = Emergency
Default value = R
aaaaaaaaaaaa
a
EXECUTE TIME
(Same as MF \#14)
(Same as MF \#14)
NARRATIVE TEXT
69 characters per line, terminated with
“QQQQ” such that message length is
less than 25,000 characters
a……………….a
a………………..a
QQQQ
ENDSIT
LASSIT
LASSIT
ENDMSG
ENDMSG
ENDMSG
ZERO
MERIDIAN
REAL
EARTH
ROTATIONAL
REAL
EQUATO
Z
Y
X
ZERO
MERIDIAN
REAL
EARTH
ROTATIONAL
REAL
EQUATO
Z
Y
X
![Image 1 from page 32](/images/cospas-sarsat/A-series/A002/A002_page_32_img_1.png)
![Image 2 from page 32](/images/cospas-sarsat/A-series/A002/A002_page_32_img_2.png)
![Image 3 from page 32](/images/cospas-sarsat/A-series/A002/A002_page_32_img_3.png)
![Image 4 from page 32](/images/cospas-sarsat/A-series/A002/A002_page_32_img_4.png)
![Image 5 from page 32](/images/cospas-sarsat/A-series/A002/A002_page_32_img_5.png)
![Image 6 from page 32](/images/cospas-sarsat/A-series/A002/A002_page_32_img_6.png)
![Image 7 from page 32](/images/cospas-sarsat/A-series/A002/A002_page_32_img_7.png)
![Image 8 from page 32](/images/cospas-sarsat/A-series/A002/A002_page_32_img_8.png)
![Image 9 from page 32](/images/cospas-sarsat/A-series/A002/A002_page_32_img_9.png)
B-8
MF \#
NAME
CONTENT
CHARACTER TEXT
NUMBER OF SPACECRAFT
01 to 99
nn
MESSAGE TYPE
Heading
1.bbDISTRESSbCOSPAS-SARSATb
aaaaa...a
or
1.bbSHIPbSECURITYbCOSPAS-
SARSATb
aaaaa...a
or
1.bbDISTRESSbTRACKING
bCOSPAS-SARSATb
aaaaa…a
CURRENT MESSAGE
NUMBER
Heading
Current Message Number
2.bbMSGbNOb
nnnnnbb
MCC BEACON REFERENCE
Heading
Reference Message Number
aaaaabREFb
nnnnn
48a
DETECTION TIME &
SPACECRAFT ID
DETECTION TIME
(FGB, other than ELT(DT)s)
SPACECRAFT ID
LAST DETECTION TIME
(FGB, other than ELT(DT)s,
MEOSAR only)
Heading
Day = 01 to 31
Months = (see Appendix B.1)
Year = 00 to 99
UTC – Hours = 00 to 23
Minutes = 00 to 59
LEOSAR or GEOSAR, as appropriate,
followed by either COSPAS xx,
SARSAT xx, GOES xx, INSAT- xx,
GSAT xx, MSG x, ELECTRO-L xx,
LOUCH-5x, [ARKTIKA-M] (see
Appendix B.1),
or
MEOSAR
Format per Detection Time above
bbbbbbbbDETECTEDbATb
nnbaaabnnbnnnnbUTCbBYb
aaaaaab
aaaaaaaaabnn
or
aaaaaab
bbbbbbbbALERTbLASTb
DETECTEDbATb
nnbaaabnnbnnnnbUTCbBYb
B-9
MF \#
NAME
CONTENT
CHARACTER TEXT
48b
DETECTION TIME &
SPACECRAFT ID
DETECTION TIME
(FGB ELT(DT) and SGB)
SPACECRAFT ID
LAST DETECTION TIME
(FGB ELT(DT) and SGB,
MEOSAR only)
Heading
Day = 01 to 31
Months = (see Appendix B.1)
Year = 00 to 99
UTC – Hours = 00 to 23
Minutes = 00 to 59
Seconds = 00 to 59
LEOSAR or GEOSAR, as appropriate,
followed by either COSPAS xx,
SARSAT xx, GOES xx, INSAT- x,
GSAT xx, MSG x, ELECTRO-L,
LOUCH-5, [ARKTIKA-M] (see
Appendix B.1),
or
MEOSAR
Format per Detection Time above
bbbbbbbbDETECTEDbATb
nnbaaabnnbnnnnnnbUTCbBYb
aaaaaaab
aaaaaaaaabnn
or
aaaaaab
bbbbbbbbALERTbLASTbDETECTE
DbATbnnbaaabnnbnnnnnnbUTCbBY
b
DETECTION
FREQUENCY
Heading
The actual detection frequency
(See Appendix B.1 for default values)
bbbbDETECTIONbFREQUENCYb
406.nnnnbMHZ
50a
BEACON MESSAGE
INFORMATION
Heading
(See Appendix B.1)
3.bbBEACONbMESSAGEbINFORM
ATION
50b
COUNTRY OF BEACON
REGISTRATION
COUNTRY NAME
Heading
Country Code / 10-character
abbreviation of Country (see list at
www.cospas-sarsat.int)
bbbbCOUNTRYbOFbBEACONb
REGISTRATIONb
nnn/aaaaaaaaaa
TYPE OF BEACON
Heading
(See Appendix B.1)
bbbbBEACONbTYPEb
aaaaaaaaaaaaaaa
IDENTIFICATION
(See document C/S T.001 and
C/S T.018)) or unknown unidentified
Modified-Baudot Code character = “?”
aaaaaaaaa
or
aaaaaaa/n
EMERGENCY CODE
Heading
(See document C/S T.001) or NIL
bbbbEMERGENCYbCODEb
aaaaaaaaaaaaaaa
ALERT POSITION
INFORMATION
Heading
4.bbALERTbPOSITIONb
INFORMATION
B-10
MF \#
NAME
CONTENT
CHARACTER TEXT
Note: If the latitude is exactly 90
degrees (North or South) or if the
longitude is exactly 180 degrees
(East or West) for a Confirmed,
DOA or Doppler Position, then the
corresponding value for minutes
must be exactly 00.0.
54a
MCC REFERENCE
POSITION
MCC REFERENCE
LATITUDE
MCC REFERENCE
LONGITUDE
Heading
LAT
00 to 90 (Degree)
0 to 59.9 (Minutes)
N or S (North or South)
LONG
000 to 180 (Degree)
00.0 to 59.9 (Minutes)
E or W (East or West)
bbbbbbbbMCCbREFERENCEb-b
nnbnn.nba
bbnnnbnn.nba
54b
A POSITION AND
PROBABILITY
A LATITUDE
A LONGITUDE
A PROBABILITY
Heading
(As in MF \#54a)
(As in MF \#54a)
01 to 99 (%)
bbbbbbbbDOPPLERbAb-b
nnbnn.nba
bbnnnbnn.nbabbbb
PROBbnnbPERCENT
54c
B POSITION AND
PROBABILITY
B LATITUDE
B LONGITUDE
B PROBABILITY
Heading
(As in MF \#54a)
(As in MF \#54a)
(As in MF \#54b)
bbbbbbbbDOPPLERbBb-b
nnbnn.nba
bbnnnbnn.nbabbbb
PROBbnnbPERCENT
54d
DOA POSITION AND
ALTITUDE
DOA LATITUDE
DOA LONGITUDE
DOA ACCURACY
DOA ALTITUDE
Heading
(As in MF \#54a)
(As in MF \#54a)
Use of MF \#89, rounded up
000.00 to “UNKNOWN”
If greater than to 277.8 km, then
value = “OVER 150 NMS”
Altitude (metres)
(Note: no information on DOA Altitude
shall be provided for this message field
until further notice; see Appendix B.1)
bbbbbbbDOAb-b
nnbnn.nba
bbnnnbnn.nbabbbb
ESTIMATEDbERROR
bnnnbNMS
ALTITUDEbnnnnnbMETRES
B-11
MF \#
NAME
CONTENT
CHARACTER TEXT
54e
GNSS POSITION,
TIME OF UPDATE
AND ALTITUDE
GNSS LATITUDE
GNSS LONGITUDE
TIME OF UPDATE
ALTITUDE
Heading
(As in MF \#54a /up to 59.99 min)
(As in MF \#54a /up to 59.99 min)
Time of Update
Altitude
bbbbbbbbGNSSb-b
nnbnn.nnba
bbnnnbnn.nnbabbbb
(Value per Appendix B.1)
(Value per Appendix B.1)
54f
DOA SPEED
SPEED ESTIMATE
SPEED ESTIMATION
METHOD (aaa):
IST: instantaneous
AVE: Average
UKN: Unknown
(Default value = UKN)
COURSE (nnn):
Angle in degrees (clockwise)
between the direction in which the
horizontal speed is pointing and the
true North
999 -> “UNKNOWN”
HORIZONTAL SPEED
(nnn.n):
Horizontal speed expressed in m/s
999.9 -> “UNKNOWN”
VERTICAL SPEED
(snnn.n):
Vertical speed, expressed in m/s
(positive going up)
+999.9 -> “UNKNOWN”
ESE (nnn.n):
Expected speed error, in m/s (999.9
for default)
Note: no information shall be provided
for this message field until the
associated MEOLUT is commissioned
to provide Speed information.
aaab
nnnbDEGb
nnn.nb
snnn.nb
nnn.nbERRORb
SOURCE OF GNSS
POSITION DATA
Heading
(See Appendix B.1)
bbbbbbbbGNSSbPOSITIONb
PROVIDEDbBYb
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
Not Used
(Previously Next Pass/Expected Data
Times)
57a
BEACON HEX ID
Heading
(See Appendix B.1)
bbbbHEXbIDb
hhhhhhhhhhhhhhhbb
B-12
MF \#
NAME
CONTENT
CHARACTER TEXT
57b
HOMING SIGNAL
Heading
(See Appendix B.1)
bbbbHOMINGbSIGNALb
aaaaaaaaaa
ACTIVATION TYPE
Heading
(See Appendix B.1)
bbbbACTIVATIONbTYPEb
aaaaaaaaa
BEACON NUMBER
Heading
(See Appendix B.1)
bbbbBEACONbNUMBERbON
bAIRCRAFTbORbVESSELb
aaa
OTHER ENCODED
INFORMATION
(See Appendix B.1)
aaa.........a
61a
OTHER INFORMATION
(GENERAL)
Heading
(See Appendix B.1)
5.bbOTHERbINFORMATIONb
aaa.......a
61b
HEX ID
(BEACON OPERATIONAL
CHARACTERISTICS)
Heading
(See Appendix B.1)
3.bbHEXbIDbh..[12]…hbh…[11]..h
61c
TAC DATA
(BEACON OPERATIONAL
CHARACTERISTICS)
Heading
(See Appendix B.1)
4.bbCHARACTERISTICSbFORbTA
Cb
nnnnn
REMARKS
Heading
(See Appendix B.1)
6.bbREMARKSb
aaa.......a
END OF MESSAGE
Heading
ENDbOFbMESSAGE
SARR FREQUENCY
CALIBRATION OFFSET
-9999.999 to +9999.999 (Hz)
snnnn.nnn
SARR FREQUENCY.
CALIBRATION DRIFT
-99.999 to +99.999 (Hz/day)
Default value = +00.000
snn.nnn
TIME OF SARR
FREQUENCY
CALIBRATION
DETERMINATION
(Same as MF \#3)
(Same as MF \#3)
UPLINK TOA
Year = 00 to 99
Day (Julian) = 001 to 366
Hours =
00 to 23 (UTC)
Minutes = 00 to 59
Seconds = 00.000000000 to
59.999999999
nn
nnn
nnnn
nn.nnnnnnnnn
UPLINK FOA
406000000.000 to 406100000.000 (Hz)
nnnnnnnnn.nnn
B-13
MF \#
NAME
CONTENT
CHARACTER TEXT
TIME OFFSET
0.000000000 to 9.999999999
(sec)
Default value = 0.000000
n.nnnnnnnnn
FREQUENCY OFFSET
-90000.000 to +90000.000 (Hz)
Default value =+99999.999
snnnnn.nnn
ANTENNA ID
00 to 99
nn
C/N0
00.0 to 99.9 (dBHz)
Default value = 00.0
nn.n
BIT RATE
000.000 to 999.999
Default value = 000.000
nnn.nnn
SPARE DATA
FFFF
Default value = 0000
hhhh
SATELLITE POSITION
X= -99999.9999 ->+99999.9999 (km)
Default value = +00000.0000
Y= -99999.9999 ->+99999.9999 (km)
Default value = +00000.0000
Z= -99999.9999 ->+99999.9999 (km)
Default value = +00000.0000
snnnnn.nnnn
snnnnn.nnnn
snnnnn.nnnn
SATELLITE VELOCITY
X= -999.999999 ->+999.999999 (km/s)
Default value = +000.000000
Y= -999.999999 ->+999.999999 (km/s)
Default value = +000.000000
Z= -999.999999 ->+999.999999 (km/s)
Default value = +000.000000
snnn.nnnnnn
snnn.nnnnnn
snnn.nnnnnn
FGB FULL 406 MESSAGE
36 Hex characters
Default value = All zeroes
(Bits 1-144)
(See document C/S T.001)
h...[36].......h
DOA QUALITY FACTOR
000 to 999
Default value = 000
nnn
AVERAGE CARRIER TO
NOISE RATIO
00.00 to 99.99 (dB-Hz)
Default value = 99.99
nn.nn
NETWORKED ANTENNA
CHANNELS
00 to 98
Default value = 99
nn
ANTENNA CHANNELS
01 to 99
Default value = 00
nn
ALTITUDE
00.000000 to 99.999999 (km)
Default value = 99.999999
(above ellipsoid WGS84)
nn.nnnnnn
B-14
MF \#
NAME
CONTENT
CHARACTER TEXT
SATELLITE IDS
Sarsat = 001 to 099
Cospas = 101 to 199
GOES = 201 to 220
Electro-L / Louch-5 / [Arktika-M] =
221 to 240
INSAT / GSAT = 241 to 260
MSG / MTG = 261 to 280
GPS = 300 to 399
Galileo = 400 to 499
Glonass = 500 to 599
BDS = 600 to 699
Default value = 000 (for each of the 17
satellite entries)
Per
Satellite
Status
information
provided at www.cospas-sarsat.int and
System Status information provided in
SIT 605 messages.
For MEOSAR satellites the sequence
within the range corresponds to the
Pseudo Random Noise (PRN) number
for the spacecraft (e.g., GPS PRN 23
would be 323).
nnnbnnnb…bnnn (list of 17 satellites)
QUALITY INDICATOR (and
Footprint Check Status)
00 to 99
Default value = 00
nn
(MEOSAR) TWO-LINE
ELEMENT (TLE) SET
FORMAT – LINE 1
69 characters
aaa…[69]…aaa
(MEOSAR) TWO-LINE
ELEMENT (TLE) SET
FORMAT – LINE 2
69 characters
aaa…[69]…aaa
MEOSAR ORBIT
REFERENCE COORDINATE
SYSTEM
ECEF or ECIb
aaaa
NUMBER OF PACKETS
000 to 999
Default value = 000
nnn
EXPECTED HORIZONTAL
ERROR
000.00 to 999.99 (km)
Default value = 000.00 (Unknown)
999.99 indicates greater than or equal to
999.99 kilometres
nnn.nn
SGB DATA
51 Hex characters
Default value = All Zeroes
h…… [51] ........h
BEACON MESSAGE BCH
ERROR INDICATOR
1 character
0 to 6 (= number of corrected bits)
N = Message not correctable
a
B-15
MF \#
NAME
CONTENT
CHARACTER TEXT
23 HEX BEACON ID
23 Hex characters SGB ID
(per Table “Hex ID Contents” of
document C/S T.018)
Default value = All zeroes
h…… [23] ……h
MEOSAR ANTENNA IDS
000000 to 999999 (for each of the 17
antennas)
(list of 17 antennas over two lines, with
nine antennas on the first line)
Default value = 000000 (for each unused
antenna)
(The antennas are listed in the same
sequence as the satellites in MF \#83)
nnnnnnbnnnnnnbnnnnnn…
(list of 17 antennas)
TAC NUMBER
INFORMATION
First TAC Number
Count of Current TAC numbers
TAC Number Total
TAC Sequence Number
Device Type
If nnn, the number is 001 to 999.
If nnnnnnn, the number is 0000001 to
nnnnnnn
nnn
nnnnnnn
nnnnnnn
a
BEACON MANUFACTURER
NAME
24 characters
aaa…[24]…aaa
BEACON MODEL NAME
24 characters
aaa…[24]…aaa
BEACON DATA FIELD
Up to 64 characters per line, such that
message length is less than 25,000
characters
aaa…[up to 64]…aaa
B-16
APPENDIX B.1 TO ANNEX B
MESSAGE FIELD DEFINITION
MF Message Field Definition
\#
1.
Message Number
If the outgoing message is a retransmission of a previous message, the current message
number will be followed by the message number of the original message.
For message accountability, it is recommended that the outgoing message number be unique
and sequential for each destination. See Appendix B.3 for a suggested algorithm for message
sequence tracking.
2.
Reporting Facility
The identification code corresponding to the Ground Segment Facility sending the current
message.
3.
Message Transmit Time
The time at which the current message is placed on the communication channel by the
reporting agency.
4.
SIT
The Subject Indicator Type corresponding to the format required for the message being sent.
5.
Destination MCC
The identification code corresponding to the destination of the SIT message. For the SIT 915
and 925 messages this is the final destination of the SIT message, for all other SIT messages
this is the MCC receiving the current message.
6.
Spacecraft ID
The satellite identification to which the message data applies.
7.
Orbit Number
The orbit number of the spacecraft designated in MF \#6. If the number exceeds 99,999, then
the last five (5) digits of the actual orbit number are provided; for example, orbit number
100,001 is provided as “00001”.
8.
Number of Alerts with Doppler/DOA Positions
The number of alerts of this SIT format with Doppler or DOA positions, that are included
between the SIT header and the SIT trailer as specified in Table C-1.
B-17
9.
(Not Used - previously “Number of Images Reported”)
10. Number of Alerts without Doppler/DOA Positions
The number of alerts of this SIT format without Doppler or DOA positions, that are included
between the SIT header and the SIT trailer as specified in Table C-1.
11. Source ID
The identification code corresponding to the MCC/LUT Ground Segment Facility that
originally provided the solution data being reported on in the SIT message.
12. Local/Global Flag
Indicates if the reported Doppler location has been obtained from the local mode or from the
global mode of operation. If the Doppler location is a mixture of global and real time data
and the time of the first data point is before the AOS of the LUT, the flag is set as GLOBAL.
Processing Channel
The processing channel used to produce a solution. 406 SARP solutions only use data bursts
processed through the SARP channel on-board the satellite. 406 SARR solutions only use
data bursts relayed through the repeater on-board the satellite. 406 combined SARP and
SARR are solutions where the data bursts or the solutions are combined at the LUT.
406 MHz combined LEO/GEO solutions contain Doppler locations that have been produced
by LEO/GEO processing.
The value for this field shall be computed from the ‘A’ solution.
13. Bias
This value is an estimate of the frequency offset of the computed transmission frequency of
the detected signal from the frequency of 406.025000 MHz.
The transmission frequency is calculated as part of the location processing in a LEOLUT
and a MEOLUT. For GEOSAR alerts bias is given for the last detected burst.
For interference data, Bias is required.
BSDEV
The standard deviation of the bias measurement.
For GEOSAR alerts BSDEV is the absolute value of the difference between the first and last
detected bursts.
A standard deviation of the bias measurement greater than 999 will be limited to 900.0.
For interference data, BSDEV can be defaulted.
Drift
The rate of frequency change of the beacon carrier frequency with time.
A drift rate greater than +/- 99.00 will be limited to +/- 99.00.
For GEOSAR alerts drift is the average frequency drift between the first and last detected
burst (‘+’ if frequency increases verses time).
B-18
The value for this field shall be computed from the ‘A’ solution.
For interference data, Drift can be defaulted.
14. TCA
For LEOSAR Doppler location data, the Time of Closest Approach (TCA) indicates the time
at which the satellite was closest to the beacon. For LEOSAR detect only solutions, the TCA
is the time of the last data point. For LEOSAR alerts, the value for this field shall be
computed from the ‘A’ solution.
For GEOSAR, the TCA field contains the time of the first beacon burst for the alert.
For MEOSAR, the TCA field contains the time associated with this solution, as computed
by averaging the associated TOA measurements; the time of the first burst (MF \#14a) and
the time of the last burst (MF \#14b) are provided separately.
For interference data, MF \#14a and MF \#14b signify respectively the start and the end times
for the interferer signal solution received by the MEOLUT channel and processed by the
MEOLUT.
15. Window Factor
The Window Factor is an indicator of the position of the data points relative to the TCA.
If the TCA is included in the set of data points, then the Window Factor is set to “0”. If the
TCA is not included in the set of data points, then the Window Factor has a range between
“1” and “9”. All values greater than “9” are set to “9”.
For a LEOSAR solution the value for this field shall be computed from the ‘A’ solution.
16. Number of Iterations
The number of times the LUT computer had to process the detected incident data to arrive
at the solution being reported on.
If the number of iterations is greater than 9, it shall be reported as a value of “9”.
For a LEOSAR solution the value for this field shall be computed from the ‘A’ solution.
17. Cross Track Angle
The Cross Track Angle (CTA) is the angle at the centre of the earth, between the satellite
and the beacon at TCA.
For a LEOSAR solution the value for this field shall be computed from the ‘A’ solution.
18. Secondary Source ID (previously: Power Indicator)
For 406-MHz combined LEO/GEO data, the identification code corresponding to the
GEOLUT that originally provided the GEOSAR data for combined processing.
The default value for this field is “0000”.
B-19
19. Number of Sidebands
The number of identified sideband components around the solution curve that have been
removed (filtered out) by the LUT/MCC.
20. Sweep Period
For 406-MHz interferers, use the default value “0000”.
(Previously the time taken by the amplitude modulation (AM) of the 121.5/243 MHz beacon
signal to change from the higher to the lower AM frequency limit.)
SPSDEV
For 406-MHz interferers, use the default value “99”.
(Previously the Sweep Period Standard Deviation, defined as the measured standard
deviation of the sweep period for the solution being reported, computed from the ‘A’
solution.)
21. Number of Points
For data originating from the LEOSAR system: The number of bursts detected by the
LEOLUT for each 406 MHz beacon identification, used to develop a solution. For combined
SARP and SARR, it is the number of unique time-frequency data points after the two
processes have been merged.
For data originating from the GEOSAR system: The number of independent integrations
performed to produce a 406 MHz beacon message as described in document C/S T.009. For
unconfirmed messages, the number of points shall be set to “1". For confirmed messages,
the number of independent integrations shall be reported.
For combined LEO/GEO processing, it is the number of data points used from the LEOSAR
channel in the combined processing.
For LEOSAR Doppler solutions, the value for this field shall be computed from the ‘A’
solution.
For data originating from the MEOSAR system: the number of bursts used to develop the
DOA position or, when no DOA position is provided, the number of bursts associated with
the alert.
The value for this field shall be set to “99” if the ‘Number of Points’ value exceeds 99.
22. Beacon ID
A 15 character hexadecimal representation of the beacon ID per the section titled “Beacon
Identification” of document C/S A.001.
23. FGB Beacon Message
The 406 MHz FGB binary message of the solution, in its ‘un-decoded’ form, shown in the
full 30-hexadecimal character representation. Short format messages are left justified and
zero-filled.
B-20
24. DDR/Service Area
The MCC country code for the individual MCC service area or the MCC country code of
the nodal MCC for the DDR as provided on the Cospas-Sarsat website (www.cospas-
sarsat.int).
Nodal MCCs shall fill this field with the individual service area.
Position Status Flag (PS Flag)
Indicates the position status as confirmed, image, non-image, unconfirmed or incorrect.
For position confirmation messages and messages after position confirmation, “+” indicates
the confirmed position and “-” indicates an incorrect position. For position confirmation
messages, a “-” in both the ‘A’ and ‘B’ Doppler solution, or in the DOA solution, indicates
that the confirmed position is the GNSS (i.e., encoded) position contained in the Beacon
Message.
For messages with Doppler position prior to position confirmation, a “+” in both the ‘A’ and
‘B’ solution indicates that no position is confirmed. If one (‘A’ or ‘B’) solution is set to “-”
and the other solution is set to “+”, then a “-” indicates that this position is an image
(incorrect) and a “+” indicates that this position is a non-image, as determined by the “406
MHz LEOSAR Image Position Determination” algorithm in Appendix B.2 to Annex B.
Determining that a position is an image prior to position confirmation is optional.
For messages with DOA position prior to position confirmation, a “-” indicates that the
position is unconfirmed.
25. Latitude
The calculated latitude of the solution.
26. Longitude
The calculated longitude of the solution.
27. Error Ellipse
An ellipse centred at latitude (MF \#25) and longitude (MF \#26) and containing the true
location with a 50% probability.
Angle
The orientation to true north of the major axis of the error ellipse, in a clockwise direction.
Major Axis
The half length, in kilometres, of the major axis of the ellipse.
Any half length axis value greater than 999.9 kilometres will be limited to 999.9.
Minor Axis
The half length, in kilometres, of the minor axis of the ellipse.
Any half length axis value greater than 999.9 kilometres will be limited to 999.9.
B-21
28.
Probability
The probability that the corresponding Doppler location reported in the SIT message is the
actual location and not the image location.
29. Next Time of Visibility
The predicted time (predicted Loss of Signal - LOS) at which the next beacon event (in local
mode) for the position being reported will occur. This time is provided by the originating
MCC or a nodal MCC (only if an earlier time is available at the node). The default value of
zeros shall be used when the next time of visibility is not calculated.
30. Confidence Factor
An indication of the accuracy of the calculated solution based on a correlation between a
variety of parameters. It may be calculated by the MCC based on the error estimate provided
in the alert message.
Confidence
Factor No.
Meaning
Within 1.0 nautical mile
Within 5.0 nautical miles
Within 20.0 nautical miles
Within 50.0 nautical miles
Less accurate than the above
Information not available
31. Data Residual
SDEV
The standard deviation of the actual data points to the solution Doppler curve.
A small number is desirable.
TREND
The standard deviation on the time shifted solution Doppler curve.
It is an indication of the curve dispersion and a number higher than SDEV is desirable.
32. Number of Orbit Vectors
The number of orbit vectors (MFs \#34, \#35 and \#36) that are being transmitted in the SIT
message.
33. Number of Procedure Names
The number of SARR or SARP commands that are being transmitted in the SIT message.
34. Orbit Time
The time at which the position (MF \#35) and the velocity (MF \#36) vectors of the satellite,
are valid.
B-22
35. Orbit Position
The position of the satellite in relation to the centre of the earth in X, Y and Z co-ordinate,
in effect at the time specified by MF \#34.
36.
Orbit Velocity
Velocity of the spacecraft relative to the earth-fixed co-ordinate system shown for MF \#35,
expressed in that same co-ordinate system.
37. Calibration Time
The time at which the Ultra-Stable Oscillator (USO) time reference on Sarsat was rolled over
as per MF \#38.
38. USO Frequency
The oscillator frequency that was measured at the time specified in MF \#37.
38a. USO Frequency for SARP-3
The same as MF \#38 above but with an additional integer to accommodate SARP-3
frequencies.
39. Command Procedure Name
The name of the commands to be executed at the time specified by MF \#40 for both SARR
and SARP command messages.
Priority
The indication of urgency for the execution of the spacecraft command procedure.
40. Execute Time
The time at which the command procedure name specified in MF \#39 is to be executed.
41. Narrative Text
The character text to be transmitted as part of SIT message. Always terminated by 2 Carriage
Returns, 1 Line Feed, 4 Qs, 2 Carriage Returns and 1 Line Feed. In SIT 605, 915 and 925
messages, the originating MCC shall identify itself and the final destination MCC(s) in plain
text; in SIT 605 messages, the final destination is “ALL MCCS”.
42. ENDSIT
This field always contains the code “LASSIT” at the end of every SIT message.
43. ENDMSG
This field is inserted at the end of every current message to be transmitted. It will always
follow the “ENDSIT” field (MF \#42) “LASSIT”.
44. Number of Spacecraft
The number of spacecraft for which orbit vectors are being transmitted in the SIT message.
B-23
45. Message Type
For a SIT 985 message, the Message Type shall be provided as “BEACON OPERATIONAL
CHARACTERISTICS”.
For a SIT 185 message, the Message Type shall be provided as three sub-fields in the form
“[Beacon Message Type] COSPAS-SARSAT [Alert Status]”, where:
a)
[Beacon Message Type] is “SHIP SECURITY” for a ship security beacon alert,
“DISTRESS TRACKING” for an ELT(DT) alert, or “DISTRESS” for all other types
of beacons; and
b)
[Alert Status] is the type of alert
-
“POSITION CONFLICT ALERT”
-
“POSITION UPDATE ALERT”
-
“INITIAL ALERT (UNLOCATED)”
-
“INITIAL LOCATED ALERT”
-
“UNRESOLVED DOPPLER POSITION MATCH ALERT”
-
“DOA POSITION MATCH ALERT”\*
-
“NOTIFICATION OF COUNTRY OF BEACON REGISTRATION ALERT”
or “NOCR”
-
“USER CANCELLATION ALERT”**
-
“OTHER INFORMATION UPDATE ALERT”***
-
“UNLOCATED UPDATE ALERT”****
Notes:
\*
Provided when DOA and GNSS (i.e., encoded) position in the alert match for an
ELT(DT). Only applies to ELT(DT)s.
**
Provided when cancellation is confirmed, per document C/S A.001 section
“Cancellation Message Procedures”. Only applies to ELT(DT)s and SGBs.
*** Provided when the message is sent due to an update of the “Other information”
section of the SIT 185 message and without new position information (based on
the SRF Flag definition in C/S A.001 section 4.2.5.4.1 “Tests and Flag Setting
for Special Processing Procedures”).
**** Provided when the message is sent due to a new detection without position
information.
Not all Alert Status values are applicable with all Beacon Message Types. For example, a
Notification of Country of Beacon Registration Alert is not applicable with a Ship Security
message type.
If the alert message is sent because the GNSS (i.e., encoded) position does not meet the
GNSS-to-GNSS position match criterion (per document C/S A.001) and the GNSS position
differs from a previous GNSS position by less than 20 km, then the message type shall
indicate “POSITION UPDATE ALERT”.
B-24
If the first alert that contains location data does not contain position conflict, or a DOA
position match (ELT(DT) only), then the message type shall indicate “INITIAL LOCATED
ALERT”.
46. Current Message Number
The message number assigned to this message by the transmitting MCC.
47. MCC Beacon Reference
This reference is a unique designator supplied by the MCC to identify all messages sent for
that beacon.
48. Detection Time & Spacecraft ID
The detection time is TCA (as defined at MF \#14) and abbreviation for months is as per table
below.
For LEOSAR and GEOSAR alerts, the time is followed on the same line by “LEOSAR” or
“GEOSAR”, as appropriate, and the identity of the LEOSAR or GEOSAR satellite which
provided the alert data.
For MEOSAR alerts, the time of the first burst is provided and is followed on the same line
by “MEOSAR”. For MEOSAR alerts the time of the last burst shall be included with the
prefix “ALERT LAST DETECTED AT”.
Abbreviation
Month
Abbreviation
Month
JAN
January
JUL
July
FEB
February
AUG
August
MAR
March
SEP
September
APR
April
OCT
October
MAY
May
NOV
November
JUN
June
DEC
December
49. Detection Frequency
For FGBs, the actual beacon detection frequency value shall be reported if available. If no
FGB detection frequency is available (e.g., in a LEOSAR solution without Doppler location),
the value “406 MHZ” shall be reported (i.e., no decimals).
For SGBs, the actual beacon detection frequency value shall be reported if available. If no
SGB detection frequency is available (e.g., in a MEOSAR solution without a DOA position),
the value “406.05 MHZ” shall be reported (i.e., only two decimals).
B-25
50a. Beacon Message Information
Key information about the beacon derived from the beacon message. If the Beacon Message
is invalid per document C/S A.001, section “Alert Message Validation (Filtering Anomalous
Data)” – then:
a)
the warning “DATA DECODED FROM THE BEACON MESSAGE IS NOT
RELIABLE” shall be included in SIT 185 message (if the associated beacon Id does
not match a previous valid beacon Id, per document C/S A.001, section referenced
above); or
b)
the warning “NEW BEACON MESSAGE IS NOT RELIABLE. BEACON
MESSAGE DATA PROVIDED FROM A PREVIOUS RELIABLE BEACON
MESSAGE” shall be included in SIT 185 message (if the associated beacon Id
matches a previous valid beacon, per document C/S A.001, section referenced
above).
For any beacon message information field that is part of the associated section per Table C-
3, the data line may be omitted if the value is “NIL”.
50b. Country of Beacon Registration
Three-numeric characters of the Country Code followed by the ten-character abbreviation of
the country where the detected beacon is registered as defined on the Cospas-Sarsat website
(www.cospas-sarsat.int).
Enter “NIL” if the Beacon Message is invalid per document C/S A.001, section “Alert
Message Validation (Filtering Anomalous Data)”.
Enter “N/A” (i.e., not available) if the Beacon Message contains a Country Code in the form
“97A” (see document C/S A.001 ”Determination of Country Code for Beacons with Country
Codes <200 or >780” for further details).
51. Type of Beacon
Beacon type information as per table below and produced from beacon information by the
MCC. Otherwise, provide information for beacon type as described below.
Enter “NIL” if the Beacon Message is invalid per document C/S A.001, section “Alert
Message Validation (Filtering Anomalous Data)”.
Enter “BEACON TYPE”, then:
For FGBs:
FGB Protocol
Beacon Type in SPOC/RCC Message
Standard Location protocol:
“STANDARD LOCATION – ” followed by
Aviation
ELT - AIRCRAFT SERIAL NO
ELT - AIRCRAFT 24-BIT ADDRESS
ELT - AIRCRAFT OPERATOR DESIGNATOR
OPERATOR SERIAL NO
Maritime
EPIRB - SERIAL NO
B-26
EPIRB - MMSI ALL 9 DIGITS
Personal Locator Beacon
PLB - SERIAL NO
Ship Security
SHIP SECURITY - MMSI ALL 9 DIGITS
National Location protocol:
“NATIONAL LOCATION – “followed by:
Aviation
ELT - SERIAL NO
Maritime
EPIRB - SERIAL NO
Personal Locator Beacon
PLB - SERIAL NO
Return Link protocol:
Aviation
ELT (RETURN LINK) - SERIAL NO
Maritime
EPIRB (RETURN LINK) - SERIAL NO
EPIRB (RETURN LINK) MMSI - ALL 9
DIGITS
Personal Locator Beacon
PLB (RETURN LINK) - SERIAL NO
Distress Tracking ELT protocol:
“ELT DISTRESS TRACKING” followed by:
24-BIT AIRCRAFT ADDRESS
ELT - SERIAL NO
AIRCRAFT OPERATOR DESIGNATOR
OPERATOR SERIAL NO
User or User Location protocol:
“USER” or “USER LOCATION” - followed by:
Maritime
EPIRB USER
MMSI - ALL 9 DIGITS
RADIO CALLSIGN
Radio Call Sign
EPIRB USER
RADIO CALLSIGN
Aviation
ELT USER
AIRCRAFT REGISTRATION
Serial protocol:
“SERIAL USER” or “SERIAL USER LOCATION”
followed by:
(a) Aviation
ELT - AIRCRAFT SERIAL NO
(b) Maritime (Float-Free)
EPIRB (FLOAT FREE) -
SERIAL NO
(c) Maritime (Non Float-Free)
EPIRB (NON FLOAT FREE) -
SERIAL NO
(d) Personal Locator Beacon
PLB SERIAL NO
(e) Aircraft 24-Bit Address
ELT - AIRCRAFT 24-BIT ADDRESS
(f) Aircraft Operator Designator
ELT - AIRCRAFT OPERATOR DESIGNATOR
OPERATOR SERIAL NO
(g) Not assigned
UNKNOWN
Spare
UNKNOWN
Test
TEST
B-27
For SGBs:
SGB – [TYPE-1] [TEST]
Where “TYPE-1” is:
“EPIRB”,
“ELT”, followed by “DISTRESS TRACKING” for ELT(DT), or
“PLB”.
Enter “TEST” if SGB message bit 43 = 1. Provide the aircraft or vessel ID and associated
Type as available using the format specified for FGBs. TAC is the Cospas-Sarsat type
approval certificate number.
“[Aircraft/Vessel ID Type and Aircraft/Vessel ID]”
“TAC [XXXXX] SERIAL NO. [YYYYY]” where [XXXXX] is the TAC number,
and [YYYYY] is the Serial number.
For FGBs and SGBs:
Every vessel/aircraft identifier and Aircraft Operator relevant to beacon type available in the
FGB or SGB message shall be provided.
If a beacon message contains the value “ZGA” as the Aircraft Operator; then the aircraft
operator designator shall be provided as “ZGA (AIRCRAFT OPERATOR NOT
AVAILABLE)”.
If the SGB message contains identification information on the vessel/aircraft type, then the
vessel/aircraft type shall be provided, and when a secondary vessel/aircraft identifier is
available, an associated title shall be provided, as follows.
VESSEL ID
TYPE
2nd Vessel ID Title
Additional Information
MMSI
EPIRB-AIS ID
(SGB only)
If available, the EPIRB-AIS ID is provided in the format
“97AXXYYYY”, where “97AXX” has to be determined from the
TAC Database and “YYYY” is encoded in the SGB message and
‘zero-left’ filled (e.g., encoded decimal value 123 is shown as
“0123”).
RADIO CALL
SIGN
not applicable
A 2nd Vessel ID is not available.
TAIL NUMBER
not applicable
A 2nd Vessel ID is not available.
AIRCRAFT 24
BIT ADDRESS
AIRCRAFT
OPERATOR
DESIGNATOR\*
* The 2nd Vessel ID Title and 3-letter aircraft operator designator
(3LD) are provided, when the 3LD is available.
AIRCRAFT
OPERATOR
AIRCRAFT
OPERATOR
SERIAL NUMBER
The serial number for the Aircraft Operator.
B-28
SYSTEM TEST
not applicable
(national use only)
Alerts for System test beacons are normally not sent to SPOCs,
but may be sent as part of a controlled system test. National use
information encoded in the SGB message Vessel ID field may be
included.
If the registration marking corresponding to the 24-bit address is known, it shall be given. If
the registration marking is unknown, the full 24-bit address shall be given as a six-character
hexadecimal number. For protocol containing the aircraft 24-bit address, the country which
assigned the 24-bit address shall be indicated. If the country that assigned the 24-bit address
is unknown, this value shall be set to “UNKNOWN”.
Note: The data line for this message field may be omitted if the value is “NIL”.
52. Identification
The identification information as described in the Cospas-Sarsat beacon specifications per
documents C/S T.001 and C/S T.018.
Enter “NIL” if the Beacon Message is invalid per document C/S A.001, section entitled
“Alert Message Validation (Filtering Anomalous Data)”.
Note: The data line for this message field may be omitted if the value is “NIL”.
53. Emergency Code
The emergency code as indicated by the beacon coding as described in the Cospas-Sarsat
beacon specification.
Enter “NIL” if the Beacon Message is invalid per document C/S A.001, section entitled
“Alert Message Validation (Filtering Anomalous Data)”.
Note: The data line for this message field may be omitted if the value is “NIL”.
54. Alert Position Information
Alert detection information (including detection time and satellite) and position information
associated with the MCC reference position, A & B Doppler positions, DOA position and
the GNSS (i.e., encoded) position as appropriate. Any data line for position (e.g., MCC
reference position, DOA position) may be omitted if no associated position is available for
the data line.
54a. MCC Reference Position
Latitude and longitude of the MCC reference position. This position may be formed by a
merge of matching positions, which may be based on a weighting factor assigned to each
matching position.
See section “Confirmation of Beacon Positions” in document C/S A.001 and
section “General Principle / Confirmation” in document C/S G.007.
Note: The data line for this message field may be omitted if the value is “NIL”.
B-29
54b. A Position & Probability
The latitude and longitude of the A Doppler Position and the percentage probability that the
A Position is the actual position of the incident. If the A Position (but not the B position)
matches the MCC reference position, per the Position Matching criteria specified in
document C/S A.001, then the A Probability and/or the B Position information (including
the B Probability) may be omitted from the message.
Note: The data line for this message field may be omitted if the value is “NIL”.
54c. B Position & Probability
Same as MF \#54b above but for B Position.
54d. DOA Position, Accuracy and Altitude
Latitude and longitude of the DOA position with expected accuracy (i.e., estimated error) in
nautical miles. The accuracy uses the value of the expected horizontal error, rounded up. If
the expected horizontal error has the default value of “000.00”, the accuracy1 is
“UNKNOWN”. If the expected horizontal error is greater than 277.8 km (150 NM), the
accuracy is shown as “OVER 150 NMS”.
(1) If the reporting MEOLUT is not commissioned to meet MEOSAR IOC requirements for DOA
position accuracy and the reliability of the EHE as specified in document C/S T.020, the expected
horizontal error shall be defaulted in MF \#54d (text set to “UNKNOWN”). The MEOLUT capability
to provide the EHE reliably shall be configured in the MCC separately for FGBs and SGBs.
The altitude of the DOA position is provided from the mean sea level in metres. The DOA
altitude is not verified as part of MEOLUT commissioning and shall be set to “NIL” until
further notice2.
(2) As a future enhancement, the altitude of the DOA position could be provided when a related
MEOLUT requirement is specified in documents C/S T.019 and C/S T.020, the MEOLUT is
appropriately commissioned, and the altitude (MF \#82) does not contain a default value of
“99.999999”.
Note: The data line for this message field may be omitted if the value is “NIL”.
54e. GNSS Position, Time of Update and Altitude
Latitude and longitude of GNSS (i.e., encoded) position. Enter “NIL” if the Beacon Message
is invalid per document C/S A.001, section entitled “Alert Message Validation (Filtering
Anomalous Data)” or if the GNSS position is not provided.
For FGBs:
If the GNSS position is provided, then:
a)
if an ELT(DT), set the Time of Update to:
“UPDATE TIME WITHIN [AAAA] OF DETECTION TIME” where
[AAAA] is:
-
“0 - 2 SECONDS”,
-
“2 - 60 SECONDS”, or
B-30
-
“1 MINUTE TO 4 HOURS”,
based on bits 113 to 114;
b)
otherwise, set the Time of Update to “UPDATE TIME WITHIN 4 HOURS
OF DETECTION TIME” for an FGB.
If location data is present in PDF-1 for an FGB ELT(DT) location protocol, then information
shall be provided on the GNSS position altitude based on the usability of PDF-2 and bits
109-112, as follows:
-
“ALTITUDE OF GNSS LOCATION LESS THAN 400 METRES (1300
FEET)”,
-
“ALTITUDE OF GNSS LOCATION BETWEEN [XXXX1] AND [YYYY1]
METRES (BETWEEN [XXXX2] AND [YYYY2] FEET)”, where [XXXX1]
and [YYYY1] are the values provided in document C/S T.001 and [XXXX2] and
[YYYY2] are the corresponding values rounded to the nearest hundreds of feet,
-
“ALTITUDE OF GNSS LOCATION GREATER THAN 10000 METRES
(32800 FEET)”, or
-
“ALTITUDE OF GNSS LOCATION NOT AVAILABLE”.
For SGBs:
The following information about the GNSS location shall be indicated, if available, using
data from the beacon message:
-
For an ELT(DT), “TIME OF GNSS POSITION UPDATE:” followed by the time
of the GNSS position update, per format specified for MF \#48b,
-
“TIME SINCE GNSS LOCATION GENERATED: [nnnn] MINUTES” if the
value < 2046,
or
“TIME SINCE GNSS LOCATION GENERATED: 2046 MINUTES OR
MORE” if the value = 2046, and
-
“ALTITUDE OF GNSS LOCATION: [nnnnn] METRES ([yyyyyyy]
FEET)” where the value in feet is rounded to the nearest foot.
Note: The data line for this message field may be omitted if the value is “NIL”.
54f. DOA Speed
Estimated speed for DOA position. The speed estimates field provides the independently
estimated course in degrees, horizontal speed in m/s, vertical speed in m/s and expected
speed error in m/s.
Note: no information shall be provided for this message field until the associated MEOLUT
is commissioned to provide DOA Speed information.
B-31
55. Source of GNSS Position Data
This indicates whether the GNSS (i.e., encoded) position data was provided to the beacon
by an internal or external device. Enter “NIL” if the Beacon Message is invalid per document
C/S A.001, section entitled “Alert Message Validation (Filtering Anomalous Data)”.
Note: The data line for this message field may be omitted if the value is “NIL”.
56. (Not used – previously “Next Pass / Expected Data Times”)
57a. Beacon HEX ID
Hexadecimal representation of beacon identification code per the section titled “Beacon
Identification” of document C/S A.001 (15 characters for an FGB or 23 characters for an
SGB) and type of homing signal as per table below.
The last 11 characters of the 23 character hexadecimal identification code shall be provided
with a space after the first 12 characters. Information is taken from the Beacon Message
(reference MF \#23, MF \#77 or MF \#90) by the MCC.
If the Beacon Message of an FGB is invalid per document C/S A.001, section entitled “Alert
Message Validation (Filtering Anomalous Data)”, then the fifteen-character hexadecimal
representation shall be based on bits 26 - 85 of the Beacon Message with no bits defaulted.
57b. Homing Signal
Interpretation
Term:
Meaning:
“NIL”
no homing transmitter or, for SGB only, no homing device is
functional after beacon activation.
“121.5”
121.5 MHz ELT/EPIRB signal in addition to 406 MHz (FGB).
“MARITIME”
9 GHz Search and Rescue Radar Transponder (SART) in addition
to 406 MHz (FGB).
“OTHER”
a nationally assigned signal has been included in the beacon
(FGB).
“NIL OR NOT 121.5”
no homing transmitter or homing transmitter other than 121.5
MHz (FGB: National, Standard or RLS Location Protocol).
“YES”
SGB homing is active (after beacon activation) or SGB homing
device is present (on beacon activation).
For SGBs, additional information may be provided based on the TAC number.
Note: The data line for this message field may be omitted if the value is “NIL”.
58. Activation Type
Type of beacon activation for USER protocols only (i.e., FGB non-location protocols):
-
“MANUAL”
if Bit 108 is set to “0”
B-32
-
“AUTOMATIC OR MANUAL” if Bit 108 is set to “1”
For Ship Security (Standard Location Protocol), enter “MANUAL”.
If otherwise available using data from the beacon message, the activation method of the
beacon shall be indicated as either:
-
“MANUAL”,
-
“AUTOMATIC BY BEACON” \*,
-
“AUTOMATIC BY BEACON (G-SWITCH/PROBABLE CRASH)” **,
-
“AUTOMATIC BY EXTERNAL MEANS (AVIONICS)” **,
\*
Does not apply to ELTs and ELT(DT)s.
**
Only applies to ELTs and ELT(DT)s,
If no information is available in the current alert, then the activation type is provided from
the most recent alert (based on detect time) with available information. Enter “NIL” if no
information is available or the Beacon Message is invalid per document C/S A.001, section
entitled “Alert Message Validation (Filtering Anomalous Data)”.
Note: The data line for this message field may be omitted if the value is “NIL”.
59. Beacon Number
Beacon number on the vessel or aircraft, with the first beacon on the vessel or aircraft
designated as “0”. Information is determined by decoding the 406 MHz message.
Enter “NIL” if no information is available or the Beacon Message is invalid per document
C/S A.001, section entitled “Alert Message Validation (Filtering Anomalous Data)”.
Note: The data line for this message field may be omitted if the value is “NIL”.
60. Other Encoded Information
Other information decoded from the Beacon Message as determined by the servicing MCC.
Could include such information as Cospas-Sarsat type approval certificate (TAC) number,
resolution of the GNSS position data, or data according to national assignment. If the TAC
number is provided, it shall be preceded by “TAC”. Note that the TAC number is provided
for SGBs as part of User Class of Beacon (MF \#51).
For FGBs:
When GNSS position data is present, the degree of uncertainty (i.e., the maximum possible
difference between the GNSS position processed by the beacon and the GNSS position
transmitted in the SIT 185 message) shall be provided as follows:
For user location protocol beacons when location data is present in PDF-2 enter:
−
“GNSS POSITION UNCERTAINTY PLUS-MINUS 2 MINUTES OF
LATITUDE AND LONGITUDE”.
For Standard, National, Return Link Service (RLS) and ELT(DT) location protocol beacons
when location data is present in PDF-2 enter:
B-33
−
“GNSS POSITION UNCERTAINTY PLUS-MINUS 2 SECONDS OF
LATITUDE AND LONGITUDE”.
For standard location protocol beacons when location data is present in PDF-1 and missing
in PDF-2 enter:
−
“GNSS POSITION UNCERTAINTY PLUS-MINUS 30 MINUTES OF
LATITUDE AND LONGITUDE”.
For national location protocol beacons when location data is present in PDF-1 and missing
in PDF-2 enter:
−
“GNSS POSITION UNCERTAINTY PLUS-MINUS 4 MINUTES OF
LATITUDE AND LONGITUDE”.
For RLS and ELT(DT) location protocol beacons when location data is present in PDF-1
and missing in PDF-2 enter:
-
“GNSS POSITION UNCERTAINTY PLUS-MINUS 15 MINUTES OF
LATITUDE AND LONGITUDE”.
For SGBs:
If the SGB has TWC capability, for each Initial Question (see document C/S T.018) where
an answer has been provided via the TWC rotating field, enter the TWC Question and its
TWC Answer. For example:
-
“TWC QUESTION: HOW MANY PEOPLE NEED HELP?”.
-
“TWC ANSWER: 2-4”.
If the SGB has TWC capability, and if the encoded Questions-Answers-and-Instructions
Database Version ID is not recognized at the MCC level for any reason, enter:
-
“TWC QUESTIONS, ANSWERS AND INSTRUCTIONS DATABASE
UNKNOWN”.
If an SGB lacks GNSS position capability, enter:
-
“BEACON DOES NOT HAVE GNSS POSITION CAPABILITY”.
When GNSS location data is present, the degree of uncertainty shall be provided by:
- “GNSS POSITION UNCERTAINTY PLUS-MINUS 10 METRES”.
Other information shall be indicated, if available, using data from the beacon message:
-
“ELAPSED TIME SINCE ACTIVATION: [nn] HOURS” if the value < 63, or
“ELAPSED TIME SINCE ACTIVATION: 63 HOURS OR MORE” if the value
= 63,
where the time since activation is truncated,
and:
-
“REMAINING BATTERY CAPACITY: BETWEEN [nn] AND [nnn]
PERCENT”.
B-34
Note: The data line for this message field may be omitted if the value is “NIL”.
61a. Other Information (General)
Information obtained separately from encoded beacon information such as:
-
reliability indicator for GNSS, DOA or Doppler position data \*,
-
database registry information,
-
optionally the number of packets used to generate the alert (based on MF \#88,
MEOSAR only),
-
optionally the number of MEOSAR satellites used to generate the alert,
-
optionally the LUT identification,
-
people on board,
-
“NIL” if not available.
The statement, “THE [A/B] POSITION IS LIKELY TO BE AN IMAGE POSITION.”
shall be included, as appropriate, per the “LEOSAR Image Position Determination”
algorithm in Appendix B.2 to Annex B.
Notes :for * above:
1:
The warning “RELIABILITY OF DOPPLER POSITION DATA – SUSPECT
DUE TO TECHNICAL PARAMETERS” for DOPPLER 406 MHz solutions shall
be included on the SIT 185 message when at least one of the following criteria
from the alert data values is satisfied:
-
Window factor > 3, or
-
Bias standard deviation > 20 Hz, or
-
The absolute value of the cross track angle is < 1 or > 22, or
-
Position calculated from < 4-point solution.
2:
The warning “RELIABILITY OF DOPPLER POSITION DATA - SUSPECT
DUE TO SATELLITE MANOEUVRE.” shall be included in the SIT 185 message
during the 24-hour period after the manoeuvre, when the maximum expected error
in Doppler location exceeds ten (10) kilometres within 24 hours of the manoeuvre.
See document C/S A.001, section entitled “Scheduled Satellite Manoeuvres”.
3:
The warning “WARNING: AMBIGUITY IS NOT RESOLVED” shall be included
in the SIT 185 message for an Unresolved Doppler Position Match, as defined in
document C/S A.001, section entitled “Position Matching”
4:
The warning “RELIABILITY OF DOA POSITION DATA - SUSPECT DUE
TO SATELLITE FOOTPRINT CHECK” shall be included in the SIT 185 message
if the MCC determines that the DOA position is outside the footprint of any
reporting satellite. See Figure B.2.
B-35
5:
The warning “RELIABILITY OF DOPPLER POSITION DATA - SUSPECT
DUE TO SATELLITE FOOTPRINT CHECK” shall be included in the SIT 185
message if the MCC determines that the DOPPLER position is outside the footprint
of any reporting satellite. See Figure B.2.
The statement “POSITION CONFLICT BASED ON DISTANCE SEPARATION OF
AT LEAST 20 KM” shall be included in the SIT 185 Position Conflict message.
The statement “ELT(DT) POSITION DOES NOT REFERENCE ANY PREVIOUS
POSITION” shall be included if the beacon type is ELT(DT) and the alert contains position
data.
The statement “POSITION UPDATE BASED ON DISTANCE SEPARATION OF 3
TO 20 KM OR FIRST REFINED GNSS POSITION” shall be included in the SIT 185
message if the alert message is sent because:
a)
the GNSS (i.e., encoded) position does not meet the GNSS position match criterion
(per document C/S A.001, section entitled “Position Matching”) and the GNSS
position differs from a previous GNSS position by less than 20 km; or
b)
the new GNSS position is refined, no previous refined GNSS position has been sent,
and a coarse GNSS position was previously sent.
If the alert is an uncorroborated MEOSAR alert, then:
a)
the warning “UNCORROBORATED MEOSAR ALERT” shall be provided in the
SIT 185 message; and
b)
the statement “UNCORROBORATED
MEOSAR
ALERT:
BEACON
IS
REGISTERED” shall be provided in the SIT 185 message, if it is determined that the
associated beacon ID is registered.
Uncorroborated MEOSAR alerts are distributed in accordance with document C/S A.001,
section “Uncorroborated MEOSAR Alerts”.
If cancellation is confirmed as specified in document C/S A.001 section “Cancellation
Message Procedures”, then the statement “CANCELLATION CONFIRMED” shall be
included in the SIT 185 message.
If information on beacon characteristics is available for the Type Approval Certification
(TAC) number encoded in the beacon message, based on relevant information provided at
the Cospas-Sarsat website link [TBD] and in SIT 927 messages, then the following
statement shall be provided: “BEACON CHARACTERISTICS PER TAC DATABASE
PROVIDED IN A SEPARATE MESSAGE”.
If beacon registration information is available and provided in a single SIT 925 message,
then the following statement shall be provided: “BEACON
REGISTRATION
INFORMATION PROVIDED IN A SEPARATE MESSAGE”.
If the LUT identification is provided, it shall include the prefix “LUT ID”, include the 4
digit identification per MF \#11 and optionally include a name for the LUT.
61b. Hex ID (Beacon Operational Characteristics)
B-36
23 character hexadecimal beacon identification per the section titled “Beacon Identification”
of document C/S A.001, with a space provided after the first 12 characters.
61c. TAC Data (Beacon Operational Characteristics)
Based on relevant information provided at the Cospas-Sarsat website and in SIT 927
messages, information on operational characteristics of a beacon associated with the Type
Approval Certification (TAC) number encoded in the beacon message shall be provided as
follows:
-
“CHARACTERISTICS FOR TAC [NNNNNNN]”
-
“- MANUFACTURER:”
-
“- BEACON MODEL:”
-
“- [DATA LINE N]”
-
“- [DATA LINE N]”
where [NNNNNNN] is the TAC number, and each data line [DATA LINE N] contains
one data field, in the format “Field-ID: Field-Value”, per the description of MF \#97 in
this Appendix.
62.
Remarks
Heading for the variable length section of the message. Additional information may be
provided at the discretion of the originating MCC as illustrated in the sample alert messages.
“NIL” if no Remarks are available. Remarks about beacon type (e.g., for ship security
beacons and return link service beacons) are not provided if the Beacon Message is invalid
per document C/S A.001, section entitled “Alert Message Validation (Filtering Anomalous
Data)”.
For ship security alerts, the following should be included:
“This is a ship security alert. Process this alert according to relevant security
requirements.”
For ELT(DT) alerts, the following shall be included:
“THIS
DISTRESS
TRACKING
MESSAGE
IS
BEING
SENT
TO
APPROPRIATE SAR AUTHORITIES” and “PROCESS THIS ALERT
ACCORDING TO RELEVANT REQUIREMENTS”.
For a return link service beacon alert, if the second protected data field of an FGB (bits
107-132) is not usable, or the RLS rotating data field of an SGB is not usable or
available, then indicate:
“THIS BEACON HAS RETURN LINK CAPABILITY”.
For a return link service beacon alert, if the second protected data field of an FGB. or
the RLS rotating data field of an SGB is usable, then provide two lines in the following
format, as described below:
“THIS BEACON HAS [RLS-ID] RETURN LINK CAPABILITY
B-37
RLM
TYPE-[X]
[RECEIVED/CAPABLE]
([AUTO/MANUAL]
ACKNOWLEDGEMENT)”
In line 1, replace “[RLS-ID]” with “GALILEO”, “GLONASS” or blank based on FGB
bits 113 – 114 or SGB bits 167 – 169.
In line 2, replace [X] with “1” or “2”, replace “[RECEIVED/CAPABLE]” with
“RECEIVED”
or
“CAPABLE”,
and
replace
“[AUTO/MANUAL]”
with
“AUTOMATIC” or “MANUAL” based on FGB bits 109 – 112 or SGB bits 161 – 162
and 170 – 171.
Note: TYPE-1 provides “AUTOMATIC” acknowledgement and TYPE-2 provides “MANUAL”
acknowledgment.
For a two-way-communication beacon alert, if the TWC rotating field of an SGB is
usable, then provide the following:
“THIS BEACON HAS [TWC-ID] TWO-WAY-COMMUNICATION CAPABILITY”
In provided line, replace “[TWC-ID]” with, e.g., “GALILEO”, “GLONASS”, etc., or
blank, based on SGB bits 159-161 according to document C/S T.018.
63. End of Message
To indicate to the message recipient that no more information is to come on this message.
64. SARR Frequency Calibration Offset
Difference (in Hz) between the computed frequency produced by the calibration LEOLUT
and the known transmit frequency of a reference beacon.
The SARR frequency calibration offset prepared for distribution to other MCCs shall be
based on the average of a minimum of twenty satellite passes, each of which includes at least
ten data measurements and each of which is associated with a computed location which is
accurate to within three kilometres.
65. SARR Frequency Calibration Drift
Drift (in Hz/day) of the SARR frequency provided by the LEO satellite.
66. Time of SARR Frequency Calibration Determination
Time when a SARR frequency calibration offset for a given LEO satellite was determined
through the procedure described for MF \#64.
See the note under MF \#69.
67. Uplink TOA †
Time that the burst is received at the satellite as calculated by the MEOLUT.
The time reference point (anchor) of a 406 MHz SAR burst for an FGB is the end of the 24th
bit in the message Preamble. The end of the 24th bit is defined as the mid-point of the 50%
phase crossing (i.e., “zero-crossing”) of the mid-transitions of the 24th and 25th bits.
B-38
The time reference point (anchor) of a 406 MHz SAR burst for an SGB is the beginning of
the first chip of the I channel of the local replica that best matches the received signal.
68. Uplink FOA †
Burst frequency measured at the time of the Uplink TOA.
See the note under MF \#70.
69. Time Offset †
This is the calculated difference in time between the reception of the beacon burst at the
satellite and the ground station. Adding this offset to the Uplink TOA provides the time the
burst was received at the ground station.
† If the offset is set to the default value, the Uplink TOA refers to the time when the anchor
point was received at the ground station (i.e., offset is included). The intended use of the
default value pertains to “antenna only” installations that may not have the capacity to
compute this offset.
70. Frequency Offset
This is the offset in frequency due the relative motion between the satellite and the antenna
at the ground station. The frequency offset depends on the downlink frequency (either L-
band or S-band).
The frequency offset is computed using the following formula:
•
∆f = −fd.
Vrad
c for satellites without spectral inversion in payload,
•
∆f = +fd.
Vrad
c for satellites with spectral inversion in payload,
with fd the downlink frequency, Vrad is radial velocity of the satellite relative to the LUT,
and c is the speed of light.
Note: If the offset is set to the default value, the Uplink FOA refers to the frequency measured at the
ground station (i.e., offset is included). The intended use of the default value pertains to “antenna
only” installations that may not have the capacity to compute this offset.
71. Antenna ID
The identification code corresponding to the individual antenna associated with the ground
station that originally provided the burst data being reported in the SIT message.
72. C/N0
The Carrier over Noise Density of the detected burst as determined by the ground station.
73. Bit Rate
The number of bits per second as measured by the ground station.
74. Spare Data
This field consists of four hexadecimal characters as place holders for additional
information.
B-39
75. Satellite Position (Optional)
The X, Y and Z components of the satellite position with respect to the centre of the earth in
kilometres, in the earth-fixed co-ordinate system and in effect at the time specified by
MF \#67.
76. Satellite Velocity (Optional)
The X, Y and Z components of the satellite velocity vectors with respect to the centre of the
earth in kilometres per second, in the earth-fixed co-ordinate system and in effect at the time
specified by MF \#67.
77. FGB Full 406 Message
The 406 MHz binary message of the solution for an FGB, in its ‘un-decoded’ form, shown
in the full 36-hexadecimal character representation. Set to all zeroes for interference data
(SIT 141 message).
78. DOA Quality Factor
A measure of quality associated with the DOA position (algorithm TBD). A higher number
indicates higher quality. Set as applicable to “000” for interference data (SIT 141 message).
79. Average Carrier to Noise Ratio
The average Carrier to Noise Ratio (dB-Hz) as computed from all contributing TOA/FOA
measurements, computed by taking the log of the average of inverse logs of all
measurements.
80. Networked Antenna Channels
Number of networked antenna channels used to generate this alert. “99” indicates that
information is not available for a networked MEOLUT.
If the number of networked antenna channels exceeds 98, the value is set to “98”.
81. Antenna Channels
Number of antenna channels used to generate this alert.
If the number of antennas exceeds 99, the value is set to “99”.
82. Altitude
The calculated altitude of the DOA position relative to an ellipsoid (WGS84), given in
kilometres.
83. Satellite IDs
The list of satellites used to compute the solution for this alert. The satellites are listed in the
same sequence as the antennas specified in MF \#93, when MF \#93 is present. Unused
satellite entries are filled with zeroes.
B-40
84. Quality Indicator
This field is used to provide additional information regarding the quality or quality related
processing performed by MEOLUTs and/or MCCs. If not used it contains the default value
“00”. Otherwise the following values are defined: Bit values are defined to be additive (i.e.,
value 6 = 2 + 4), where the “1” bit is the least significant digit and the “8” bit is the most
significant digit.
MEOLUT Single Burst Location Confirmation performed: position confirmed,
MEOLUT Single Burst Location Confirmation performed: position not confirmed,
DOA Position Outside Satellite Footprint.
85. Two-Line Element (TLE) Set Format - Line 1
1 annnnu nnnnnaaa nnnnn.nnnnnnnn +.nnnnnnnn +nnnnn-n +nnnnn-n n nnnnn
Note: Fields within this Line may contain leading blanks, as described below.
Column
Description
Line Number of Element Data
03-07
Satellite Number \*
Classification (U=Unclassified)
10-11
International Designator (Last two digits of launch year)
12-14
International Designator (Launch number of the year)
15-17
International Designator (Piece of the launch)
19-20
Epoch Year (Last two digits of year)
21-32
Epoch (Day of the year and fractional portion of the day). May contain leading blanks.
34-43
First Time Derivative of the Mean Motion
45-52
Second Time Derivative of Mean Motion (decimal point assumed)
54-61
BSTAR drag term (decimal point assumed)
Ephemeris type
65-68
Element number
Checksum (Modulo 10)
(Letters, blanks, periods, plus signs = 0; minus signs = 1)
* The Satellite Number is provided using the TLE Alpha-5 numbering scheme.
B-41
86. Two-Line Element (TLE) Set Format - Line 2
2 annnn nnn.nnnn nnn.nnnn nnnnnnn nnn.nnnn nnn.nnnn nn.nnnnnnnnnnnnnn
Note: Fields within this Line may contain leading blanks, as described below.
Column
Description
Line Number of Element Data
03-07
Satellite Number\*
09-16
Inclination [Degrees]
18-25
Right Ascension of the Ascending Node [Degrees]
27-33
Eccentricity (decimal point assumed)
35-42
Argument of Perigee [Degrees]
44-51
Mean Anomaly [Degrees]
53-63
Mean Motion [Revs per day]
64-68
Revolution Number at Epoch [Revs]. May contains leading blanks.
Checksum (Modulo 10)
* The Satellite Number is provided using the TLE Alpha-5 numbering scheme.
87. MEOSAR orbit reference coordinate system
Has one of two possible values:
-
“ECEF” - Earth-Centred Earth-Fixed (a coordinate system that rotates with the Earth),
-
“ECI” - Earth-Centred Inertial (a coordinate system that does not rotate with the
Earth).
88. Number of Packets
Number of packets (i.e., distinct TOA/FOA measurements) used to generate this alert. Set
as applicable to “000” for interference data (SIT 141 message).
89. Expected Horizontal Error
The expected horizontal error is a value between 000.00 and 999.99 kilometres and provides
an indication of the accuracy of a DOA location. The value of “999.99” is used if the
expected horizontal error is greater than 999.99 kilometres. The default value of “000.00”
indicates that the expected horizontal error is unknown.
The Expected Horizontal Error is the radius of the circle that is centered on the estimated
location and contains the true location with a probability of 95 2 %.
90. Second Generation Beacon (SGB) Data
51 hexadecimal characters (204 bits) comprised as follows:
B-42
-
bit 1: self-test indicator based on PRN sequence detected by the MEOLUT (0 = normal
mode, 1 = self-test mode),
-
bit 2: 0 (spare),
-
bits 3 to 204: data bits 1 - 202 of the most recent, valid SGB message (i.e., after BCH
correction) for the solution, as described in Figure ”Message content bits” of document
C/S T.018.
The effective time of the beacon data is the last detect time (MF \#14b for MEOLUT data).
If a valid SGB message is not available, the most recent SGB message for the solution is
provided.
91. Beacon Message BCH Error Indicator
Flag to indicate the number of corrected bits in the beacon message. Value is 0 (if the BCH
was correct), 1 to 6 (if the BCH has been corrected) or “N” (if the BCH correction was not
possible). For FGBs, this value refers to the BCH-1 field only, and the maximum number of
corrected bits is limited to 3.
92. 23 Hex Beacon ID
The 23 hexadecimal character SGB ID, per Table “Hex ID Contents” of document
C/S T.018.
93. MEOSAR Antenna IDs
The list of antennas used to compute the solution for this alert. The antenna ID is composed
of the four-digit LUT identifier followed by the two-digit antenna identifier per MEOLUT.
The two-digit antenna identifier shall be set to a unique value for each phased-array antenna.
The antennas are listed in the same sequence as the satellites in MF \#83, so that information
is provided about each satellite antenna pair that contributed to the solution, including local
and networked antennas.
Unused antenna entries are filled with zeroes. If there is not enough space in the message to
add all the local and networked antennas, priority should be given to the local antennas.
94.
C/S Type Approval Certificate (TAC) Number information
The first TAC number is the first TAC number for which information is provided in the
SIT 927 message.
The Count of Current TAC Numbers is the number of consecutive TAC numbers for which
information is provided in the SIT 927 message, so that the last TAC number for which
information is provided in the SIT 927 message = “First TAC Number” + “Count of Current
TAC Numbers” - 1.
The TAC Number Total indicates the total number of TACs for which related database
information is available, including the range of TAC number for which information is
provided in the SIT 927 message.
B-43
The TAC Sequence Number is assigned by the originating MCC and incremented each time
it provides new or updated information about a range of TAC numbers in a SIT 927 message;
this value is maintained when a SIT 927 message is retransmitted or forwarded by any MCC.
Destination MCCs may use the TAC Number Total and TAC Sequence Number to help
determine if their local repository of TAC related information (i.e., their TAC database) is
up to date.
The Device Type indicates the type of device which the TAC range is assigned:
“B” = Beacon,
“A” = Programming Adapter.
The use of Programming Adapters is described in section ‘Programming Adapters’ of
document C/S T.018.
95.
Beacon Manufacturer Name
The name of the beacon manufacturer for the associated TAC number, whether the TAC
number is allocated to a beacon model or to a programming adapter.
96.
Beacon Model Name
The name of the beacon model for the associated TAC number, whether the TAC number is
allocated to a beacon model or to a programming adapter.
97.
Beacon Data Field
Beacon data field narrative text for the associated beacon model. Each data line contains one
data field, in the format “Field-ID: Field-Value”; e.g., “BEACON SUBTYPE: ELT(DT)”.
The data line length is limited to 64 characters, so that associated information can be included
directly in a SIT 185 message data line (69-character limit); 5 characters (i.e., 69 – 64) in the
SIT 185 data line are reserved for alignment. The data field shall contain all relevant
information for the associated TAC number, so that the beacon data field provided in a new
SIT 927 message replaces all beacon data provided in a previous SIT 927 message for a
specific TAC number. Defined data fields are provided below.
Field ID
Allowable Data Values
Remarks
BEACON TYPE ELT, EPIRB, PLB
BEACON
SUBTYPE
For ELTs: (DT), (AF), (AP),
(S), or (AD)
For EPIRBs: FLOAT-FREE or
NON-FLOAT-FREE
If no information is available, then the field
is not provided.
TEMPERATURE
RANGE
Operating
temperature
range,
per
document C/S T.018.
HOMING
Type-1=Power Level, Type-
2=Power Level, Type-n=Power
Level… or “NONE”.
Identify each available type of homing and
the associated power level, where “Type”
is “121.5”, “243”, “406”, “AIS” or
other value. “Power level” is typically
B-44
Field ID
Allowable Data Values
Remarks
Example: “406=25MW,
AIS=20 MW”
provide in milli-watts (e.g., “25 MW”). The
value is “NONE” if no homing capability is
available.
HOMING
AIS ID 97AXXYYYY
(SGB only)
If the beacon has an AIS transmitter, then the
identity “97AXX” is obtained from the TAC
Database. When combined with the AIS
identity “YYYY” contained in the beacon
transmitted message, it provides a complete
AIS ID in the form 97AXXYYYY.
If the field is not provided, it is assumed that
the beacon does not contain an AIS transmitter.
GNSS
RECEIVER
YES, NO
The beacon has a GNSS receiver: “YES”
or “NO”.
If the field is not provided, then it is
assumed that the value is “NO”.
NAT
PROTOCOL
YES, [description]
If national protocol, indicate “YES”
followed by description. If not national
protocol, then the field is not provided.
VOICE
FREQUENCY
NNN.NN MHZ
Voice transmission frequency, if voice
transmission capability is available; if not
available, then the field is not provided.
STROBE
BRIGHTNESS=nn.nn
CANDELA, DUTY-CYCLE=
nn FLASH/MINUTE
If a strobe is available, indicate brightness
and duty cycle; if a strobe not available,
then the field is not provided.
BATTERY
DURATION
NN HOURS
Tested life for battery duration. If no
information is available, then the field is
not provided.
OTHER
Free form description
Other
information
about
beacon
characteristics. If no information is
available, then the field is not provided.
Beacon Characteristics Field Description
B-45
APPENDIX B.2 TO ANNEX B
DETERMINING THE LEOSAR IMAGE POSITION
AND VALIDATING THE SATELLITE FOOTPRINT
The LEOSAR Doppler processing produces two solutions for each satellite pass; a “real”
position corresponding to the actual location of the beacon and an “image” position on the
opposite side of the satellite track. Prior to determining the “real” position of a beacon, it is
possible to use unlocated alert data to determine if one position is an image, as summarised in
Figure B.2.
The LEOSAR image position can be determined using the following inputs:
a)
LEOSAR Doppler alert, including beacon ID, A and B latitude/longitude positions
(defined as Input “I2” in the DDP);
b)
GEOSAR or LEOSAR unlocated alert with beacon ID (defined as Input “I1” in DDP); and
c)
ephemeris data and orbit propagation software, if the unlocated alert originated from a
LEOSAR satellite, or the position of the GEOSAR satellite if the alert originated from a
GEOSAR satellite.
Figure B.1 and the text below document the procedures for MCCs to follow to determine if a
position is inside the footprint of the LEOSAR or GEOSAR satellite at time of detection, and
whether a position is an image.
The process of determining an image position is triggered when a LEOSAR Doppler alert (I2) is
received at the MCC (reference process 1 in Figure B.1) for a beacon which has been previously
detected, but no location information is available (I1). The status of the MCC processing prior to
receiving the LEOSAR Doppler alert must be at Sw1 (i.e., only identification information
available, no location information present). If the status of the MCC processing is not at Sw 1,
then an image position will not be indicated when the alert message is sent by the MCC.
All unlocated alerts on file with a detect time within 60 minutes of the Doppler TCA are
examined (reference 3) to determine if the image position can be determined. For LEOSAR
unlocated alerts the time of the detection, along with orbit propagation software, is used to
determine the sub-satellite position of the LEOSAR satellite at time of detection (reference 4).
For GEOSAR satellites the sub-satellite position is obtained from www.cospas-sarsat.int
(reference 5).
Each of the LEOSAR Doppler positions are analysed to determine if they are within the
GEOSAR or LEOSAR unlocated footprint using the algorithm shown in Figure B.2 and using
the sub-satellite points as input (reference 6). Each unlocated footprint must be analysed before
a position can be determined to be an image.
If one of the LEOSAR Doppler positions is conclusively outside the footprint for at least one
unlocated alert, then it is the image position, as long as the other position is inside the footprint
of every unlocated alert. If neither position is outside of any footprint or each position is outside
of any footprint, then the image position cannot be determined.
B-46
When a position has been determined to be an image, this will be indicated on the alert message
sent by the MCC, as specified in the description of MF \#24 and MF \#61a in Appendix B.1 to
Annex B.
2Figure B.1: Using Unlocated Alerts to Determine and Flag the Image Position
![Image 1 from page 71](/images/cospas-sarsat/A-series/A002/A002_page_71_img_1.png)
B-47
To determine if MEOSAR DOA and/or GNSS (i.e., encoded) position is within the footprint of
the associated MEOSAR satellite(s), the time of the detection, along with orbit propagation
software, is used to determine the sub-satellite position of the MEOSAR satellite at time of
detection. The algorithm to determine this is provided at Figure B.2.
When a DOA or GNSS (i.e., encoded) position has been determined to be outside the footprint
of any reporting MEOSAR satellite, at both the first and last detect times of the associated alert then
the action described in document C/S A.001, section entitled “Alert Message Validation
(Filtering Anomalous Data)” is to be followed.
Input:
lat
estimated position latitude in degrees
lon
estimated position longitude in degrees
llat
sub-satellite point at time of detection, latitude in degrees
llon sub-satellite point at time of detection, longitude in degrees
Emin Minimum elevation angle required (set to -5 degrees)
Constants:
Rg
altitude of satellite (note differences among the various satellite
constellations)
Re
Equatorial radius of earth = 6378 km
ro
Re / (Re + Rg)
PI
3.1415927
Compute:
rlat
=
PI * lat / 180
rlon =
PI * lon / 180
rllat =
PI * llat / 180
rllon =
PI * llon / 180
c
=
sin(rlat) * sin(rllat) + cos(rlat) * cos(rllat) * cos(rllon - rlon)
e
=
( c - ro ) / sqrt (1 - c2 )
E
=
180 * arctan ( e ) / PI
Output: If E Emin then estimated position is within satellite footprint, else
If E Emin then estimated position is outside satellite footprint.
3Figure B.2: Algorithm to Determine if Computed Position is Inside Satellite Footprint
B-48
APPENDIX B.3 TO ANNEX B
SUGGESTED ALGORITHM FOR MESSAGE SEQUENCE TRACKING
The flowcharts in this Appendix define a procedure for the identification of missed messages
through message sequence tracking. The procedure relies on the following data items or structures:
Data Item
Purpose
CurMsgNo
The current message number contained in MF \#1 of the arriving message
PrvMsgNo
The previous message number contained in MF \#1 of the arriving
message
NextExpected
The next message number expected from a given source. This item could
be represented as an array indexed by source: Next Expected [MF \#2] i.e.,
each MCC must maintain a table of Next Expected message numbers –
one such number for each reporting MCC. When a message is received,
the reporting MCC in MF \#2 is used to lookup the appropriate
NextExpected message number from the table.
MissedMsgList
A list of messages that have been identified (by the sequence checking
procedure) as overdue. MCCs may choose to implement this as a single
list of MF \#2: MF \#1 pairs or maintain a separate list for each source.
TimeMissed
The time at which a message was declared “missing” by the message
sequence tracking facility. The message would be added to the
MissedMsgList at that time.
MAX\_MISSING
A configuration constant that limits the number of missed messages that
can be generated by a single sequence check. This minimises the impact
of an MCC unilaterally resetting its message sequence generator to an
arbitrary value. Set to 15.
MAX\_MSGNO
A configuration constant that defines the largest message number before
message number wrap around is to occur. Set to 99999.
MAX\_WAIT\_TIME
A configuration constant that defines the length of time the MCC will wait
for an out of sequence message to arrive before a lost message is declared
(and recovery action initiated). Set to 15 minutes.
The procedure is executed in two threads (parallel streams of execution):
1.
message-checking thread, where each arriving message is subjected to a message
sequence check; and
2.
monitor thread which constantly checks the missed message list for lost messages.
The two threads are represented in separate flowcharts.
B-49
4Figure B.3: Message Sequence Checking Flowchart
(For each message received)
START
PrvMsgNo = 0?
FINISH
CurMsgNo =
NextExpected?
Yes
Extract CurMsgNo and
PrvMsgNo from MF\#1
Use MF\#2 to lookup
NextExpected for source
Set
NextExpected to 1
Set
NextExpected to
CurMsgNo +1
Delete PrvMsgNo
from MissedMsgList
No
CurMsgNo in
MissedMsgList?
CurMsgNo >
NextExpected?
CurMsgNo -
NextExpected >
MAX\_MISSING?
No
No
Yes
Delete CurMsgNo from
MissedMsgList
Yes
MAX\_MSGNO -
NextExpected +
CurMsgNo >
MAX\_MISSING
No
Yes
Yes
CurMsgNo =
MAX\_MSGNO?
For each N
NextExpected to
MAX\_MSGNO
Add entry N to
MissedMsgList
For each N from 1 to
(CurMsgNo -1)
Add entry N to
MissedMsgList
For each N from
NextExpected to
(CurMsgNo -1)
Add entry N to
MissedMsgList
No
Yes
No
Yes
No
Notify Operator
B-50
Monitor MissedMsgList
START
Select next message
from MissedMsgList
age >
MAX\_WAIT\_TIME
?
Calculate age = timeNow -
timeMissed
No
Initiate recovery procedure (e.g.
alert operator)
Declare
message lost!
Delete message from
MissedMsgList
Yes
5Figure B.4: Missed Message List Monitoring Flowchart
– END OF ANNEX B –
C-1
ANNEX C
MESSAGE CONTENT BY SIT
1. MESSAGE TEXT
Cospas-Sarsat messages are uniquely identified by specific Subject Indicator Types (SITs). The
SIT specifies the format and category of content within the message. MCCs process messages
automatically. Therefore, it is mandatory that the structure of the message formats be adhered to,
so that each MCC can route and/or take action as required by the message. Tables C-1, C-2 and
C-3 detail the format of the text for all messages exchanged between the MCCs in terms of
Message Fields (MFs) used.
Once the SIT is known for the desired message, the corresponding column identifies which
Message Field numbers (MF \#) are necessary to produce the message. Annex B is then used to
find the format and the produced message will be similar to those given in the appendices to this
annex.
2. SAMPLE MESSAGE TEXT
For SIT messages depicted in Tables C-1, C-2 and C-3, sample messages are given in Appendix 1
to this Annex. The sample messages in Appendix 1 also indicate the message line that contains the
individual MF \#.
C-2
8Table C-1:
MESSAGE CONTENT
FOR ALERT MESSAGES
MESSAGE
FORMAT
MF
\#
TITLE
SIT NUMBERS
MESSAGE
MESSAGE NUMBER
A
A
A
HEADER
REPORTING FACILITIY
A
A
A
MESSAGE TRANSMIT TIME
A
A
A
SIT
SIT
A
A
A
HEADER
DESTINATION MCC
A
A
A
SPACECRAFT ID
A
A
A
NUMBER OF ALERTS WITH DOPPLER POSITIONS
A
.
.
NUMBER OF ALERTS WITHOUT DOPPLER POSITIONS
.
A
A
SOLUTION
SOURCE ID
A
A
A
HEADER
LOCAL or GLOBAL FLAG and FREQUENCY BAND
A
.
.
BIAS, BSDEV and DRIFT
X
X
X
TCA
A
A
A
WINDOW FACTOR
A
.
.
NUMBER OF ITERATIONS
X
.
.
CROSS TRACK ANGLE
A
.
.
SECONDARY SOURCE ID
X
.
.
NUMBER OF SIDEBANDS
X
.
.
SWEEP PERIOD and SPSDEV
X
.
.
NUMBER OF POINTS
.
A
A
FGB 406 MESSAGE
.
A
A
A DATA
DDR/SERVICE AREA and PS FLAG
A
.
.
LATITUDE
A
.
.
LONGITUDE
A
.
.
ERROR ELLIPSE
A
.
.
PROBABILITY
A
.
.
NEXT TIME OF VISIBILITY
X
.
.
CONFIDENCE FACTOR
A
.
.
DATA RESIDUAL: SDEV and TREND
X
.
.
B DATA
Repeat MF \#s 24 to 31 as required but with data for B Location
A
.
.
Repeat MF \#s 11 to 31 as required, by MF \#8 or \#10 and B DATA as required by
MF \#8
A
A
A
SIT
TRAILER
ENDSIT
A
A
A
MSG
TRAILER
ENDMSG
A
A
A
Note: “A” indicates actual values
“X” indicates default values are allowed.
The underline “__” is an indication where the New Line (NL) code is to be inserted.
C-3
Table C-1 (Cont.):
MESSAGE CONTENT
FOR ALERT MESSAGES
MESSAGE
FORMAT
MF
\#
TITLE
SIT NUMBERS
MESSAGE
MESSAGE NUMBER
A
A
A
HEADER
REPORTING FACILITIY
A
A
A
MESSAGE TRANSMIT TIME
A
A
A
SIT
SIT
A
A
A
HEADER
DESTINATION MCC
A
A
A
NUMBER OF ALERTS WITH DOA POSITIONS
A
.
.
NUMBER OF ALERTS WITHOUT DOA POSITIONS
.
A
A
SOLUTION
SOURCE ID
A
A
A
HEADER
BIAS, BSDEV and DRIFT (FREQUENCY)
A
X
X
14a
TIME OF FIRST BURST (AVERAGE TOA)
A
A
A
14b
TIME OF LAST BURST (AVERAGE TOA)
A
A
A
NUMBER OF BURSTS
X
A
A
FGB FULL 406 MESSAGE
X
A
A
INFO
DDR/SERVICE AREA
A
.
.
LATITUDE
A
.
.
LONGITUDE
A
.
.
DOA QUALITY FACTOR
X
.
.
EXPECTED HORIZONTAL ERROR
X
.
.
AVERAGE C/No
X
X
X
NETWORKED ANTENNA CHANNELS
X
X
X
ANTENNA CHANNELS
X
X
X
ALTITUDE
X
.
.
QUALITY INDICATOR
X
.
.
NUMBER OF PACKETS
X
A
A
ERROR ELLIPSE
A
.
.
SATELLITE IDs
A
A
A
Repeat SOLUTION HEADER and DOA/POSITION INFORMATION as required by MF \#8
Repeat SOLUTION HEADER as required by MF \#10
SIT
TRAILER
ENDSIT
A
A
A
MSG
TRAILER
ENDMSG
A
A
A
Note: “A” indicates actual values
“X” indicates default values are allowed.
The underline “__” is an indication where the New Line (NL) code is to be inserted..
C-4
Table C-1 (Cont.):
MESSAGE CONTENT
FOR ALERT MESSAGES
MESSAGE
FORMAT
MF
\#
TITLE
SIT NUMBERS
MESSAGE
MESSAGE NUMBER
A
A
A
HEADER
REPORTING FACILITIY
A
A
A
MESSAGE TRANSMIT TIME
A
A
A
SIT
SIT
A
A
A
HEADER
DESTINATION MCC
A
A
A
SPACECRAFT ID
A
A
A
NUMBER OF ALERTS WITH DOPPLER POSITIONS
A
.
A
NUMBER OF ALERTS WITHOUT DOPPLER POSITIONS
.
A
.
SOLUTION
SOURCE ID
A
A
A
HEADER
LOCAL or GLOBAL FLAG and FREQUENCY BAND
A
.
A
BIAS, BSDEV and DRIFT
X
X
X
TCA
A
A
A
WINDOW FACTOR
A
.
A
NUMBER OF ITERATIONS
X
.
X
CROSS TRACK ANGLE
X
.
X
SECONDARY SOURCE ID
X
.
X
NUMBER OF SIDEBANDS
.
.
.
NUMBER OF POINTS
A
A
A
FGB 406 MESSAGE
A
A
A
A DATA
DDR/SERVICE AREA and PS FLAG
A
.
A
LATITUDE
A
.
A
LONGITUDE
A
.
A
ERROR ELLIPSE
A
.
A
PROBABILITY
A
.
A
NEXT TIME OF VISIBILITY
X
.
X
CONFIDENCE FACTOR
A
.
A
DATA RESIDUAL: SDEV and TREND
X
.
X
B DATA
Repeat MF \#s 24 to 31 as required but with data for B Location
A
.
A
Repeat MF \#s 11 to 31 as required, by MF \#8 or \#10
A
A
A
Repeat SOLUTION HEADER and DOA/POSITION INFORMATION as required by MF \#8
Repeat SOLUTION HEADER as required by MF \#10
SIT
TRAILER
ENDSIT
A
A
A
MSG
TRAILER
ENDMSG
A
A
A
Note: “A” indicates actual values
“X” indicates default values are allowed.
The underline “__” is an indication where the New Line (NL) code is to be inserted.
C-5
Table C-1 (Cont.):
MESSAGE CONTENT
FOR ALERT MESSAGES
MESSAGE
FORMAT
MF
\#
TITLE
SIT NUMBERS
MESSAGE
MESSAGE NUMBER
A
A
A
HEADER
REPORTING FACILITIY
A
A
A
MESSAGE TRANSMIT TIME
A
A
A
SIT
SIT
A
A
A
HEADER
DESTINATION MCC
A
A
A
NUM. OF ALERTS WITH DOA POSITIONS
A
.
A
NUMBER OF ALERTS WITHOUT DOA POSITIONS
.
A
.
SOLUTION
SOURCE ID
A
A
A
HEADER
BIAS BSDEV and DRIFT (FREQUENCY)
X
X
X
14a
TIME OF FIRST BURST (AVERAGE TOA)
A
A
A
14b
TIME OF LAST BURST (AVERAGE TOA)
A
A
A
NUMBER OF BURSTS
A
A
A
FGB FULL 406 MESSAGE
A
A
A
INFO
DDR/SERVICE AREA and PS FLAG
A
.
A
LATITUDE
A
.
A
LONGITUDE
A
.
A
DOA QUALITY FACTOR
A
.
A
EXPECTED HORIZONTAL ERROR
A
.
A
AVERAGE CARRIER TO NOISE RATIO
X
X
X
NETWORKED ANTENNA CHANNELS
X
X
X
ANTENNA CHANNELS
X
X
X
ALTITUDE
X
.
X
QUALITY INDICATOR
X
.
X
NUMBER OF PACKETS
A
A
A
ERROR ELLIPSE
A
.
A
SATELLITE IDs
A
A
A
Repeat SOLUTION HEADER and DOA/POSITION INFORMATION as required by MF \#8
SIT TRAILER
ENDSIT
A
A
A
MSG TRAILER
ENDMSG
A
A
A
Note: “A” indicates actual values
“X” indicates default values are allowed.
The underline “__” is an indication where the New Line (NL) code is to be inserted.
C-6
Table C-1 (Cont.):
MESSAGE CONTENT
FOR ALERT MESSAGES
MESSAGE
FORMAT
MF
\#
TITLE
MESSAGE
MESSAGE NUMBER
A
A
HEADER
REPORTING FACILITIY
A
A
MESSAGE TRANSMIT TIME
A
A
SIT
SIT
A
A
HEADER
DESTINATION MCC
A
A
SPACECRAFT ID
A
A
NUMBER OF ALERTS WITHOUT DOPPLER or DOA
POSITIONS
A
A
SOLUTION
SOURCE ID
A
A
HEADER
BIAS, BSDEV and DRIFT
X
X
TCA
A
A
NUMBER OF POINTS
A
A
INFO
SGB DATA
A
A
BEACON MESSAGE BCH ERROR INDICATOR
A
A
23 HEX BEACON ID
A
A
Repeat SOLUTION HEADER as required by MF \#10
SIT TRAILER
ENDSIT
A
A
MSG TRAILER
ENDMSG
A
A
Note: “A” indicates actual values
“X” indicates default values are allowed.
The underline “__” is an indication where the New Line (NL) code is to be inserted.
C-7
Table C-1 (Cont.):
MESSAGE CONTENT
FOR ALERT MESSAGES
MESSAGE
FORMAT
MF
\#
TITLE
SIT NUMBERS
336, 338
342, 343, 344
MESSAGE
MESSAGE NUMBER
A
HEADER
REPORTING FACILITY
A
MESSAGE TRANSMIT TIME
A
SIT
SIT
A
HEADER
DESTINATION MCC
A
NUMBER OF ALERTS WITHOUT DOA POSITIONS
A
SOLUTION
SOURCE ID
A
HEADER
BIAS, BSDEV and DRIFT (FREQUENCY)
X
14a
TIME OF FIRST BURST (AVERAGE TOA)
A
14b
TIME OF LAST BURST (AVERAGE TOA)
A
NUMBER OF BURSTS
A
INFO
SGB DATA
A
BEACON MESSAGE BCH ERROR INDICATOR
A
23 HEX BEACON ID
A
AVERAGE C/No
X
NETWORKED ANTENNA CHANNELS
X
ANTENNA CHANNELS
X
NUMBER OF PACKETS
A
SATELLITE IDs
A
MEOSAR ANTENNA IDs
A
Repeat SOLUTION HEADER as required by MF \#10
SIT TRAILER
ENDSIT
A
MSG TRAILER
ENDMSG
A
Note: “A” indicates actual values
“X” indicates default values are allowed.
The underline “__” is an indication where the New Line (NL) code is to be inserted.
C-8
Table C-1 (Cont.):
MESSAGE CONTENT
FOR ALERT MESSAGES
MESSAGE
FORMAT
MF
\#
TITLE
SIT NUMBERS
337, 339
345, 346, 347
MESSAGE
MESSAGE NUMBER
A
HEADER
REPORTING FACILITY
A
MESSAGE TRANSMIT TIME
A
SIT
SIT
A
HEADER
DESTINATION MCC
A
NUMBER OF ALERTS WITH DOA POSITIONS
A
NUMBER OF ALERTS WITHOUT DOA POSITIONS
.
SOLUTION
SOURCE ID
A
HEADER
BIAS, BSDEV and DRIFT (FREQUENCY)
X
14a
TIME OF FIRST BURST (AVERAGE TOA)
A
14b
TIME OF LAST BURST (AVERAGE TOA)
A
NUMBER OF BURSTS
A
INFO
SGB 406 MESSAGE
A
BEACON MESSAGE BCH ERROR INDICATOR
A
23 HEX BEACON ID
A
DDR/SERVICE AREA
A
LATITUDE
A
LONGITUDE
A
DOA QUALITY FACTOR
A
EXPECTED HORIZONTAL ERROR
A
AVERAGE C/No
X
NETWORKED ANTENNA CHANNELS
X
ANTENNA CHANNELS
X
ALTITUDE
X
QUALITY INDICATOR
X
NUMBER OF PACKETS
A
ERROR ELLIPSE
A
SATELLITE IDs
A
MEOSAR ANTENNA IDs
A
Repeat SOLUTION HEADER and DOA/POSITION INFORMATION as required by MF \#8
SIT TRAILER
ENDSIT
A
MSG TRAILER
ENDMSG
A
Note: “A” indicates actual values,
“X” indicates default values are allowed.
The underline “__” is an indication where the New Line (NL) code is to be inserted.
C-9
9Table C-2:
MESSAGE CONTENT FOR
SYSTEM INFORMATION AND NARRATIVE MESSAGES
MESSAGE
FORMAT
MF
\#
TITLE
SIT NUMBERS
MESSAGE
MESSAGE NUMBER
A
A
A
A
A
HEADER
REPORTING FACILITY
A
A
A
A
A
MESSAGE TRANSMIT TIME
A
A
A
A
A
SIT BODY
SPACECRAFT ID
A
.
.
A
.
ORBIT NUMBER
A
.
.
.
.
BEACON ID
.
.
.
.
.
NUMBER OF ORBIT VECTORS
.
.
.
.
.
NUMBER OF PROCEDURE NAMES
.
.
.
A
.
ORBIT TIME
.
.
.
.
.
ORBIT POSITION
.
.
.
.
.
ORBIT VELOCITY
.
.
.
.
.
CALIBRATION TIME
A
.
.
.
.
USO FREQUENCY
A
.
.
.
.
COMMAND PROCEDURE NAME AND PRIORITY
.
.
.
A
.
EXECUTE TIME
.
.
.
A
.
406 MHZ SARR FREQ. CALIB. OFFSET
.
.
.
.
.
406 MHZ SARR FREQ. CALIB. DRIFT
.
.
.
.
.
TIME OF 406 MHZ SARR FREQ. CALIB.
.
.
.
.
.
Repeat MF \#s 39 and 40 for each procedure name (MF \#33)
.
.
.
A
.
Repeat MF \#s 6 to 66 as required by MF \#44
.
.
.
.
.
Narrative text
.
A
A
A
A
SIT TRAILER
ENDSIT
A
A
A
A
A
MSG
TRAILER
ENDMSG
A
A
A
A
A
Note: The narrative text is terminated as specified in MF \#41.
See section 4.1 for size specification.
“A” indicates actual values,
“X” indicates default values are allowed.
The underline “__” is an indication where the New Line (NL) code is to be inserted.
C-10
Table C-2 (Cont.):
MESSAGE CONTENT FOR
SYSTEM INFORMATION AND NARRATIVE MESSAGES
MESSAGE
FORMAT
MF
\#
TITLE
SIT NUMBERS
MESSAGE
MESSAGE NUMBER
A
A
A
A
A
A
A
A
HEADER
REPORTING FACILITY
A
A
A
A
A
A
A
A
MESSAGE TRANSMIT TIME
A
A
A
A
A
A
A
A
SIT
SIT
A
A
A
A
A
A
A
A
HEADER
DESTINATION MCC
A
A
A
A
A
A
A
A
NUMBER OF SPACECRAFT
A
A
A
.
.
SPACECRAFT ID
A
.
A
.
.
.
.
.
INFO
ORBIT NUMBER
A
.
.
.
.
.
.
.
BEACON ID
.
.
.
.
.
A
.
.
NUMBER OF ORBIT VECTORS
A
.
.
.
.
.
.
.
NUMBER OF PROCEDURE NAMES
.
.
.
.
.
.
.
.
ORBIT TIME
A
.
.
.
.
.
.
.
ORBIT POSITION
A
.
.
.
.
.
.
.
ORBIT VELOCITY
A
.
.
.
.
.
.
.
CALIBRATION TIME
.
.
.
.
.
.
.
.
USO FREQUENCY
.
.
.
.
.
.
.
.
COMMAND PROCEDURE NAME AND
PRIORITY
.
.
.
.
.
.
.
.
EXECUTE TIME
.
.
.
.
.
.
.
.
406 MHZ SARR FREQ. CALIB. OFFSET
.
.
A
.
.
.
.
.
406 MHZ SARR FREQ. CALIB. DRIFT
.
.
X
.
.
.
.
.
TIME OF 406 MHZ SARR FREQ. CALIB.
.
.
A
.
.
.
.
.
TWO-LINE ELEMENT (TLE) SET – LINE 1
.
A
.
.
.
.
.
.
TWO-LINE ELEMENT (TLE) SET – LINE 2
.
A
.
.
.
.
.
.
Repeat MF \#s 39 and 40 for each PROCEDURE
NAME (MF \#33)
.
.
.
.
.
.
.
.
Repeat MF \#s6 to 86 as required by MF \#44
A
.
A
A
.
.
.
.
23 HEX BEACON ID
.
.
.
.
.
.
A
.
NARRATIVE TEXT
.
.
.
A
A
A
A
.
TAC NUMBER INFORMATION
.
.
.
.
.
.
.
A
BEACON MANUFACTURER NAME
.
.
.
.
.
.
.
A
BEACON MODEL NAME
.
.
.
.
.
.
.
A
BEACON DATA FIELD
.
.
.
.
.
.
.
A
SIT TRAILER
ENDSIT
A
A
A
A
A
MSG TRAILER
ENDMSG
A
A
A
A
A
Note: The narrative text is terminated as specified in MF #41. See section 4.1 for size specification.
“A” indicates actual values, “X” indicates default values are allowed.
The underline “__” is an indication where the New Line (NL) code is to be inserted.
C-11
MESSAGE CONTENT FOR MEOSAR DATA MESSAGES (XML)
The TOA/FOA data to be transferred between MEOLUTs is described by the schema below in
Figure C.1. This XML schema document can be copied to an appropriate folder on a local
MEOLUT data server for immediate use by any third-party XML parser. Note that each “element
name” corresponds to the message field name as provided in Annex B.1 of this document or the
corresponding information above in this Annex, with the explicit replacement of all spaces and
other punctuation characters by the underscore characters (“\_”).
6Figure C.1: XML Schema for the Transfer of TOA/FOA Data Between MEOLUTs
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:packet-schema"
elementFormDefault="qualified" targetNamespace="urn:packet-schema">
<xsd:element name="TOA\_FOA\_LIST" type="TOA\_FOA\_LIST" />
<xsd:complexType name="TOA\_FOA\_LIST">
<xsd:sequence>
<xsd:element name="TOA\_FOA\_DATA" minOccurs="0" maxOccurs="unbounded">
</xsd:element>
</xsd:sequence>
<xsd:complexType>
<xsd:all>
<xsd:element name="MF6" type="xsd:positiveInteger"> </ xsd:element>
<xsd:element name="MF11" type="xsd:positiveInteger"> </ xsd:element>
<xsd:element name="MF71" type="xsd:positiveInteger"> </ xsd:element>
<xsd:element name="MF22">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[0-9A-F]{15}" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MF77">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[0-9A-F]{36}" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element> <xsd:element name="MF90">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[0-9A-F]{51}" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MF91">
C-12
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[0-6N]{1}" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MF92">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[0-9A-F]{23}" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MF67">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[0-9]{2} [0-9]{3} [0-9]{4} [0-9]{2}[\.][0-9]{9}" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MF68" type="xsd:decimal" />
<xsd:element name="MF69" type="xsd:decimal" />
<xsd:element name="MF70">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[+-][0-9]{5}[\.][0-9]{3}" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MF72" type="xsd:decimal"> </ xsd:element>
<xsd:element name="MF73" type="xsd:decimal"> </ xsd:element>
<xsd:element name="MF74" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[0-9A-F]{4}" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MF75">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[+-][0-9]{5}[\.][0-9]{4} [+-][0-9]{5}[\.][0-9]{4} [+-][0-9]{5}[\.][0-
9]{4}" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
C-13
<xsd:element name="MF76">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="[+-][0-9]{3}[\.][0-9]{6} [+-][0-9]{3}[\.][0-9]{6} [+-][0-9]{3}[\.][0-
9]{6}" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="MF87" >
<xsd:simpleType>
<xsd:restriction base="xsd:normalizedString">
<xsd:enumeration value="ECEF"/>
<xsd:enumeration value="ECI\_"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:all>
</xsd:complexType>
</xsd:element>
</xsd:schema>
C-14
10Table C-3:
MESSAGE CONTENT FOR
SIT 185 MESSAGES
PRINTED
SECTION \#
MF \#
TITLE
MESSAGE TYPE
M
CURRENT MESSAGE NUMBER
M
MCC BEACON REFERENCE
M
3+n
50a
BEACON MESSAGE INFORMATION
M
TYPE OF BEACON
O
IDENTIFICATION
O
57a
BEACON HEX ID
M
50b
COUNTRY OF BEACON REGISTRATION
O
BEACON NUMBER
O
57b
HOMING SIGNAL
O
ACTIVATION TYPE
O
SOURCE OF GNSS POSITION DATA
O
EMERGENCY CODE
O
4+n
ALERT POSITION INFORMATION
M
48a or 48b
DETECTION TIME & SPACECRAFT
M
54e
GNSS POSITION, TIME OF UPDATE AND ALTITUDE
O
54a
MCC REFERENCE POSITION
O
54d
DOA POSITION AND ALTITUDE
O
54b
A POSITION & PROBABILITY
O
54c
B POSITION & PROBABILITY
O
5+n
61a
OTHER INFORMATION (GENERAL)
M
DETECTION FREQUENCY
M
OTHER ENCODED INFORMATION
O
6+n
REMARKS
M
END OF MESSAGE
M
Notes:
1. "M" means that the field is mandatory
2. "O" means that the field may be omitted if the value is NIL.
3. The underline "\_" is an indication where the New Line (NL) code is to be inserted.
4. “+n” indicates that a variable number of lines is required to provide specified information
5. MF \#48a is used for FGB other than ELT(DT)s, MF \#48b is used for SGBs and FGB ELT(DT)s.
6. The “END OF MESSAGE” does not contain an associated section number.
C-15
11Table C-4:
MESSAGE CONTENT FOR
SIT 985 MESSAGES
PRINTED
LINE \#
MF
\#
TITLE
MESSAGE TYPE
X
CURRENT MESSAGE NUMBER
X
MCC BEACON REFERENCE
X
61b
HEX ID (BEACON OPERATIONAL CHARACTERISTICS)
X
61c
TAC DATA (BEACON OPERATIONAL CHARACTERISTICS)
X
5+a
END OF MESSAGE
X
a = number of lines required for MF \#61c
The underline "\_" is an indication where the New Line (NL) code is to be inserted.
C-16
MESSAGE CONTENT FOR MESSAGES SENT TO THE LADR
The Global Aeronautical Distress and Safety System (GADSS) specifies that data is provided to
the LADR via a System Wide Information Management (SWIM) compliant interface. A SWIM
interface is a means through which information can be produced or consumed via a
“publish/subscribe” or “request/reply” messaging pattern. ELT(DT) alert data shall be exchanged
with the LADR using a SWIM compliant format known as FIXM (Flight Information Exchange
Model), a standardized method to exchange Flight and Flow information in XML format. Details
on FIXM can be found at www.fixm.aero.
ELT(DT) alert shall be sent to the LADR using, in part, the information provided in the following
table, which provides key XML field names specified for the LADR with example values and
explanatory notes. The complete XML specification is provided by ICAO directly to LADR
Contributors, i.e., nodal MCCs.
12Table C-5:
KEY LADR MESSAGE FIELD DESCRIPTIONS
XML Field Name
Example/Value
Comments
identifier
eca23996-df29-4ee2-
a886-bf8f150a75a4
Required: Universally Unique Identifier (UUID) –
unique reference for the message to the LADR
which is generated using standard modern
programming language utilities
timestamp
2022-01-19T06:00:12Z
Required: Time of message
contributorCode
Required: Assigned by ICAO to each nodal MCC
type
ELT\_DT (note: there is
underscore between ELT
and DT)
Required: Type of ADT device: Fixed for all C/S
ELT(DT) data
adtActivationMethod
Required: Lookup table1:
[100001] Manual
[100002] Automatic by Beacon
[100003] Automatic by External Means
[100004] Distress Cancelled
[100005] Test Beacon
aircraftAddress
AF0F89
Required if “registration” is not provided: Standard
24 Bit Address for aircraft
registration
9GMKJ
Required if “aircraftAddress” is not provided:
Aircraft registration marking
1 These entries are six-digit values, and as indicated by the brackets, these values apply if they remain under the control
and specification of Cospas-Sarsat; however, they may yet be specified by ICAO as part of a larger list of options.
C-17
XML Field Name
Example/Value
Comments
carriedEltHexIdentifier
21F25787C4BFDFF
Required: While this field might be used by other
ADT Contributors (non-ELT(DT) devices) to refer
to an onboard ELT, for C/S purposes, this is
required and shall be populated with the Hex ID for
the ELT(DT)
pos
32.925 15.106
Required: Signed floating point values for latitude
and longitude (there is no strict limit on the number
digits after the decimal point, although five is a
practical upper limit, as appropriate for SGB
encoded positions in particular)
timeAtPosition
2022-01-19T06:00:01Z
Required: Detect time for the location above
designatorIcao
ABC
Required: The 3LD aircraft designator
---------------------------
---------------------------
------------------------------------------------------
altitude
Optional: A single numerical value in meters as
provided by the beacon, and determined as possible
per other guidance for messages fields. When only
a range is available, the average of the high and low
values shall be provided.
horizontalAccuracy
Optional: A numerical value in meters assigned as
follows:
SGB Encoded Position: 10
FGB Encoded Coarse Position: 27781
FGB Encoded Refined Position: 62
DOA Position: EHE (converted to meters)
C-18
APPENDIX C.1 TO ANNEX C
SAMPLE MESSAGES
1.
GENERAL
This Appendix contains examples of messages formatted for transmission. The examples are
shown double spaced for ease of reading. Each example is composed of 3 sections:
a.
FORMAT FRAMES
b.
MF \#
c.
CONTENT
1.1
Format Frames
The FORMAT FRAME corresponds to the required format given in section 4 of the document.
The INFO frame contains the text message and can therefore be formatted as required by Cospas-
Sarsat. The HEADER and TRAILER frames are specified by the host network.
1.2
MF \#
This MF # provides the field number used within a particular message line and correspond to the
MF # shown in Tables C-1, C-2, C-3, C-4 and C-5.
1.3
Content
This section contains the actual information transmitted. Only the content in the examples is
transmitted and not the FORMAT FRAME column and the MF \#s column.
1.4
SIT 185 and SIT 985
Because of their nature, examples for SIT 185 and SIT 985 are presented differently from examples
for other SIT messages and show only the content as it would be displayed or printed at the
receiving agency. The optional SIT header and SIT footer are omitted from these examples sent
by MCCs.
2.
SAMPLES
Sample messages for each SIT format are provided in the following pages.
C-19
SAMPLE MESSAGE FOR
SIT 121
FORMAT
MF \#
CONTENT
FRAMES
HEADER
(As per communication network requirements if any.)
1,2,3
/01612 01600/3660/91 280 1705
4-6,8
/121/3160/002/01
11-15
/3663/+4/-03446.0 006.0 +11.00/91 280 1630
23.50/0
16-20
/3/12.057/0000/01/0000 99
INFO
24-31
/-366/+48.981/-113.906/052 011.8 003.2/52/91
1715/2/010.0 004.0
24-31
/+316/+53.225/-090.102/160 019.7 009.7/48/91
1750/2/010.0 004.0
/LASSIT
/ENDMSG
TRAILER
(As per communication network requirements if any.)
C-20
SAMPLE MESSAGE FOR
SIT 122, 123, 124, 132, 134
FORMAT
MF \#
CONTENT
FRAMES
HEADER
(As per communication network requirements if any.)
_______
1,2,3
/01614 00000/3660/80 005 1750
4-6,10
/122/3160/102/02
11,13,14,21
/3661/-03496.0 006.0 +11.00/80 005 1700
20.00/02
/123456789ABCDEF012345600000000
INFO
11,13,14,21
/3661/-03496.0 006.0 +11.00/80 005 1700
20.00/02
/23456789ABCDEF0123456700000000
/LASSIT
/ENDMSG
_______
TRAILER
(As per communication network requirements if any.)
Note:
MF \#4 must reflect SIT which is being used.
C-21
SAMPLE MESSAGE FOR
SIT 125, 126, 127, 133, 135
FORMAT
MF \#
CONTENT
FRAMES
HEADER
(As per communication network requirements if any.)
1,2,3
/00127 00117/5120/91 280 1843
4-6,8
/125/3660/004/02
11-15
/5121/-4/-00405.0 001.0 -00.70/91 280 1516
16.00/1
16-18,21
/0/15.859/0000/07
/56E680AD19602009C7C7D000000000
24-31
/+227/+22.811/-017.447/276 000.3
000.1/90/00 000 0000/3/010.0 000.0
INFO
24-31
/+366/+24.755/+017.906/074 003.5
001.6/10/00 000 0000/3/040.0 002.0
11-15
/5121/-4/-00407.9 001.0 +00.40/91 280 1657
06.00/1
16-18,21
/0/00.707/0000/18
/56E680AD19602009C7C7D000000000
24-31
/+227/+22.826/-017.686/077 001.5
000.1/51/00 000 0000/2/020.0 001.0
24-31
/+366/+23.181/-016.104/077 001.5
000.1/49/00 000 0000/2/020.0 001.0
/LASSIT
/ENDMSG
TRAILER
(As per communication network requirements if any.)
Note: MF \#4 must reflect SIT which is being used.
C-22
SAMPLE MESSAGE FOR
SIT 137, 139, 141, 145, 146, 147
FORMAT
MF \#
CONTENT
FRAMES
HEADER
(As per communication network requirements if any.)
_______
1,2,3
/01614 00000/3660/09 280 1518
4,5,8
/145/3160/02
11,13,14a
/3669/-00405.0 001.0 +99.99/09 280 1516 36.21
14b,21,77
/09 280 1518
16.19/03/FFFE2F789ABCDEF012345600000000123456
INFO
24,25,26,78,89
/+316/+53.225/-130.102/007/010.42
79,80,81,82,84,88,27 /35.12/00/04/06.379410/00/012/000 000.0 000.0
/301 302 303 304 000 000 000 000 000 000 000
000 000 000 000 000 000
11,13,14a,
/3667/+01923.0 999.9 +99.99/09 280 1517 10.01
14b,21,77
/09 280 1517 10.01/01/
FFFE2F789ABCDEF0123456700000000123456
24,25,26,78,89
/+316/+58.451/-140.810/002/103.57
79,80,81,82,84,88,27 /34.39/00/05/99.999999/00/012/000 000.0 000.0
/301 302 303 304 000 000 000 000 000 000 000
000 000 000 000 000 000
/LASSIT
/ENDMSG
_______
TRAILER
(As per communication network requirements if any.)
Note:
MF \#4 must reflect SIT which is being used.
C-23
SAMPLE MESSAGE FOR
SIT 136, 138, 142, 143, 144
FORMAT
MF \#
CONTENT
FRAMES
HEADER
(As per communication network requirements if any.)
1,2,3
/01614 00000/3660/09 280 1518
4,5,8
/142/3160/02
11,13,14a
/3669/-00405.0 001.0 +99.99/09 280 1516 36.21
14b,21,77
/09 280 1518 16.19/03/
FFFE2F789ABCDEF012345600000000123456
79,80,81,88
/35.12/01/04/001
/301 302 303 304 000 000 000 000 000 000 000
000 000 000 000 000 000
INFO
11,13,14a
/3667/+01923.0 999.9 +99.99/09 280 1517 10.01
14b,21,77
/09 280 1517 10.01/01/
FFFE2F789ABCDEF0123456700000000123456
79,80,81,88
/34.39/00/05/002
/301 302 303 304 000 000 000 000 000 000 000
000 000 000 000 000 000
/LASSIT
/ENDMSG
TRAILER
(As per communication network requirements if any.)
Note:
MF \#4 must reflect SIT which is being used.
C-24
SAMPLE MESSAGE FOR
SIT 322, 323, 324, 332, 334
FORMAT
FRAMES
MF \#
CONTENT
HEADER
(As per communication network requirements if any.)
1,2,3
/01614 00000/3660/80 005 1750
4-6,10
/322/3160/102/02
11,13,14,21
/3661/-03496.0 006.0 +11.00/80 005 1700 20.00/02
/0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF012
91,92
/3/0123456789ABCDEF0123456
INFO
11,13,14,21
/3661/-03496.0 006.0 +11.00/80 005 1700 20.00/02
/0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF012
91,92
/0/0123456789ABCDEF0123456
/LASSIT
/ENDMSG
TRAILER
(As per communication network requirements if any.)
Note:
MF \#4 must reflect SIT which is being used.
C-25
SAMPLE MESSAGE FOR
SIT 337, 339, 345, 346, 347
FORMAT
FRAMES
MF \#
CONTENT
HEADER
(As per communication network requirements if any.)
1,2,3
/01614 00000/3660/09 280 1518
4,5,8
/345/3160/01
11,13,14a,14b,21
/3669/-00405.0 001.0 +99.99/09 280 1516 36.21/09 280
1518 16.19/03
INFO
/0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF012
91,92
/3/0123456789ABCDEF0123456
24,25,26,78,89
/+316/+53.225/-130.102/007/010.42
79,80,81,82,84,88,27 /35.12/09/04/06.379410/00/012/000 000.0 000.0
/301 302 303 304 000 000 000 000 000 000 000 000 000
000 000 000 000
/366901 366902 366903 366904 000000 000000 000000
000000 000000
000000 000000 000000 000000 000000 000000 000000
/LASSIT
/ENDMSG
TRAILER
(As per communication network requirements if any.)
Note: MF \#4 must reflect SIT which is being used.
C-26
SAMPLE MESSAGE FOR
SIT 336, 338, 342, 343, 344
FORMA
T
FRAMES
MF \#
CONTENT
HEADE
R
(as per communication network requirements if any)
1,2,3
/01614 00000/3660/09 280 1518
4,5,8
/342/3160/01
11,13,14a,14b,2
/3669/-00405.0 001.0 +99.99/09 280 1516 36.21/09
280 1518 16.19/03
INFO
/0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF
91,92
/3/1234567890ABCDEF1234567
79,80,81,88
/35.12/09/04/001
/301 302 303 304 000 000 000 000 000 000 000 000
000 000 000 000 000
/366901 366902 366903 366904 000000 000000 000000
000000 000000 000000 000000 000000 000000 000000
000000 000000 000000
/LASSIT
/ENDMSG
TRAILE
R
(as per communication network requirements if any)
Note: MF \#4 must reflect SIT which is being used.
C-27
SAMPLE MESSAGE FOR
TOA/FOA XML DATA TRANSFER
(FGB)
<?xml version="1.0" encoding="utf-8"?>
<TOA\_FOA\_LIST xmlns="urn:packet-schema" xsi:schemaLocation="urn:packet-schema schema.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<TOA\_FOA\_DATA>
<MF6>312</MF6>
<MF11>7106</MF11>
<MF71>16</MF71>
<MF22>ADDFFFFFFFFFFFC</MF22>
<MF77>42BB1F56EFFFFFFFFFFFE5CB630000000000</MF77>
<MF67>10 272 0003 50.623698123</MF67>
<MF68>406036073.075</MF68>
<MF69>0.076403123</MF69>
<MF70>+02255.694</MF70>
<MF72>37.6</MF72>
<MF73>400.046</MF73>
<MF74>0000</MF74>
<MF87>ECEF</MF87>
<MF75>+22797.7391 -13074.3953 -00794.0700</MF75>
<MF76>+001.064675 +002.052740 -003.157027</MF76>
</TOA\_FOA\_DATA>
</TOA\_FOA\_LIST>
C-28
SAMPLE MESSAGE FOR SIT 185 (1)
SAMPLE 406 MHz UNRESOLVED DOPPLER POSITION MATCH
(FGB - STANDARD LOCATION - EPIRB)
1. DISTRESS COSPAS-SARSAT UNRESOLVED DOPPLER POSITION MATCH ALERT
2. MSG NO 00741 AUMCC REF 1C04273BC0FFBFF
3. BEACON MESSAGE INFORMATION
BEACON TYPE STANDARD LOCATION – EPIRB
MMSI ALL 9 DIGITS 224080350
HEX ID 1C04273BC0FFBFF
COUNTRY OF BEACON REGISTRATION 224/SPAIN
BEACON NUMBER ON AIRCRAFT OR VESSEL 0
(line may be omitted as value is NIL)
HOMING SIGNAL 121.5 MHZ
ACTIVATION TYPE NIL
(line may be omitted as value is NIL)
GNSS POSITION PROVIDED BY INTERNAL DEVICE
(line may be omitted as value is NIL)
EMERGENCY CODE NIL
(line may be omitted as value is NIL)
4. ALERT POSITION INFORMATION
DETECTED AT 19 MAR 24 0514 UTC BY LEOSAR SARSAT 12
GNSS - NIL
(line may be omitted as value is NIL)
MCC REFERENCE - NIL
(line may be omitted as value is NIL)
DOA - NIL
(line may be omitted as value is NIL)
DOPPLER A - 41 07.1 N 001 12.7 E PROB 69 PERCENT
DOPPLER B - 36 48.4 N 022 20.2 E PROB 31 PERCENT
5. OTHER INFORMATION
WARNING: AMBIGUITY IS NOT RESOLVED
DETECTION FREQUENCY 406.0250 MHZ
6. REMARKS NIL
END OF MESSAGE
Note: Lines which may be omitted as value is NIL per Table C-3 have not been omitted in this FGB
message
C-29
SAMPLE MESSAGE FOR SIT 185 (2)
SAMPLE 406 MHz INITIAL GNSS POSITION ALERT
(FGB - STANDARD LOCATION - EPIRB: SERIAL NUMBER)
1. DISTRESS COSPAS-SARSAT INITIAL LOCATED ALERT
2. MSG NO 00306 AUMCC REF 278C362E3CFFBFF
3. BEACON MESSAGE INFORMATION
BEACON TYPE STANDARD LOCATION - EPIRB
SERIAL NO 05918
HEX ID 278C362E3CFFBFF
COUNTRY OF BEACON REGISTRATION 316/CANADA
HOMING SIGNAL 121.5 MHZ
GNSS POSITION PROVIDED BY INTERNAL DEVICE
4. ALERT POSITION INFORMATION
DETECTED AT 17 APR 24 1627 UTC BY GEOSAR GOES 18
GNSS - 05 00.00 S 178 00.00 E
UPDATE TIME WITHIN 4 HOURS OF DETECTION TIME
5. OTHER INFORMATION
BEACON REGISTRATION AT CMCC
TAC 0108
BEACON MODEL - ACR, RLB-33
DETECTION FREQUENCY 406.0250 MHZ
GNSS POSITION UNCERTAINTY PLUS-MINUS 30 MINUTES
OF LATITUDE AND LONGITUDE
LUT ID 5123 GOUDIES ROAD GEOLUT, NEW ZEALAND
6. REMARKS NIL
END OF MESSAGE
C-30
SAMPLE MESSAGE FOR SIT 185 (3)
SAMPLE 406 MHz INITIAL ALERT WITH NO LOCATION
(FGB - NATIONAL LOCATION - ELT)
1. DISTRESS COSPAS-SARSAT INITIAL ALERT (UNLOCATED)
2. MSG NO 00141 SPMCC REF 12345
3. BEACON MESSAGE INFORMATION
BEACON TYPE NATIONAL LOCATION - ELT
SERIAL NO 000006
HEX ID 331000033F81FE0
COUNTRY OF BEACON REGISTRATION 408/BAHRAIN
HOMING SIGNAL 121.5 MHZ
GNSS POSITION PROVIDED BY EXTERNAL DEVICE
4. ALERT POSITION INFORMATION
DETECTED AT 21 FEB 24 0646 UTC BY GEOSAR MSG-2
5. OTHER INFORMATION
BEACON REGISTRATION AT WWW.406REGISTRATION.COM
DETECTION FREQUENCY 406.0249 MHZ
6. REMARKS NIL
END OF MESSAGE
C-31
SAMPLE MESSAGE FOR SIT 185 (4)
SAMPLE 406 MHz POSITION CONFIRMATION ALERT
(FGB - NATIONAL LOCATION - PLB)
1. DISTRESS COSPAS-SARSAT POSITION UPDATE ALERT
2. MSG NO 00812 AUMCC REF 2DD747073F81FE0
3. BEACON MESSAGE INFORMATION
BEACON TYPE NATIONAL LOCATION - PLB
SERIAL NO 167438
HEX ID 2DD747073F81FE0
COUNTRY OF BEACON REGISTRATION 366/USA
HOMING SIGNAL 121.5 MHZ
GNSS POSITION PROVIDED BY INTERNAL DEVICE
4. ALERT POSITION INFORMATION
DETECTED AT 28 APR 24 0920 UTC BY LEOSAR SARSAT 12
GNSS - 33 25.93 N 038 55.67 E
UPDATE TIME WITHIN 4 HOURS OF DETECTION TIME
MCC REFERENCE - 33 27.1 N 038 56.2 E
DOPPLER B - 33 27.1 N 038 56.2 E PROB 45 PERCENT
5. OTHER INFORMATION
TAC 123
DETECTION FREQUENCY 406.0278 MHZ
GNSS POSITION UNCERTAINTY PLUS-MINUS 2 SECONDS
OF LATITUDE AND LONGITUDE
LUT ID 2272 TOULOUSE, FRANCE
6. REMARKS NIL
END OF MESSAGE
C-32
SAMPLE MESSAGE FOR SIT 185 (5)
SAMPLE 406 MHz POSITION CONFIRMATION ALERT
(SGB - PLB)
1. DISTRESS COSPAS-SARSAT INITIAL LOCATED ALERT
2. MSG NO 00812 AUMCC REF ADD4BF935B61574
3. BEACON MESSAGE INFORMATION
BEACON TYPE SGB – PLB
MMSI 366123456
EPIRB-AIS ID 974 0123
TAC 12260 SERIAL NO 13750
HEX ID ADD4BF935B61 574A670007B
COUNTRY OF BEACON REGISTRATION 366/USA
BEACON NUMBER ON AIRCRAFT OR VESSEL NIL
(line may be omitted as value is NIL)
HOMING SIGNAL YES
ACTIVATION TYPE MANUAL
EMERGENCY CODE NIL
(line may be omitted as value is NIL)
4. ALERT POSITION INFORMATION
DETECTED AT 28 APR 23 092045 UTC BY MEOSAR
ALERT LAST DETECTED AT 28 APR 23 092405 UTC
GNSS - 33 26.93 N 038 55.67 E
TIME SINCE GNSS LOCATION 0 MINUTES
ALTITUDE OF GNSS LOCATION 125 METRES (410 FEET)
MCC REFERENCE - 33 27.1 N 038 56.2 E
DOA - 33 27.1 N 038 56.2 E ESTIMATED ERROR 003 NMS
ALTITUDE NIL
(line may be omitted as value is NIL)
5. OTHER INFORMATION
BEACON CHARACTERISTICS PER TAC DATABASE
PROVIDED IN A SEPARATE MESSAGE
GNSS POSITION UNCERTAINTY PLUS-MINUS 10 METRES
DETECTION FREQUENCY 406.05 MHZ
ELAPSED TIME SINCE ACTIVATION 0 HOURS
REMAINING BATTERY CAPACITY BETWEEN 75 AND 100 PERCENT
6. REMARKS NIL
END OF MESSAGE
Note: Lines which may be omitted as value is NIL per Table C-3 have not been omitted in this SGB message
C-33
SAMPLE MESSAGE FOR SIT 185 (6)
SAMPLE 406 MHz DOA POSITION CONFIRMATION ALERT
(FGB - STANDARD LOCATION – EPIRB: SERIAL NUMBER)
1. DISTRESS COSPAS-SARSAT POSITION UPDATE ALERT
2. MSG NO 00306 BRMCC REF 12345
3. BEACON MESSAGE INFORMATION
BEACON TYPE STANDARD LOCATION - EPIRB
SERIAL NO 05919
HEX ID 278C36AE3EFFBFF
COUNTRY OF BEACON REGISTRATION 316/CANADA
HOMING SIGNAL 121.5 MHZ
GNSS POSITION PROVIDED BY INTERNAL DEVICE
4. ALERT POSITION INFORMATION
DETECTED AT 17 DEC 23 1630 UTC BY MEOSAR
ALERT LAST DETECTED AT 17 DEC 23 1646 UTC
MCC REFERENCE - 05 10.1 S 178 01.3 E
DOA - 05 10.2 S 178 01.2 E ESTIMATED ERROR 003 NMS
5. OTHER INFORMATION
BEACON REGISTRATION AT CMCC
TAC 0109
BEACON MODEL - ACR, RLB-33
DETECTION FREQUENCY 406.0371 MHZ
6. REMARKS NIL
END OF MESSAGE
C-34
SAMPLE MESSAGE FOR SIT 185 (7)
SAMPLE 406 MHz NOCR GNSS POSITION ALERT
(FGB - NATIONAL LOCATION - PLB)
1. DISTRESS COSPAS-SARSAT NOTIFICATION OF COUNTRY OF BEACON
REGISTRATION ALERT
2. MSG NO 01737 AUMCC REF 3EF6C34FBF81FE0
3. BEACON MESSAGE INFORMATION
BEACON TYPE NATIONAL LOCATION - PLB
SERIAL NO 099999
HEX ID 3EF6C34FBF81FE0
COUNTRY OF BEACON REGISTRATION 503/AUSTRALIA
HOMING SIGNAL NIL OR NOT 121.5 MHZ
GNSS POSITION PROVIDED BY INTERNAL DEVICE
4. ALERT POSITION INFORMATION
DETECTED AT 20 MAR 23 0504 UTC BY LEOSAR SARSAT 10
GNSS - 28 06.00 S 153 40.07 E
UPDATE TIME WITHIN 4 HOURS OF DETECTION TIME
5. OTHER INFORMATION
DETECTION FREQUENCY 406.0216 MHZ
GNSS POSITION UNCERTAINTY PLUS-MINUS 2 SECONDS
OF LATITUDE AND LONGITUDE
LUT ID 6011 CAPE TOWN, SOUTH AFRICA
6. REMARKS NIL
END OF MESSAGE
C-35
SAMPLE MESSAGE FOR SIT 185 (8)
SAMPLE 406 MHz INITIAL DOPPLER POSITION ALERT
(FGB - STANDARD LOCATION – ELT: 24-BIT ADDRESS)
1. DISTRESS COSPAS-SARSAT INITIAL LOCATED ALERT
2. MSG NO 00741 AUMCC REF 3266E2019CFFBFF
3. BEACON MESSAGE INFORMATION
BEACON TYPE STANDARD LOCATION - ELT
AIRCRAFT 24 BIT ADDRESS 7100CE ASSIGNED TO SAUDI ARABIA
HEX ID 3266E2019CFFBFF
COUNTRY OF BEACON REGISTRATION 403/SAUDI
HOMING SIGNAL 121.5 MHZ
GNSS POSITION PROVIDED BY EXTERNAL DEVICE
4. ALERT POSITION INFORMATION
DETECTED AT 22 APR 23 0912 UTC BY LEOSAR SARSAT 10
DOPPLER A - 32 49.1 N 081 54.2 E PROB 69 PERCENT
DOPPLER B - 24 18.1 N 041 18.2 E PROB 31 PERCENT
5. OTHER INFORMATION
DETECTION FREQUENCY 406.0247 MHZ
LUT ID 4191 BANGALORE, INDIA
6. REMARKS NIL
END OF MESSAGE
C-36
SAMPLE MESSAGE FOR SIT 185 (9)
SAMPLE 406 MHz INITIAL DOA POSITION ALERT
(FGB - STANDARD LOCATION – EPIRB: SERIAL NUMBER)
1. DISTRESS COSPAS-SARSAT INITIAL LOCATED ALERT
2. MSG NO 00306 BRMCC REF 12345
3. BEACON MESSAGE INFORMATION
BEACON TYPE STANDARD LOCATION - EPIRB
SERIAL NO 05920
HEX ID 278C372E40FFBFF
COUNTRY OF BEACON REGISTRATION 316/CANADA
HOMING SIGNAL 121.5 MHZ
GNSS POSITION PROVIDED BY INTERNAL DEVICE
4. ALERT POSITION INFORMATION
DETECTED AT 17 DEC 23 1627 UTC BY MEOSAR
ALERT LAST DETECTED AT 17 DEC 23 1627 UTC
DOA - 05 10.1 S 178 01.4 E ESTIMATED ERROR 015 NMS
5. OTHER INFORMATION
BEACON REGISTRATION AT CMCC
TAC 0110
BEACON MODEL - ACR, RLB-33
DETECTION FREQUENCY 406.0371 MHZ
6. REMARKS NIL
END OF MESSAGE
C-37
SAMPLE MESSAGE FOR SIT 185 (10)
SAMPLE 406 MHz INITIAL ALERT
(FGB - RETURN LINK LOCATION –PLB: SERIAL NUMBER)
1. DISTRESS COSPAS-SARSAT POSITION CONFLICT ALERT
2. MSG NO 00308 USMCC REF 12345
3. BEACON MESSAGE INFORMATION
BEACON TYPE PLB (RETURN LINK)
SERIAL NO 07551
HEX ID 1C7B006EBFBFDFF
COUNTRY OF BEACON REGISTRATION 227/FRANCE
HOMING SIGNAL 121.5 MHZ
GNSS POSITION PROVIDED BY INTERNAL DEVICE
4. ALERT POSITION INFORMATION
DETECTED AT 18 DEC 23 1630 UTC BY LEOSAR SARSAT 13
GNSS - 17 44.13 N 087 26.33 E
UPDATE TIME WITHIN 4 HOURS OF DETECTION TIME
5. OTHER INFORMATION
GNSS POSITION UNCERTAINTY PLUS-MINUS 2 SECONDS
OF LATITUDE AND LONGITUDE
BEACON REGISTRATION AT FMCC
TAC 3003
DETECTION FREQUENCY 406.0370 MHZ
POSITION CONFLICT BASED ON DISTANCE SEPARATION AT LEAST 20KM
6. REMARKS
THIS BEACON HAS GALILEO RETURN LINK CAPABILITY
TYPE 1 CAPABILITY (AUTOMATIC ACKNOWLEDGEMENT)
END OF MESSAGE
C-38
SAMPLE MESSAGE FOR SIT 185 (11)
SAMPLE 406 MHz ALERT WITH UNRELIABLE BEACON MESSAGE
(FGB - AS PER DOCUMENT C/S A.001,
SECTION “406 MHZ BEACON MESSAGE VALIDATION”)
1. DISTRESS COSPAS-SARSAT INITIAL LOCATED ALERT
2. MSG NO 00506 AUMCC REF 4C4B4E007688888
3. BEACON MESSAGE INFORMATION
DATA DECODED FROM THE BEACON MESSAGE IS NOT RELIABLE
HEX ID 4C4B4E007688888
4. ALERT POSITION INFORMATION
DETECTED AT 01 APR 23 0610 UTC BY LEOSAR SARSAT 12
DOPPLER A - 07 23.1 S 136 46.2 E PROB 92 PERCENT
DOPPLER B - 03 00.1 S 155 08.2 E PROB 08 PERCENT
5. OTHER INFORMATION
DETECTION FREQUENCY 406.0315 MHZ
6. REMARKS NIL
END OF MESSAGE
C-39
SAMPLE MESSAGE FOR SIT 185 (12)
SAMPLE 406 MHz CONFIRMED UPDATE POSITION ALERT
(FGB - STANDARD LOCATION – SHIP SECURITY)
1. SHIP SECURITY COSPAS-SARSAT POSITION UPDATE ALERT
2. MSG NO 00192 AUMCC REF 2AB82AF800FFBFF
3. BEACON MESSAGE INFORMATION
BEACON TYPE STANDARD LOCATION – SHIP SECURITY
MMSI ALL 9 DIGITS 341088000
HEX ID 2AB82AF800FFBFF
COUNTRY OF BEACON REGISTRATION 341/ST KITTS
BEACON NUMBER ON AIRCRAFT OR VESSEL 0
HOMING SIGNAL NIL OR NOT 121.5 MHZ
ACTIVATION TYPE MANUAL
GNSS POSITION PROVIDED BY INTERNAL DEVICE
4. ALERT POSITION INFORMATION
DETECTED AT 03 MAY 23 0853 UTC BY LEOSAR SARSAT 12
GNSS - 01 54.40 N 045 37.53 E
UPDATE TIME WITHIN 4 HOURS OF DETECTION TIME
MCC REFERENCE - 02 15.1 N 046 00.2 E
DOPPLER A - 02 25.1 N 046 06.2 E
5. OTHER INFORMATION
GNSS POSITION UNCERTAINTY PLUS-MINUS 2 SECONDS
OF LATITUDE AND LONGITUDE
DETECTION FREQUENCY 406.0276 MHZ
6. REMARKS
THIS IS A SHIP SECURITY ALERT.
PROCESS THIS ALERT ACCORDING TO RELEVANT SECURITY REQUIREMENTS
END OF MESSAGE
C-40
SAMPLE MESSAGE FOR SIT 185 (13)
SAMPLE 406 MHz POSITION ALERT
(SGB, ELT(DT))
1. DISTRESS TRACKING COSPAS-SARSAT DOA POSITION MATCH ALERT
2. MSG NO 00192 AUMCC REF B274FA041FD4710
3. BEACON MESSAGE INFORMATION
BEACON TYPE SGB – ELT DISTRESS TRACKING
AIRCRAFT 24 BIT ADDRESS 7100CE ASSIGNED TO SAUDI ARABIA
AIRCRAFT OPERATOR DESIGNATOR SVA
TAC 16001 SERIAL NO 509
HEX ID B274FA041FD4 7100CEA3F00
COUNTRY OF BEACON REGISTRATION 403/SAUDI
ACTIVATION TYPE AUTOMATIC BY BEACON (G-SWITCH/PROBABLE CRASH)
4. ALERT POSITION INFORMATION
DETECTED AT 03 MAY 23 085310 UTC BY MEOSAR
ALERT LAST DETECTED AT 03 MAY 23 085310 UTC
GNSS - 02 24.40 N 046 04.11 E
TIME OF GNSS POSITION UPDATE: 03 MAY 23 085308 UTC
TIME SINCE GNSS LOCATION GENERATED: 0 MINUTES
ALTITUDE OF GNSS LOCATION: 125 METRES (410 FEET)
DOA - 02 25.1 N 046 06.2 E ESTIMATED ERROR 001NMS
5. OTHER INFORMATION
BEACON CHARACTERISTICS PER TAC DATABASE PROVIDED IN A SEPARATE MESSAGE
GNSS POSITION UNCERTAINTY PLUS-MINUS 10 METRES
ELAPSED TIME SINCE ACTIVATION: 0 HOURS
REMAINING BATTERY CAPACITY BETWEEN 75 AND 100 PERCENT
DETECTION FREQUENCY 406.05 MHZ
ELT(DT) POSITION DOES NOT REFERENCE ANY PREVIOUS POSITION
6. REMARKS
THIS DISTRESS TRACKING MESSAGE IS BEING SENT TO APPROPRIATE
SAR AUTHORITIES.
PROCESS THIS ALERT ACCORDING TO RELEVANT REQUIREMENTS.
END OF MESSAGE
C-41
SAMPLE MESSAGE FOR SIT 185 (14)
SAMPLE 406 MHz DOPPLER POSITION CONFLICT ALERT
(FGB - SERIAL USER-LOCATION - ELT: 24-BIT ADDRESS)
1. DISTRESS COSPAS-SARSAT POSITION CONFLICT ALERT
2. MSG NO 02698 AUMCC REF C1ADE28809C0185
3. BEACON MESSAGE INFORMATION
BEACON TYPE SERIAL USER LOCATION – ELT
AIRCRAFT 24-BIT ADDRESS 8A2027 ASSIGNED TO INDONESIA
HEX ID C1ADE28809C0185
COUNTRY OF BEACON REGISTRATION 525/INDONESIA
BEACON NUMBER ON AIRCRAFT OR VESSEL 0
HOMING SIGNAL 121.5 MHZ
GNSS POSITION PROVIDED BY EXTERNAL DEVICE
4. ALERT POSITION INFORMATION
DETECTED AT 06 APR 23 1440 UTC BY LEOSAR COSPAS 14
DOPPLER A - 07 00.1 S 098 42.2 E PROB 50 PERCENT
DOPPLER B - 05 42.1 S 107 20.2 E PROB 50 PERCENT
5. OTHER INFORMATION
TAC 0097
BEACON MODEL - TECHTEST, UK 503-1
DETECTION FREQUENCY 406.0246 MHZ
RELIABILITY OF DOPPLER POSITION DATA SUSPECT DUE TO
TECHNICAL PARAMETERS
POSITION CONFLICT BASED ON DISTANCE SEPARATION AT LEAST 20KM
LUT ID 4191 BANGALORE, INDIA
6. REMARKS NIL
END OF MESSAGE
C-42
SAMPLE MESSAGE FOR SIT 185 (15)
SAMPLE 406 MHz DOPPLER INITIAL ALERT
(FGB - SERIAL USER – EPIRB: NON-FLOAT FREE)
1. DISTRESS COSPAS-SARSAT INITIAL LOCATED ALERT
2. MSG NO 01087 AUMCC REF ADCE402FA80028D
3. BEACON MESSAGE INFORMATION
BEACON TYPE SERIAL USER – EPIRB (NON-FLOAT FREE)
SERIAL NO 0003050
HEX ID ADCE402FA80028D
COUNTRY OF BEACON REGISTRATION 366/USA
HOMING SIGNAL 121.5 MHZ
ACTIVATION TYPE MANUAL
4. ALERT POSITION INFORMATION
DETECTED AT 20 MAY 23 1613 UTC BY LEOSAR SARSAT 13
DOPPLER A - 36 38.1 S 168 58.2 E PROB 70 PERCENT
DOPPLER B - 36 39.1 S 169 01.2 E PROB 30 PERCENT
5. OTHER INFORMATION
TAC 0163
BEACON MODEL - MCMURDO LTD G5 OR E5 SMARTFIND
RELIABILITY OF DOPPLER POSITION DATA – SUSPECT DUE TO
SATELLITE MANOEUVRE
DETECTION FREQUENCY 406.0266 MHZ
6. REMARKS NIL
END OF MESSAGE
C-43
SAMPLE MESSAGE FOR SIT 185 (16)
SAMPLE 406 MHz DOPPLER CONFIRMED ALERT
(FGB - AVIATION USER - AIRCRAFT REGISTRATION)
1. DISTRESS COSPAS-SARSAT POSITION UPDATE ALERT
2. MSG NO 00932 AUMCC REF 9D064BED62EAFE1
3. BEACON MESSAGE INFORMATION
BEACON TYPE USER- ELT AVIATION USER
AIRCRAFT REGISTRATION VP-CGK
HEX ID 9D064BED62EAFE1
COUNTRY OF BEACON REGISTRATION 232/G.BRITAIN
BEACON NUMBER ON AIRCRAFT OR VESSEL 0
HOMING SIGNAL 121.5 MHZ
ACTIVATION TYPE MANUAL
4. ALERT POSITION INFORMATION
DETECTED AT 10 MAY 23 0654 UTC BY LEOSAR SARSAT 13
MCC REFERENCE - 25 13.1 N 055 22.2 E
DOPPLER A - 25 17.1 N 055 23.2 E PROB 90 PERCENT
5. OTHER INFORMATION
DETECTION FREQUENCY 406.0246 MHZ
6. REMARKS NIL
END OF MESSAGE
C-44
SAMPLE MESSAGE FOR SIT 185 (17)
SAMPLE 406 MHz CANCELLATION MESSAGE
(SGB, ELT(DT)
1. DISTRESS TRACKING COSPAS-SARSAT USER CANCELLATION ALERT
2. MSG NO 00192 AUMCC REF B274FA041FD4710
3. BEACON MESSAGE INFORMATION
BEACON TYPE SGB – ELT DISTRESS TRACKING
AIRCRAFT 24 BIT ADDRESS 7100CE ASSIGNED TO SAUDI ARABIA
AIRCRAFT OPERATOR DESIGNATOR SVA
TAC 16001 SERIAL NO 509
HEX ID B274FA041FD4 7100CEA3F00
COUNTRY OF BEACON REGISTRATION 403/SAUDI
ACTIVATION TYPE AUTOMATIC BY EXTERNAL MEANS (AVIONICS)
4. ALERT POSITION INFORMATION
DETECTED AT 03 MAY 24 085810 UTC BY MEOSAR
ALERT LAST DETECTED AT 03 MAY 24 085310 UTC
DOA – 02 25.1 N 046 06.2 E ESTIMATED ERROR UNKNOWN
5. OTHER INFORMATION
ELT(DT) POSITION DOES NOT REFERENCE ANY PREVIOUS POSITION
CANCELLATION CONFIRMED
BEACON CHARACTERISTICS PER TAC DATABASE PROVIDED
IN A SEPARATE MESSAGE
REMAINING BATTERY CAPACITY BETWEEN 75 AND 100 PERCENT
DETECTION FREQUENCY 406.0510 MHZ
6. REMARKS
THIS DISTRESS TRACKING MESSAGE IS BEING SENT TO APPROPRIATE
SAR AUTHORITIES
PROCESS THIS ALERT ACCORDING TO RELEVANT REQUIREMENTS
END OF MESSAGE
C-45
SAMPLE MESSAGE FOR SIT 185 (18)
SAMPLE 406 MHz POSITION ALERT (FGB, ELT(DT))
1. DISTRESS TRACKING COSPAS-SARSAT DOA POSITION CONFLICT ALERT
2. MSG NO 21013 CMCC REF 1D1220F03BBFDFF
3. BEACON MESSAGE INFORMATION
BEACON TYPE ELT DISTRESS TRACKING
AIRCRAFT 24 BIT ADDRESS 41E077 ASSIGNED TO G BRITAIN
AIRCRAFT OPERATOR DESIGNATOR MMB
HEX ID 1D1220F03BBFDFF
COUNTRY OF BEACON REGISTRATION 232/G BRITAIN
ACTIVATION TYPE MANUAL
GNSS POSITION PROVIDED BY EXTERNAL DEVICE
4. ALERT POSITION INFORMATION
DETECTED AT 04 AUG 23 101501 UTC BY MEOSAR
ALERT LAST DETECTED AT 04 AUG 23 101501 UTC
GNSS - 61 54.40 N 045 37.53 W
UPDATE TIME WITHIN 2 – 60 SECONDS OF DETECTION TIME
ALTITUDE OF GNSS LOCATION BETWEEN 1600 AND 2200 METRES
(BETWEEN 5200 AND 7200 FEET)
DOA - 62 00.1 N 046 06.2 W
5. OTHER INFORMATION
GNSS POSITION UNCERTAINTY PLUS-MINUS 2 SECONDS
OF LATITUDE AND LONGITUDE
DETECTION FREQUENCY 406.0400 MHZ
POSITION CONFLICT BASED ON DISTANCE SEPARATION OF AT LEAST 20KM
ELT(DT) POSITION DOES NOT REFERENCE ANY PREVIOUS POSITION
6. REMARKS
THIS DISTRESS TRACKING MESSAGE IS BEING SENT TO APPROPRIATE
SAR AUTHORITIES
PROCESS THIS ALERT ACCORDING TO RELEVANT REQUIREMENTS
END OF MESSAGE
C-46
SAMPLE MESSAGE FOR SIT 185 (19)
406 MHz TWC UPDATE ALERT – NEW POSITION
(SGB, TWC PLB SERIAL USER)
1. DISTRESS COSPAS-SARSAT OTHER INFORMATION UPDATE ALERT
2. MSG NO 00308 USMCC REF 12345
3. BEACON MESSAGE INFORMATION
BEACON TYPE PLB (RETURN LINK)
SERIAL NO 07551
HEX ID 1C7B006EFB00 000000BFDFF
COUNTRY OF BEACON REGISTRATION 227/FRANCE
HOMING SIGNAL 121.5 MHZ
GNSS POSITION PROVIDED BY INTERNAL DEVICE
4. ALERT POSITION INFORMATION
DETECTED AT 03 MAY 25 085310 UTC BY MEOSAR
ALERT LAST DETECTED AT 03 MAY 25 085310 UTC
GNSS – 02 24.40 N 046 04.11 E
TIME OF GNSS POSITION UPDATE: 03 MAY 25 085308 UTC
TIME SINCE GNSS LOCATION GENERATED: 0 MINUTES
ALTITUDE OF GNSS LOCATION: 125 METERS (410 FEET)
DOA – 02 25.1 N 046 06.2 E ESTIMATED ERROR 001NMS
5. OTHER INFORMATION
DETECTION FREQUENCY 406.0510 MHZ
TWC QUESTION: NUMBER OF PEOPLE IN DISTRESS?
TWC ANSWER: 2
TWC QUESTION: DO YOU NEED MEDICAL ASSISTANCE?
TWC ANSWER: YES
6. REMARKS
THIS BEACON HAS GALILEO TWO-WAY COMMUNICATION CAPABILITY
END OF MESSAGE
C-47
SAMPLE MESSAGE FOR
SIT 215, 216
FORMAT
MF \#
CONTENT
FRAMES
HEADER
(As per communication network requirements if any.)
1,2,3
/00011 00005/3660/91 280 1844
4,5,44
/215/3160/02
6,7,32
/002/35144/01
/91 281 0000 00.000
35,36
/+1624.4912 -8839.7195
-1719.9279/-001.28323 -002.07614 +007.11246
INFO
6,7,32
/106/02872/01
/91 281 0000 00.000
35,36
/-5287.2876 +4838.8309
+1711.7118/-001.55450 +000.87006 -007.08719
/LASSIT
/ENDMSG
TRAILER
(As per communication network requirements if any.)
C-48
SAMPLE MESSAGE FOR
SIT 217
FORMAT
MF \#
CONTENT
FRAMES
HEADER
(As per communication network requirements if any.)
1,2,3
/00011 00005/3660/15 280 1844
4,5, 44
/217/3160/02
1 28874U 05038A 15207.37312269 -.00000033 00000-0
00000+0 0 9999
2 28912 0.8892 59.3238 0001404 192.0935 85.5157
1.00281209 35179
INFO
1 27663U 03005A 15321.27963824 -.00000054 00000-
0 00000+0 0 9994
2 27663 56.7665 7.3715 0081081 16.3518
103.0593 2.00565996 93786
/LASSIT
/ENDMSG
TRAILER
(As per communication network requirements if any.)
C-49
SAMPLE MESSAGE FOR
SIT 415
FORMAT
MF \#
CONTENT
FRAMES
HEADER
(As per communication network requirements if any.)
1,2,3
/00022 00015/3660/80 100 1630
4-7,37,38
/415/3160/101/01135/80 161 1856
24.239/1234567.123
INFO
/LASSIT
/ENDMSG
TRAILER
(As per communication network requirements if any.)
C-50
SAMPLE MESSAGE FOR
SIT 416, 425, 445, 515, 525, 545, 605, 915
FORMAT
MF \#
CONTENT
FRAMES
HEADER
(As per communication network requirements if any.)
_______
1,2,3
/00030 00015/3660/80 160 1550
4,5
/416/3160
/THE NARRATIVE TEXT IN PRINTABLE CHARACTERS
IS PLACED HERE, WITH NO MORE THAN 69
CHARACTERS PER LINE.
INFO
QQQQ
/LASSIT
/ENDMSG
_______
TRAILER
(As per communication network requirements if any.)
Note:
MF \#4 must reflect SIT which is being used.
C-51
SAMPLE MESSAGE FOR
SIT 417
FORMAT
MF \#
CONTENT
FRAMES
HEADER
(As per communication network requirements if any.)
_______
1,2,3
/00022 00015/3660/80 100 1630
4-7,37,38a
/417/3160/011/01135/80 161 1856
24.239/12345678.123
INFO
/LASSIT
/ENDMSG
TRAILER
(As per communication network requirements if any.)
C-52
SAMPLE MESSAGE FOR
SIT 435, 535
FORMAT
MF \#
CONTENT
FRAMES
HEADER
(As per communication network requirements if any.)
1,2,3
/79566 00000/3160/08 191 1348
4,5,6,33
/535/3660/008/02
39,40
/DISC121A R/08 211 0000 00.00
INFO
39,40
/DISC243A R/08 211 0000 00.00
/TO: USMCC
FM: CTEC
SATELLITE S8 NOAA 16
COMMANDS TO BE SENT AT THE SOCC CONVENIENCE ON
29 JULY 2008
QQQQ
/LASSIT
/ENDMSG
TRAILER
(As per communication network requirements if any.)
Note:
MF \#4 must reflect the SIT being used.
C-53
SAMPLE MESSAGE FOR
SIT 510
FORMAT
MF \#
CONTENT
FRAMES
HEADER
(As per communication network requirements if any.)
1,2,3
/66289 00000/3160/01 147 2249
4,5,44
/510/3160/04
6,64,65,66
/008/-0039.238/+57.201/01 147 1936
6,64,65,66
/007/-0038.325/+99.999/01 147 1520
INFO
6,64,65,66
/004/-0007.357/-52.301/01 147 1641
6,64,65,66
/006/-0001.000/+99.999/01 147 2056
/LASSIT
/ENDMSG
TRAILER
(As per communication network requirements if any.)
C-54
SAMPLE MESSAGE FOR REPORTING
SATELLITE PAYLOAD STATUS USING
SIT 605 (1/5)
FORMAT
MF \#
CONTENT
FRAMES
HEADER
(As per communication network requirements if any.)
_______
1,2,3
/12345 00000/3660/97 123 1234
4,5
/605/5030
/
TO: ALL MCCS
FROM: USMCC
SUBJECT: INITIAL OPERATIONAL CAPABILITY FOR SARSAT-6
SAR PAYLOAD
DATA CONSIDERED OPERATIONAL IN COSPAS-SARSAT
(WWW.COSPAS-SARSAT.INT)
-------------------------------------------------------
---------------------------
406 SARR: OPERATIONAL
406 SARP (LOCAL): NOT OPERATIONAL
406 SARP (GLOBAL): NOT OPERATIONAL
PSEUDO MODE: NOT APPLICABLE
INFO
STATUS OF SAR PAYLOAD (WWW.COSPAS-SARSAT.INT)
-------------------------------------------------------
----------------------
L-BAND DOWNLINK: NORMAL
406 SARR: NORMAL
406 SARR GAIN CONTROL: AUTOMATIC
406 SARP (LOCAL): UNUSABLE
406 SARP (GLOBAL): UNUSABLE
PSEUDO MODE: NOT APPLICABLE
BANDWIDTH: NOT APPLICABLE
COMMENTS
-----------------
SARP FAILED AFTER LAUNCH
QQQQ
/LASSIT
/ENDMSG
TRAILER
(As per communication network requirements if any.)
[Ensure consistency of MEOSAR satellite status messages with document C/S A.001]
C-55
SAMPLE MESSAGE FOR REPORTING
SATELLITE PAYLOAD STATUS USING
SIT 605 (2/5)
FORMAT
MF \#
CONTENT
FRAMES
HEADER
(As per communication network requirements if any.)
_______
1,2,3
/12345 00000/2730/97 123 1234
4,5
/605/5030
/
TO: ALL MCCS
FROM: CMC
SUBJECT: DECLARATION OF OPERATION FOR COSPAS-6 SAR
PAYLOAD
DATA CONSIDERED OPERATIONAL IN COSPAS-SARSAT
(WWW.COSPAS-SARSAT.INT)
-------------------------------------------------------
--------------------------------
406 SARR: NOT APPLICABLE
406 SARP (LOCAL): OPERATIONAL
406 SARP (GLOBAL): OPERATIONAL
PSEUDO MODE: NOT APPLICABLE
INFO
STATUS OF SAR PAYLOAD (WWW.COSPAS-SARSAT.INT)
-------------------------------------------------------
-------------------
L-BAND DOWNLINK: NORMAL
406 SARR: NOT APPLICABLE
406 SARR GAIN CONTROL: NOT APPLICABLE
406 SARP (LOCAL): DEGRADED
406 SARP (GLOBAL): DEGRADED
PSEUDO MODE: NOT APPLICABLE
BANDWIDTH: NOT APPLICABLE
COMMENTS
------------------
FAILURE IN ONE OF THE ON-BOARD DRUS
QQQQ
/LASSIT
/ENDMSG
TRAILER
(As per communication network requirements if any.)
C-56
SAMPLE MESSAGE FOR REPORTING
SATELLITE PAYLOAD STATUS USING
SIT 605 (3/5)
FORMAT
MF \#
CONTENT
FRAMES
HEADER
(As per communication network requirements if any.)
_______
1,2,3
/12345 00000/3160/97 123 1234
4,5
/605/3660
/
TO: ALL MCCS
FROM: CMCC
SUBJECT: CHANGE IN STATUS FOR SARSAT-4 SAR PAYLOAD
DATA CONSIDERED OPERATIONAL IN COSPAS-SARSAT
(WWW.COSPAS-SARSAT.INT)
------------------------------------------------------
406 SARR: NOT OPERATIONAL
406 SARP (LOCAL): OPERATIONAL
406 SARP (GLOBAL): OPERATIONAL
PSEUDO MODE: NOT APPLICABLE
STATUS OF SAR PAYLOAD (WWW.COSPAS-SARSAT.INT)
------------------------------------------------------
INFO
L-BAND DOWNLINK: NORMAL
406 SARR: UNUSABLE
406 SARR GAIN CONTROL: NOT APPLICABLE
406 SARP (LOCAL): NORMAL
406 SARP (GLOBAL): NORMAL
PSEUDO MODE: NOT APPLICABLE
BANDWIDTH: NOT APPLICABLE
------------------------------------------------------
COMMENTS
------------------
THE 406 SARR IS NO LONGER USABLE, IT SHOULD NOW BE
CONSIDERED NOT OPERATIONAL
QQQQ
/LASSIT
/ENDMSG
TRAILER
(As per communication network requirements if any.)
C-57
SAMPLE MESSAGE FOR REPORTING
SATELLITE PAYLOAD STATUS USING
SIT 605 (4/5)
FORMAT
MF \#
CONTENT
FRAMES
HEADER
(As per communication network requirements if any.)
_______
1,2,3
/12345 00000/2730/97 123 1234
4,5
/605/5030
/
TO: ALL MCCS
FROM: CMC
SUBJECT: DECOMMISSIONING OF COSPAS-5 SAR PAYLOAD
DATA CONSIDERED OPERATIONAL IN COSPAS-SARSAT
(WWW.COSPAS-SARSAT.INT)
------------------------------------------------------
406 SARR: NOT APPLICABLE
406 SARP (LOCAL): NOT OPERATIONAL
INFO
406 SARP (GLOBAL): NOT OPERATIONAL
PSEUDO MODE: NOT APPLICABLE
STATUS OF SAR PAYLOAD (WWW.COSPAS-SARSAT.INT)
------------------------------------------------------
L-BAND DOWNLINK: UNUSABLE
406 SARR: NOT APPLICABLE
406 SARR GAIN CONTROL: NOT APPLICABLE
406 SARP (LOCAL): UNUSABLE
406 SARP (GLOBAL): UNUSABLE
PSEUDO MODE: NOT APPLICABLE
BANDWIDTH: NOT APPLICABLE
COMMENTS
------------------
COSPAS-5 DECOMMISSIONED ON 5 FEBRUARY 1996
QQQQ
/LASSIT
/ENDMSG
TRAILER
(As per communication network requirements if any.)
C-58
SAMPLE MESSAGE FOR REPORTING
SATELLITE PAYLOAD STATUS USING
SIT 605 (5/5)
FORMAT
MF \#
CONTENT
FRAMES
HEADER
(As per communication network requirements if any.)
_______
1,2,3
/12345 00000/3660/97 123 1234
4,5
/605/5030
/
TO: ALL MCCS
FROM: USMCC
SUBJECT: DECLARATION OF OPERATION FOR GOES-9 SAR
PAYLOAD
DATA CONSIDERED OPERATIONAL IN COSPAS-SARSAT
(WWW.COSPAS-SARSAT.INT)
------------------------------------------------------
406 SARR: OPERATIONAL
INFO
STATUS OF SAR PAYLOAD (WWW.COSPAS-SARSAT.INT)
------------------------------------------------------
406 SARR: NORMAL
406 SARR GAIN CONTROL: AUTOMATIC
BANDWIDTH: 406.005 - 406.045
POSITION: 135 W
DOWNLINK FREQUENCY/TYPE: 1544.5 MHZ / BROAD
COMMENTS
------------------
GOES-9 SHOULD BE CONSIDERED OPERATIONAL AS OF 5 MAY
QQQQ
/LASSIT
/ENDMSG
TRAILER
(As per communication network requirements if any.)
C-59
SAMPLE MESSAGE FOR
SIT 925
FORMAT
MF \#
CONTENT
FRAMES
HEADER
(As per communication network requirements if any.)
_______
1,2,3
/12345 00000/3160/94 194 2200
4,5
/925/3660
/A78D00597040401
INFO
/
FROM: CMCC
TO: USMCC
SUBJECT: BEACON REGISTRATION INFORMATION
BEACON INFO:
FF 0/PF 1/CC 316/UC SER/ID 0005724/MODEL
MAR/HS121/EC/AUT/00
HEX A78D0 05970 40401/LAT :::/LNG ::::
OWNER INFO:
LAST NAME: COAST GUARD-M FIRST NAME: N/A
COMPANY NAME: CCG DARTMOUTH BASE
ADDRESS: P.O. BOX 1000
CITY: DARTMOUTH PROVINCE: NS
COUNTRY: CANADA POSTAL CODE: B2Y SZ8
HOME PHONE: 123 45678 OFFICE PHONE: 987 654321 EXTENSION:
PREFERRED LANGUAGE: ENGLISH
COMMENTS: HOME NO: OPERATIONS NOTSHIP DESK (123 45678)
BUSS NO: FLEET SUPERINTENDENT (987 654321)
SEW WORKSHOP NO: (426 7017)
VESSEL INFO:
NAME: CCGS SIR WILLIAM ALE
REGISTRATION/LICENCE NUMBER: 807685
HOME PORT: DARTMOUTH
CALL SIGN: CGUM VESSEL LENGTH: 83 METERS
CLASS: COLOUR:
VESSEL TYPE: GOVERNMENT HULL: RED
HULL: SINGLE HULL SAIL: N/A
PROPULSION: POWER INBOARD SUPER STRUCTURE: WHITE
DISTINCTIVE FEATURE:
HELO DECK AND HANGAR; LIGHT ICEBREAKER/BUOY TENDER
COMMENTS: 1-28FT F.G. BOAT
1-28FT SELF-PROPELLED STEEL BARGE
1-15FT ZODIAC; 1-6 MAN LIFERAFT
CELLULAR: 123 456789
QQQQ
/LASSIT
/ENDMSG
TRAILER
(As per communication network requirements if any.)
Note:
MF \#41
The narrative text in printable characters is placed here, with no more than 69 characters per line.
C-60
SAMPLE MESSAGE FOR
SIT 927
FORMAT
FRAMES
MF \#
CONTENT
HEADER
(As per communication network requirements if any.)
1,2,3
/12345 00000/2270/18 194 2200
4,5
/927/5030
INFO
/0004567 001 0004005 0004321 B
/APPLIED TECHNOLOGY CORP.
/BEACON MODEL XXXYYY-01234
/
BEACON SUBTYPE: FLOAT-FREE
TEMPERATURE RANGE:-35C +70C
HOMING: 406=25 MW, AIS=20 MW
STROBE: BRIGHTNESS=0.75 CANDELA, DUTY-CYCLE=15
FLASH/MINUTE
/LASSIT
/ENDMSG
TRAILER
(As per communication network requirements if any.)
C-61
SAMPLE MESSAGE FOR
SIT 985
SGB CHARACTERISTICS BASED ON TAC NUMBER
1.
BEACON OPERATIONAL CHARACTERISTICS
2.
MSG NO 00192 AUMCC REF ADD481135B60000 - 21348
3.
HEX ID ADD481135B60 00000000000
4.
CHARACTERISTICS FOR TAC 12345
-
MANUFACTURER: APPLIED TECHNOLOGY CORP.
-
BEACON MODEL: XXXYYY-01234
-
BEACON TYPE: PLB
-
BEACON SUBTYPE: FLOAT-FREE
-
TEMPERATURE RANGE: -40C +55C
-
HOMING: 121.5=5 MW - 406=25 MW - AIS=20 MW
-
NAV DEVICE: GALILEO, GLONASS
-
STROBE: BRIGHTNESS=0.75 CANDELA, DUTY-CYCLE=15 FLASH/MINUTE
END OF MESSAGE
C-62
SAMPLE MESSAGE FOR ELT(DT) DATA TO BE SENT TO
THE LADR
<?xml version="1.0" encoding="UTF-8"?>
<ladr:DistressMessageUpload xmlns:fb=http://www.fixm.aero/base/4.2
xmlns:fx="http://www.fixm.aero/flight/4.2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ladr="http://www.eurocontrol.int/nm/fixm/app/ladr/1.0"xsi:schemaLocation=
"./files/schemas/LadrApplicationMessage/ladrmessage/LadrApplicationMessage.xsd">
<ladr:metadata>
<ladr:identifier codeSpace="urn:uuid">
eca23996-df29-4ee2-a886-bf8f150a75a4
</ladr:identifier>
<ladr:timestamp>2022-01-19T06:00:12Z</ladr:timestamp>
</ladr:metadata>
<ladr:distressMessage>
<ladr:contributorCode>001</ladr:contributorCode>
<ladr:typeOfAdt>
<ladr:type>
<ladr:type>ELT\_DT</ladr:type>
</ladr:type>
</ladr:typeOfAdt>
<ladr:adtActivationMethod>10003</ladr:adtActivationMethod>
<ladr:flight>
<fx:aircraft>
<fx:aircraftAddress>AF0F89</fx:aircraftAddress>
<fx:capabilities>
<fx:communication>
<fx:selectiveCallingCode>ABCD</fx:selectiveCallingCode>
</fx:communication>
<fx:survival>
<fx:extension xsi:type="ladr:LadrSurvivalCapabilitiesExtensionType">
<ladr:carriedEltHexIdentifier>21F25787C4BFDFF</ladr:carriedEltHexIdentifier>
</fx:extension>
C-63
</fx:survival>
</fx:capabilities>
<fx:registration>9GMKJ</fx:registration>
</fx:aircraft>
<fx:emergency>
<fx:lastContact>
<fx:position>
<fx:extension xsi:type="ladr:LadrLastPositionReportExtensionType">
<ladr:altitude uom="FT" altitudeSource="GNSS">10000</ladr:altitude>
<ladr:horizontalAccuracy uom=”M">62</ladr:horizontalAccuracy>
</fx:extension>
<fx:position>
<fb:position srsName="urn:ogc:def:crs:EPSG::4326">
<fb:pos>32.925 15.106</fb:pos>
</fb:position>
</fx:position>
<fx:timeAtPosition>2022-01-19T06:00:01Z</fx:timeAtPosition>
</fx:position>
</fx:lastContact>
</fx:emergency>
<fx:operator>
<fb:designatorIcao>ABC</fb:designatorIcao>
</fx:operator>
</ladr:flight>
</ladr:distressMessage>
</ladr:DistressMessageUpload>
– END OF ANNEX C –
D-1
ANNEX D
USEFUL INFORMATION FOR
STANDARD MESSAGE FORMATS BETWEEN MCC AND RCC
1.
Acknowledgment of distress alert message:
FM: RCC
TO: MCC
DISTRESS ALERT REPORT (NUMBER)
A. MESSAGE RECEIVED
2.
Request to repeat message:
FM: RCC
TO: MCC
DISTRESS ALERT REPORT (NUMBER)
A. REPEAT REQUESTED
3.
SAR operation completed:
FM: RCC
TO: MCC
DISTRESS ALERT REPORT (NUMBER)
A. CASE CLOSED (SUSPENDED)
B. BEACON TURNED OFF
4.
Request to "listen to" particular geographic area:
FM: RCC
TO: MCC
REQUEST FOR ALERT DATA
A. GEOGRAPHIC LOCATION
B. FREQUENCY
C. CANCELLATION DATE/TIME
5.
Request for SAR data associated with satellite beacon:
FM: RCC
TO: MCC
REQUEST FOR ADDITIONAL INFORMATION FROM BEACON REGISTER
A. BEACON IDENTIFICATION CODE
– END OF ANNEX D –
E-1
ANNEX E
COSPAS-SARSAT STANDARD FOR
THE TRANSMISSION OF SIT MESSAGES VIA FTP
1.
FILE TRANSFER PROTOCOL (FTP) COMMUNICATIONS
Each ground segment facility (e.g., MCC or LUT) communicating via FTP shall comply with the
applicable standards described in the Internet Engineering Task Group document RFC 959 - File
Transfer Protocol, which can be found at the following web address: www.ietf.org.
File Naming Convention
A ground segment facility shall send a message by writing a file on the FTP server of the receiving
facility. Each file shall contain exactly one message.
The FTP file name format shall be “?SRCE\_?DEST\_?CUR\#.TXT”, where:
- “?SRCE” is the name of the facility that originated this message (www.cospas-sarsat.int);
- “?DEST” is the name of the facility to which this message is being sent (www.cospas-
sarsat.int); and
- “?CUR#” is the Current Message Number (Message Field 1).
The FTP file name shall contain only upper-case characters. For example, a file with the name
“USMCC\_CMCC\_02345.TXT” contains Current Message Number 02345 sent by the USMCC to
the CMCC.
Any facility that wants to receive data via FTP shall provide the Host Name and/or Internet
Protocol (IP) Address, User Name, Password, and Message Directory Name in Table F-1, to enable
other ground segment facilities to place data on the FTP server of the receiving facility. On a
bilateral basis, the receiving and sending facility should agree on passwords and other security
measures. It is the responsibility of the receiving facility to provide adequate security for its FTP
server.
The sending facility shall write a file with a file name extension of “.TMP” on the FTP server of
the receiving facility. A file is given a temporary name to prevent the receiving facility from
processing a file before it is complete. Once the file transfer is complete, the sending facility shall
rename the file with an extension “.TXT”. Once the file has been renamed, the sending facility
shall not manipulate the file. The receiving facility shall not process files with an extension of
“.TMP”. The receiving facility shall be responsible for disposing of files placed on its FTP server.
If the receiving MCC detects an anomalous condition in the FTP file transfer, it shall notify the
transmitting MCC. If an FTP file transfer fails for any reason the transmitting MCC shall try to
resend the message, and notify the receiving MCC if the failure persists.
If the receiving MEOLUT detects an anomalous condition in the FTP file transfer, it shall notify
E-2
its associated MCC. If an FTP file transfer fails for any reason the transmitting MEOLUT shall
maintain a 10-minute buffer of messages. Upon re-establishment of a connection the transmitting
MEOLUT shall send the buffered messages. If MEOLUT FTP file transfer failures persist, the
transmitting MEOLUT shall notify its associated MCC.
Each facility communicating via FTP shall operate in binary transfer mode.
2.
FILE TRANSFER PROTOCOL (FTP) INFORMATION LIST
A list of information used to send messages to a facility via FTP is provided in this section. This
list is composed of 6 items:
1. Receiving Ground Segment Facility,
2. Host Name,
3. IP Address,
4. User Name,
5. Password,
6. Message Directory Path.
2.1
Receiving Ground Segment Facility
The name of the ground segment facility to receive data via FTP. For an MCC, this name matches
the MCC Identification Code in the Cospas-Sarsat website. For a MEOLUT, this name matches
the MEOLUT name in the Cospas-Sarsat website, noting that spaces are always replaced with an
underscore (“\_”) character.
2.2
Host Name
This is the FTP Host Name of the receiving ground segment facility. ***
2.3
Internet Protocol (IP) Address
This is the Internet Protocol Address referenced to reach the receiving ground segment facility.
***
2.4
User Name
The User Name required to login to the FTP server of the receiving facility. If the value is “Sending
Ground Segment facility Name”, then the user name is the name of the sending ground segment
facility, per the Cospas-Sarsat website (www.cospas-sarsat.int). ***
E-3
2.5
Password
The password required to access the FTP server of the receiving facility. ***
“*** indicates that the information is provided on a need to know basis.”
2.6
Message Directory Path
The path of the directory into which message files shall be written. <facilityname> indicates that
each facility will put messages in a sub-directory per facility, where the sub-directory name is the
name of the sending facility, per the Cospas-Sarsat website, (www.cospas-sarsat.int).
3.
SECURITY
All ground segment facilities with an Internet connection must be protected by firewall technology.
3.1
Passwords
Ground segment facilities shall formulate passwords using security best practices. The passwords
shall have the following characteristics:
−
contain at least 8 characters,
−
not have any characters that are “blank”,
−
six of the characters shall occur once in the password,
−
at least one of the characters must be a number (0-9) or a special character (~, !, $, \#,
%, \*) – see Table E-1,
−
at least one of the characters must be from the alphabet (upper or lower case),
−
passwords shall not include:
•
words found in any dictionary (English or other language), spelled forward or
backward,
•
system User Ids,
•
addresses or birthdays,
•
common character sequences (e.g., 123, ghijk, 2468),
•
vendor-supplied default passwords (e.g., SYSTEM, Password, Default, USER,
Demo),
•
words that others might guess.
Ground segment facilities shall change passwords at least semi-annually.
E-4
To protect passwords from unauthorized disclosure facilities shall exchange passwords by
telephone or facsimile if allowed by security authorities at each facility. Facilities shall coordinate
the exchange of new passwords during the last full work week of April and October of each year.
Facilities exchanging passwords shall agree on an implementation date that is not later than the
end of the week during which new passwords are exchanged.
13Table E-1: FTP Password Special Characters
SYMBOL
NAME
~
TILDE
!
EXCLAMATION POINT
@
AT SYMBOL
\#
OCTOTHORPE
$
DOLLAR SIGN
%
PERCENT
^
CHAPEAU / HAT
&
AMPERSAND
\*
ASTERIX
)
CLOSE PARENTHESES
(
OPEN PARENTHESES
`
APOSTROPHE
-
HYPHEN
“
QUOTATION
/
SLASH
3.2
Access
Access permissions on all directories and files on the FTP server shall follow the principle of “least
permissions” to ensure that no unauthorized access is allowed. “Least permissions” means that
each user is granted the minimum access required to perform their assigned tasks.
Facilities shall check IP addresses to limit server access only to authorized users.
Facilities shall allow access to their FTP servers only through ports 20 and 21. All other ports that
are not being used shall be closed.
3.3
Anonymous FTP
Facilities shall not use anonymous FTP.
3.4
Encryption of Critical Information
Facilities shall implement methodologies to encrypt FTP login names (userids) and passwords
during file transmission to prevent unauthorized disclosure. These methodologies include FTP
E-5
over Internet Virtual Private Network (VPN). Standards for the use of hardware VPN are contained
in Annex F.
3.5
Monitoring for a Potential Security Breach
Facilities shall monitor the FTP servers for abnormal activity. If a breach of security is found,
ground segment facilities shall notify all FTP correspondents as soon as possible to minimize
exposure.
Examples of items that should be monitored on a FTP server include:
•
Event logs:
•
should be set and checked for failed login attempts,
•
gaps in time and date stamps,
•
attempts to elevate privileges;
•
Disk Space:
•
unexplained loss of disk space,
•
unexplained disk access;
•
Unexplained events:
•
large number of failures (system or programs crash),
•
unexplained process or programs running,
•
new users added,
•
virus protection has been disabled.
3.6
Security Patches
Facilities shall apply the latest software and security patches to their FTP servers as soon as
possible.
– END OF ANNEX E –
F-1
ANNEX F
COSPAS-SARSAT STANDARD FOR THE TRANSMISSION
OF SIT MESSAGES VIA HARDWARE VPN
1.
INTRODUCTION
A Virtual Private Network (VPN) provides a secure method to transmit information over the
Internet. A tunnelling technology such as Internet Protocol IPSec is used to set up private
connections between separate sites. A tunnel provides a means for forwarding data across a
network from one site to another, as if they were directly connected.
Prior to an MCC setup/installation an MCC installer should ensure that the IP address range
selected for the MCC’s network does not conflict with the IP range of all other MCCs with which
it may potentially connect.
IP conflicts will not stop the creation of the VPN tunnel but will prevent the transfer of data using
FTP between the hosts.
This aspect is especially relevant when a new ground segment is being installed.
2.
STANDARDS
2.1
Tunnelling
MCCs that use VPN to transmit data via the Internet shall use IPSec. IPSec is a framework of open
standards developed by the Internet Engineering Task Force (IETF). IPSec provides security for
transmission of sensitive information over the Internet. IPSec acts at the network layer, protecting
and authenticating IP packets between participating IPSec devices (“peers”), such as Cisco routers.
IPSec provides the following network security services:
•
Data Confidentiality - The IPSec sender can encrypt packets before transmitting them across
a network.
•
Data Integrity - The IPSec receiver can authenticate packets sent by the IPSec sender to
ensure that the data has not been altered during transmission.
•
Data Origin Authentication - The IPSec receiver can authenticate the source of the IPSec
packets sent. This service is dependent upon the data integrity service.
•
Anti-Replay - The IPSec receiver can detect and reject replayed packets.
F-2
2.2
Mutual Confirmation Method
This step performs the function of a negotiator. It will allow two IPSec nodes to decide which
algorithms they will use for authentication and encryption, as well as how long this session will
last. The Cospas-Sarsat standard is the PreShared Key Internet Key Exchange (IKE) method.
2.3
Code Algorithm (Crypto Algorithm)
This step applies a mathematical formula to the information to be encrypted. MCCs should
implement the highest level of encryption that is available on a bilateral basis. Possible choices
include:
•
DES,
•
3DES,
•
CAST128,
•
Blowfish.
2.4
Confirmation Algorithm
This step applies an algorithm that is used to validate that both ends of a session (MCCs) are in
fact who they claim to be. The Cospas-Sarsat standard is the MD5 confirmation algorithm.
2.5
Perfect Forward Security
Perfect Forward Security (PFS) should be set to group 1, 2, or 3.
2.6
Lifetime
Specify lifetime at an agreed standard time (e.g., 120 minutes).
3.
HARDWARE CONFIGURATION
Hardware VPN is defined as any piece of commercial or industrial-grade hardware that supports
international and non-proprietary VPN standards, for example IPSec. Some possible hardware
VPN devices include, but are not limited to Routers, Concentrators, VPN appliances and Firewalls,
in any combination.
These devices provide the security called for in section E.3.4 of the FTP standard (Annex E).
4.
CONFIGURING FTPV BETWEEN MCCS
The following two templates can be used when configuring FTPV between two MCCs. The two
MCCs are shown as XXMCC and YYMCC.
F-3
The first template, Table G-1, is used for configuring the VPN concentrators at each end of the
VPN.
The second column lists all parameters configured on the XXMCC VPN concentrator. The third
column lists all parameters configured on the YYMCC VPN concentrator. The IKE Peer Address
on the XXMCC VPN concentrator is provided by YYMCC. The IKE Peer Address on the
YYMCC VPN concentrators is provided by XXMCC. All other IKE and IPSEC parameters are
the same on both VPN concentrators and must be negotiated by the two MCCs.
14Table F-1: Template for VPN Concentrator Parameters
FTP-VPN Configuration
As Configured on the XXMCC
VPN Concentrator
As Configured on the YYMCC
VPN Concentrator
Peer Site ID
YYMCC
XXMCC
IKE Details
IKE Peer Address
IKE Encryption
IKE Authentication
IKE Key Exchange
IKE Pre-Shared Key
IKE Time Lifetime
IKE Data Lifetime
IPSEC Details
IPSEC Encryption
IPSEC Authentication
IPSEC PFS
IPSEC Data Lifetime
IPSEC NAT-T
IPSEC Encapsulation
Mode
IPSEC Connection Type
The second template, Table G-2, lists the information required by each MCC to establish a FTP
connection and to transmit SIT messages. The information in the second column lists all
information required by XXMCC to transmit SIT messages to YYMCC. The information in the
second column is provided by YYMCC for use by XXMCC. The third column lists all information
required by YYMCC to transmit SIT messages to XXMCC. The information in the third column
is provided by XXMCC for use by YYMCC.
F-4
15Table F-2: Template for FTP Server Logon Information
FTP Server Logon Information
Used by XXMCC to Log onto
YYMCC FTP Server
Used by YYMCC to Log onto
XXMCC FTP Server
Remote Primary FTP
Address
Remote Secondary FTP
Address
FTP Username
FTP Password
Incoming Directory
Data Transfer
Examples of the templates are shown in the Tables F-3 and F-4 that list parameters and information
that could be used by AUMCC and INMCC.
16Table F-3: Example of Template of VPN Concentrator Parameters
FTP-VPN Configuration
As Configured on the AUMCC
VPN Concentrator
As Configured on the
INMCC VPN Concentrator
Peer Site ID
INMCC
AUMCC
IKE Details
IKE Peer Address
220.228.67.145
203.20.107.66
IKE Encryption
3DES-168
3DES-168
IKE Authentication
MD5/HMAC-128
MD5/HMAC-128
IKE Key Exchange
DH Group 2
DH Group 2
IKE Pre-Shared Key
***
***
IKE Time Lifetime
IKE Data Lifetime
IPSEC Details
IPSEC Encryption
3DES-168
3DES-168
IPSEC Authentication
ESP/MD5/HMAC-128
ESP/MD5/HMAC-128
IPSEC PFS
Group 2
Group 2
IPSEC Data Lifetime
IPSEC NAT-T
Not Enabled
Not Enabled
IPSEC Encapsulation
Mode
Tunnel
Tunnel
IPSEC Connection Type
Bi-directional
Bi-directional
F-5
17Table F-4: Example of Template of FTP Server Logon Information
FTP Server Logon Information
Used by AUMCC to Log onto
INMCC FTP Server
Used by INMCC to Log onto
AUMCC FTP Server
Remote Primary FTP
Address
106.104.13.110
203.119.16.99
Remote Secondary FTP
Address
106.104.13.115
FTP Username
***
***
FTP Password
***
***
Incoming Directory
.
.
Data Transfer
Binary
Binary
Note that the IKE Pre-Shared Key, FTP Username and FTP Password are shown as “***” in the
above tables as the information must be kept secure. Exchange of these details must be undertaken
via fax or telephone only. Other details may be transmitted by email.
– END OF ANNEX F –
G-1
ANNEX G
COSPAS-SARSAT STANDARD FOR THE TRANSMISSION
OF SIT MESSAGES VIA AFTN
1.
INTRODUCTION
The Aeronautical Fixed Telecommunications Network (AFTN) is a worldwide system of
aeronautical fixed circuits provided, as part of the aeronautical fixed service, for the exchange of
messages, and/or digital data between aeronautical fixed stations having the same or compatible
communications characteristics. Communication procedures for the AFTN are detailed in
Annex 10 to the Convention on International Civil Aviation, Volume II, Communication
Procedures, which can be downloaded from the ICAO web site.
AFTN provides a store-and-forward messaging service for the conveyance of text messages, which
supports the entire character set authorised for use in Cospas-Sarsat SIT messages.
All AFTN messages include a Transmission Identification (TI) of the form “MSO003” where the
TI is comprised of the Channel Identifier (CI) = “MSO” and the Channel Sequence Number
(CSN)=”003”.
Channel checks (heartbeat) are undertaken between an AFTN station and its AFTN
communication centre to ensure the link is available and for synchronising of message numbers.
These checks are usually undertaken every twenty minutes on the hour and will contain a unique
Channel Sequence Number (CSN).
Although the AFTN communications centre ensures that messages are received correctly in terms
of the “heading, address, origin and ending syntax” the system does not perform checks to validate
the message text. Some MCCs have reported corruption in AFTN messages. The corruption can
be quite severe and obvious to the recipient, however at other times they may be extremely difficult
to detect.
The ICAO AFTN standard requires long term retention of AFTN traffic records to be maintained
for 30 days. The AFTN standard for retaining messages does not obviate the MCC archiving
requirement specified in document C/S A.005 (MCC specification).
G-2
2.
CATEGORIES AND PRIORITIES OF MESSAGES
The AFTN supports the following categories of messages:
a)
distress messages;
b)
urgency messages;
c)
flight safety messages;
d)
meteorological messages;
e)
flight regularity messages;
f)
aeronautical information services (AIS) messages;
g)
aeronautical administrative messages; and
h)
service messages.
Each AFTN message type has an associated message priority. Section 5 provides
recommendations in respect of message priorities for the various SIT message types. The highest
priority used in the AFTN is SS, followed by DD.
Distress messages (priority indicator SS)
This message category comprises those messages sent by mobile stations reporting that they are
threatened by grave and imminent danger and all other messages relative to the immediate
assistance required by the mobile station in distress.
AFTN requires that messages transmitted with an SS priority be acknowledged using the format
defined by ICAO. MCCs should ensure that SS priority messages are acknowledged by the MCC
itself.
Urgency messages (priority indicator DD)
This category comprises messages concerning the safety of a ship, aircraft or other vehicles, or of
some person on board or within sight.
3.
AFTN MESSAGE FORMAT
The AFTN message formats for the International Telegraph Alphabet No.2 (ITA2) and
International Alphabet No.5 (IA5) formats are provided in Figures 1 and 2. AFTN messages are
comprised of a header, message body (SIT MESSAGE), and trailer. The SIT message is to be
inserted into the fields identified as “Message Text” indicated in Figures 1 and 2.
AFTN messages cannot exceed 2100 characters in total, and the content of the SIT message inserted
into an AFTN message cannot exceed 1800 characters.
G-3
3.1
AFTN Address Indicator
An AFTN address comprises 8 characters of the form:
a)
four-letter location indicator listed in ICAO document, Doc 7910, e.g., YSAR for
the Australian RCC/AUMCC, Canberra;
b)
three-letter designator as listed in ICAO document, Doc 8585, e.g., ZSZ (which has
been allocated for Sarsat Centre) for the French MCC and YCY for the Norwegian
MCC; and
c)
an additional letter which can represent a department, division or process within the
organization/function of the originator. The letter X shall be used to complete the
eight-letter address when explicit identification is not required.
3.2
Multiple Address Distribution
AFTN includes a facility for distributing messages to multiple addresses. The use of this capability
is not recommended for communications from an MCC since it reduces the effectiveness of
message number sequence checking.
G-4
4.
EXAMPLES OF AFTN MESSAGES
The following are examples of AFTN messages using the IA5 format:
a) Example of an SS Priority AFTN Message transmitted by the UKMCC to the FMCC:
UKZ003
< Transmission Identification >
SS LFIAZSZX
050021 EGQPZSZX
/55325 00000/2320/04 065 0021
/126/2270/008/01
/2321/-4/+00108.0 001.0 -12.20/04 064 2156 11.05/0
/5/18.756/0000/18
/5116209D1E00104FF6F59000000000
/+273/+56.342/+119.438/000 002.7 001.2/77/00 000 0000/4/001.0 001.0
/+273/+70.036/+037.655/000 007.3 003.1/23/00 000 0000/3/004.0 003.0
/LASSIT
/ENDMSG
b) Example of an SS Priority Acknowledgement Message from FMCC to UKMCC:
FRZ457
SS EGQPZSZX
050022 LFIAZSZX
R 050021 EGQPZSZX
c) Example of a DD Priority AFTN Message transmitted by the SPMCC to the NMCC:
SPZ101
DD ENBOYCYX
260934 GCMPZSZX
/66934 00000/2240/04 054 0934
/115/2570/004/01
/2241/+2/+02400.0 018.2 -25.21/04 054 0919 07.00/0
/3/02.856/0000/01/0247 99
/+257/+55.394/+012.072/088 008.1 004.5/50/04 054 0956/3/005.4 030.8
/+232/+52.975/-013.808/118 008.2 004.6/50/04 054 0956/3/005.2 029.8
/LASSIT
/ENDMSG
G-5
5.
RECOMMENDED SIT MESSAGE AFTN PRIORITIES
Table 1 provides the suggested AFTN priorities for the various SIT message types. MCCs may,
on a bilateral basis, use different priorities from those suggested.
18Table G-1: Suggested AFTN Priority for SIT Messages
SIT
Number
Type
Suggested
Priority
Comments
121, 141
406 INTERFERER NOTIFICATION
DD
122, 142
322,342
406 INCIDENT (NO DOPPLER and NO DOA
SS
123, 143
323, 343
406 POSITION CONFLICT (ENCODED
ONLY)
SS
124, 144
324, 344
406 CONFIRMATION (ENCODED ONLY)
SS
125, 145
406 INCIDENT
SS
126, 146
406 POSITION CONFLICT
SS
127, 147
406 POSITION CONFIRMATION
SS
132, 136
332, 336
406 NOTIFICATION OF COUNTRY OF
REGISTRATION (ENCODED ONLY)
DD / SS
133 & 137
406 NOTIFICATION OF COUNTRY OF
REGISTRATION
DD / SS
134, 138
334, 338
406 RLSP (ENCODED ONLY)
SS
135, 139
406 RLSP
SS
COSPAS-SARSAT DISTRESS ALERTS TO
RCCs/SPOCs
DD / SS
ORBIT VECTORS
DD
SARP CALIBRATION
DD
406 MHz SARR FREQUENCY
CALIBRATION OFFSET
DD
SYSTEM STATUS TO ALL MCCs
SS / DD
Operator to decide dependent
upon content
NARRATIVE MESSAGES FOR MCCs
SS / DD
Operator to decide dependent
upon content
406 BEACON REGISTRATION
INFORMATION (15 HEX ID)
DD / SS
406 BEACON REGISTRATION
INFORMATION (23 HEX ID)
DD / SS
927, 985
BEACON OPERATIONAL
CHARACTERISTICS INFORMATION
DD / SS
G-6
7Figure G.1: Message Format International Telegraph Alphabet No.2 (ITA2)
![Image 1 from page 155](/images/cospas-sarsat/A-series/A002/A002_page_155_img_1.png)
G-7
8Figure G.2: Message Format International Alphabet No.5 (IA5)
– END OF ANNEX G –
![Image 1 from page 156](/images/cospas-sarsat/A-series/A002/A002_page_156_img_1.png)
H-1
ANNEX H
IMPLEMENTATION PLAN FOR NEW COMMUNICATION LINKS
1.
IMPLEMENTATION PHASES
1.1
Phase I - Internal Development and Testing
In order to implement a new communication link, each MCC must begin with a phase of internal
development and testing. This may require the procurement of communication equipment,
specialized hardware, physical connections and/or other communication provider services.
The key purpose of this phase is to ensure that the new communication link is properly installed,
configured and coded. Ideally, a capability should be available within the MCC environment to
facilitate near “real world” testing. Completion of comprehensive development and testing is
essential before proceeding to subsequent phases.
1.2
Phase II - Nodal Level Testing and Activation
Nodal MCCs operate as central entities or “hubs” in the Cospas-Sarsat Network and should be
capable of handling any new communication link or protocol. There is limited benefit for an MCC
within a DDR to implement a protocol that the nodal MCC does not yet support.
Nodal MCCs can in effect validate the new communication link while also establishing it at the
core level of the Cospas-Sarsat System network. Lessons learned and resulting adjustments made
can be passed along to other MCCs to minimize costs resulting from redundant efforts. During
this phase, each nodal MCC coordinates bilaterally, first testing and then activating each link.
1.3
Phase III - DDR Level Testing and Activation
This phase provides for establishing a new communication protocol between the nodal MCC and
each of the MCCs within its DDR. When this phase starts, the nodal MCC will have operational
links with most other nodal MCCs, and the experience gained should facilitate efforts under Phase
III.
1.4
Phase IV - System Wide Testing and Activation
This phase provides for establishing links between MCCs as well as between MCCs and - other
destinations, as appropriate. The intent is to test and activate all links outside the standard nodal
configuration, most importantly the connections between additional MCC pairings to support the
transmission of Cospas-Sarsat narrative traffic. Communication agreements between neighbouring
MCCs shall be addressed during this phase.
– END OF ANNEX H –
I-1
ANNEX I
PROTOCOL FOR THE TRANSMISSION OF
SIT MESSAGES VIA ELECTRONIC MAIL (EMAIL)
1.
EMAIL COMMUNICATIONS
1.1
Electronic mail is a store-and-forward method of composing, sending, receiving and
storing messages over Internet or other networks.
1.2
Email is an optional means of communication that shall be adopted on a bilateral
contingency basis. Email should be used during the period it takes to implement MCC
backup procedures (less than 30 minutes) when AFTN and FTP-VPN have failed or are
unavailable.
1.3
Email communication shall be organized via mail Servers announced by MCCs. In the
main, these mail Servers are the ones used for general purpose unformatted
communications from MCCs.
1.4
Mail Boxes shall be created at Mail Servers exclusively for exchange by SIT information.
1.5
An MCC shall create and send messages with SIT data which would be transmitted via
Internet to Mail Box of the receiving MCC. The receiving MCC shall be responsible for
disposing the messages received in its Mail Box to the SIT processing programs of MCC.
1.6
Where a front-end communications server is used for Email transmissions it shall adhere to
the national Administration’s Email security provisions. The following Cospas-Sarsat
Email security provisions outlined in section I.3 may be used as a guide by national
Administrations in addition to any government security measures.
I-2
2.
MESSAGE FORMING CONVENTION
2.1
Each message shall contain exactly one SIT message. The message is formed of the
following parts:
1. Receiving MCC Address (To),
2. Subject field,
3. Message Body.
2.2
Receiving MCC Address (To) is formed as Recipient-Name@Domain-Name and is
received from corresponding MCC on need-to-know basis. Example: sit-reception-
?777@marsat.ru
2.3
Subject field format shall include “?SRCE\_?DEST\_?CUR\#.”, where:
- “?SRCE” is the Source MCC Name (per www.cospas-sarsat.int);
- “?DEST” is the Destination MCC Name (per www.cospas-sarsat.int); and
- “?CUR#” is the Current Message Number (Message Field 1).
The Subject field shall contain only upper case characters. For example, a file with the name
“USMCC\_CMCC\_02345” contains Current Message Number 02345 sent by the USMCC
to the CMCC.
2.4
Message Body shall be created using SIT conventions so only text mode will be used. No
attachments should be included in the message.
I-3
3.
SECURITY
3.1
To ensure security of the Cospas-Sarsat System MCCs using Email for SIT messages
transmission must be protected by firewall. The computer used for email communications
should be protected inside a demilitarized zone (DMZ).
3.2
The Software Firewall used shall be limited to highest level of security.
3.3
Message shall be encrypted to prevent corruption.
3.4
Adequate filters shall be implemented (on Email address, electronic signature, IP address,
etc.). These controls shall be made before the messages are processed by MCC system.
3.5
The identity of the sender shall be determined via a system check or via operational
coordination.
3.6
Initial check of message formats (SIT format, filename, etc.) shall be undertaken prior to
processing of the message by the MCC. Any non-conforming message shall be rejected
and an alarm raised to allow operator intervention.
3.7
Receipt of multiple redundant messages shall result in an alarm being raised to allow for
operator intervention.
3.8
Routine Cospas-Sarsat message number checks shall be adopted to identify any message
loss including operational checks during periods of low message traffic exchange.
3.9
All transmitted messages shall be archived.
- END OF ANNEX I -
- END OF DOCUMENT -
Cospas-Sarsat Secretariat
1250 boulevard René-Lévesque West, Suite 4215, Montréal, Québec H3B 4W8 Canada
Telephone: + 1 514 500 7999
Fax: + 1 514 500 7996
Email: mail@cospas-sarsat.int
Website: www.cospas-sarsat.int
Reference in New Issue View Git Blame Copy Permalink