H2020HORIZONFP7
Eurocontrol - European Organisation for the Safety of Air Navigation
- Country
- BEBelgium
- Defence projects
- 0
- Projects, all programmes
- 140
- As coordinator
- 30
- EU contribution (CORDIS)
- EUR 7,536,860
- Active
- 2008 to 2025
Projects
140 projects, newest first
| Project | Programme | Year | Role | EU contribution |
|---|---|---|---|---|
| CAMERACoordination and support Action for Mobility in Europe: Research and Assessment | H2020 | 2017 | Participant | EUR 0 |
| ICAReInternational Cooperation in Aviation Research | H2020 | 2017 | Participant | EUR 55,294 |
| PJ24 NCMPJ24 VLD Network Collaborative Management | H2020 | 2016 | Coordinator | EUR 640,816 |
| PJ08 AAMAdvanced Airspace Management | H2020 | 2016 | Coordinator | EUR 0 |
| PJ18 4DTM4D Trajectory Management | H2020 | 2016 | Participant | EUR 1,281,831 |
| PJ31 DIGITSInitial Trajectory Information Sharing | H2020 | 2016 | Participant | EUR 1,164,100 |
| PJ14 EECNSEssential and Efficient Communication Navigation and Surveillance Integrated System | H2020 | 2016 | Participant | EUR 0 |
| PJ10 PROSAController Tools and Team Organisation for the Provision of Separation in Air Traffic Management | H2020 | 2016 | Participant | EUR 0 |
| PJ27 IOPVLDFlight Object Interoperability VLD Demonstration | H2020 | 2016 | Participant | EUR 221,667 |
| PJ05 Remote TowerRemote Tower for Multiple Airports | H2020 | 2016 | Participant | EUR 0 |
| BESTAchieving the BEnefits of SWIM by making smart use of Semantic Technologies | H2020 | 2016 | Participant | EUR 0 |
| PJ07 OAUOPJ07 Optimised Airspace Users Operations | H2020 | 2016 | Coordinator | EUR 0 |
| PJ16 CWP HMIController Working Position / Human Machine Interface - CWP/HMI | H2020 | 2016 | Participant | EUR 0 |
| STRESSHuman Performance neurometricS Toolbox foR highly automatEd Systems deSign | H2020 | 2016 | Participant | EUR 0 |
| PJ03b SAFEAirport Safety Nets | H2020 | 2016 | Participant | EUR 0 |
| PJ11 CAPITOEnhanced Air and Ground Safety Nets | H2020 | 2016 | Coordinator | EUR 0 |
| PJ22 SEabirdPJ22:Validation and Demonstration Engineering | H2020 | 2016 | Participant | EUR 0 |
| PJ17 SWIM-TISWIM Technical Infrastructure | H2020 | 2016 | Participant | EUR 0 |
| SafeClouds.euData-driven research addressing aviation safety intelligence | H2020 | 2016 | Participant | EUR 435,891 |
| PJ09 DCBAdvanced DCB | H2020 | 2016 | Coordinator | EUR 0 |
The country is the one the source records for the organisation’s registration (its PIC), and each profile says what it rests on. Where the record contradicts itself (the address in one country, the site name and the VAT number in another) we follow the two that agree: the Spanish research council CSIC is shown under Spain although its address is recorded in Italy. A body with sites in several countries is shown under the first of them in alphabetical order, and its profile lists the others. Beyond that we do not guess.
Where this comes from
- CORDIS: EU research projects (Horizon Europe, Horizon 2020, FP7)Last read on . Licence: Commission Decision 2011/833/EU (reuse of Commission documents). Source: CORDIS, European Commission.Participants and amounts as the Commission's CORDIS database states them (reuse under Commission Decision 2011/833/EU).
EU contribution is the amount CORDIS's open data pays to the participant. For a participant with linked third parties it may include their share (the CORDIS page prints the net); an amount the data does not hold is left out, not counted as zero. EDF factsheets state none per participant, so EDF projects count as projects but add nothing to the amounts.
Organisation-level facts only: a name, a country, a role, an amount, a year. A participant is recognised by its PIC where the source gives one, otherwise by name; the page says which. How the data is built.
Names are as CORDIS and the EDF project factsheets publish them. We do not list an organisation whose name looks like a natural person’s. If this entry is you, or a business named after you, and you want it removed, write to the contact in the imprint; the privacy notice (sections 7 and 9) says how a request is handled.