H2020HORIZONFP7
Austro Control Osterreichische Gesellschaft Fur Zivilluftfahrt Mbh
- Country
- ATAustria
- Defence projects
- 0
- Projects, all programmes
- 46
- As coordinator
- 0
- EU contribution (CORDIS)
- EUR 3,686,714
- Active
- 2008 to 2024
Projects
46 projects, newest first
| Project | Programme | Year | Role | EU contribution |
|---|---|---|---|---|
| PJ01-W2 EADPJ01 Wave 2 Enhanced Arrivals and Departures | H2020 | 2019 | Participant | EUR 0 |
| PJ19-W2 CIPJ.19 W2 Content Integration, Performance Management and Business Case Development | H2020 | 2019 | Participant | EUR 0 |
| PJ13 - W2 ERICAEnable RPAS Insertion in Controlled Airspace | H2020 | 2019 | Participant | EUR 0 |
| PJ25 XSTREAMCross Border SESAR Trials for Enhanced Arrival Management | H2020 | 2017 | Participant | EUR 0 |
| PNOWWAProbabilistic Nowcasting of Winter Weather for Airports | H2020 | 2016 | Participant | EUR 152,500 |
| PJ24 NCMPJ24 VLD Network Collaborative Management | H2020 | 2016 | Participant | EUR 23,240 |
| PJ18 4DTM4D Trajectory Management | H2020 | 2016 | Participant | EUR 63,269 |
| PJ31 DIGITSInitial Trajectory Information Sharing | H2020 | 2016 | Participant | EUR 0 |
| 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 62,860 |
| PJ27 IOPVLDFlight Object Interoperability VLD Demonstration | H2020 | 2016 | Participant | EUR 7,198 |
| PJ05 Remote TowerRemote Tower for Multiple Airports | H2020 | 2016 | Participant | EUR 150,150 |
| MALORCAMachine Learning of Speech Recognition Models for Controller Assistance | H2020 | 2016 | Participant | EUR 86,563 |
| PJ16 CWP HMIController Working Position / Human Machine Interface - CWP/HMI | H2020 | 2016 | Participant | EUR 122,074 |
| PJ17 SWIM-TISWIM Technical Infrastructure | H2020 | 2016 | Participant | EUR 104,300 |
| PJ09 DCBAdvanced DCB | H2020 | 2016 | Participant | EUR 42,351 |
| PJ01 EADEnhanced Arrivals and Departures | H2020 | 2016 | Participant | EUR 32,936 |
| PJ20 AMPLEMaster Plan Maintenance | H2020 | 2016 | Participant | EUR 32,293 |
| EUNADICS-AVEuropean Natural Airborne Disaster Information and Coordination System for Aviation | H2020 | 2016 | Participant | EUR 165,728 |
| PJ15 COSERCommon Services | H2020 | 2016 | Participant | 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.