We respect the intellectual property rights of others and we ask everyone creating airports using this service to do the same. Your login will identify you as the author of any airport you build using FSCloudPort and of any accompanying description. Do not breach anyone else's copyright when entering an airport description. We recommend Wikipedia as a primary source as well as your own personal knowledge. Do not enter any personally identifiable information or enter anything defamatory or likely to cause offense. Airport descriptions should be written in English and should not include external links.
Airports should exist in the real world so that FSCloudPort can become a useful resource for others. Fictional airports may be supported in the future but are not permitted at present. Moderators will scan airports and may remove any information at their discretion.
No personally identifiable information is stored by this website service. Your IPACS Forum user name and FSCloudPort password are used only for access control and usage statistics. We do not use cookies for any other purpose than access control and we do not share information with third parties. We do use Google Maps to provide a summary view of airports and to power the editor. Google has their own terms and conditions and privacy policy which you should read in addition to these terms. A link to Google’s terms of use is shown at the bottom of every Google Map.
Do not give out your login to others.
The content and works published on this website are governed by the copyright laws of the United Kingdom. Any duplication, processing, distribution or any form of utilisation beyond the scope of copyright law shall require our prior written consent.
By uploading data to this website you agree to our unrestricted use of that data for the purposes of improving or modifying FSCloudPort or for any lawful purpose, including but not limited to additional freeware or commercial services.
Phil Hulme, admin@loudport.com
FSCloudPort was created as a free community service to simplify the process of building airports for the AeroFlyFS2 Flight Simulator and to easily share those airports via the cloud. This guide provides a brief overview. Full documentation can be obtained from the IPACS website. Airport downloads contain only the airport models without scenery or autogen buildings/cultivation. For freeware scenery and cultivation try Freeware Scenery for FS2. Version 1.0 : Released 29th March 2018
There are currently well over 2,000 airports across 100+ countries in FSCloudPort which you can download right now. There is no need for a login to do this, simply click the appropriate country and zoom in to see if a particular airport exists. If it does, click the airport flag and you can instantly download it as a zip file containing everything you need (see limitations below). The download page explains what to download and where to place the files so that the airport is added to FS2. All airports have been created by the user community so airports have been "built" to varying degrees. The simplest airport possible includes a control tower, modelled runway(s) and parking spaces. Once added to FS2, the airport will show up on the navigation screen and it can be flown from though it may not have any airport buildings other than the tower. More built up airports have a darker orange flag and include airport buildings and static aircraft.
There are 3 limitations to be aware of when using airports from FSCloudPort (FSCP).
You need a login to create airports. Prior to public launch airports were created by a small group of IPACS forum members who participated in alpha testing. The current version v1.0 should be considered a beta release and during this phase it is being extended to a maximum of 30 users. This limitation is needed to allow the administrators of FSCP to refine administration procedures especially during this beta phase. To request a login you need to be a member of the IPACS forum and should send a PM to Spit40 including your Steam ID.
IPACS forum members should send a PM to Spit40 including their Steam ID. Accounts will be limited at various stages to ensure the administration workload is manageable. There is a separate tutorial FSCloudPort: Creating Airports available from the IPACS website and a YouTube video Introduction to FSCloudPort.
Bulk download is not currently available. The in-browser ZIP creation technology is not capable of supporting large numbers of airports but other approaches are being worked on.
The current preferred option requires additional (hopefully small) development by IPACS which is under discussion.
The current version does not support these. They are on the list to be added as soon as possible.
The same issue which causes runway cross-over conflicts can also affect runways which are close to each other due to terrain flattening. Until a better solution is implemented the only alternative is to exclude one of the runways by commenting it out in the TSC file.
Please use the IPACS forum Developer Discussions General and Aircraft
This option provides a prototype TSC file, similar to the normal one, to be employed when an experienced user wants to do a 3D modelling of the airport using the appropriate 3D tools.
Please use the IPACS forum Developer Discussions General and Aircraft
FSCP was created by IPACS forum member Spit40.
Created by IPACS forum member Spit40 with substantial assistance from a small group of forum members edpatino, Gooseno1, Ian C, JetJockey10, KJKSimmer, larrylynx, Oldar, pmb, Rodeo and last but far from least TomSimMuc.
The content and works published on this website are governed by the copyright laws of the United Kingdom. Any duplication, processing, distribution or any form of utilisation beyond the scope of copyright law shall require the prior written consent of the author.
No personally identifiable information is stored by this website service. We do not use cookies for any other purpose than access control and we do not share information with third parties. We do use Google Maps to provide a summary view of airports and to power the editor. Google has its own terms and conditions and privacy policy which you should read in addition to these terms. A link to Google’s terms of use is shown at the bottom of every Google Map.
We respect the intellectual property rights of others and we ask everyone using this service to do the same. Anyone who believes that their work has been reproduced in FSCloudPort in a way that constitutes copyright infringement should notify us at the address below.
Phil Hulme (Spit40) admin@cloudport.com
