Requests sent to NMOC can handled in two ways: Automatic or Manual.
In a number of cases, the request can be handled automatically, as it is analysed by a script that returns the appropriate response. And in cases where specific interactions need to occur, the response will be issued manually by NMOC staff.
As automated response might however not always be plain enough for the user, here's a summary table of the currently existing automated responses:
| Type of the request | Response sent by NOM (AUTO processing of request) | Operational Explanation for the User | ||
|
Not suitable for manual improvement |
Sorry, no improvement possible as your CTOT is the best, based on handling or TWR constraints. | Your slot cannot be improved based on the operational constraints at airport side. Once the conditions change, the true revision process will try to improve your flight. | ||
| Not suitable for exclusion (FMP, TWR) |
Sorry, your exclusion request cannot be approved. | The requested exclusion has an impact in other areas of responsibility and cannot be granted. | ||
| Local Average Delay rejection (AO, FMP, TWR) |
Sorry, no improvement possible as you have less than the Local Average Delay parameter value of the regulation. | The flight is affected by a regulation and the delay (OLA) of the flight is smaller than the Modulated local Average Delay (MLAO) parameter. The parameter is a factor of the average delay around the ETO of your flight. Please avoid using telephone to contact NMOC | ||
| Superseding (AO, FMP, TWR) |
We have already received the same request from a different originator - it will be processed ASAP. | In order to manage the requests received from multiple actors, the requests have a pre-defined hierarchy in accordance to ATFCM criteria. A different operational unit with higher priority has sent the same request to NMOC for the same flight. Please consult the history of your request to identify such operational unit. Please avoid using telephone to contact NMOC. | ||
| Duplicate processing (Different users (AO, FMP, TWR) |
We have already received the same request from a different originator -it will be processed ASAP. | In order to manage the requests received from multiple actors, the requests have a pre-defined hierarchy in accordance to ATFCM criteria. A different operational unit with higher priority has sent before you the same request to NMOC for the same flight. Please consult the history of your request to identify such operational unit. Please avoid using telephone to contact NMOC. | ||
| SIT1 rejection (AO, FMP, TWR) |
Sorry, no improvement possible before the Slot is issued. | Your request for slot improvement has been received before the slot has been issued and distributed for the flight. Your improvement requests can only be processed once the slot is issued. | ||
| Slot extension (s) (AO) |
CDM | COBT-20 | CDM | COBT-20 |
| Your flight is departing from a CDM airport. If your flight has received start-up approval only the pilot can call the TWR (over the frequency) for a slot extension. If your flight has not received start-up approval an update of the TOBT is required. | No extension possible as the current time is not within the 20 minutes window before COBT (CTOT-Taxitime). Send a DLA, please. |
Your flight is departing from an A-CDM airport. If the flight has received start-up approval, the pilot can request a slot extension to the TWR over the frequency. If your flight has NOT received start-up approval, you need to send an update of your TOBT via the corresponding DPI message or update your FPL via CHG/DLA. |
The flight is departing from a standard airport (non A-CDM) and your request should be received between 20 minutes before COBT and COBT. As the slot extension is not possible, you need to send a DLA message. | |
| Request is locked and duplicate received (AO, FMP, TWR) |
We have already received the same request from a different originator. The request is currently being processed by NMOC staff. | We have already received the same request from a different originator. The request is currently being processed by NMOC staff. A response will follow. Please avoid using telephone to contact NMOC. | ||