Developing & Operating the Norwegian Airport Network

Air Navigation Services (ANS)

The Air Navigation Services Division is organised into two business areas.

Business Area Air Traffic Management is responsible for providing air traffic services within Norwegian airspace, including designated parts of the North Atlantic airspace. In addition, air traffic services are provided at 21 controlled aerodromes, including Oslo Airport, Norway's main Airport.

The Business Area is divided into 5 Business Units, which also includes the AIM/AIS services and the meteorological services. Air traffic services are provided to both military and civilian operators.

Business Area ATM/CNS Systems is responsible for installation and management of ATM/CNS equipment to the Business Area Air Traffic Management and to 52 aerodromes in Norway.

The Business Area ATM/CNS Systems is divided into tree Business Units, which are ATM/CNS Operations, ATM/CNS System Projects, and ATM/CNS Systems Development & Support.

Avinor's traffic information system (LETIS)

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.