H2020HORIZONFP7
Centro de Referencia Investigacion Desarrollo e Innovacion Atm, A.I.E.
- Country
- ESSpain
- Defence projects
- 0
- Projects, all programmes
- 70
- As coordinator
- 11
- EU contribution (CORDIS)
- EUR 7,026,287
- Active
- 2009 to 2024
Projects
70 projects, newest first
| Project | Programme | Year | Role | EU contribution |
|---|---|---|---|---|
| PJ13 - W2 ERICAEnable RPAS Insertion in Controlled Airspace | H2020 | 2019 | Third party | Not stated |
| PJ07-W2 OAUOSESAR2020 PJ07-W2 OAUO Optimised Airspace Users Operations | H2020 | 2019 | Third party | Not stated |
| COTTONCapacity Optimisation in TrajecTory-based OperatioNs | H2020 | 2018 | Coordinator | EUR 191,023 |
| SAFEDRONEActivities on drone integration and demonstration in VLL operations | H2020 | 2018 | Participant | EUR 75,339 |
| EVOAtmEvolutionary ATM. A modelling framework to assess the impact of ATM evolutions | H2020 | 2018 | Participant | EUR 149,318 |
| TERRATechnological European Research for RPAS in ATM | H2020 | 2017 | Participant | EUR 113,250 |
| IMPETUSInformation Management Portal to Enable the inTegration of Unmanned Systems | H2020 | 2017 | Coordinator | EUR 180,750 |
| PJ24 NCMPJ24 VLD Network Collaborative Management | H2020 | 2016 | Third party | Not stated |
| PJ08 AAMAdvanced Airspace Management | H2020 | 2016 | Third party | Not stated |
| PJ18 4DTM4D Trajectory Management | H2020 | 2016 | Third party | Not stated |
| PJ10 PROSAController Tools and Team Organisation for the Provision of Separation in Air Traffic Management | H2020 | 2016 | Third party | Not stated |
| PJ27 IOPVLDFlight Object Interoperability VLD Demonstration | H2020 | 2016 | Third party | Not stated |
| PJ07 OAUOPJ07 Optimised Airspace Users Operations | H2020 | 2016 | Third party | Not stated |
| PJ16 CWP HMIController Working Position / Human Machine Interface - CWP/HMI | H2020 | 2016 | Third party | Not stated |
| SafeClouds.euData-driven research addressing aviation safety intelligence | H2020 | 2016 | Participant | EUR 458,625 |
| PJ09 DCBAdvanced DCB | H2020 | 2016 | Third party | Not stated |
| COPTRACOmbining Probable TRAjectories | H2020 | 2016 | Coordinator | EUR 225,225 |
| DARTData-driven AiRcraft Trajectory prediction research | H2020 | 2016 | Participant | EUR 120,500 |
| datACRONBig Data Analytics for Time Critical Mobility Forecasting | H2020 | 2016 | Participant | EUR 311,958 |
| PJ20 AMPLEMaster Plan Maintenance | H2020 | 2016 | Third party | Not stated |
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.