SYNCHRONOUS_REQUEST_RESPONSE

This operation allows the operator to correct the erroneous fields upon the reception of a CHG or ICHG message.
Whenever a change is made to the data contained in a Flight Plan message already sent to the ATSUs concerned with the flight, they must all be notified. It is particularly important to notify changes of Flight Level or Flight Rules, whether the change is made before departure or en-route. Such notification may be done by phone or ATS/DS when possible; otherwise it must be done by means of a modification message sent to AFTN.

The following CHG fields can be corrected through this operation:
CHG content: callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), totalEstimatedElapsedTime (F16b), otherInformation (F18), amendments of other ICAO fields (F22), alternativeDestinationAerodromeDesignator (F16c).
In CHG, F22 should only amend F7b/c, F8, F9, F10, F13b, F14, F15, F16, F18, F19.

The following ICHG fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD),
estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

This operation allows the operator to correct the erroneous fields upon the reception of an FPL or IFPL message.
The FPL message is the flight plan as filed with an ATS unit by the pilot or a designated representative, without any subsequent changes.
The following FPL fields can be corrected through this operation:
callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), flightRules (F8a), flightType (F8b), numberOfAircraft (F9a), aircraftTypeICAOIdentifier (F9b), wakeTurbulenceCategory (F9c), NCAEquipment (F10a), surveillance equipment (F10b), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), enRouteCruiseSpeed (TAS or Mach) (F15a), requestedFlightLevel (F15b), icaoRoute (F15c), destinationAerodromeDesignator (F16a), totalEstimatedElapsedTime (F16b), alternativeDestinationAerodromeDesignator (F16c), otherInformation (F18), supplementaryInformation (F19).

The following IFPL fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP),
NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

This operation allows the operator to correct the erroneous fields upon the reception of an IAPL message (ICAO format message APL is not applicable CCS).

The following IAPL fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

This operation allows the operator to correct the erroneous fields in the SFPL upon the reception of an IACH message (ICAO format message ACH is not applicable CCS). It is the modification message type distributed by the IFPS upon receipt and successful processing of an FNM, MFS, and AFP for which a valid associated flight plan exists in the IFPS.

The following IACH fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

This operation allows the operator to correct the erroneous fields upon the reception of an ARR or IARR message. Where an Arrival message is required for an IFR/GAT flight or part thereof operating within the IFPZ, the appropriate air traffic services unit shall submit such to the IFPS for processing

The following ARR fields can be corrected through this operation:
callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), destinationAerodromeDesignator and actualLandingTime (F17), date of flight in otherInformation (F18).

The following IARR fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), actualLandingTime (ATA), destinationAerodromeDesignator (ADARR)

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

This operation allows the operator to correct the erroneous fields upon the reception of an CNL or ICNL message. When a schedule flight or a flight for which a Flight Plan Message has been sent, is subsequently cancelled, the ATSU at the point where the flight is cancelled shall send a Cancellation Message.

The following CNL fields can be corrected through this operation:
callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), otherInformation (F18).

The following ICNL fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE)

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

This operation allows the operator to correct the erroneous fields upon the reception of an DLA or IDLA message. When a scheduled flight, or a flight for which a FPL was despatched, has not left the loading apron within 30 minutes after the scheduled or estimated time of departure; or where there is reason to believe that such a flight will not be in a position to leave within the 30 minutes due to the late arrival of the aircraft on the previous sector or for any other reason.

The following DLA fields can be corrected through this operation:
callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), otherInformation (F18).

The following IDLA fields can be corrected through this operation via decoded data:
departureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).

Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section "Operations"..

Operation to process the input of a manual SFPL cancellation..

Operation to process the creation of an abbreviated SFPL. .

Operation to process the creation of a full SFPL whatever is the type of flight (OAT/GAT, VFR/IFR), according to the given initial FP fields..

Operation to process the deletion of a specified Flight Plan from ADSP.

Operation to process an SFPL(s) consultation request..

