H2020HORIZONFP7
Enav SpA
- Country
- ITItaly
- Defence projects
- 0
- Projects, all programmes
- 59
- As coordinator
- 5
- EU contribution (CORDIS)
- EUR 23,685,316
- Active
- 2009 to 2024
Projects
59 projects, newest first
| Project | Programme | Year | Role | EU contribution |
|---|---|---|---|---|
| PJ38-W3-ADSCENSIOADS-C ENables and Supports Improved ATM Operations | H2020 | 2020 | Participant | EUR 450,000 |
| PJ14-W2 I-CNSSIntegrated Communication, Navigation and Surveillance System | H2020 | 2019 | Participant | EUR 68,935 |
| PJ10-W2 PROSASeparation Management and Controller Tools | H2020 | 2019 | Participant | EUR 665,000 |
| PJ05-W2 DTTPJ05-W2 Digital Technologies for Tower | H2020 | 2019 | Participant | EUR 1,125,667 |
| PJ20-W2 AMPLEPJ.20 W2 Master Planning | H2020 | 2019 | Participant | EUR 110,296 |
| PJ02-W2 AARTAirport airside and runway throughput | H2020 | 2019 | Participant | EUR 997,006 |
| PJ18-W2 4D Skyways4D Skyways | H2020 | 2019 | Participant | EUR 557,844 |
| PJ09-W2 DNMSDigital Network Management Services | H2020 | 2019 | Participant | EUR 565,600 |
| PJ01-W2 EADPJ01 Wave 2 Enhanced Arrivals and Departures | H2020 | 2019 | Participant | EUR 385,000 |
| PJ19-W2 CIPJ.19 W2 Content Integration, Performance Management and Business Case Development | H2020 | 2019 | Participant | EUR 928,250 |
| PJ13 - W2 ERICAEnable RPAS Insertion in Controlled Airspace | H2020 | 2019 | Participant | EUR 457,938 |
| PJ07-W2 OAUOSESAR2020 PJ07-W2 OAUO Optimised Airspace Users Operations | H2020 | 2019 | Participant | EUR 220,593 |
| CORUSConcept of Operations for EuRopean UTM Systems | H2020 | 2017 | Participant | EUR 105,000 |
| PJ08 AAMAdvanced Airspace Management | H2020 | 2016 | Participant | EUR 105,000 |
| PJ18 4DTM4D Trajectory Management | H2020 | 2016 | Participant | EUR 557,970 |
| PJ31 DIGITSInitial Trajectory Information Sharing | H2020 | 2016 | Participant | EUR 452,850 |
| PJ10 PROSAController Tools and Team Organisation for the Provision of Separation in Air Traffic Management | H2020 | 2016 | Participant | EUR 1,558,172 |
| PJ27 IOPVLDFlight Object Interoperability VLD Demonstration | H2020 | 2016 | Participant | EUR 140,973 |
| PJ05 Remote TowerRemote Tower for Multiple Airports | H2020 | 2016 | Participant | EUR 315,000 |
| BLUEGNSSPromoting EGNSS Operational Adoption in BLUEMED FAB | H2020 | 2016 | Coordinator | EUR 893,787 |
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.