Scenario Details can come with or without a picture, as shown on the two examples below.

Definitions of the field labels

• Identifier: The Scenario name (in the blue header)
• Origin: Where the flow of the traffic to which the scenario applies, is coming from.
• Destination: Where the flow of the traffic to which the scenario applies, is going to.
• Types:
  AR - Alternative Route scenario: A route (usually non-RAD compatible) opened to alleviate congestion in an area. Due to the non-standard nature of the route, this flow is usually regulated when available.
  FL - Flight Level Cap scenario: the flow of traffic is level-capped (for a portion of its route) to take it out of a congested area.
  PR - Preferred Routing scenario: a suggested route which the concerned ACCs on a particular axis would prefer the flow to follow. This field can be empty.
  RR - Re-Route scenario: the flow of traffic is forced to refile geographically to avoid a congested area.
• Refile: Specific condition(s) to which the of traffic is required to comply.
• Suggested Alternative Routes: Proposed profiles for the Aircraft Operators to consider when selecting a route in order to comply with the Condition(s)
• Comments: Used to provide additional information relating to the scenario. For example: RAD restrictions which will be ignored by IPFS to allow compliance with the Condition(s) or Refile fields.
• Location (Area): The specific airspace(s)/point(s) of congestion alleviated by the application of the scenario.
• On-load Areas: The key airspaces which may expect to receive additional traffic as a result of the application of the scenario.
• Off-load Areas: The key airspaces which may expect to receive less traffic as a result of the application of the scenario.
• Applicability: If the availability of the scenario for the ATFCM use is limited to a specific period they are listed here. For example: weekend only during the ski season.
• Status: can be either Published, Agreed or Active
  • Published: Used to indicate if the scenario is in 'draft' mode or has been 'published' for operational use.
  • Agreed: The specific periods (dates + hours) for which the concerned FMPs and Network Operations Division have agreed to apply the scenario.
  • Active: The actual specific periods (dates + hours) for which the scenario is/was applied, derived from the ETFMS.

Explanations of the map labels

Map labels contain information from the scenario definition and are used to highlight on the map items of specific interest or which are worthy of particular care and attention.