| DDR | Destination MCC | Maximum Number of Alerts Requested after Position Confirmation (1) | LGM Operational (2) | LGM entry in Operation Date | FGB ELT(DT) (3) | SGB (4) |
| Central DDR | CYMCC | 999 | YES | Nov-19 | ||
| FMCC | 0 | YES | Dec-16 | JC-36 | EWG-3C/2022 | |
| GRMCC | 999 | YES | Jun-21 | |||
| ITMCC | 999 | YES | Mar-22 | |||
| NMCC | 0 | YES | Sep-17 | |||
| TRMCC | 0 | YES | Dec-20 | |||
| UKMCC | 999 | YES | Jun-19 | |||
| Eastern DDR | CMC | 0 | YES | Sep-22 | ||
| INMCC | 999 | NO | ||||
| PAMCC | 999 | NO | ||||
| North West Pacific DDR | CNMCC | 0 | NO | |||
| HKMCC | 1 | NO | ||||
| JAMCC | 999 | YES | Apr-20 | |||
| KOMCC | 0 | NO | ||||
| TAMCC | 0 | YES | Mar-22 | |||
| VNMCC | 1 | NO | ||||
| South Central DDR | AEMCC | 999 | NO | |||
| ALMCC | 999 | YES | May-20 | |||
| NIMCC | 999 | NO | ||||
| QAMCC | 999 | YES | Oct-19 | |||
| SAMCC | 999 | NO | ||||
| SPMCC | 999 | YES | Jan-19 | |||
| South West Pacific DDR | ASMCC | 999 | NO | |||
| AUMCC | 999 | YES | Jul-19 | |||
| IDMCC | 999 | NO | ||||
| SIMCC | 999 | YES | Apr-20 | |||
| THMCC | 999 | NO | ||||
| Western DDR | ARMCC | 999 | NO | |||
| BRMCC | 999 | NO | ||||
| CHMCC | 999 | YES | Nov-20 | |||
| CMCC | 0 | NO | ||||
| PEMCC | 999 | NO | ||||
| USMCC | 999 | YES | Dec-16 | JC-36 | JC-36 |
as at 14-Mar-2023
Legend
| 0 | MCC has requested that no additional alert messages for a particular beacon activation be sent to it after a message has been received that includes a confirmed position for that beacon. |
| 999 | MCC has requested to receive unlimited additional alert messages for a particular beacon activation even after receiving a confirmed beacon position. |
| [xx] | The number specifies the maximum number of additional alert messages desired by the MCC after receiving a confirmed position from a particular beacon activation. |
Notes:
(1) Maximum Number of Alerts Requested after Position Confirmation:
- All MCCs by default will receive continued transmission of MEOSAR data for a beacon, even after initial position confirmation (and will be shown as 999 above) unless the MCC has notified its nodal MCC and the Secretariat of a preferred numerical limit to messages after initial confirmation of a beacon’s position.
- Per document C/S A.001 section 3.2.5, the capability to limit the number of alerts after position confirmation is not required.
(2) For current operational status of MCCs, see the Cospas-Sarsat Quality Monitoring System (QMS) tables.
The following status information is provided from the EWG/JC formal recommendation when:
(3) the MCC is commissioned for FGB ELT(DT) capability.
(4) the MCC is commissioned for SGB capability (including SGB ELT(DT)).