Ground Segment Changes CSC-71

Ground Segment Changes CSC-73 - MCC
SUBMISSION DEADLINE: 1 April 2026
At CSC-73, the Council decided to approve the list of new changes to ground segment equipment (GSE) and associated implementation dates agreed at JC-39, as shown at Annex 26 to the JC-39 Report, as amended at CSC-73/OPN/SR/Annex 10. The Council invited Ground Segment Providers to report their status of implementation of approved changes to GSE using the survey tool provided by the Secretariat, with a submission deadline of 1 April 2026, to enable consideration at JC-40.
Please note that this survey contains questions for over 200 action items - there is no facility to save and resume your work, please be prepared to complete it entirely before proceeding.

A PDF version of this list (for reference purposes only) can be found here: https://www.cospas-sarsat.int/images/cospas_sarsat/pdf_uploads/2025-06-GSE_changes_complete_list_approved_at_CSC-73.pdf

Responses are required for all items listed. Available responses are:
- Compliant
- Planned Compliance
- Non-compliant
Example explanatory note:
- system not yet commissioned
- equipment scheduled to be installed/commissioned in [2027]
Note: If there are any questions, concerns, or problems completing this form please contact mail@cospas-sarsat.int
- Report Origin
- Submitting Officer or Contact Person
  
  First NameLast Name
- Submitting Officer or Contact Person - E-mail address
  example@example.com


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee / Council References	Document Section(s)/Page(s)
LG-MCC-1	Changes in the RLS protocol (per C/S T.001, section A3.3.7 and Figure A.10, no fixed bits starting in bit 107)	Critical	Adaptive	Dec-17	JC-30 Report, sections 5.1.32 to 5.1.37	A.001 - Issue 7 - Rev. 1: Table II / B.4, Annex II / B.10.1; A.002 - Issue 6 - Rev. 1: MF #62, pages B-28 and B-29

LG-MCC-1
LG-MCC-1 Planned compliance date

MonthDayYear
Date
LG-MCC-1 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee / Council References	Document Section(s)/Page(s)
LG-MCC-2	Processing orbit numbers for LEOSAR satellites that exceed 5 digits	Critical	Adaptive	Jun-17	JC-30 Report, Annex 5	A.002 - Issue 6 - Rev. 1: Annex B, MF #7, pages B-2 and B-13

LG-MCC-2
LG-MCC-2 Planned compliance date

MonthDayYear
Date
LG-MCC-2 Comments

What type of MCC does this report describe?
The following questions relate to LGM MCC only. If you do not have an LGM MCC, please select "LG" and click "Next" - you will proceed immediately to the end of the form.


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-001	Sending new non-matching encoded position (referencing the most recent encoded position)	Critical	Adaptive	Jun-17	JC-30 Report, Annex 4	A.001 - Issue 7 - Rev. 1: section 3.2.3.2, page 3-9 (see a.ii.b)

MCC-001
MCC-001 Planned compliance date

MonthDayYear
Date
MCC-001 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-002	Sending alerts with better quality DOA position (taking into account default values)	Critical	Corrective	Jun-17	JC-30 Report, Annex 4	A.001 - Issue 7 - Rev. 1: section 3.2.3.3, page 3-9

MCC-002
MCC-002 Planned compliance date

MonthDayYear
Date
MCC-002 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee References	Document Section(s)/Page(s)
MCC-003	Beacon message validation - same beacon ID match	Critical	Corrective	Jun-17	JC-30 Report, Annex 4	A.001 - Issue 7 - Rev. 1: section II/B.1.1.3, page II/B-5

MCC-3
MCC-3 Planned compliance date

MonthDayYear
Date
MCC-3 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-004	Clarification of the distribution of DOA position conflict alerts (based on the time of lastest beacon burst)	Critical	Corrective	Jun-17	JC-30 Report, Annex 4	A.001 - Issue 7 - Rev. 1: section 3.2.3.2, page 3-8, section II/B.5.4.1, page II/B-19

MCC-004
MCC-004 Planned compliance date

MonthDayYear
Date
MCC-004 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-005	Changes to the message field character text description for MF #64 to 84 and MF #87 to 89	Critical	Corrective	Jun-17	JC-30 Report, Annex 5	A.002 - Issue 6 - Rev. 1: Annex B, MF #24, page B-1

MCC-005
MCC-005 Planned compliance date

MonthDayYear
Date
MCC-005 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-006	Suspect MEOSAR alerts	Critical	Enhancement	Jun-17	JC-30 Report, Annex 5	A.002 - Issue 6 - Rev. 1: Annex B, MF #61, page B-28

MCC-006
MCC-006 Planned compliance date

MonthDayYear
Date
MCC-006 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-007	Return link message information	Critical	Adaptive	Jun-17	JC-30 Report, Annex 5	A.002 - Issue 6 - Rev. 1: Annex B, MF #62, pages B-28 and B-29

MCC-007
MCC-007 Planned compliance date

MonthDayYear
Date
MCC-007 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-008	Received transponded bursts	Critical	Corrective	Jun-17	JC-30 Report, Annex 5	A.002 - Issue 6 - Rev. 1: Annex B, MF #80, pages B-11 and B-31

MCC-008
MCC-008 Planned compliance date

MonthDayYear
Date
MCC-008 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-009	End of data line after expected horizontal error	Critical	Corrective	Dec-16	JC-30 Report, Annex 5	A.002 - Issue 6 - Rev. 1: Annex C, page C-5

MCC-009
MCC-009 Planned compliance date

MonthDayYear
Date
MCC-009 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-010	Sample message references to next expected detection time above	Critical	Corrective	Jun-17	JC-30 Report, Annex 5	A.002 - Issue 6 - Rev. 1: Annex C, page C-21

MCC-010
MCC-010 Planned compliance date

MonthDayYear
Date
MCC-010 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-011	MEOSAR alert last detection time	Critical	Enhancement	Jun-17	JC-30 Report, Annex 5	A.002 - Issue 6 - Rev. 1: Annex B, MF #48, page B-21, MF #61, page B-26, Annex C, pages C-21 and C-24

MCC-011
MCC-011 Planned compliance date

MonthDayYear
Date
MCC-011 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-012	Processing orbit numbers for LEOSAR satellites that exceed 5 digits	Critical	Adaptive	Jun-17	JC-30 Report, Annex 5	A.002 - Issue 6 - Rev. 1: Annex B, MF #7, pages B-2 and B-13

MCC-012
MCC-012 Planned compliance date

MonthDayYear
Date
MCC-012 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-013	Processing time for alert data	Critical	Adaptive	Jun-17	JC-30 Report, Annex 8	A.005 - Issue 4 - Rev. 1 (CSC-57): section 5.6, page C-3

MCC-013
MCC-013 Planned compliance date

MonthDayYear
Date
MCC-013 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-014	Changes in the RLS protocol (per C/S T.001, section A3.3.7 and Figure A.10, no fixed bits starting in bit 107)	Critical	Adaptive	Jun-17	JC-30 Report, sections 5.1.32 to 5.1.37	A.001 - Issue 7 - Rev. 1: Table II / B.4, Annex II / B.10.1; A.002 - Issue 6 - Rev. 1: MF #62, pages B-28 and B-29

MCC-014
MCC-014 Planned compliance date

MonthDayYear
Date
MCC-014 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-015	Default the expected horizontal error (message field #54d) to UNKNOWN	Critical	Adaptive	Jun-17	CSC-57/OPN Report, Section 5.3.5	A.002 - Issue 6 - Rev. 1: Table B-1, page B-10

MCC-015
MCC-015 Planned compliance date

MonthDayYear
Date
MCC-015 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-016	MCC Processing of RLS Beacon incident alert Use bits 37-40 to identify RLS FGB. After position confirmation: b) distribution of unlocated alerts for RLS beacons; c) use TCA if last burst time not known .	Critical	Corrective	Dec-18	JC-31 Report, section 7.1	A.001 - Issue 8 (CSC-59) a) section 3.2.3.2.3; b) section 4.2.10.1, item b

MCC-016
MCC-016 Planned compliance date

MonthDayYear
Date
MCC-016 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-017	Revised formats for RLS Beacon SIT 185 messages	Critical	Corrective	Dec-18	JC-31 Report, section 7.1	A.002 - Issue 7 (CSC-59) MF #51 page B-24

MCC-017
MCC-017 Planned compliance date

MonthDayYear
Date
MCC-017 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-018	Data distribution changes and new message formats for ELT(DT) incident alert data	Critical	Enhancement	Dec-18	JC-31 Report, section 7.1 and Annex 34	A.001 - Issue 8 (CSC-59); A.002 - Issue 7 (CSC-59) (too numerous to list)

MCC-018
MCC-018 Planned compliance date

MonthDayYear
Date
MCC-018 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-019	Data distribution changes and new message formats for SGB incident alert data	Critical	Enhancement	Dec-18	JC-31 Report, section 7.1	A.001 - Issue 8 (CSC-59); A.002 - Issue 7 (CSC-59) (too numerous to list)

MCC-019
MCC-019 Planned compliance date

MonthDayYear
Date
MCC-019 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-020	Redundant Doppler position check	Routine	Corrective	Dec-19	JC-31 Report, section 7.1	A.001 - Issue 8 (CSC-59): sections 4.2.5.4.1 and 4.2.5.4.3.4

MCC-020
MCC-020 Planned compliance date

MonthDayYear
Date
MCC-020 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-021	Process alert cancellation messages	Critical	Enhancement	Dec-18	JC-31 Report, section 4.6	A.001 - Issue 8 (CSC-59): section 4.2.11; A.002 - Issue 7 (CSC-59) MF #45 and #61

