OpenLegislation

Division 5.1.6 Flight information exchange

United Kingdom

Original text. Later amendments are not shown.

Flight information shall be F1shared during the pre-tactical and tactical phases by ATC F2systems with the Network Manager.

Operational stakeholders shall implement services which support the exchange of the following flight information as indicated in the table below using the blue SWIM TI Profile:

  • Various operations on a flight object: Acknowledge reception, Acknowledge agreement to FO, End subscription of a FO distribution, Subscribe to FO distribution, Modify FO constraints, Modify route, Set arrival runway, Update coordination related information, Modify SSR code, Set STAR, Skip ATSU in coordination dialogue

  • Share Flight Object information. Flight Object includes the flight script composed of the ATC constraints and the 4D trajectory

Operational stakeholders shall implement the following services for exchange of flight information using the yellow SWIM TI Profile:

  • Validate flight plan and routes

  • Flight plans, 4D trajectory, flight performance data, flight status

  • Flights lists and detailed flight data

  • Flight update message related (departure information)

Service implementations shall be compliant with the applicable version of AIRM, the AIRM Foundation Material and the ISRM Foundation Material.

  1. System requirements

Annotations

Textual amendments

F1

Word in Annex point 5.1.6 substituted (31.12.2020) by The Air Traffic Management (Amendment etc.) (EU Exit) Regulations 2019 (S.I. 2019/459), regs. 1(2), 341(13)(a); 2020 c. 1, Sch. 5 para. 1(1)

F2

Words in Annex point 5.1.6 substituted (31.12.2020) by The Air Traffic Management (Amendment etc.) (EU Exit) Regulations 2019 (S.I. 2019/459), regs. 1(2), 341(13)(b); 2020 c. 1, Sch. 5 para. 1(1)