H2020HORIZON
Luftfartsverket
- Country
- SESweden
- Defence projects
- 0
- Projects, all programmes
- 49
- As coordinator
- 0
- EU contribution (CORDIS)
- EUR 13,458,923
- Active
- 2016 to 2023
Projects
49 projects, newest first
| Project | Programme | Year | Role | EU contribution |
|---|---|---|---|---|
| PJ05-W2 DTTPJ05-W2 Digital Technologies for Tower | H2020 | 2019 | Participant | EUR 475,762 |
| PJ20-W2 AMPLEPJ.20 W2 Master Planning | H2020 | 2019 | Participant | EUR 114,071 |
| PJ04-W2 TAMPJ04 W2 Total Airport Management | H2020 | 2019 | Participant | EUR 42,000 |
| PJ02-W2 AARTAirport airside and runway throughput | H2020 | 2019 | Participant | EUR 589,873 |
| PJ18-W2 4D Skyways4D Skyways | H2020 | 2019 | Participant | EUR 293,600 |
| PJ09-W2 DNMSDigital Network Management Services | H2020 | 2019 | Participant | EUR 35,000 |
| PJ01-W2 EADPJ01 Wave 2 Enhanced Arrivals and Departures | H2020 | 2019 | Participant | EUR 590,086 |
| PJ19-W2 CIPJ.19 W2 Content Integration, Performance Management and Business Case Development | H2020 | 2019 | Participant | EUR 63,000 |
| PJ13 - W2 ERICAEnable RPAS Insertion in Controlled Airspace | H2020 | 2019 | Participant | EUR 333,171 |
| PJ25 XSTREAMCross Border SESAR Trials for Enhanced Arrival Management | H2020 | 2017 | Participant | EUR 83,265 |
| PJ24 NCMPJ24 VLD Network Collaborative Management | H2020 | 2016 | Participant | EUR 0 |
| PJ18 4DTM4D Trajectory Management | H2020 | 2016 | Participant | EUR 121,223 |
| PJ31 DIGITSInitial Trajectory Information Sharing | H2020 | 2016 | Participant | EUR 67,375 |
| 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 662,217 |
| PJ27 IOPVLDFlight Object Interoperability VLD Demonstration | H2020 | 2016 | Participant | EUR 31,766 |
| PJ05 Remote TowerRemote Tower for Multiple Airports | H2020 | 2016 | Participant | EUR 1,992,700 |
| PJ16 CWP HMIController Working Position / Human Machine Interface - CWP/HMI | H2020 | 2016 | Participant | EUR 152,215 |
| PJ17 SWIM-TISWIM Technical Infrastructure | H2020 | 2016 | Participant | EUR 0 |
| SafeClouds.euData-driven research addressing aviation safety intelligence | H2020 | 2016 | Participant | EUR 357,500 |
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.