Operation to process the modification of one or several SFPL fields.
The input shall contain the flight identifier, the originator and at least a field to modify.
The fields that can be modified through this operation are related to static SFPL information (information of the SFPL independent of the modifications triggered by tactical instructions) such as: callsign aircraftIdentification (F7a), departureAerodromeDesignator (F13a), destinationAerodromeDesignator (F16a), flightType (F8b), flightRules (F8a), numberOfAircraft (F9a), aircraftTypeICAOIdentifier (F9b), wakeTurbulenceCategory (F9c), NCAEquipment (F10a), surveillance equipment (F10b), equipment status (F81), estimatedOffBlockTime (F13b), requestedFlightLevel (F15b), icaoRoute, enRouteCruiseSpeed (TAS or Mach) (F15a), totalEstimatedElapsedTime (F16b), alternativeDestinationAerodromeDesignator (F16c), ssrCodeData, otherInformation (F18), supplementaryInformation (F19), sidDesignator, starDesignator..

Operation to process the input of a Cleared Flight Level given the flight identifier and the value of the level to be applied.
The input may contain applicationStart data that can be a route point, distance before/after a route point or after current position..

Operation to process the input of a direct instruction given the flight identifier and the target point of the direct (not overflown point already belonging to the route).
The input may contain application data that can be a route point, distance before/after a route point or after current position..

Operation to process the input of a heading clearance.
It allows to assign either:
- an absolute heading. To do this:
- routePointId should not be filled
- continueHeading should be either not filled or set to FALSE
- either assignedHeading or application end point shoud be filled. If filled, the application end point should be expressed in the geographical point type
- a relative heading. To do this:
- routePointId should not be filled
- continueHeading should be either not filled or set to FALSE
- directionOfTurn and assignedHeading shoud be filled
- a maintain order. To do this:
- routePointId should not be filled
- continueHeading should be set to TRUE
- a resume own navigation order. To do this, routePointId should be filled..

Operation to process the modification of a route portion for a specified flight.
The input shall contain:
- the flight identifier,
- the new portion of route.
The input may contain either an application end point (routePoint not overflown used to rejoin the old route) or a new destination aerodrome.
The input may also contain application start data that can be a route point, distance after/before a route point, distance after current position.
.

Operation to process the input of a speed clearance..

Operation to process the input of the Entry Flight Level used for coordination between two logical positions.

Operation to process the input of the Exit Flight Level used for coordination between two logical positions.

Operation to process the input of an En-Route cruise level (ATC planning constraint) given the flight identifier and the value of the level to be applied.

Operation to process the input of a Requested Flight Level given the flight identifier and the value of the level to be applied.

Operation to process the input of an ROCD (Rate Of Climb or Descent) instruction..

The operation allows to release an assigned SSR code if it is not used for correlation purpose.
Due to the limited number of Mode 3/A SSR codes it is necessary to release assigned codes back into the pool of available codes when possible. Normally this would be handled automatically with the Flight Data Manager or other service monitoring the status of a flight and requesting the release of a code when a flight lands, leaves the Area of Responsibility of an ATSU or is cancelled..

Allows a consumer to start a simulation session.
The input of the simulationSessionStart operation shall contain the initial time of the session..

Allows a consumer to stop the current simulation session.

The applicationTime shall be not before than N seconds from the current time, where N is a configurable parameter tuned on provider platform (e.g. 10 seconds)..

Enables to activate a sector mapping: the supervisor selects a mapping (next or pre-defined mapping) that will replace the current mapping of the concerned ASTUSectorConfiguration.
The supervisor may also choose to revert back to the pre-defined default sector mapping. If not, the input parameters shall be the identifier and the state (next or pre-defined) of the origin sector mapping.
As a consequence, the parameter sectorMappingId is MANDATORY when the parameter revertToDefaultMapping is not filled or set to FALSE (but if revertToDefaultMapping is set to YES, sectorMappingId is not needed)..

Enables to modify a current mapping or a next mapping of a given ATSUSectorConfiguration..

Enables to load a pre-defined mapping as being the next mapping of a given ASTUSectorConfiguration.

The input parameters shall be:
- the ATSUSectorConfigurationIdentifier,
- the identifier of the sectorMapping.
.