Airport Operational Note

An Operational Note is a piece of textual information that is intended for Airport users, and that cannot be otherwise modelled digitally.

Scenarios that should be entered as Operational Notes include occurrences such as potential delays, special events, parking restrictions, etc.

To facilitate the filtering of Operational Notes in client systems, some machine-readable properties are included.

Airport Operational Notes should not be used for temporary airport closures, runways closures, or any other information that can be modeled in Availability or any other part of the data model.

Property	Type	Description
aid	string	A string with the AID of the Airport Operational Note, with ONA as namespace
validFrom	string	An ISO 8601 formatted date-time string that indicates when the Operational Note is first in force. This is expressed in Local Time. For example 2020-01-30T08:00:00.
validTo	string	An ISO 8601 formatted date-time string that indicates when the Operational Note ceases to be in force. This is expressed in Local Time. For example 2020-02-02T18:59:59
criticality	string	A string indicating the level of criticality of the Operational Note. Possible values are: INFORMATION_ONLY for information that have no operational impact. Knowledge is considered relevant to make the operations smoother, but no operational impact arises from not knowing of it. For example: JET-A1 pressurized refuelling not available. Only overwing refuelling possible. OPERATIONALLY_RELEVANT for information that may have an operational impact, but is not critical. Not knowing such information will likely have a minor operational impact in the form of delays or inconvenient to the crew or passengers. The flight can still take place under all circumstances. For example: Parking stands in front of the FBO are closed due to Work In Progress. Only remote stands available with a car transfer to the FBO. OPERATIONALLY_CRITICAL for information that is relevant and critical. Not knowing will likely have a major operational impact up to refusal of service. Performance of a flight might not be possible in all conditions. For example: ILS CAT I inoperative, or JET-A1 fuel not available.
source	string	A description of where this information was originated. For example Airport Authority or Ground Handler or Local news.
category	string	A string that indicates what the Airport Operational Note is about. Possible values are: RUNWAY For runways and other take-off and landing surfaces. AIRLINES_TERMINAL For the terminal building and connected services that are used by scheduled airlines. GENERAL_AVIATION_TERMINAL For the terminal building and connected services that are used by General and Business Aviation. FUEL For all fuel supplies. PARKING For parking availability and restrictions. TAXIWAYS For all taxiways and taxilanes. WEATHER For weather phenomena affecting the airport. PROCEDURES For special or non-standard procedures that are in place at the airport. EVENTS For events affecting airport traffic, such as airshows. COSTS For extraordinary costs that airport users should be aware of. STRIKES For upcoming personnel strikes that might affect airport operations. IMMIGRATION For all airport-specific immigration issues. DELAYS For upcoming events that are expected to bring delays, but are not included in any other more specific category above. RISK For all safety and security risks related to airport operations. RESTRICTIONS For all temporary restrictions that cannot be documented in other parts of the Airport model.
affectedTraffic	list	This object is reserved for future use, and it is currently defaulted to null in all API responses.
notes	string	The text of the information that is to be displayed to the human. For example JET-A1 pressurized refuelling not available
parent	string	The AID of the Airport at which this Operational Note is applicable