{
  "url": "https://openlegislation.uk/eu-regulation-2009-30/annex",
  "json_url": "https://openlegislation.uk/eu-regulation-2009-30/annex.json",
  "legislation": "eur/2009/30",
  "legislation_title": "Commission Regulation (EC) No 30/2009 of 16 January 2009 amending Regulation (EC) No 1032/2006 as far as the requirements for automatic systems for the exchange of flight data supporting data link services are concerned (Text with EEA relevance)",
  "legislation_url": "https://openlegislation.uk/eu-regulation-2009-30",
  "path": "annex",
  "kind": "annex",
  "number": null,
  "heading": null,
  "text": "Annexes I and III to Regulation (EC) No 1032/2006 are amended as follows:\n1.. in Annex I, the following Part D is added:\n‘PART D:\nREQUIREMENTS FOR PROCESSES SUPPORTING DATA LINK SERVICES\n1.\nLOGON FORWARD\n1.1.\nFlight information concerned\n1.1.1.\nThe information subject to the logon forward process shall include as a minimum:\naircraft identification,\ndeparture aerodrome,\ndestination aerodrome,\nlogon type,\nlogon parameters.\n1.2.\nRules of application\n1.2.1.\nOne logon forward process shall be performed for each data-link logged-on flight planned to cross the boundary.\n1.2.2.\nThe logon forward process shall be initiated at or as soon as possible after the earlier of the times determined from the following:\na parameter number of minutes before the estimated time at the coordination point,\nthe time at which the flight is at a bilaterally agreed distance from the coordination point,\nin accordance with the letters of agreement.\n1.2.3.\nEligibility criteria for the logon forward process shall be in accordance with the letters of agreement.\n1.2.4.\nThe logon forward information shall be included with the corresponding flight information in the receiving unit.\n1.2.5.\nThe logged-on status of the flight may be displayed at the appropriate working position within the receiving unit.\n1.2.6.\nCompletion of the logon forward process, including confirmation from the receiving unit shall be provided to the transferring unit.\n1.2.7.\nFailure of the logon forward process to confirm completion, within the applicable quality of service requirements, shall result in the initiation of an air-ground data link contact request to the aircraft.\n2.\nNEXT AUTHORITY NOTIFIED\n2.1.\nFlight information concerned\n2.1.1.\nThe information subject to the next authority notified process shall include as a minimum:\naircraft identification,\ndeparture aerodrome,\ndestination aerodrome.\n2.2.\nRules of application\n2.2.1.\nOne next authority notified process shall be performed for each eligible flight crossing the boundary.\n2.2.2.\nThe next authority notified process shall be initiated after the next data authority request with the aircraft has been acknowledged by the airborne system.\n2.2.3.\nFollowing the successful processing of the next authority notified information the receiving unit shall initiate a controller pilot data link communication (CPDLC) start request with the aircraft.\n2.2.4.\nIf the next authority notified information has not been received within a bilaterally agreed parameter time, local procedures shall be applied by the receiving unit for the initiation of data link communications with the aircraft.\n2.2.5.\nCompletion of the next authority notified process, including confirmation from the receiving unit shall be provided to the transferring unit.\n2.2.6.\nFailure of the next authority notified process to confirm completion, within the applicable quality of service requirements shall result in the initiation of local procedures in the transferring unit.’;\n2.. in Annex III, points 2 and 3 are replaced by the following:\n‘2.\nThe interoperability and performance requirements specified in paragraphs 3.2.4, 3.2.5, 4.2.3, 4.2.4, 5.2.3, 5.2.4, 6.2.3 and 6.2.4 of Annex I, Part B and 1.2.6, 1.2.7, 2.2.5 and 2.2.6 of Annex I, Part D shall also be considered as safety requirements.\n3.\nFor the revision of coordination, abrogation of coordination, basic flight data, change to basic flight data, logon forward and next authority notified processes, the quality of service requirements specified in Annex II shall also be considered as safety requirements.’.",
  "extent": "E+W+S+N.I.",
  "status": null,
  "version": "current",
  "annotations": [],
  "outstanding_effects": [],
  "provenance": {
    "source": "legislation.gov.uk",
    "source_url": "https://www.legislation.gov.uk/eur/2009/30/annex",
    "retrieved_at": "2026-11-01T14:51:42.539049+00:00"
  },
  "licence": "Open Government Licence v3.0",
  "licence_url": "https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/",
  "attribution": "Contains public sector information licensed under the Open Government Licence v3.0. Source: legislation.gov.uk, The National Archives."
}