FS2004 AFCAD file

FS2004 AFCAD For Aerosoft LTU2001

AFCAD2 layout for Aerosoft’s LTU2001 Düsseldorf EDDL scenery assigns real-world terminal gate numbers and airline parking, with extra tarmac stands to handle overflow traffic. Built for FS2004: A Century of Flight, it matches the jetway numbering shown in the scenery and uses airport-based gate allocations; requires Aerosoft LTU2001 EDDL.

73 downloads 9.99 KB Scanned clean

Microsoft Flight Simulator 2004

An AFCAD2 file only for use with Aerosoft's LTU2001 Dusseldorf (EDDL), Germany, scenery. All terminal gates assigned plus some tarmac gates for overflow traffic. All assignments use real numbers. By Michael Theisen.

For use with FS2004 a century of flight only!

I made this AFCAD as real as possible however now gate numbering at Dusseldorf has changed but I used those visible on the jetways in the scenery. All gates at the terminals are assigned to the airliners which use them as per the airport's website information. Other parkings on the tarmac are not assigned and are for overflow traffic.

Installation:

Simply copy the file and paste into your FS2004\AddOn Scenery\Scenery folder. To uninstall, simply remove from the above folder.

Ready to download AFCAD For Aerosoft LTU2001?

Free for all simmers · 9.99 KB · Scanned clean

File information

Filename

ltu2001.zip

File size

9.99 KB

Virus scan

Clean (scanned with ClamAV)

Access

Freeware

Content rating

Everyone

Download speed: Free tier is capped at 0.5 Mbps. PRO members download at full line speed.

This is a freeware file — use is subject to our freeware copyright terms.

How to install this mod

FS2004 AFCAD file

Extract the downloaded archive

Use 7-Zip (free) or WinRAR to extract the ZIP to a temporary folder. Don't install while still zipped — the simulator can't read inside ZIP files.
Place files per readme

FS2004 add-ons go into FS9\Aircraft\, FS9\Addon Scenery\, FS9\Gauges\, or FS9\Effects\.
Always read the included readme

Every mod ships with a readme.txt or README file. It tells you exactly where files go, what dependencies are needed, and any quirks specific to this add-on.