MCC-021
MCC-021 Planned compliance date

MonthDayYear
Date
MCC-021 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-022	Process TAC-related information on beacon characteristics	Critical	Enhancement	Dec-19	JC-31 Report, section 7.1 and Annex 34	A.001 - Issue 8 (CSC-59): section 3.2.13; A.002 - Issue 7 (CSC-59): MF #94, #95, #96, #97

MCC-022
MCC-022 Planned compliance date

MonthDayYear
Date
MCC-022 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-024	Designate and use MEOSAR reference beacons for QMS	Critical	Enhancement	Dec-19	JC-31 Report, section 8.1	A.003 - Issue 3 (CSC-59): section 2.3.2.1

Comment: Related MEOLUT updates need to be in place first

MCC-024
MCC-024 Planned compliance date

MonthDayYear
Date
MCC-024 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-025	MEOSAR QMS	Routine	Enhancement	Jun-19	JC-31 Report, Annex 6, Annex 32 and Annex 34	A.003 - Issue 3 (CSC-59): section 2.4.2; A.002 - Issue 7 (CSC-59): Table B-1 (MF #80)

Comment: Needed for MEOSAR IOC

MCC-025
MCC-025 Planned compliance date

MonthDayYear
Date
MCC-025 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-026	Reset beacon activation status based on latest detect time received	Routine	Enhancement	Dec-19	JC-31 Report section 7.1.25	A.001 - Issue 8 (CSC-59): section 3.2.3.1

MCC-026
MCC-026 Planned compliance date

MonthDayYear
Date
MCC-026 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-027	Determine redundancy for alert with DOA position based on previously sent DOA position alerts	Routine	Enhancement	Dec-19	JC-31 Report, section 7.1.4	A.001 - Issue 8 (CSC-59): section 3.2.3.2.1 page 3-9, para. 3, item b

MCC-027
MCC-027 Planned compliance date

MonthDayYear
Date
MCC-027 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-028	Limit the distribution of DOA position conflict alerts prior to position confirmation	Routine	Enhancement	Dec-19	JC-31 Report, section 7.1.4	A.001 - Issue 8 (CSC-59): section 3.2.3.2.1 page 3-9, para. 4, item c

MCC-028
MCC-028 Planned compliance date

MonthDayYear
Date
MCC-028 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-029	Distribution of alerts during MCC backup (clarification)	Routine	Enhancement	Dec-19	JC-31 Report, section 7.1.4	A.001 - Issue 8 (CSC-59): section 3.7.1

MCC-029
MCC-029 Planned compliance date

MonthDayYear
Date
MCC-029 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-030	Validation of SIT message content	Routine	Enhancement	Dec-18	JC-31 Report, section 7.1.4	A.001 - Issue 8 (CSC-59): section 4.2.1.1.2

MCC-030
MCC-030 Planned compliance date

MonthDayYear
Date
MCC-030 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-031	Validation of RLS FGB TAC number (bits 43 – 52)	Routine	Enhancement	Dec-18	JC-31 Report, section 7.1.4	A.001 - Issue 8 (CSC-59): Table 4-6

MCC-031
MCC-031 Planned compliance date

MonthDayYear
Date
MCC-031 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-032	Distribution of alerts with an invalid beacon message to Distress authorities (clarification)	Routine	Corrective	Dec-18	JC-31 Report Annex 4	A.001 - Issue 8 (CSC-59): section 4.2.1.1.4.b

MCC-032
MCC-032 Planned compliance date

MonthDayYear
Date
MCC-032 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-033	DOA position footprint validation based on first and last detect time	Routine	Enhancement	Dec-19	JC-31 Report, section 7.1.4	A.001 - Issue 8 (CSC-59): 4.2.1.2; A.002 - Issue 7 (CSC-59) Appendix B.2 to Annex B

MCC-033
MCC-033 Planned compliance date

MonthDayYear
Date
MCC-033 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-034	Filter redundant data to the sending MCC	Routine	Corrective	Dec-19	JC-31 Report, section 7.1.27	A.001 - Issue 8 (CSC-59): section 4.2.5.1

MCC-034
MCC-034 Planned compliance date

MonthDayYear
Date
MCC-034 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-035	Set new status word (Sw) for non ELT(DT) alerts (clarification).	Routine	Corrective	Dec-19	JC-31 Report, section 7.1.25	A.001 - Issue 8 (CSC-59): Figure 4-10

MCC-035
MCC-035 Planned compliance date

MonthDayYear
Date
MCC-035 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-036	Revised procedures for the co-ordination of beacon tests.	Routine	Enhancement	Dec-18	JC-31 Report, section 7.1.4	A.001 - Issue 8 (CSC-59): section 4.3

Comment: MCC software change is not required

MCC-036
MCC-036 Planned compliance date

MonthDayYear
Date
MCC-036 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-037	Access to beacon registry based on vessel Id and on 15 and hex FGB/SGB Id, 23 hex SGB ID	Critical	Enhancement	Dec-18	JC-31 Report, section 7.1	A.005 - Issue 5 (CSC-59): section 3.9

MCC-037
MCC-037 Planned compliance date

MonthDayYear
Date
MCC-037 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-039	An MCC shall filter all DOA position data generated by a MEOLUT for ELT(DT)s, if the MEOLUT is not commissioned to provide DOA locations for fast-moving beacons.	Critical	Enhancement	Jun-19	JC-32 Report, Annex 4	A.001: section 3.2.1

MCC-039
MCC-039 Planned compliance date

MonthDayYear
Date
MCC-039 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-040	The "same beacon identification" is the 15-hexadecimal beacon ID, per the section titled "Beacon Identification"	Critical	Enhancement	Jun-19	JC-32 Report, Annex 4	A.001: sections 3.2.3, 3.2.7, Annex B Appendix B.1 MF #57; A.005: sections 3.9, 3.2.10

MCC-040
MCC-040 Planned compliance date

MonthDayYear
Date
MCC-040 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-041	MCCs shall distribute alert data that is otherwise redundant for all SGBs (revised wording)	Critical	Enhancement	Jun-19	JC-32 report, Annex 4	A.001: section 3.2.3.2

MCC-041
MCC-041 Planned compliance date

MonthDayYear
Date
MCC-041 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-042	LEOLUT alert data for the same beacon ID after position confirmation is deemed to be redundant if ... a Doppler position in the new alert matches a position in an alert previously sent for the same beacon event	Critical	Enhancement	Jun-19	JC-32 Report, Annex 4	A.001: section 3.2.3.2.1

MCC-042
MCC-042 Planned compliance date

MonthDayYear
Date
MCC-042 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-043	Filtering of Redundant Data for ELT(DT)s	Critical	Enhancement	Jun-19	JC-32 Report, Annex 4	A.001: section 3.2.3.2.2

MCC-043
MCC-043 Planned compliance date

MonthDayYear
Date
MCC-043 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-044	Continued Transmission after Position Confirmation for confirmed or conflict alerts	Routine	Enhancement	Jan-21	JC-32 Report, Annex 4	A.001: Section 3.2.5

MCC-044
MCC-044 Planned compliance date

MonthDayYear
Date
MCC-044 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-045	MCCs shall provide information to relevant destinations (i.e., Distress authorities and FGB-only-capable MCCs) based on the TAC number encoded in the beacon message (e.g., for SGB homing characteristics) in SIT 985 messages, in accordance with document C/S A.002 and indicate that TAC related information is provided in a separate message.	Critical	Enhancement	Jun-19	JC-32 Report, Annex 4	A.001: section 3.2.12; A.002: Table C.4, Annex B Appendix B.1 MF #61a

MCC-045
MCC-045 Planned compliance date

MonthDayYear
Date
MCC-045 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-046	Until all MCCs are SGB-capable, SGB-capable MCCs shall transmit a SIT 915 message (that contains data in SIT 985 format) with Message Field #5 set to the identification code of the final destination MCC, if the immediate destination MCC is FGB-only-capable, as specified in section 3.2.12.	Critical	Enhancement	Jun-19	JC-32 Report, Annexes 4 and 7	A.001: section 3.7.6; A.005: section 4.12

MCC-046
MCC-046 Planned compliance date

MonthDayYear
Date
MCC-046 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-047	Operational Distribution of Alert Data for SGBs and FGB ELT(DT)s until the Cospas-Sarsat Council declares that they may be used operationally	Critical	Enhancement	Jun-19	JC-32 Report, Annex 4	A.001: section 3.7.10; A.005: sections 4.11 and 4.12

MCC-047
MCC-047 Planned compliance date

MonthDayYear
Date
MCC-047 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-048	If the SGB alert is a self-test transmission (per Message Field #90), then the MCC shall suppress the associated alert.	Critical	Enhancement	Jun-19	JC-32 Report, Annex 4	A.001: section 4.2.1.1.3; A.002 section Annex B Appendix B.1 MF #90

MCC-048
MCC-048 Planned compliance date

MonthDayYear
Date
MCC-048 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-049	Protocol validation for SGB Vessel ID Type and Beacon Type	Critical	Enhancement	Jun-19	JC-32 Report, Annex 4	A.001: section 4.2.1.1.3 and Table 4-6

MCC-049
MCC-049 Planned compliance date

MonthDayYear
Date
MCC-049 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-050 (Change No Longer Required)	If an SGB message fails validation only provide information in alert messages to Distress authorities based on the "same Beacon Id" per item (a) above.	Critical	Enhancement	Jun-19 (OBE)	JC-32 Report, Annex 4	A.001: Section 4.2.1.1.5

Comment: OBE due to changes at EWG-1/2021. Replaced by MCC-149

MCC-050 (OBE)
MCC-050 (OBE) Planned compliance date

MonthDayYear
Date
MCC-050 (OBE) Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-051	Uncorroborated MEOSAR Alert data distribution and format	Critical	Enhancement	Jun-19	JC-32 Report, Annex 4	A.001: section 4.2.1.4; A.002: Annex B Appendix B.1 MF #61a

MCC-051
MCC-051 Planned compliance date

MonthDayYear
Date
MCC-051 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-052	For ELT(DT)s, the Action Word is Aw2 if only DOA position ins present, Aw2 if positions in the new alert (i.e., encoded and DOA position) match each other, Aw3 if only encoded position is present, Aw4 if positions in the new alert do not match each other.	Critical	Enhancement	Jun-19	JC-32 Report, Annex 4	A.001: Section 4.2.5.2

MCC-052
MCC-052 Planned compliance date

MonthDayYear
Date
MCC-052 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-053	For uncorroborated MEOSAR alerts, the Status Word is set to "Sw0"	Critical	Enhancement	Jun-19	JC-32 Report, Annex 4	A.001: Section 4.2.5.2

MCC-053
MCC-053 Planned compliance date

MonthDayYear
Date
MCC-053 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-054	The co-ordination of a beacon test shall consist of an advance submission of a text (SIT 605) message that includes the 15 hexadecimal ID (per section titled "Beacon Identification") and indicate if the beacon will transmit in self-test mode.	Critical	Enhancement	Jun-19	JC-32 Report, Annex 4	A.001: Section 4.3

MCC-054
MCC0-54 Planned compliance date

MonthDayYear
Date
MCC-054 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-055	Confidence Factor: range and default value	Routine	Corrective	Jan-21	JC-32 Report, Annex 5	A.002: Annex B Table B.1 MF #30

MCC-055
MCC-055 Planned compliance date

MonthDayYear
Date
MCC-055 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-056	FGB Encoded Location update time	Routine	Corrective	Jan-21	JC-32 Report, Annex 5	A.002: Annex B Table B.1 MF #54e

MCC-056
MCC-056 Planned compliance date

MonthDayYear
Date
MCC-056 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-057	DOA speed for associated MEOLUTs commissioned for reporting speed	Routine	Enhancement	Jan-21	JC-32 Report, Annex 5	A.002: Annex B Table B.1 MF #54f

Comment: Due date is tentative, as this only applies once A.002 MCC to MCC formats include speed

MCC-057
MCC-057 Planned compliance date

MonthDayYear
Date
MCC-057 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-060	SGB that lacks encoded position capability	Routine	Corrective	Jan-21	JC-32 Report, Annex 5	A.002: Annex B Appendix B.1 MF #60

MCC-060
MCC-060 Planned compliance date

MonthDayYear
Date
MCC-060 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-061	Invalid beacon message data when beacon Id matches previous valid beacon message	Critical	Enhancement	Jun-19	JC-32 Report, Annex 5	A.002: Annex B Appendix B.1 MF 61a

MCC-061
MCC-061 Planned compliance date

MonthDayYear
Date
MCC-061 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-062	ELT(DT) located alert	Critical	Enhancement	Jun-19	JC-32 Report, Annex 5	A.002: Annex B Appendix B.1 MF #61a

MCC-062
MCC-062 Planned compliance date

MonthDayYear
Date
MCC-062 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-066	Report MEOSAR QMS metrics for Location Accuracy, Location Probability and Detection Probability by individual reference beacon	Routine	Enhancement	Mar-23	JC-32 Report, Annex 6	A.003: sections 2.4.2, 2.5.5.2, 2.5.5.3 and 2.5.5.4

Comment: Due date only applies once automated updating of QMS metric on the C/S website is implemented

MCC-066
MCC-066 Planned compliance date

MonthDayYear
Date
MCC-066 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-067	Include 20 km threshold in MEOSAR location accuracy metrics	Routine	Enhancement	Jun-19		A.003: sections 2.4.2.2, 2.5.2.2, 2.5.5.2

MCC-067
MCC-067 Planned compliance date

MonthDayYear
Date
MCC-067 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-071	Quality of Location Expected Horizontal Error	Critical	Enhancement	Jun-19	JC-32 Report, Annex 6	A.003: Sections 2.4.2.7, 2.5.5.7

MCC-071
MCC-071 Planned compliance date

MonthDayYear
Date
MCC-071 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-072	Reporting status changes on the Cospas-Sarsat web site	Routine	Enhancement	Jan-21	JC-32 Report, Annex 6	A.003: Section 2.5.5.1

MCC-072
MCC-072 Planned compliance date

MonthDayYear
Date
MCC-072 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-073	Nodal MCCs updates to location accuracy and location probability status on Cospas-Sarsat web site	Routine	Enhancement	Mar-23	JC-32 Report, Annex 6	A.003: Sections 2.5.5.2, 2.5.5.3

MCC-073
MCC-073 Planned compliance date

MonthDayYear
Date
MCC-073 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-077	MEOLUT Location Accuracy for opportunity beacons	Routine	Enhancement	Jan-21	JC-32 Report, Annex 6	A.003: Section 3.1.3.1

Comment: Optional

MCC-077
MCC-077 Planned compliance date

MonthDayYear
Date
MCC-077 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-078	XML Format for QMS and Space Segment Status Report	Routine	Enhancement	Mar-23	JC-32 Report, Annex 6	A.003: Annex J

MCC-078
MCC-078 Planned compliance date

MonthDayYear
Date
MCC-078 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-079	SGB Alerts	Critical	Enhancement	Jun-19	JC-32 Report, Annex 7	A.005: Section 4.12

MCC-079
MCC-079 Planned compliance date

MonthDayYear
Date
MCC-079 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-080	Distribution of RLS alerts to non-RLS-capable MCCs	Critical	Enhancement	Jun-19	JC-32 Report, Annex 7	A.001: section 3.7.7; A.005: section 4.9

MCC-080
MCC-080 Planned compliance date

MonthDayYear
Date
MCC-080 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-081	Distribution of ELT(DT) alerts to non-ELT(DT)-capable MCCs	Critical	Enhancement	Jun-19	JC-32 Report, Annex 7	A.001: section 3.7.8; A.005 section 4.11

MCC-081
MCC-081 Planned compliance date

MonthDayYear
Date
MCC-081 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-082	Refinement to Nodal MCC procedure to handle MCC entry into CNO status and restoration of operational status	Routine	Enhancement	Jan-21	JC-32 Report, Annex 4	A.001: section 3.7.4.1; A.003: section 6.3.4

MCC-082
MCC-082 Planned compliance date

MonthDayYear
Date
MCC-082 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-083	Validation of FGB Encoded Position	Routine	Corrective	Jan-21	JC-32 Report, Annex 4	A.001: section 4.2.1.1.3 and Table 4‐6

MCC-083
MCC-083 Planned compliance date

MonthDayYear
Date
MCC-083 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-084	Clarify that the minor axis error ellipse for “A” position is used in determining the relative quality of Doppler position conflict alerts	Routine	Corrective	Jan-21	JC-32 Report, Annex 4	A.001: section 4.2.4.2

MCC-084
MCC-084 Planned compliance date

MonthDayYear
Date
MCC-084 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-085	If an FGB message fails validation, only provide information in alert messages to Distress authorities based on the “same Beacon Id”	Routine	Enhancement	Jan-21	JC-32 Report, Annex 4	A.001: section 4.2.1.1.4

MCC-085
MCC-085 Planned compliance date

MonthDayYear
Date
MCC-085 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-086	Clarify the setting the DBE flag (based on the associated set of satellites) and the PQF (for position conflict alerts prior to position confirmation) for DOA position alerts	Routine	Corrective	Jan-21	JC-32 Report, Annex 4	A.001: section 4.2.5.4.1

MCC-086
MCC-086 Planned compliance date

MonthDayYear
Date
MCC-086 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-087	Clarify the distribution of RLS beacon alerts if the RLSP is not known and the distribution of alerts for test coded RLS SGBs	Critical	Corrective	Jun-19	JC-32 Report, Annex 4	A.001: section 4.2.10.1

MCC-087
MCC-087 Planned compliance date

MonthDayYear
Date
MCC-087 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-088	Modified processing of non-ELT(DT) beacon messages when a new (non-cancellation) message is received after cancellation has been confirmed	Critical	Enhancement	Jun-19	JC-32 Report, Annex 4	A.001: section 4.2.11

MCC-088
MCC-088 Planned compliance date

MonthDayYear
Date
MCC-088 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-089	Message Type for initial (located and unlocated) alert and DOA position match	Routine	Corrective	Jan-21	JC-32 Report, Annex 5	A.002: Annex B Appendix B.1 MF #45

MCC-089
MCC-089 Planned compliance date

MonthDayYear
Date
MCC-089 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-090	Indicate test for SGB	Critical	Corrective	Jun-19	JC-32 Report, Annex 5	A.002: Annex B Appendix B.1 MF #51

MCC-090
MCC-090 Planned compliance date

MonthDayYear
Date
MCC-090 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-091	Content for Satellite Id (MF 83) clarified (used for message field validation)	Critical	Corrective	Jun-19	JC-32 Report, Annex 5	A.002: Annex B Appendix B.1 MF #83

MCC-091
MCC-091 Planned compliance date

MonthDayYear
Date
MCC-091 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-092	New fields with Count of Current TAC numbers allocated and Beacon Type	Critical	Enhancement	Jun-19	JC-32 Report, Annex 5	A.002: Annex B Appendix B.1 MFs #94 and #97

MCC-092
MCC-092 Planned compliance date

MonthDayYear
Date
MCC-092 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-093	Process fields with leading blanks in MEOSAR TLEs	Routine	Enhancement	Jan-21	JC-32 Report, Annex 5	A.002: Annex B Appendix B.1 MFs #85 and #86

MCC-093
MCC-093 Planned compliance date

MonthDayYear
Date
MCC-093 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-094	Notification of Designated Reference Beacons	Critical	Enhancement	Jun-19	JC-32 Report, Annex 6	A.003: section 2.3.2.1

Comment: Notification procedure to be implemented by Nodal MCCs only

MCC-094
MCC-094 Planned compliance date

MonthDayYear
Date
MCC-094 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-095	Designated Reference Beacon transmission characteristics (linear polarization, bit pattern of beacon message)	Critical	Enhancement	Jun-19	JC-32 Report, Annex 6	A.003: section 2.3.2.1

MCC-095
MCC-095 Planned compliance date

MonthDayYear
Date
MCC-095 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-096	Computation of Registration Rate in C/S Annual Report	Critical	Enhancement	Feb-19	JC-32 Report, Annex 6	A.003: Annex A section 1.3

Comment: Due date reflects the intent to do this for JC-33 reports

MCC-096
MCC-096 Planned compliance date

MonthDayYear
Date
MCC-096 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-097	Distribution of Notifications for RLS-Capable FGB Alerts to the RLSP on Behalf of MCCs that are Not FGB-RLS-Capable	Critical	Enhancement	Jun-19	JC-32 Report, Annex 7	A.001: Section 3.7.9

MCC-097
MCC-097 Planned compliance date

MonthDayYear
Date
MCC-097 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-098	Procedure for proactively sending NOCRs.	Critical	Enhancement	Feb-20	CSC-61 SR, Annex 5	A.001: Section 4.2.7.1

MCC-098
MCC-098 Planned compliance date

MonthDayYear
Date
MCC-098 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-099	Clarification of RLS message processing	Routine	Enhancement	Nov-21	JC-33 Report, Annex 4	A.001: sections 4.2.5.3 and 4.2.10.1

MCC-099
MCC-099 Planned compliance date

MonthDayYear
Date
MCC-099 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-100	Clarification of DBE processing	Routine	Enhancement	Nov-21	JC-33 Report, Annex 4	A.001: sections 3.2.3.2 and 4.2.5.4.1

MCC-100
MCC-100 Planned compliance date

MonthDayYear
Date
MCC-100 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-101	SGB display of user class of beacon	Critical	Corrective	Nov-20	JC-33 Report, Annex 5	A.002: Appendix B.1 to Annex B, MF #51

MCC-101
MCC-101 Planned compliance date

MonthDayYear
Date
MCC-101 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-102	Display of ELT(DT) encoded location and time of update (currency)	Critical	Enhancement	Nov-20	JC-33 Report and CSC-62, Annexes 5	A.002: Appendix B.1 to Annex B, MF #54.e

MCC-102
MCC-102 Planned compliance date

MonthDayYear
Date
MCC-102 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-103	Display of FGB TAC number	Routine	Corrective	Nov-21	JC-33 Report, Annex 5

MCC-103
MCC-103 Planned compliance date

MonthDayYear
Date
MCC-103 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee References	Red Book Reference (Council Session)	Document Section(s)/Page(s)
MCC-104	Other Encoded Information: Activation method for ELT(DT)	Critical	Adaptive	Nov-20	JC-33 Report, Annex 5		A.002: Appendix B.1 to Annex B, MF #60

MCC-104
MCC-104 Planned compliance date

MonthDayYear
Date
MCC-104 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-105	For MEOSAR QMS updates including 12 bursts in the 10- minute TRP	Routine	Adaptive	Nov-21	JC-33 Report, Annex 6	A.003: section 2.3.2.1 “Designated QMS Reference Beacons”

Comment: Nodal MCCs only

MCC-105
MCC-105 Planned compliance date

MonthDayYear
Date
MCC-105 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-106	Reporting of Maintenance Activations	Routine	Enhancement	Nov-21	JC-33 Report, Annex 6	A.003: Annex A

MCC-106
MCC-106 Planned compliance date

MonthDayYear
Date
MCC-106 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-107	Introduction of RLS LP MMSI - Protocol name "MMSI - Last 6 Digits"	Critical	Enhancement	Nov-20	CSC-62 SR, Annex 5	A.002: Appendix B.1 to Annex B, MF #51

MCC-107
MCC-107 Planned compliance date

MonthDayYear
Date
MCC-107 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-108	Protocol Validation for RLS LP - TAC# Validation (949 < TAC# < 960)	Critical	Enhancement	Nov-20	CSC-62 SR, Annex 4	A.001: Table 4-6 "Protocol Validation […]"

MCC-108
MCC-108 Planned compliance date

MonthDayYear
Date
MCC-108 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-109	Protocol validation for FGB ELT(DT) LP - bits 25=1, 26=0, 37-40=1001 and 41-42=11	Critical	Enhancement	Nov-20	CSC-62 SR, Annex 4	A.001: Table 4-6 "Protocol Validation […]"

MCC-109
MCC-109 Planned compliance date

MonthDayYear
Date
MCC-109 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee References	Red Book Reference (Council Session)	Document Section(s)/Page(s)
MCC-110 (Change No Longer Required)	Protocol validation for FGB, SGB Binary Code Decimal - (four bit group > 9)	Routine	Enhancement	Nov-21 (OBE)	CSC-62 SR, Annex 4		A.001: Table 4-6 "Protocol Validation […]"

Comment: OBE due to changes at JC-34, see MCC-122.

MCC-110 (OBE)
MCC-110 (OBE) Planned compliance date

MonthDayYear
Date
MCC-110 (OBE) Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-111	Distribution of ELT(DT) alerts to the LADR	Critical	Adaptive	Jan-22	EWG-2-2020 Annex 4	A.001: sections 3.7.11, 3.12, 4.2.11; A.002: Table C-5

MCC-111
MCC-111 Planned compliance date

MonthDayYear
Date
MCC-111 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-112	FGB and SGB Message Validation, including ELT(DT)s	Critical	Adaptive	Jan-22	EWG-2-2020 Annex 4	A.001: Table 4-6

Comment: Includes adaptive changes per updates to beacon message formats in T.001 and T.018

MCC-112
MCC-112 Planned compliance date

MonthDayYear
Date
MCC-112 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-113 (Change No Longer Required)	MCC use of the 23 Hex Id per updated definition in T.018 Table 3.10	Routine	Adaptive	Mar-22 (OBE)	EWG-2-2020, Annexes 4 and 5	A.001: sections 3.1.4, 3.8.2, 4.3; A.002: Table B.1 (MF #57), Tables B.1, C.1 and C.2 (MF #92)

MCC-113 (OBE)
MCC-113 (OBE) Planned compliance date

MonthDayYear
Date
MCC-113 (OBE) Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-114	Update to SIT 927 message to account for the use of SGB Programming Adapters	Critical	Adaptive	Jan-22	EWG-2-2020, Annex 5	A.002: Table B.1 (MF #94), Appendix B.1 to Annex B (MFs #94 – #97)

Comment: MF #94 sub-field added to identify a Programming Adapter (P/A). Clarify that details are provided for the beacon model not the P/A.

MCC-114
MCC-114 Planned compliance date

MonthDayYear
Date
MCC-114 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-115 (Clarified at EWG-1/2021)	Provide in the message to the SPOC: for FGB ELT(DT)s the 3-letter aircraft operator designator or refined encoded position, as provided in each beacon message; for SGB ELT(DT)s, provide 3-letter aircraft operator designator.	Critical	Adaptive	Jan-22	EWG-2-2020 Annex 5	A.002: Appendix B.1 to Annex B (MF #51, MF #54e)

Comment: Adaptive change per updates to T.001 for FGB ELT(DT) bits 113-114 and other bits in PDF-2 and per updates to T.018 for SGB ELT(DT) bits 94-137

MCC-115
MCC-115 Planned compliance date

MonthDayYear
Date
MCC-115 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-116	Provide currency (FGB) or time (SGB) of encoded position update in SPOC message for ELT(DT)	Critical	Adaptive	Jan-22	EWG-2-2020 Annex 5	A.002: Appendix B.1 to Annex B (MF #54e, MF #60)

Comment: Adaptive change per update to T.001 for FGB ELT(DT) bits 113-114

MCC-116
MCC-116 Planned compliance date

MonthDayYear
Date
MCC-116 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee References	Document Section(s)/Page(s)
MCC-117	Provide each vessel/aircraft identifier and Aircraft Operator relevant to User Class in SPOC message	Routine	Adaptive	Mar-22	EWG-2-2020 Annex 5	A.002: Appendix B.1 to Annex B (MF #51)

Comment: FGB ELT(DT)s and SGBs may contain multiple identification items relevant to User Class

MCC-117
MCC-117 Planned compliance date

MonthDayYear
Date
MCC-117 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-118	Provide encoded position uncertainty and altitude in SPOC message for FGB ELT(DT)	Critical	Adaptive	Jan-22	EWG-2-2020 Annex 5	A.002: Appendix B.1 to Annex B (MF #60)

MCC-118
MCC-118 Planned compliance date

MonthDayYear
Date
MCC-118 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-119	Provide encoded position altitude in feet (as well as metres) in SPOC message for FGB ELT(DT) and SGB	Routine	Adaptive	Mar-22	EWG-2-2020 Annex 5	A.002: Appendix B.1 to Annex B (MF #60)

MCC-119
MCC-119 Planned compliance date

MonthDayYear
Date
MCC-119 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-120	Clarify required MCC responses for SIT 216 messages	Routine	Corrective	Mar-22	JC-34, Annex 4	A.001: section 3.6.5 "Scheduled Satellite Manoeuvres"

MCC-120
MCC-120 Planned compliance date

MonthDayYear
Date
MCC-110 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-121	Protocol Validation for RLS LP - Bits 43 to 46 value for non-MMSI protocols	Critical	Corrective	Mar-22	JC-34, Annex 4	A.001: Table 4-6 "Protocol Validation […]"

MCC-121
MCC-121 Planned compliance date

MonthDayYear
Date
MCC-121 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-122	Protocol validation for FGB, SGB Binary Code Decimal - (four bit group > 10)	Critical	Corrective	Mar-22	JC-34, Annex 4	A.001: Table 4-6 "Protocol Validation […]"

Comment: Overtaking MCC-110

MCC-122
MCC-122 Planned compliance date

MonthDayYear
Date
MCC-122 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee References	Document Section(s)/Page(s)
MCC-123	Distribution of RLS alerts to non-RLS-capable MCCs via SIT 122 to 147	Critical	Corrective	Mar-22	JC-34, Annex 4	A.001: section 3.7.7, "Distribution of Alerts for RLS FGBs"

Comment: See MCC-080

MCC-123
MCC-123 Planned compliance date

MonthDayYear
Date
MCC-123 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-124	Clarification for NOCRs	Routine	Corrective	Mar-23	JC-34, Annex 4	A.001: sections 3.2.3 "Processing Multiple Alerts for the Same Beacon Identification" and 4.2.10.1 "Return Link Service (RLS) Procedures"

MCC-124
MCC-124 Planned compliance date

MonthDayYear
Date
MCC-124 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-125	Clarification for NOCRs	Routine	Corrective	Mar-23	JC-34, Annex 4	A.001: sections 4.2.1.4 "Uncorroborated MEOSAR Alerts" and 4.2.7.1 "NOCR Procedures"

MCC-125
MCC-125 Planned compliance date

MonthDayYear
Date
MCC-125 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-126	SIT messages sent with same information for FGBs	Critical	Corrective	Mar-22	JC-34, Annex 4	A.001: section 4.2.5.1 "Analysis and General Representation of Alert Data Processing"

Comment: See MCC-034

MCC-126
MCC-126 Planned compliance date

MonthDayYear
Date
MCC-126 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-127	Corrections for Doppler/DOA position to Encoded match (DEM) and encoded to encoded position match (EEM) conditions.	Critical	Corrective	Mar-22	JC-34, Annex 4	A.001: section 4.2.5.4.1 "Tests and Flag setting for Special Processing Procedures"

Comment: See MCC-020, MCC-086, MCC-100

MCC-127
MCC-127 Planned compliance date

MonthDayYear
Date
MCC-127 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-128	Distribute RLS beacon alerts to SPMCC during FMCC backup	Critical	Corrective	Mar-21	JC-34, Annex 4	A.001: sections 5.3.13.4 "FMCC" and 5.3.29.4 "SPMCC" subsection "Backup procedures and agreements"

Comment: Nodal and CDDR MCCs only

MCC-128
MCC-128 Planned compliance date

MonthDayYear
Date
MCC-128 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-129	Default values for the DOA Altitude (MF #54d) and DOA speed (MF #54f).	Critical	Corrective	Mar-22	JC-34, Annex 5	A.002: Table B.1 and Appendix B.1 - MF #54d

MCC-129
MCC-129 Planned compliance date

MonthDayYear
Date
MCC-129 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-130	Addition of the Alert Status 'ROTATING FIELD UPDATE ALERT' as a new msg type	Critical	Enhancement	Mar-22	JC-34, Annex 5	A.002: Appendix B.1 - MF #45 - Message Type

MCC-130
MCC-130 Planned compliance date

MonthDayYear
Date
MCC-130 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-131	Addition of the Alert Status 'NOCR' as a possible msg type (optional)	Routine	Enhancement	N/A	JC-34, Annex 5	A.002: Appendix B.1 - MF #45 - Message Type

Comment: Optional

MCC-131
MCC-131 Planned compliance date

MonthDayYear
Date
MCC-131 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-132	Format Correction for TAC and Serial # in MF #51	Critical	Corrective	Mar-22	JC-34, Annex 5	A.002: Appendix B.1 - MF #51 - User Class of Beacon

MCC-132
MCC-132 Planned compliance date

MonthDayYear
Date
MCC-132 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-133	Addition of the EHE value for IOC commissioned MEOLUT	Critical	Enhancement	Mar-22	JC-34, Annex 5	A.002: Appendix B.1 - MF #54d - DOA Position, Accuracy and Altitude

MCC-133
MCC-133 Planned compliance date

MonthDayYear
Date
MCC-133 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-134	Correction of the Homing Signal interpretation value	Critical	Corrective	Mar-22	JC-34, Annex 5	A.002: Appendix B.1 - MF #57 - Homing Signal Interpretation

MCC-134
MCC-134 Planned compliance date

MonthDayYear
Date
MCC-134 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-135	Correction of the Activation Type	Critical	Corrective	Mar-22	JC-34, Annex 5	A.002: Appendix B.1 - MF #58 - Activation Type

MCC-135
MCC-135 Planned compliance date

MonthDayYear
Date
MCC-135 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee References	Document Section(s)/Page(s)
MCC-136	Correction of the Beacon Number if no information is available	Critical	Corrective	Mar-22	JC-34, Annex 5	A.002: Appendix B.1 - MF #59 - Beacon Number

MCC-136
MCC-136 Planned compliance date

MonthDayYear
Date
MCC-136 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-137	Standard, national location protocol encoded position accuracy uncertainty, encoded position altitude value, elapsed time, battery capacity	Critical	Corrective	Mar-22	JC-34, Annex 5	A.002: Appendix B.1 - MF #60 - Other Encoded Information

Comment: See MCC-104

MCC-137
MCC-137 Planned compliance date

MonthDayYear
Date
MCC-137 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-138	Provide warning for suspect Doppler position data after position confirmation	Critical	Corrective	Mar-22	JC-34, Annex 5	A.002: Appendix B.1 - MF #61a - Other Information (General)

MCC-138
MCC-138 Planned compliance date

MonthDayYear
Date
MCC-138 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-139	Provide note for ELT(DT) alerts	Critical	Enhancement	Jan-22	JC-34, Annex 5	A.002: Appendix B.1 - MF #62 - Remarks

MCC-139
MCC-139 Planned compliance date

MonthDayYear
Date
MCC-139 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-140	Default value for number of Networked Antennas above 98	Critical	Corrective	Mar-22	JC-34, Annex 5	A.002: Appendix B.1 - MF #80 - Networked Antennas

Note: See MEOLUT-022

MCC-140
MCC-140 Planned compliance date

MonthDayYear
Date
MCC-140 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-141	Provision in the LADR of Altitude and Airspeed	Critical	Corrective	Jan-22	JC-34, Annex 5	A.002: Table C6 - LADR Message Field Descriptions

MCC-141
MCC-141 Planned compliance date

MonthDayYear
Date
MCC-141 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-142	Provision of the information to the LADR by nodal MCCs using web services	Critical	Enhancement	Jan-22	JC-34, Annex 7	A.005: section 3.4 - Data Communication links

Comment: Nodal MCCs only.

MCC-142
MCC-142 Planned compliance date

MonthDayYear
Date
MCC-142 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-143	Retrieval of alerts for ELT(DT)s and SSAS beacons by beacon type	Critical	Enhancement	Jan-22	JC-34, Annex 7	A.005: section 3.10.1 - Information Archival and Retrieval

MCC-143
MCC-143 Planned compliance date

MonthDayYear
Date
MCC-143 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-144	Alert distribution after position confirmation	Routine	Enhancement	Mar-23	JC-34, Annex 7	A.005: section 4.5.2 - Position Confirmation

Comment: Details moved to A.001 section 3.2.5

MCC-144
MCC-144 Planned compliance date

MonthDayYear
Date
MCC-144 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-145	Processing of the MCC unavailability period	Routine	Enhancement	Mar-23	JC-34, Annex 7	A.005: section 5.1 - Availability

MCC-145
MCC-145 Planned compliance date

MonthDayYear
Date
MCC-145 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-146	Suppression of alert data for SARP failure, QMS notification for location accuracy failure	Critical	Enhancement	Mar-22	JC-34, Annex 7	A.005: section 5.10.1 - Additional Timing Requirements

MCC-146
MCC-146 Planned compliance date

MonthDayYear
Date
MCC-146 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-147	Updates of LEOLUTs with orbital data after satellite manoeuvre and after SARP reset	Critical	Enhancement	Mar-22	JC-34, Annex 7	A.005: section 5.10.5 and 5.10.6 - Additional Timing Requirements

MCC-147
MCC-147 Planned compliance date

MonthDayYear
Date
MCC-147 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-148	Addition of MEOSAR orbit vector validation parameters: 30 km (default), 50 km following MEOSAR satellite manoeuvre, and validation parameters configurable per satellite	Routine	Enhancement	Mar-23	JC-34, Annex 6	A.003: Annex C, Table C.1 LEOSAR and MEOSAR System Performance Parameters

MCC-148
MCC-148 Planned compliance date

MonthDayYear
Date
MCC-148 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-149	Same beacon identification is based on the 23 Hex ID for SGBs	Critical	Enhancement	Jan-22	EWG-1/2021, Annex 4	A.001: sections 3.2.3 "Processing Multiple Alerts for the Same Beacon Identification" and 4.2.1.1.5 "406 MHz SGB Message Validation"

Comment: Replacing MCC-050. (No change for FGB ID matching, but related cross-references were changed)

MCC-149
MCC-149 Planned compliance date

MonthDayYear
Date
MCC-149 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-150	15 Hex ID for SGBs	Critical	Enhancement	Sep-22	JC-35, Annex 4	A.001: section 3.1.4 "Beacon Identification"

MCC-150
MCC-150 Planned compliance date

MonthDayYear
Date
MCC-150 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-151	ELT(DT) alert distribution within 30 seconds of the earliest reference time	Critical	Corrective	Sep-22	JC-35, Annex 4	A.001: section 3.2.3.2.2 "Filtering of Redundant Data for ELT(DT)s

MCC-151
MCC-151 Planned compliance date

MonthDayYear
Date
MCC-151 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-152	FGB ELT(DT) alert distribution of refined encoded position when the reference time differs by at least 3 seconds from the reference time of all previously sent alert	Critical	Corrective	Sep-22	JC-35, Annex 4	A.001: section 3.2.3.2.2 "Filtering of Redundant Data for ELT(DT)s

MCC-152
MCC-152 Planned compliance date

MonthDayYear
Date
MCC-152 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-153	Distribution of the best ELT(DT) solution when the current time is at least 10 minutes more recent than the reference time of all previously sent alerts	Routine	Enhancement	Mar-24	JC-35, Annex 4	A.001: section 3.2.3.2.2 "Filtering of Redundant Data for ELT(DT)s

MCC-153
MCC-153 Planned compliance date

MonthDayYear
Date
MCC-153 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-154	Validation of rotating field for SGBs	Routine	Corrective	Mar-24	JC-35, Annex 4	A.001: section 4.2.1.1.5 "406 MHz SGB Message Validation", Table 4-7 "Rotating Field Validation for SGBs"

MCC-154
MCC-154 Planned compliance date

MonthDayYear
Date
MCC-154 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-155	Distribution of uncorroborated SGB alerts to an MCC that is not SGB-capable.	Routine	Corrective	Mar-24	JC-35, Annex 4	A.001: section 4.2.1.4 "Uncorroborated MEOSAR Alerts"

MCC-155
MCC-155 Planned compliance date

MonthDayYear
Date
MCC-155 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-156	Distribution of uncorroborated FGB and SGB alerts based on the respective MEOLUT capability for FGB and SGB processing anomalies	Routine	Enhancement	Mar-24	JC-35, Annex 4	A.001: section 4.2.1.4 "Uncorroborated MEOSAR Alerts"

MCC-156
MCC-156 Planned compliance date

MonthDayYear
Date
MCC-156 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-157	Distribution of unconfirmed FGB ELT(DT) and SGB cancellation messages based on the destination MCC capability to process FGB ELT(DT)s and SGBs, respectively.	Routine	Enhancement	Mar-24	JC-35, Annex 4	A.001: section 4.2.11 "Cancellation Message Procedures"

MCC-157
MCC-157 Planned compliance date

MonthDayYear
Date
MCC-157 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-158	Coordination of beacon tests with SIT 605 messages using standard geographic coordinates	Routine	Enhancement	Mar-24	JC-35, Annex 4	A.001: section 4.3 "Procedures for the Co-Ordination of Beacon Tests"

MCC-158
MCC-158 Planned compliance date

MonthDayYear
Date
MCC-158 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-159	Clarify that FGB ELT(DT) Location Protocol Supplementary bits 115-117 are validated only if the cancellation message sequence is not present.	Critical	Corrective	Sep-22	JC-35, Annex 4 [A.001]	A.001: section 4.2.1.1.3 "406 MHz Beacon Message Validation" Table 4-6 “Protocol Validation for 406 MHz Alert Messages”

MCC-159
MCC-159 Planned compliance date

MonthDayYear
Date
MCC-159 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-160	Revised SIT 185 message (including a reorganized message format, and new terms "GNSS" position, "MCC Reference" position, etc.).	Critical	Enhancement	Mar-23	JC-35, Annex 5	A.002: Annex B "Message Field Description" and Annex C "Message Content by SIT"

MCC-160
MCC-160 Planned compliance date

MonthDayYear
Date
MCC-160 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-161	SIT 185 message to Include seconds of the minute in the detect times for FGB ELT(DT)s	Critical	Corrective	Sep-22	JC-35, Annex 5	A.002: Table B-1: "Message Field Description", MF #48a and MF #48b

MCC-161
MCC-161 Planned compliance date

MonthDayYear
Date
MCC-161 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-162	Update C/S website with the status for each ratio provided for MEOLUT location accuracy, MEOLUT location probability and MEOLUT detection probability	Critical	Corrective	Mar-23	JC-35, Annex 6	A.003: section 2.5.5 "MEOLUT Assessment, Status Reporting and Follow-up Actions"

MCC-162
MCC-162 Planned compliance date

MonthDayYear
Date
MCC-162 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-163	Use of 5 km and 20 km distance thresholds for the MEOLUT location accuracy metric	Critical	Corrective	Mar-23	JC-35, Annex 6	A.003: section 2.4.2 "MEOSAR Data Analysis"

MCC-163
MCC-163 Planned compliance date

MonthDayYear
Date
MCC-163 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-164	Modified XML format for QARS	Critical	Corrective	Mar-23	JC-35, Annex 6	A.003: Annex J "QMS Automated Reporting System"

MCC-164
MCC-164 Planned compliance date

MonthDayYear
Date
MCC-164 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-165	Status messages for MEOLUT Location Accuracy and MEOLUT Location EHE Quality	Critical	Corrective	Mar-23	JC-35, Annex 6	A.003: Annex D "Anomaly Notification Messages" section 4 "MEOLUT ACCURACY STATUS MESSAGES" (3 messages) and section 9 "MEOLUT Location EHE Quality Status Messages.

MCC-165
MCC-165 Planned compliance date

MonthDayYear
Date
MCC-165 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-166	Manual upload XML file to the QARS (optional)	Critical	Enhancement	Mar-23	JC-35, Annex 6	A.003: Annex J "QMS Automated Reporting System"

MCC-166
MCC-166 Planned compliance date

MonthDayYear
Date
MCC-166 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-167	Not distributing SGBs alerts (including NOCRs) for test coded RLS beacons to RCCs or SPOCs, or MCCs that are not SGB capable.	Routine	Corrective	Nov-24	JC-36, Annex 4	A.001: section 3.7.6 "Distribution of Second-Generation-Beacon (SGB) Alerts to MCCs that Are Only First-Generation-Beacon (FGB)-Capable"

MCC-167
MCC-167 Planned compliance date

MonthDayYear
Date
MCC-167 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-168	Manual upload XML file to the QARS (optional)	Routine	Corrective	Nov-24	JC-36, Annex 4	A.001: section 3.7.7 "Distribution of Alerts for RLS-Capable FGBs to MCCs that Are Not FGB-RLS-Capable"

MCC-168
MCC-168 Planned compliance date

MonthDayYear
Date
MCC-168 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-169	Distribution of BDS Spacecraft & Ephemeris Data.	Critical	Enhancement	Nov-23	JC-36, Annex 4	A.001: section 4.1.6 " Inter-MCC Routing of System Information" Table 4-2 "System Information Distribution", A002: Table B-1: "Message Field Description", MF #6 and MF #83

MCC-169
MCC-169 Planned compliance date

MonthDayYear
Date
MCC-169 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-170	Validation of SGB messages when MF #91 does not contain a value within the range of 0 to 6.	Critical	Corrective	Nov-23	JC-36, Annex 4	A.001: section 4.2.1.1.5 "406 MHz SGB Message Validation"

MCC-170
MCC-170 Planned compliance date

MonthDayYear
Date
MCC-170 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-171	Corroborate MEOSAR alert, based on receipt by a different MEOLUT that does not receive antenna data from any other MEOLUT.	Critical	Corrective	Nov-23	JC-36, Annex 4	A.001: section 4.2.1.4 "Uncorroborated MEOSAR Alerts"

MCC-171
MCC-171 Planned compliance date

MonthDayYear
Date
MCC-171 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-172	Reset the beacon status word to zero when a non-cancellation message is detected after cancellation confirmation.	Critical	Corrective	Dec-22	JC-36, Annex 4	A.001: section 4.2.11 "Cancellation Message Procedures"

MCC-172
MCC-172 Planned compliance date

MonthDayYear
Date
MCC-172 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-173	Coordination of an operationally-coded ELT(DT) test with the LADR host.	Critical	Adaptive	Jan-23	JC-36, Annex 4	A.001: section 4.3 "Procedures for the Co-Ordination of Beacon Tests"

MCC-173
MCC-173 Planned compliance date

MonthDayYear
Date
MCC-173 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-174	Message title "UNLOCATED UPDATE ALERT" when a SIT 185 message is sent for a new detection without position information.	Routine	Adaptive	Nov-24	JC-36, Annex 5	A.002: Appendix B.1 to Annex B "Message Field Description", MF #45

MCC-174
MCC-174 Planned compliance date

MonthDayYear
Date
MCC-174 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-175	Default Detection Frequency value for an SGB solution without a DOA position.	Routine	Adaptive	Nov-24	JC-36, Annex 5	A.002: Appendix B.1 to Annex B "Message Field Description", MF #49

MCC-175
MCC-175 Planned compliance date

MonthDayYear
Date
MCC-175 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-176	Provision of the 3LD as "ZGA" in the SIT 185 message.	Critical	Adaptive	Nov-23	JC-36, Annex 5	A.002: Appendix B.1 to Annex B "Message Field Description", MF #51

MCC-176
MCC-176 Planned compliance date

MonthDayYear
Date
MCC-176 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-177	Provision of additional SGB Vessel ID information in the SIT 185 message.	Routine	Adaptive	Nov-24	JC-36, Annex 5	A.002: Appendix B.1 to Annex B "Message Field Description", MF #51

MCC-177
MCC-177 Planned compliance date

MonthDayYear
Date
MCC-177 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-178	Allow 'Automatic by Beacon' as the Activation Type for EPIRB alerts.	Routine	Enhancement	Nov-24	JC-36, Annex 5	A.002: Appendix B.1 to Annex B "Message Field Description", MF #58

MCC-178
MCC-178 Planned compliance date

MonthDayYear
Date
MCC-178 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-179	Provide the GNSS position uncertainty for an SGB as 10 metres.	Routine	Corrective	Nov-24	JC-36, Annex 5	A.002: Appendix B.1 to Annex B "Message Field Description", MF #60

MCC-179
MCC-179 Planned compliance date

MonthDayYear
Date
MCC-179 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-180	The MEOLUT capability to provide the EHE reliably shall be configured in the MCC separately for FGBs and SGBs.	Critical	Adaptive	Nov-23	JC-36, Annex 5	A.002: Appendix B.1 to Annex B "Message Field Description", MF #54d

MCC-180
MCC-180 Planned compliance date

MonthDayYear
Date
MCC-180 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-181	Provide only one set of QMS statistics for “per-beacon” and the “all beacons collectively” when the MEOLUT is associated to only one QMS reference beacon.	Routine	Corrective	Nov-24	JC-36, Annex 6	A.003: section J.2 "XML Format for QMS and Space Segment Status Report"

MCC-181
MCC-181 Planned compliance date

MonthDayYear
Date
MCC-181 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-182	Increase upper bound of Country Codes to 987	Critical	Adaptive	Nov-23	CSC-67/OPN, Annex 4	A.001: Table 4-6 “Protocol Validation for 406 MHz Alert Messages”

MCC-182
MCC-182 Planned compliance date

MonthDayYear
Date
MCC-182 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-183	Distribution of alert data if rotating field type (bits 155-158) is not 15 (i.e., cancellation message)	Routine	Corrective	Oct-25	JC-37, Annex 4	A.001: section 3.2.3.2 "Filtering of Redundant Data"

MCC-183
MCC-183 Planned compliance date

MonthDayYear
Date
MCC-183 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-184	Matching of encoded position against encoded position information previously sent by the MCC	Critical	Corrective	Oct-24	JC-37, Annex 4	A.001: section 3.2.3.2.1 "Filtering of Redundant Data for Beacons except ELT(DT)s"

MCC-184
MCC-184 Planned compliance date

MonthDayYear
Date
MCC-184 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-185	New ELT(DT) alerts sent if containing a different activation type	Critical	Enhancement	Oct-24	JC-37, Annex 4	A.001: section 3.2.3.2.2 "Filtering of Redundant Data for Beacons for ELT(DT)s”

MCC-185
MCC-185 Planned compliance date

MonthDayYear
Date
MCC-185 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-186	Provision of alert data to the LADR by the destination nodal MCC if received from all different sources to the destination MCC	Critical	Enhancement	Oct-24	JC-37, Annex 4	A.001: section 3.12 "Location of an Aircraft in Distress Repository (LADR) for ELT(DT) Alert Data”

MCC-186
MCC-186 Planned compliance date

MonthDayYear
Date
MCC-186 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-187	Provision of alert data to the LADR by the destination nodal MCC if 3LD and Aircraft Identifier are available	Critical	Enhancement	Oct-24	JC-37, Annex 4	A.001: section 3.12 "Location of an Aircraft in Distress Repository (LADR) for ELT(DT) Alert Data”

MCC-187
MCC-187 Planned compliance date

MonthDayYear
Date
MCC-187 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-188	Provision of alert data to the LADR with the default 3LD "ZGA" after 3 minutes	Critical	Enhancement	Oct-23	JC-37, Annex 4	A.001: section 3.12 "Location of an Aircraft in Distress Repository (LADR) for ELT(DT) Alert Data"

MCC-188
MCC-188 Planned compliance date

MonthDayYear
Date
MCC-188 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-189	Determination of Country Code for Beacons with Country Codes that appear to be 780	Critical	Adaptive	Oct-24	JC-37, Annex 4	A.001: section 4.2.1.1.3 "406 MHz Beacon Message Validation"

MCC-189
MCC-189 Planned compliance date

MonthDayYear
Date
MCC-189 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-190	Matching with the same Beacon ID	Routine	Adaptive	Oct-25	JC-37, Annex 4	A.001: section 4.2.1.1.4 "406 MHz FGB Message Validation"

MCC-190
MCC-190 Planned compliance date

MonthDayYear
Date
MCC-190 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-191	Not filtering data when rotating field criteria meet validation criteria per Table 4-7	Critical	Corrective	Oct-24	JC-37, Annex 4	A.001: section 4.2.1.1.5 "406 MHz SGB Message Validation"

MCC-191
MCC-191 Planned compliance date

MonthDayYear
Date
MCC-191 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-192	For DOA to DOA matches, use at least five (5) position conflict alerts	Routine	Corrective	Oct-25	JC-37, Annex 4	A.001: section 4.2.5.4.1 "Tests and Flag Setting for Special Processing Procedures"

MCC-192
MCC-192 Planned compliance date

MonthDayYear
Date
MCC-192 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-193	Association of RLS/BDS as one of the RLSPs	Routine	Adaptive	Oct-25	JC-37, Annex 4	A.001: section 4.2.10 "Return Link Service (RLS) Procedures"

MCC-193
MCC-193 Planned compliance date

MonthDayYear
Date
MCC-193 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-194	Formatting of SIT185 messages (character texts)	Routine	Adaptive	Oct-25	JC-37, Annex 5	A.002: Table B-1: Message Field Description: MFs #45, #48a, #49, #50b, #52,

MCC-194
MCC-194 Planned compliance date

MonthDayYear
Date
MCC-194 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-195	Default value = 99 for Networked Antenna Channels	Routine	Adaptive	Oct-25	JC-37, Annex 5	A.002: Table B-1: Message Field Description: MF #80 and MF #81

MCC-195
MCC-195 Planned compliance date

MonthDayYear
Date
MCC-195 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-196	Pseudo Country Code for distributing NOCR for coding per ITU R-585	Critical	Adaptive	Oct-24	JC-37, Annex 5	A.002: Appendix B-1: Message Field Description: MF #50b, MF #51

MCC-196
MCC-196 Planned compliance date

MonthDayYear
Date
MCC-196 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-197	Information on Time Since GNSS Location Generated	Routine	Corrective	Oct-25	JC-37, Annex 5	A.002: Appendix B-1: Message Field Description: MF #54e and MF #60

MCC-197
MCC-197 Planned compliance date

MonthDayYear
Date
MCC-197 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-198	Exclusion of network antennas if defaulted or equal or above 98 for QMS	Routine	Corrective	Oct-25	JC-37, Annex 6	A.003: section 2.4.2.5 "MEOLUT Local Antenna Channel Availability (for Networked MEOLUTs)"

MCC-198
MCC-198 Planned compliance date

MonthDayYear
Date
MCC-198 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-199	NODAL MCC ONLY Distribution of ELT(DT) Data to the LADR by LDPs	Critical	Adaptive	Jan-24	EWG-1C/2024/S1, Annex 4	A.001: sections 3.7.11 "3.7.11 Distribution of ELT(DT) Alerts to the Location of an Aircraft in Distress Repository (LADR) on Behalf of Nodal MCCs that Are Not LADR-Capable" and 3.12 "Location of an Aircraft in Distress Repository (LADR) for ELT(DT) Alert Data"

MCC-199
MCC-199 Planned compliance date

MonthDayYear
Date
MCC-199 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-200	NODAL MCC ONLY Message contents used for sending ELT(DT) Data to the LADR by LDPs	Critical	Adaptive	Jan-25	EWG-1C/2024/S1, Annex 5	A.002: Table C-5 "Key LADR Message Field Descriptions"

MCC-200
MCC-200 Planned compliance date

MonthDayYear
Date
MCC-200 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-201	Confirmation processing of ELT(DT) alerts when activated by the G-switch	Critical	Adaptive	Oct-25	JC-38 Annex 4 (A.001)	A.001: section 2.2 "Alert Data Distribution Principles" A.001: section 3.2.1 "Doppler, DOA and Encoded Positions" A.001: section 3.2.3.2.3 "Distribution of Alerts with Better Quality DOA Position" A.001: section 4.2.2 "Position Matching" A.001: section 4.2.5.1 "Analysis and General Representation of Alert Data Processing" A.001: section 4.2.5.2 "Definition of Input, Status and Action Words"

MCC-201
MCC-201 Planned compliance date

MonthDayYear
Date
MCC-201 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-202	Provision of Doppler positions in addition to the DOA positions for ELT(DT) alerts when activated by the G-switch	Critical	Adaptive	Oct-25	JC-38 Annex 4 (A.001)	AA.001: section 3.2.3.2.2 "Filtering of Redundant Data for ELT(DT)s" A.001: section 4.2.4.1 "Procedure to Determine Better Quality LEOSAR Alert Data for SBE position conflict"

MCC-202
MCC-202 Planned compliance date

MonthDayYear
Date
MCC-202 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-203	Provision of a new EHE when it was previously unavailable	Routine	Corrective	Oct-26	JC-38 Annex 4 (A.001)	A.001: section 3.2.3.2.3 "Distribution of Alerts with Better Quality DOA Position"

MCC-203
MCC-203 Planned compliance date

MonthDayYear
Date
MCC-203 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-204	Contingency procedure for MCC not TWC-capable	Critical	Enhancement	Oct-25	JC-38 Annex 4 (A.001)	A.001: section 3.7.12 "Distribution of alerts for TWC-capable beacon to MCCs that are not TWC-capable"

MCC-204
MCC-204 Planned compliance date

MonthDayYear
Date
MCC-204 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-205	Rotating Field Validation for TWC beacons	Critical	Enhancement	Oct-25	JC-38 Annex 4 (A.001)	A.001: Table 4-7 "Rotating Field Validation for SGB"

MCC-205
MCC-205 Planned compliance date

MonthDayYear
Date
MCC-205 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-206	Determination of a new Reference Position after multiple conflicts	Critical	Corrective	Oct-25	JC-38 Annex 4 (A.001)	A.001: section 4.2.5.4.3.4 "Special Filtering Matrix After Position Confirmation"

MCC-206
MCC-206 Planned compliance date

MonthDayYear
Date
MCC-206 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-207	Distribution of TWC beacon alerts	Critical	Enhancement	Oct-25	JC-38 Annex 4 (A.001)	A.001: section 3.12 "Return Link Service - Two-Way Communication (TWC)" A.001: section 4.2.11 "TWC Procedures"

MCC-207
MCC-207 Planned compliance date

MonthDayYear
Date
MCC-207 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-208	Provision of TWC Initial Q&A in MF #60 (Other Encoded Information)	Critical	Enhancement	Oct-25	JC-38 Annex 5 (A.002)	A.002: Appendix B.1 to Annex B / MF #60 "Other Encoded Information"

MCC-208
MCC-208 Planned compliance date

MonthDayYear
Date
MCC-208 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-209	Alert data processing capacity of a minimum to 500 solutions for a MEOLUT	Routine	Adaptive	Oct-26	JC-38 Annex 7 (A.005)	A.005: section 5.3 "Alert Data Processing Capacity"

MCC-209
MCC-209 Planned compliance date

MonthDayYear
Date
MCC-209 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-210	Consideration of the SGB ELT(DT) Alert Site in Post-Crash Activation status when the rotating field is valid	Routine	Adaptive	Oct-27	JC-39 Annex 4 (A.001)	A.001: section 2.2 "Alert Data Distribution Principles"

MCC-210
MCC-210 Planned compliance date

MonthDayYear
Date
MCC-210 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-211	New definition of the Reference Time for filtering redundant ELT(DT) data (10-min window)	Routine	Corrective	Oct-27	JC-39 Annex 4 (A.001)	A.001: section 3.2.3.2.2 "Filtering of Redundant Data for ELT(DT)s"

MCC-211
MCC-211 Planned compliance date

MonthDayYear
Date
MCC-211 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-212	Distribution of coarse position intended to the LADR if no refined position is available	Critical	Corrective	Oct-26	JC-39 Annex 4 (A.001)	A.001: section 3.13.2 "LADR Position Type Priority"

MCC-212
MCC-212 Planned compliance date

MonthDayYear
Date
MCC-212 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-213	Distribution of ELT(DT) data from non-nodal MCCs to nodal MCCs only if 24-bit address is available	Routine	Corrective	Oct-27	JC-39 Annex 4 (A.001)	A.001: section 3.13.3.1 "LADR Responsibilities for Non-Nodal MCCs"

MCC-213
MCC-213 Planned compliance date

MonthDayYear
Date
MCC-213 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-214	Distribution of ELT(DT) data from LDPs to the LADR only if 24-bit address is available	Routine	Corrective	Oct-27	JC-39 Annex 4 (A.001)	A.001: section 3.13.3.2 "LADR Responsibilities for Nodal MCCs"

MCC-214
MCC-214 Planned compliance date

MonthDayYear
Date
MCC-214 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-215	Distribution of ELT(DT) Uncorroborated Alerts only if refined position is available	Routine	Adaptive	Oct-27	JC-39 Annex 4 (A.001)	A.001: section 4.2.1.4 "Uncorroborated MEOSAR Alerts"

MCC-215
MCC-215 Planned compliance date

MonthDayYear
Date
MCC-215 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-216	Option to filter Uncorroborated Alerts by MCCs based on SPOC agreements	Routine	Adaptive	Oct-27	JC-39 Annex 4 (A.001)	A.001: section 4.2.1.4 "Uncorroborated MEOSAR Alerts"

MCC-216
MCC-216 Planned compliance date

MonthDayYear
Date
MCC-216 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-217	New or updated information provided in a Rotating Data Field for TWC, SRF (c) and (f)	Critical	Enhancement	Oct-26	JC-39 Annex 4 (A.001)	A.001: section 4.2.5.4.1 "Tests and Flag Setting for Special Processing Procedures"

MCC-217
MCC-217 Planned compliance date

MonthDayYear
Date
MCC-217 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-218	Redundant Doppler alert distribution depending on the Doppler quality, SRF (e)	Routine	Corrective	Oct-27	JC-39 Annex 4 (A.001)	A.001: section 4.2.5.4.1 "Tests and Flag Setting for Special Processing Procedures"

MCC-218
MCC-218 Planned compliance date

MonthDayYear
Date
MCC-218 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-219	MCC processing of the TWC Initial Questions/Answers	Critical	Enhancement	Oct-26	JC-39 Annex 4 (A.001)	A.001: section 4.2.11.1 Two-Way Communication (TWC) - Procedures

MCC-219
MCC-219 Planned compliance date

MonthDayYear
Date
MCC-219 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-220	Sending cancellation messages to RLSP and TWC-SP	Critical	Enhancement	Oct-26	JC-39 Annex 4 (A.001)	A.001: section 4.2.12 "Cancellation Message Procedures"

MCC-220
MCC-220 Planned compliance date

MonthDayYear
Date
MCC-220 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-221	Not distributing unconfirmed cancellation messages	Critical	Corrective	Oct-26	JC-39 Annex 4 (A.001)	A.001: section 4.2.12 "Cancellation Message Procedures"

MCC-221
MCC-221 Planned compliance date

MonthDayYear
Date
MCC-221 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-222	Restructuration of the SIT 141 message for MEOSAR interference (MFs #13, #14ab, #78, #88)	Routine	Enhancement	Oct-27	JC-39 Annex 5 (A.002)	A.002: Table B-1: Message Field Description and Appendix B.1

MCC-222
MCC-222 Planned compliance date

MonthDayYear
Date
MCC-222 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-223	Creation of the type of alert for the TWC Message to RCCs/SPOCs MF #45 "Message Type"	Critical	Enhancement	Oct-26	JC-39 Annex 5 (A.002)	A.002: Table B-1: Message Field Description and Appendix B.1

MCC-223
MCC-223 Planned compliance date

MonthDayYear
Date
MCC-223 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-224	Rebuilt of the AIS Identifier for transmission to RCCs/SPOCs, MF #51 "Type of Beacon" - "Vessel ID" in SIT 185, and MF #97 "Beacon Data Field" in SIT 927	Routine	Enhancement	Oct-27	JC-39 Annex 5 (A.002)	A.002: Table B-1: Message Field Description and Appendix B.1

MCC-224
MCC-224 Planned compliance date

MonthDayYear
Date
MCC-224 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-225	Insertion in SIT185 of information that TWC Dataset is Unknown when dataset is not recognized, MF #60 "Other information"	Critical	Enhancement	Oct-26	JC-39 Annex 5 (A.002)	A.002: Table B-1: Message Field Description and Appendix B.1

MCC-225
MCC-225 Planned compliance date

MonthDayYear
Date
MCC-225 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-226	Change MFs #85 and #86 "Two-Line Element (TLE) Set Format - Line 1" and "...Line 2" using Alpha-5 numbering scheme	Critical	Corrective	Oct-26	JC-39 Annex 5 (A.002)	A.002: Table B-1: Message Field Description and Appendix B.1

MCC-226
MCC-226 Planned compliance date

MonthDayYear
Date
MCC-226 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-227	Implementation of the MEOSAR QMS	Routine	Enhancement	Oct-27	JC-39 Annex 6 (A.003)	A.003: Section 2 "Methodology and Procedures for Continuous Monitoring and Objective Assessment of Cospas-Sarsat System Status"

MCC-227
MCC-227 Planned compliance date

MonthDayYear
Date
MCC-227 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-228	Capability to filter Doppler or DOA locations, based on a specified source of data (LUT), per beacon generation (FGB or SGB)	Routine	Enhancement	Oct-27	JC-39 Annex 7 (A.005)	A.005: Section 4.3 "Process Data Selectively"

MCC-228
MCC-228 Planned compliance date

MonthDayYear
Date
MCC-228 Comments


Reference	Brief Description	Criticality	Type	Implementation Due Date	Joint Committee/Council References	Document Section(s)/Page(s)
MCC-229	Validation of Rotating Field #4 reduced from two spare bits to one	Critical	Enhancement	Oct-26	CSC-73/OPN Red Book (A.001)	A.001: Table 4-7 Rotating Validation SGB

MCC-229
MCC-229 Planned compliance date

MonthDayYear
Date
MCC-229 Comments

Thank you for completing this questionnaire - after completing the Captcha and clicking the "Submit" button below you should receive an e-mail confirmation of your submission.

By clicking this "Preview Answers" button you will be given the opportunity to check your submission and, if necessary, to make changes to your responses. PLEASE DO NOT FORGET TO CLICK “SUBMIT” AT THE BOTTOM OF THE PREVIEW PAGE
Please verify that you are human
Should be Empty:

Ground Segment Changes CSC-73 - MCC