Traffic information is important to both passengers and other parties at the airport. Traffic information at Avinor contains a variety of data on all commercial flights in Norway, as well as flights to and from Norway, e.g. scheduled flights, charter flights, cargo and mail flights and helicopter traffic.
LETIS: Areas of use
Avinor’s traffic information system is called LETIS and is used as the data basis in a number of areas:
Information screens, boards and IT systems at all Norwegian airports (except Rygge)
avinor.no, m.avinor.no
Baggage systems at all Norwegian airports
Air traffic control systems at some Norwegian airports
Various external websites
Systems for de-icing, fuelling, catering and cleaning
Duty invoicing systems in Avinor
Statistics and reports at Avinor, Statistics Norway and Eurostat
Distribution to external parties with connections to Norwegian airports
LETIS: Responsibility and terms
LETIS was created in cooperation with a number of Norwegian airlines and parties. The distribution of responsibility was then as it is now:
The airlines are responsible for reporting updated data to LETIS at the correct time and in the correct format and for ensuring that the content is correct.
Avinor is responsible for reading and processing received notifications, as well as for administering and operating the system’s infrastructure and functionality. Avinor is also responsible for LETIS support and helpdesk, as well as short- and long-term administration.
In the regulations relating to fees concerning government aviation facilities and services Section 3-6, it is stated which type of notifications owners or users of aircraft are responsible for providing to LETIS. The regulations are published by the Ministry of Transport and Communications and are updated once yearly. The latest version is available at lovdata.no.
In Norway, all traffic information notifications must comply with standards defined by the International Air Transport Association (IATA). The formats are provided in publications every year, some of them twice yearly. The notification types that are used in Norway are defined in IATA Standard Schedules Information Manual and in IATA Airport Handling Manual. The airlines are themselves responsible for ensuring that the notifications they submit are correct. Updated manuals may be ordered from iata.org.
LETIS: Structure
At the top level LETIS consists of a central database that contains aircraft data for the upcoming and current seasons. In addition there are local databases at 14 airports, which contain data for the upcoming week, that are continually updated with updated data from the central database.
Data for local use, e.g. for information screens and boards, is retrieved from the local database, while data for more general purposes is retrieved from the central database. Some data is synchronized between the central and local databases.
All updates must be submitted to the central LETIS database, via the SITA network, to the SITA address OSLNOYA. Direct updates from local databases should only occur in exceptional circumstances and in case of system faults. Avinor does not continuously monitor or control the quality of received IATA notifications, and it is therefore always the submitter who is responsible for the reliability of the data.
Updates that are submitted to OSLNOYA and which apply to the current week, are immediately distributed to the local databases. Other updates are saved at OSLNOYA for subsequent distribution.
LETIS relates primarily to IATA standards, which entails that data cannot be submitted to the system unless it complies with the standards. IATA has defined a large number of notification formats, and the following are used in Norway:
SSIM, for reporting of complete season plans. Should be used at least 3 weeks before season changes.
SSM, for permanent additions or changes to season plans. Should be used at least 24 hours before departure.
ASM, for temporary/time-limited additions to or deviations from the original season plan. Should be used at least 6 hours before departure.
MVT, for reporting of estimated and actual departure and arrival times and delays. Ongoing.
MVA, for reporting of estimated and actual departure and arrival times and delays. Sent directly from individual aircraft, e.g. via ACARS. Ongoing.
DIV, for reporting of “diversions” from the original flight route. Ongoing.
LDM, for reporting of passenger numbers and weight. Should be reported at the latest 12 hours after departure.
