Access to EAD

The European AIS Database (EAD) adapts to your needs – and your budget. The page provides all relevant information related to requesting access to and setting up a connection with the EAD.

Access Types

  • EAD Pro (B2C)
    is the ready to run EAD software package that, when installed on a PC, provides you access to all EAD services (SDO, INO, PAMS, BF) via a user-friendly, graphical interface. It can be run on a dedicated terminal (ECIT, EAD Client Interface Terminal), or through a secure internet connection.

    EADPro is subject to a software license and yearly maintenance fee, payable to the EAD IT Service Provider through a dedicated software contract between the client and the IT Service Provider.

    In case you have already an EAD Pro account, you can logon to the application using your EAD UserID: www.ead.eurocontrol.int
  • MyEAD (EAD B2B)
    is interface to establish a system-to-system connection to the EAD. MyEAD can be either an API based EAD System Interface (ESI) or can be based on Web services (AIMSL). This is the solution if you have an existing system into which you would like to embed data directly. All necessary technical documentation and software packages is available once the EAD Agreement for Data Users has been signed.
  • Data Download
    enables the user to retrieve a dedicated data set at intervals (e.g. AIRAC cycle) from the EAD that can then be manually inserted/loaded into a local system. This is the solution if a continuous connection with the database is not required and only updates are needed when there are data changes. Data files are made available through the EAD Internet Filing System (EAD IFS).
  • AFTN
    if needed, NOTAM information contained in the EAD can also be made available through regular AFTN connection.
  • EAD Basic
    EAD Basic is the EAD general access for private pilots, general aviation, training schools and any member of the public searching for aeronautical information. Access can be obtained from: www.ead.eurocontrol.int

Charges

  • Client Types
    Depending on the type of client, different charges will be applied. These charges can be Service Charges, applied by EURCONTROL and, in cases where EAD data is made available by the Client to third party end-users, Royalty Fees as applied by the Member States. The table below shows the possible client types and which charges are being applied.
  Service
Charges
Royalty
Fees
Type 1
Clients that are acting on behalf of a EUROCONTROL member state
Clients that are recognized airspace users paying en-route charges
No No
Type 2
Clients using the data for their own operational business without reselling and/or commercialising it, but which do not contribute to EUROCONTROL budget or are not recognised airspace users.
Yes No
Type 3
Clients that intend to commercialize the data with or without value added products and make data available to third party end-users.
Yes Yes
  • Level of charges applied
    The level of charges applied for the use of EAD data is based on how and where the data will be used, as well as the related turnover (in €/year) of the product or service in question that makes use of EAD data. This method ensures that all users pay charges commensurate with the size of their business.
    The amount of charges will be determined during the agreement discussion and clients will be asked to produce the related turnover evidence.

Registration

Clients who want to connect to the EAD, shall complete the online “Service Request Form”. This is the formal expressing of interest and allows to indicate the required services (INO, SDO, PAMS) as well as which type of access will be required.
In the shortest delay possible, the client will then be contacted to confirm the interest, followed by the start the agreement discussion.

EAD Service Request Form

EAD Agreement

  • EAD Agreement
    Prior to any connection with the EAD, the EAD Agreement for Data Users must be concluded between the client and EUROCONTROL. The agreement outlines the responsibilities and obligations of both parties as well as the charges that will be applied and the level of liability insurance needed.

    When Service Request Form has been received, the EAD will send the first draft of the agreement to the client, marking the start of the agreement discussion. When the discussion is concluded the successfully, the client will receive 2 signed paper copies with the request for countersigning. As soon as the counter signed agreement has been received, the technical implementation phase can start.

Implementation

  • Technical Implementation

    Once the agreement is concluded the technical implementation phase can start. Clients having chosen the MyEAD (EAD B2B) solution will at this point be given access to the technical library allowing them to download all related documentation. The pre-requisite for this access is to have a user account at EUROCONTROL’s Extranet “OneSky Oneline”

    OneSky Online Extranet

    In addition to this, the client will be contacted by the EAD Migration Manager who will be the client’s counterpart for all technical matters related to network requirements, available interfaces (B2B, B2C, etc.). The EAD Migration Manager also deals will all request related to the purchase of the EAD Pro software (B2C) and related software licenses.

    At this point the client will receive access to the EAD Service Desk, allowing them to request support in case needed.

    Client training requirements will be re-directed to the EAD Training Manager for further coordination with the client.

     
  • Start of Operations
    As soon as the Client’s interface has been tested, validated and approved, in case of MyEAD, a Technical Acceptance Decision will be issued. This is the formal indication that the Client is ready to connect to the EAD Operational Systems after which they are handed over to the Operational team.

    The Technical Acceptance Decision for EAD Pro users will be issued at the moment the software package has been installed and is functional. Also EAD Pro users will from this points on be able to retrieve data from the EAD Operational environment.
Tagged under: