This Aeronautical Information Circular aims to present the concept of Flight and Flow Information for a Collaborative Environment (FF-ICE) as well as provisions of the International Civil Aviation Organization (ICAO) regarding this concept.
This AIC applies to all users of the Brazilian Airspace Control System (SISCEAB).
2.1. DECEA is responsible for overseeing and managing activities within Brazilian territorial airspace, as well as the airspace above the oceanic area, covering a total of 22 million km². With projections showing a rise in air traffic volume over the next 20 years, this management requires that national authorities implement measures to establish highperformance air navigation and airspace control systems. To address this challenge, DECEA and its partners have joined forces to develop and build an agile, safe, sustainable, high-performance and interoperable air navigation infrastructure.
2.2. One of the initiatives proposed by ICAO included in DECEA’s SIRIUS Brazil Program and aligned with the Global Air Navigation Plan (GANP), is the implementation of the Flight and Flow – Information for a Collaborative Environment (FF-ICE) concept at SISCEAB. This concept is linked to the ATM Service Delivery Management (SDM) component, as outlined in the Global ATM Operational Concept (GATMOC). Its
implementation will support the development of high-performance and interoperable airspace control system in the country. By adopting the FF-ICE concept, the current flight
implementation will support the development of high-performance and interoperable airspace control system in the country. By adopting the FF-ICE concept, the current flight
2.3. Plan format will be enhanced, while also enabling the implementation of other concepts outlined in the GANP, with emphasis on Trajectory Based Operations (TBO).
2.4. When implementing FF-ICE services, Brazil must ensure compliance with the requirements for exchanging flight plans and other movement messages from aircraft operators and ATS Units that have not yet adopted these services, in accordance with DECEA regulations.
2.5. It is important to emphasize that the implementation of the FF-ICE concept in Brazil relies on the successful deployment of SWIM, an ICAO-proposed concept aimed at creating a global environment for the interoperability of air traffic management (ATM) data and information. SWIM will enable the integration of ATM systems on a global scale, facilitating the exchange of information between ground and onboard systems through a shared architecture.
2.6. The FF-ICE concept includes the following services:
2.6.1.
Planning Services: Allows the evaluation of a preliminary flight plan (PFP) in relation to its acceptability and, when applicable, identifies any relevant restrictions and resulting limitations to the flight;
2.6.2.
Filing Services: Enables the evaluation of an eFPL for the provision of air traffic services and indication of the flight plan acceptability;
2.6.3.
Trial Services:Allows the assessment of a request for testing the acceptability of a flight plan and, when applicable, identifies any relevant restrictions and resulting limitations to the flight. This service also provides an operator or designated representative with the ability to present what-if scenarios and receive feedback from an FF-ICE service unit prior to submitting a PFP, eFPL, or flight plan update;
2.6.4.
Flight Data Request Service: Provides data relating to a specific flight, such as the most recent version of a filed flight plan or search and rescue data, upon request by a recipient authorized to request such data;
2.6.5.
Notification Service: Provides data relating to a particular flight event (e.g. departure, arrival) to the required recipients; and
2.6.6.
Publication Service: Publishes flight and flow data for access by authorized subscribers.
2.7. When FF-ICE services begin to be provided in Brazil, the competent ATS authority must designate at least one FF-ICE service unit in the country, in addition to taking the necessary measures so that, at a minimum, the flight data request and filing services are provided. In addition, it shall ensure that the FF-ICE service unit maintains the necessary capacity to exchange ATS messages with operators and ATS
units that have not implemented FF-ICE services, in accordance with the provisions of ICA 100-15 (ATS Messages). Furthermore, Brazil must ensure the dissemination of information regarding the availability of FF-ICE services, along with the related procedures and conditions, in Aeronautical Information Publications (AIP).
units that have not implemented FF-ICE services, in accordance with the provisions of ICA 100-15 (ATS Messages). Furthermore, Brazil must ensure the dissemination of information regarding the availability of FF-ICE services, along with the related procedures and conditions, in Aeronautical Information Publications (AIP).
2.8. The procedures and conditions to be published in the AIP, as outlined in the previous section, must include guidelines for preparing valid flight plans for submission, details on the time and/or conditions that modify the procedures for filing a flight plan update message, the timeframe, the moment, and/or conditions under which updates to the planning status and filing status messages are provided, if applicable, the types of flight data that may be requested via the FF-ICE flight data request service, if applicable, and the deadlines for submitting a PFP message, if applicable.
Information required for flight planning, coordination and notification, shared in a standardized format among ATM community members, including those involved in flight and aerodrome operations.
Unit designated by the competent ATS authority to provide FF-ICE services. The competent ATS authority may designate an existing unit, such as an ATS unit, or a local or regional air traffic flow management unit, as the unit for providing the FF-ICE service.
Specific information relating to a flight or part of a planned flight of an aircraft. The term “flight plan” can be paired with adjectives such as “preliminary”, “filed”, or “current” to specify the context and the different stages of a flight. When the word “message” is used with this phrase, it refers to the content and format of the flight plan data as transmitted.
Latest FPL or eFPL plan filed by the pilot, operator, or designated representative for use by air traffic service units. FPL refers a Filed Flight Plan using the aeronautical fixed service. eFPL refers to a Filed Flight Plan that uses FF-ICE services, enabling the exchange of additional information not contained in the FPL.
Information relating to a flight submitted by an operator or a representative designated to carry out collaborative planning of a flight, prior to submitting a flight plan.
5.1. The messages specified in Table 1 will be used to exchange information as indicated in the procedures for FF-ICE services.
5.2. The content of an FF-ICE message must allow for conversion into a corresponding ATS message when required to comply with the standards outlined in ICA 100-15 (ATS Messages). This involves translating an eFPL message into an FPL message, a flight plan update message into a CHG or DLA message, and a flight cancellation message into a CNL message. It is important to note that any additional data
elements defined for use in FF-ICE messages that do not have a corresponding data element in ATS messages cannot be translated.
elements defined for use in FF-ICE messages that do not have a corresponding data element in ATS messages cannot be translated.
5.3. Personnel involved in the provision and use of FF-ICE services will not have access to the full content of FF-ICE messages, as the majority will be generated and processed by computer systems. However, flight plan information must be displayed or made available to relevant individuals, such as flight dispatchers or other designated staff, for verification, coordination, and any necessary modifications.
Table 1 – Messages for exchanging information in FF-ICE services
6.1. Each FF-ICE service has a set of applicable messages and associated procedures. Some of these procedures are used by more than one service.The originator must ensure that the FF-ICE message complies with the applicable data format and conventions, and the recipient must validate the FF-ICE message and verify its compliance with the applicable data format and conventions. To the extent possible, it must additionally verify its completeness and accuracy.
6.2. Following the validation of the message referenced in the previous item, the recipient must promptly send a submission response message to PFP, eFPL, flight plan update, trial, flight cancellation, DEP, ARR, and data request messages. If the submission response indicates that the message has been rejected, the recipient is required to take appropriate action.
6.3. The originator of PFP, eFPL or flight plan update messages shall include information about the flight plan version. This information allows the recipient to confirm that the flight plan version in the message is more recent than the previously received version and that no further updates have been made. If the flight plan version in a received message is outdated or lacks necessary updates, the recipient will take action to obtain the most recent version of the flight plan.
6.4. The FF-ICE planning service will be provided upon submission of a PFP message by an operator or a designated representative for each FF-ICE unit that needs to evaluate the message and has available service capability. This message, when first sent, shall include, as a minimum, the GUFI, the departure and destination aerodromes, the date and estimated off block time. Data elements can be expanded as more information becomes available to the operator.
6.5. When implementing FF-ICE services in Brazil the deadlines for submitting PFP messages, as established by the relevant ATS authority or in accordance with regional air navigation agreements, will be published in AIP. It is important to note that the PFP message will be rejected if there is a flight plan submitted for the flight in question. Additionally, FF-ICE service units will evaluate the validated PFP message and provide an appropriate response. It should be noted that sending a PFP message does not replace the submission of an eFPL message.
6.6. It is important to note that, in the future, the AIP should specify that an operator or its authorized representative opting to use FF-ICE services must submit an eFPL for each relevant FF-ICE service unit along the flight route. Additionally, an FPL must be submitted for each ATS unit that lacks the capability to process an eFPL, covering each airspace the flight will cross.
6.7. An FF-ICE service unit may choose to provide a similar functionality, taking on the responsibility of supplying plan information and its updates in an appropriate format to the relevant interested units along the flight route. Additionally, it must provide suitable responses to an operator or their authorized representative when they send an eFPL solely to the FF-ICE service unit serving the departure aerodrome.
6.8. The eFPL message must include, as a minimum, the GUFI and the flight data elements required by ICA 100-11, MCA 100-11 and other related publications.
6.9. The FF-ICE service unit will ensure that the filed flight plan is accessible to all relevant ATS units within its area of responsibility. Additionally, as agreed upon by the ATS authorities, an extra eFPL message may need to be sent to the FF-ICE service units of each FIR near the routes a flight will use or in specific airspaces that the flight is anticipated to cross. The purpose of sending this additional eFPL message is to facilitate the identification of aircraft and thus eliminate or reduce the need for interceptions due to deviations from the assigned route.
6.10. An FF-ICE service unit shall include in the AIP the relevant conditions that modify the procedures for transmitting a flight plan update message, as outlined in this publication. It should be noted that depending on the local agreement between the FF-ICE service unit and the ATS unit that issues ATC clearances, flight plan updates may not be accepted after a certain time, which constitutes important information for operators.
6.11. When a change is necessary for a previously filed flight plan (PFP or eFPL, as applicable), the operator or authorized representative must submit a flight plan update message to all recipients of the original flight plan.
6.12. It is important to note that if such a change leads to new entities that have not previously received the flight plan, the operator or authorized representative must provide an updated version of the full flight plan (PFP or eFPL, as applicable) to the affected recipients, including all prior updates.
6.13. If a filed flight plan message (PFP or eFPL) contains a version number that is one higher than the current version, it shall be treated as an update to the previously submitted flight plan. However, when the flight plan version number contained in a flight plan update message is not a higher number than the currently available version, the flight plan update message will be rejected, and the operator will be informed of the version mismatch.
6.14. It is important to note that when a flight plan update rejection message is received due to version delays, the operator or authorized representative must submit the latest version of the full flight plan (PFP or eFPL, as applicable). If a flight plan is submitted according to items 6.6 and 6.7, the FF-ICE service unit must inform recipients of any changes to the filed flight plan, including instances where the flight is no longer relevant to them after a modification. After validating a flight plan update message, the FF-ICE service units will assess the updates to previously filed flight plans and provide an appropriate response.
6.15. Each FF-ICE service unit will assess the acceptability of the flight plan or flight plan update and send the relevant FF-ICE message (either a planning status message or a filing status message) as soon as possible. For the planning status message, it is important to note that it must be sent no later than three hours prior to the estimated off block time. The acceptability of the flight plan is determined through an evaluation of its semantics and an additional assessment to ensure compliance with relevant restrictions and/or limitations. The response messages generated from the flight plan evaluation are supplementary to the submission response message provided.
6.16. An FF-ICE service unit will send planning or filing status update messages to reflect changes in restrictions and/or limitations applicable to the flight. In such cases, the timeframe and/or conditions for providing updates to planning status and filing status messages will be published in the AIP. In response to the planning or filing status message, the operator or authorized representative will evaluate the content and take appropriate action.
6.17. To cancel a flight for which a preliminary flight plan has already been submitted, the operator or authorized representative must send a flight cancellation message to each FF-ICE service unit that received the corresponding flight plan. It is important to note that after validating the flight cancellation message, the FF-ICE service unit will take the necessary actions to ensure that the flight is no longer regarded as a scheduled flight. These actions include ceasing to accept FF-ICE messages that contain the GUFI of the canceled flight, notifying FF-ICE service units and/or ATS units aware of the flight, and removing the flight from the ATC systems. Additionally, it is important to note that when a previously cancelled flight needs to be reinstated, a new flight plan must be filed.
6.18. An FF-ICE service unit may share any information it deems relevant about a flight, but must be prepared to provide, upon request, at least the latest version of a preliminary flight plan, a filed flight plan, supplementary search and rescue information, and the most recent planning status or latest filing status.
6.19. To obtain flight plan information for a specific flight, a flight data request must be sent to the relevant FF-ICE service unit identified as having the necessary information.The flight data request message, sent by an authorized operator or representative, will pertain only to a flight that is under their operational control. It is the responsibility of the FF-ICE service unit to verify that the flight data request message comes from an entity authorized to request such information.
6.20. After validating the flight data request message, the FF-ICE service unit must provide the requested flight data as quickly as possible; when it is unable to provide the requested data, it will send a send-reject response message and indicate the reasons why it is unable to provide the requested data.
6.21. The FF-ICE trial service will be provided by sending a trial request message by an operator or authorized representative to each FF-ICE service unit that requires assessment and that has indicated the availability of providing the service. The trial request message may be sent to a FF-ICE service unit that is not on the original flight path and that has not previously received the flight plan, for the purpose of evaluating a route change in the airspace under the jurisdiction of that FF-ICE service unit.
6.22. It should be noted that an FF-ICE service unit must determine, as soon as possible and after validation of the trial request message, the acceptability of possible changes to a planned flight and send a trial response message. The information contained in the trial request message will not be used for air traffic flow management or air traffic services purposes.
7.1. When it is determined that the FF-ICE notification service will be used as a means of meeting the flight departure and arrival submission requirements prescribed in ICA 100-15 (ATS Messages) 4.2.1.5 and 4.2.1.6, flight departure messages and flight arrival messages shall be used in place of DEP and ARR messages.
8.1. FF-ICE services will make use of information services. In the context of system-wide information management, information service refers to automatic interaction within a service delivery framework. Information service procedures are contained in ICAO Doc 10199 (Procedures for Air Navigation Services - Information Management (PANS-IM)).
8.2. Providers and users of FF-ICE services shall adopt an information exchange model that provides the structure and format of the required flight and flow data elements, including their properties, associations and data types, as well as restrictions on data values. In addition, the model must allow the construction and exchange of the standardized FF-ICE messages listed in Table 1 and provide a mechanism by which additional flight and flow data and/or FF-ICE messages can be used without affecting overall interoperability.
9.1. Regarding the flight plan, it is important to note that both operators and air traffic service units must use either the future flight plan form or the flight plan message outlined in this AIC to prepare the corresponding flight plans.
9.2. When implementing FF-ICE services, operators and ATS units are required to follow the guidelines for preparing and/or completing the relevant flight plan, as outlined in this AIC and any future DECEA publications. In addition, they must adhere to any restrictions, limitations, or advisory information related to flight planning as specified in the relevant Aeronautical Information Publications (AIP) or other publications, such as NOTAMs.
9.3. It is important to note that, except for preliminary flight plans, flight plans should not be submitted more than 120 hours prior to the scheduled departure time. For the acceptance of a flight plan, it must be filed before departure at an FF-ICE Service unit or any other facility providing service at the departure aerodrome, in accordance with DECEA regulations.
9.4. The ICAO Manual on Collaborative Air Traffic Flow Management (Doc 9965) offers instructions for completing a Flight Plan Form and provides guidance on the flight plan codes applicable during the transition period, along with additional flight information that can be exchanged through FF-ICE services.
9.5. When implementing FF-ICE services in Brazil, the procedures and messages related to these services will be detailed in a specific DECEA regulation. For air traffic services, ATS messages must be generated by an ATS unit, an AIS unit, or the aircraft, as outlined in this publication. The filed flight plan messages and the corresponding update messages may originate from another duly accredited sector, provided that the other applicable regulations are observed. The delegation of the accredited sector referred to in the previous item may be carried out through publication in the AIP, by agreement with the interested operators, or through FF-ICE services.
10.1. Additional procedures related to the implementation of FF-ICE services will be published in due course.
10.2. DECEA provides a communication channel for sending questions, suggestions, comments, criticisms, compliments and error notifications through the Citizen Service at https://servicos.decea.mil.br/sac/index.cfm.
10.3. This AIC republishes the AIC A 28/24.