Presents - BluePrint Simulationsthe US such as KIAD and KATL, DIA’s terminal consists of three remote concourses connected to each other and to the main terminal via an underground

OnDuty Support Systems LLC. 2007 - 2014 All rights reserved. 1

Presents

http://www.blueprintsimulations.com/



Contents Scenery Description Scenery Features Software Compatibility Suggested Hardware Configuration Installation Instructions Parking spot configuration and airline gate assignments Technical support and contact information Scenery fixes and upgrades Acknowledgements

Scenery Description Denver International (DIA) is the last major airport built from the ground up in the United States, replacing the aging Stapleton airport on February 28, 1995. By surface area, DIA is one of the largest facilities of its kind in the world. It was designed to facilitate and expedite aircraft traffic flow on the ground and in the air thanks to a unique set of runways made possible by the sparse population in the plains just east of the city of Denver. KDEN’s six runways are arranged to enable no less than three simultaneous approaches during reduced visibility conditions regardless of prevailing winds and to practically eliminate runway crossings during taxiing to and from the terminal and other general aviation and cargo facilities. It also features the longest runway of any civilian airport in the US which, at 16,000 ft., enables fully-loaded, large aircraft to take off for long-haul flights from Denver’s 5400 ft. elevation. DIA’s most distinctive feature is the main terminal with its iconic white roof designed to mimic the snow-caped peaks of the Rocky Mountains to the west. Adopting the practical and efficient design typical of newer airports in the US such as KIAD and KATL, DIA’s terminal consists of three remote concourses connected to each other and to the main terminal via an underground tram. This configuration now used in almost every major airport in the world maximizes the number of gates that can be accommodated around each concourse while enabling unrestricted flow of aircraft between them. In addition, the concourses’ modular design will enable easy and affordable growth to accommodate the increasing traffic expected for this centrally-located airport that also serves one of the fastest growing metropolitan areas in the country. BluePrint Simulations’ Denver International airport scenery depicts the airport as it exists in the fall of 2013 and features highly detailed, full-3D models (BluePrint’s True3D) of the main terminal and three concourses including the ATC tower. It also includes all cargo, general aviation and maintenance facilities within the airport boundaries, all aircraft maintenance and storage hangars being fully three-dimensional and usable. All 3D models feature custom-made, high-resolution (32 px/meter) textures including transparency and reflection effects. The scenery also includes every gate available at each of the three concourses. Each gate is accurately numbered and equipped with a static jetway configured and branded to match current gate usage by every airline serving DIA. Each aircraft parking position is located as accurately as possible based on current satellite imagery of the airport and features realistic ramp markings, illumination effects and a basic parking alignment aid. A set of optional static service vehicles is also included for every gate. An advanced mapping file (AFCAD) enables realistic AI traffic operations.


BluePrint’s KDEN scenery also depicts the runway and taxiway complex superimposed on a set of high-resolution, custom-made terrain textures positioned as accurately as it is possible in the flight simulator environment to match official FAA charts and publications. The terrain textures depict seasonal changes and are painstakingly blended with the surrounding terrain to provide a realistic experience during flight in the vicinity of the airport. Runways and taxiways feature accurately placed signs and markings as well as hold-short signs and lighting at every relevant intersection.

Scenery Features

Custom-made, optimized and fully three-dimensional Gmax models of the entire facility including:

o The main terminal and three concourses o The ATC tower o Accurately located aircraft parking positions around every terminal and

individually customized static jetways at every gate. Static service vehicles (optional) and parking alignment aids at every gate

o All parking structures adjacent to the terminal o A significant fraction of the general aviation, aircraft maintenance and cargo

facilities within the field’s boundary o Approach lighting fixtures and navigation aid antennae for every runway.

Custom-made, high-resolution (32 px/meter) textures for all Gmax generated models including transparency effects

Custom-made, high-resolution photo real ground textures depicting seasonal changes and carefully blended with the surrounding terrain

Accurate runway and taxiway layout, including detailed markings and signs

Realistic taxiway and ramp markings and ramp illumination effects

Two levels of scenery complexity and detail: o NORMAL complexity includes terrain texturing, autogen vegetation, airport layout

with taxiway signs and basic navigation equipment models (actual localizer and glide slope radio signals are available regardless of the scenery complexity setting), and most buildings within the field’s boundaries including the terminals, the air traffic control tower and cargo and maintenance facilities

o VERY DENSE complexity adds detailed instrument approach lighting system models, animated runway intersection lighting, gate parking position alignment aids and static ramp vehicles (optional).

Advanced, custom-made AI mapping file (AFCAD) including realistic gate and parking spot layout as well as airline gate assignments. A basic AI mapping file without gate assignments is also available as an option.

Software Compatibility FS2004 (FS9) and Windows XP, Vista, 7 or 8 (All versions) Note: A FSX compatible version is available and sold separately. Please visit our web site for additional information.




Minimum Hardware Configuration BluePrint sceneries are designed to work properly in the average computer at the time of each release. For optimum performance while taking advantage of most scenery features we suggest the following hardware configuration:

Intel Core Quad CPU or better (Q9300 @ 4 x 2.50 GHz fully tested)

4 GB RAM (fully tested) nVidia 8000 series video processor with 256-bit memory interface and 512 MB dedicated video memory or better (nVidia GeForce 8800 GT fully tested). nVidia 9000 series video processor and 1 GB dedicated memory may be required for best performance when using the VERY_DENSE scenery complexity setting (nVidia GeForce 9800 GT fully tested).

Installation Instructions

1. Download the installer and save it in any folder of your choice. The installer is a file labeled KDENv1.1.1.exe.

2. Double click on the file labeled KDENv1.1.1.exe to run the scenery installer. 3. Please read carefully and make sure that you understand all the terms of the End User

License Agreement (EULA) before continuing with the installation. 4. Select the folder where the scenery will be located. The installer will search your

computer registry for the location of the Microsoft Flight Simulator and suggest a path to a folder to be created inside the folder containing the simulator’s files in your hard drive. IMPORTANT: If for any reason the installer fails to locate a valid registry entry for the simulator it will suggest a path to a folder to be created inside the folder where the simulator files should be located if the default path was used during the simulator’s installation. In this case, however, the suggested location for the scenery files provided by the installer may not be adequate for your FS2004 installation and you must enter a valid path before proceeding with the installation process. You may choose any installation path at this point as long as you are able to locate the folder containing the scenery files in order to add the scenery to the simulator’s scenery library as explained below.

5. Complete the installation by following the onscreen instructions.

Add the KDEN to FS2004’s scenery library as follows: 6. Run the Flight Simulator 7. Upon starting the flight simulator the following window should open:


8. If you have setup your simulator to skip this window at start up, you can reach it as

follows:

Press the “Esc” key or from the main menu bar, under “Flights” select “End Flight”.

Confirm “End Flight” on the next window:

Now select “Settings” on the window shown in the previous step. The following window should open:


9. Select Scenery Library … The following window should open:


10. Select Add Area … 11. Navigate to the “FS9_root_directory”\BluePrint Simulations\ directory. . In a default

installation, the KDEN scenery folder is located at: o C:\Program Files\Microsoft Games\Flight Simulator 9\BluePrint Simulations in a

32-bit version of windows or o C:\Program Files (x86)\Microsoft Games\Flight Simulator 9\BluePrint Simulations

in a 64-bit version of Windows. If you specified a different directory during installation of FS or the BluePrint scenery, please navigate to the directory you specified to find the scenery files.

12. Select the KDEN folder (Select only, do not “double click”) 13. Press OK 14. The KDEN directory should appear at the top in the Scenery Area list shown in the

following image: (KCLE is used in this image as an example. KDEN should appear at the top instead).

Note: the scenery may be moved down on the list. You must ensure, however, that it is located above any other add-on that may affect in any way the scenery and/or terrain at KDEN’s location or its immediate vicinity (This includes regional or global terrain add-ons).

15. Press OK and restart the Flight Simulator

In some instances, an incompatibility issue between FS2004 and Windows 7 or 8 prevents the user from adding new sceneries to the FS2004 library using the standard procedure. Please visit the FAQ section of our web site for the latest information regarding the addition of new sceneries to the FS2004 library when running the Windows 7 or 8 operating systems.


Please note that detailed instructions for adding KDEN to FS2004’s scenery library may also be found in the simulator’s help menu.


Parking Spot Configuration and Airline Gate Assignments As a fundamental rule, we seek to represent the airport as closely as possible to real life using every resource available in the flight simulator. By default our sceneries are configured to handle ATC operations and AI traffic as realistically as possible based on direct observation and/or airline gate assignment information available to the public via the airport’s official website. Consequently, aircraft parking spots are configured to accommodate specific aircraft types according to the actual gate configuration and the airline and aircraft type that use that gate most often in real life. In order to ensure proper ATC and AI traffic operations you must take care of a few items that we consider and assume to be simple and basic knowledge for any user interested in our high-performance sceneries. If you are interested in AI traffic and realistic ATC operations you must ensure that your aircraft, be it the one you are flying or any AI traffic, is properly formatted as described below. MSFS’s parking spot configuration is based on the aircraft’s wingspan and the location of its center of gravity (or C.G.) as specified in each individual aircraft model. The model refers to the simulated aircraft (i.e. MSFS’s default B747-400) as opposed to the aircraft in real life! Consequently, proper handling of an aircraft by the AI traffic engine will depend on the proper configuration of the aircraft model by each individual flight simulator aircraft designer. The wingspan and C.G. location parameters are not easily accessible to the user so we must rely on the aircraft designer to accomplish the task properly. Improperly formatted aircraft models are simply not supported by our sceneries. As scenery designers we do have access to the parking spot configuration and we are not only able but required to set at least four parameters: location as lat/lon coordinates, heading, radius and type. We are also given the option to specify a few other parameters including airline, and pushback direction preference. The values assigned to each parameter will determine the way any given aircraft will be handled by the simulator air traffic control engine. There is no way at this point to instruct the traffic engine to park or direct any given aircraft to any specific parking spot (or gate). All we can do is set parking spot parameters to provide the traffic engine with a basic set of rules to follow. Assuming that the aircraft models are properly formatted, the simulator’s AI traffic engine will accommodate AI aircraft in the available parking spots according to the parameters mentioned in the previous paragraph. The most basic parameters that we must consider are the location and heading. While heading is straightforward and simple to understand, location is not. The location of a parking spot is defined by a set of latitude/longitude coordinates. It is essential to understand that all the simulator’s traffic engine can do is position aircraft that geographic location using one single point in the aircraft visual model as a reference. That point happens to be the C.G. It is also important to understand that the location of the front gear, the point actually used in real life to park an aircraft at the gate, is essentially irrelevant. The next parameter to be considered is the parking spot radius. For any given parking spot, this parameter defines the maximum size of the aircraft that will be parked at that spot by defining a circular area around the parking spot location as defined above. All the simulator’s traffic engine knows is that the aircraft must fit within that circular area using the model’s wingspan as a reference. It is important to understand that this parameter only sets a restriction on the maximum size of the aircraft that will fit on a given spot. It sets no restrictions on the minimum size at all.


As all aircraft types and models have different wingspans and C.G . locations, not all aircraft will fit perfectly in each parking spot. For example, a Boeing 737 aircraft may not fit perfectly in a parking spot configured to fit a Boeing 777 aircraft. The front gear on a B777 is much further away from its C.G. than that of a B737 is from its own C.G. Nonetheless, the simulator’s AI traffic engine may park a B737 aircraft in a parking spot configured for a B777 aircraft and it will not account for the need to move the B737 forward so that its front wheels end up at the same location where the B777’s front wheels would be as it is done in real life. The bottom line is that by properly formatting the parking spot radius all we can do is prevent the simulator’s traffic engine from parking a B777 aircraft in a parking spot that will only fit a B737 or smaller aircraft because otherwise it would end up impelled in the terminal building or its wing will crash with the aircraft parked in the adjacent gate. This is particularly important when, as in real life, some parking spots are designed and configured to fit only smaller aircraft. In our effort to represent the airport as it is in real life we have also chosen to assign specific airlines to each terminal gate by setting the optional parameter mentioned above. Detailed information about the gate assignments is provided below. The option to disregard airline gate assignments is now provided during installation of our sceneries. Please note that for a given aircraft to be directed toward or parked at a gate assigned to a specific airline the aircraft must be properly formatted. There are two parameters that must be configured within the “aircraft.cfg” file associated with each flyable or AI traffic aircraft. It is not enough that the aircraft is labeled according to the corresponding airline texture applied to each instance of a given aircraft model. You must make sure that the aircraft designer has properly formatted those two parameters for each texture associated with a given aircraft model or you must add those parameters to the aircraft.cfg file yourself. This can easily be accomplished by editing the aircraft.cfg file using a text editor such as “Window’s Notepad”. The two parameters are: A parameter that defines the type of parking spot to be used. Values may be GATE for passenger terminal gates, CARGO for cargo ramp parking spots and MILITARY for military ramp parking spots and RAMP for general aviation ramp parking spots. A parameter that specifies the airline such that the AI traffic engine can identify it. Consequently, each instance of a given aircraft as defined in the aircraft.cfg file must contain these two lines: atc_parking_types= atc_parking_codes= The following fictitious example corresponds to a properly formatted MSFS default 737-400 aircraft displaying textures representing the “Southwest Airlines” livery [fltsim.0] title=Boeing 737-400 Southwest Airlines sim=Boeing737-400 model= panel= sound= texture=SWA kb_checklists=Boeing737-400_check kb_reference=Boeing737-400_ref ui_manufacturer=Boeing


ui_type="737-400" ui_variation="Southwest Airlines" atc_id=N737 atc_airline=SOUTHWEST atc_flight_number=1123 atc_parking_types=GATE atc_parking_codes=SWA description="One should hardly …" Note: parameters labeled ui_ correspond to the User Interface only (i.e. to be used in the aircraft menu) while those labeled atc_ correspond to parameters to be used by the ATC and the AI traffic engine to properly identify and handle the aircraft. If the two parameters mentioned above have not been properly configured or are missing, which is the most common occurrence unless the user has manually modified the file, the AI traffic engine will not know the intended parking spot type and corresponding airline associated with the aircraft. On the other hand, If the aircraft is properly formatted as shown in the example above, the aircraft will be swiftly and efficiently directed toward a passenger terminal gate that has been configured for a B737-400 or smaller aircraft and that has been assigned to “Southwest Airlines”. Unless the option to disregard airline assignments is selected during installation, there are very few unassigned parking spots available for the AI traffic engine to use in our sceneries. Consequently, this option should be selected unless care has been taken either by the manufacturers or by you to properly format the aircraft.cfg file for the aircraft that you intend fly or use as AI traffic


Concourse A

Gate Maximum

Aircraft Wingspan (ft)

Airline Gate Assignment

(ICAO Codes) Typical Aircraft

Maximum AI Aircraft

Wingspan (ft) AI Aircraft Parking Type

A1 - 23 N/A N/A N/A N/A N/A

A24 120 FFT A319/A320 120 GATE

A25 120 FFT A319/A320 120 GATE

A26 120 FFT A319/A320 120 GATE

A27 120 FFT A319/A320 120 GATE

A28 120 FFT A319/A320 120 GATE

A29 120 FFT A319/A320 120 GATE

A30 120 FFT A319/A320 120 GATE

A31 120 FFT A319/A320 120 GATE

A32 120 FFT A319/A320 120 GATE

A33 120 VOI A320 120 GATE

A34 120 FFT A319, A320 120 GATE

A35 120 JBU, VOI A320 120 GATE

A36 120 FFT A319, A320 120 GATE

A37 200 BAW B772 200 GATE

A38 120 FFT A319, A320 120 GATE

A39 130 ICE B752 130 GATE

A40 120 FFT A319, A320 120 GATE

A41 220 ACA, AMX, DLH,

ICE E190, B738, B752,

B744 220 GATE

A42 120 FFT A319, A320 120 GATE

A43* 120 ACA, AMX E190, B738 N/A GATE

A44 120 NKS A319, A320 120 GATE

A45 130 AAL, EGF A319, MD80, B738,

B752, CRJ7 130 GATE

A46 120 N/A A319, A320, B737,

B738 120 GATE

A47 120 AAL, EGF A319, MD80, B738,

CRJ7 120 GATE

A48 120 TRS, SWA B737, B738 120 GATE

A49 120 AAL, EGF A319, MD80, B738,

CRJ7 120 GATE

A50 120 TRS, SWA B737, B738 120 GATE

A51 120 AAL, EGF A319, MD80, B738,

CRJ7 120 GATE

A52 120 ASA B738 120 GATE

A53 120 AAL, EGF A319, MD80, B738,

CRJ7 120 GATE

A54 N/A N/A N/A N/A N/A

A55 65 GLA B190, E120 65 GATE

A56 100 FFT DH8D 100 GATE

A57 65 GLA B190, E120 65 GATE


A59 65 GLA B190, E120 65 GATE



A61 65 GLA B190, E120 65 GATE


A63 65 GLA B190, E120 65 GATE




AE1** 120 FFT A319, A320 120 GATE

AE2** 120 FFT A319, A320 120 GATE

AE3** N/A N/A N/A N/A N/A

AE4** 120 FFT A319, A320 120 GATE

AE5** 120 FFT A319, A320 120 GATE

AE6** 120 FFT A319, A320 120 GATE

AE7** 120 FFT A319, A320 120 GATE

AE8** N/A N/A N/A N/A N/A

AE9** 120 FFT A319, A320 120 GATE

* Gates blocked when adjacent gate is occupied by heavy. Not inlcuded in AFCAD file. ** Remote stands


Concourse B

Gate

Maximum Aircraft

Wingspan (ft)



Maximum AI Aircraft


B1 - B14 N/A N/A N/A N/A N/A

B15 130 AWE A320, A321 130 GATE

B16 130 UAL A319, A320, B737, B738,

B739, B752, B753 130 GATE

B17 130 AWE A320, A321 130 GATE

B18 130 UAL A319, A320, B737, B738,

B739, B752, B753 130 GATE

B19 N/A N/A N/A N/A N/A

B20 130 UAL A319, A320, B737, B738,

B739, B752, B753 130 GATE

B21 180 UAL A319, A320, B737, B738, B739, B752, B753, B763

180 GATE

B22 130 UAL A319, A320, B737, B738,

B739, B752, B753 130 GATE

B23 120 UAL A319, A320, B737, B738,

B739, B752, B753 130 GATE

B24 130 UAL A319, A320, B737, B738,

B739, B752, B753 130 GATE

B25 130 UAL A319, A320, B737, B738,

B739, B752, B753 130 GATE

B26 130 UAL A319, A320, B737, B738,

B739, B752, B753 130 GATE

B27 130 UAL A319, A320, B737, B738,

B739, B752, B753 130 GATE

B28 130 UAL A319, A320, B737, B738,

B739, B752, B753 130 GATE

B29 130 UAL A319, A320, B737, B738,

B739, B752, B753 130 GATE


B31 130 UAL A319, A320, B737, B738,

B739, B752, B753 130 GATE

B32 220 UAL A319, A320, B737, B738, B739, B752, B753, B763,

B772, B744, B788 220 GATE

B33 130 UAL A319, A320, B737, B738,

B739, B752, B753 130 GATE


B35 200 UAL A319, A320, B737, B738, B739, B752, B753, B763,

B772, B788 200 GATE

B36 220 UAL A319, A320, B737, B738, B739, B752, B753, B763,

B772, B744, B788 220 GATE

B37* 130 UAL A319, A320, B737, B738,

B739, B752, B753 N/A GATE

B38 220 UAL A319, A320, B737, B738, 220 GATE


B739, B752, B753, B763, B772, B744, B788

B39 130 130 UAL

A319, A320, B737, B738, B739, B752,

B753

130


B41 130 130 UAL

A319, A320, B737, B738, B739, B752,

B753

130

B42 220 UAL A319, A320, B737, B738, B739, B752, B753, B763,

B772, B744, B788 220 GATE

B43 130 UAL A319, A320, B737, B738,

B739, B752, B753 130 GATE

B44 130 UAL A319, A320, B737, B738,

B739, B752, B753 130 GATE

B45 130 UAL A319, A320, B737, B738,

B739, B752, B753 130 GATE

B46 130 UAL A319, A320, B737, B738,

B739, B752, B753 130 GATE

B47 130 UAL A319, A320, B737, B738,

B739, B752, B753 130 GATE

B48 130 UAL A319, A320, B737, B738,

B739, B752, B753 130 GATE

B49 100 UAL, ASQ, GJS,

RPA, SKW

CRJ, CRJ2, CRJ7, CRJ9,DH8D, E120,E135,

E45X, 100 GATE


RPA, SKW


E45X 110 GATE


RPA, SKW


E45X 100 GATE


RPA, SKW


E45X 110 GATE


RPA, SKW


E45X, 100 GATE


RPA, SKW


E45X 110 GATE


RPA, SKW


E45X, 100 GATE


RPA, SKW


E45X 110 GATE



RPA, SKW


E45X, 100 GATE


RPA, SKW


E45X, 110 GATE


RPA, SKW


E45X, 100 GATE


RPA, SKW


E45X, 110 GATE


RPA, SKW


E45X, 100 GATE



RPA, SKW


E45X, 100 GATE



RPA, SKW


E45X, 100 GATE



RPA, SKW


E45X, 100 GATE



RPA, SKW


E45X, 100 GATE



RPA, SKW


E45X, 100 GATE



RPA, SKW


E45X, 100 GATE



RPA, SKW


E45X, 100 GATE



RPA, SKW


E45X, 100 GATE



RPA, SKW


E45X, 100 GATE



RPA, SKW


E45X, 100 GATE


RPA, SKW


E45X, 100 GATE


RPA, SKW


E45X, 100 GATE


RPA, SKW


E45X, 100 GATE


RPA, SKW


E45X, 100 GATE


RPA, SKW


E45X, 100 GATE


RPA, SKW


E45X, 100 GATE


RPA, SKW


E45X, 100 GATE


RPA, SKW


E45X, 100 GATE


RPA, SKW


E45X, 100 GATE


RPA, SKW


E45X, 100 GATE


RPA, SKW


E45X, 100 GATE


RPA, SKW


E45X, 100 GATE


RPA, SKW


E45X, 100 GATE


RPA, SKW


E45X, 100 GATE


RPA, SKW


E45X, 100 GATE

* Gates blocked when adjacent gate is occupied by heavy. Not inlcuded in AFCAD file.

** Remote stands


Concourse C

Gate Maximum




Maximum AI Aircraft


C1 - C27 N/A N/A N/A N/A N/A

C28 120 SWA B737, B738 120 GATE

C29 120 SWA B737, B738 120 GATE

C30 120 SWA B737, B738 120 GATE

C31 120 SWA B737, B738 120 GATE

C32 120 SWA B737, B738 120 GATE

C33 120 SWA B737, B738 120 GATE

C34 120 SWA B737, B738 120 GATE

C35 120 SWA B737, B738 120 GATE

C36 120 DAL, FLG, TCF CRJ9, E170, 190, A319,

A320, MD90, B738 120 GATE

C37 120 SWA B737, B738 120 GATE


A320, MD90, B738, B752

130 GATE

C39 120 SWA B737, B738 120 GATE


A320, MD90, B738, B752

130 GATE

C41 120 SWA B737, B738 120 GATE


A320, MD90, B738, B752

130 GATE

C43 120 SWA B737, B738 120 GATE


A320, MD90, B738, B752

130 GATE

C45 120 SWA B737, B738 120 GATE

C46 120 SWA B737, B738 120 GATE

C47 120 SWA B737, B738 120 GATE

C48 120 SWA B737, B738 120 GATE

C49 120 SWA B737, B738 120 GATE

CE 1 - CE6* 120 SWA B737, B738 120 GATE

GATE

N Parking 1-9, 12 - 14**

130 N/A 130 GATE

N Parking 10, 11, 15**

220 N/A 220 GATE

* Remote stands, Labeled as F gates in the AFCAD file ** Remote stands, Labeled as N Parking gates in the AFCAD file


Cargo Ramp

S PARKING Maximum




Maximum AI Aircraft


1 130 FDX B752 130 CARGO

3, 5, 9, 11, 17 200 FDX A312, DC10, MD11,

B772 200 CARGO

2, 4, 8, 12 180 N/A up to A300, B767 180 CARGO

20, 34 130 UPS B752 120 CARGO

22, 24, 26, 28, 30, 32

180 UPS A300, MD11, B767,

B747 120 CARGO

31 220 UPS A300, MD11, B767,

B747 120 CARGO

35 220 N/A up to B747 220 CARGO

GA Ramp

SE PARKING Maximum




Maximum AI Aircraft


1 - 9 80 80 RAMP

United

Maintenance Ramp

NE PARKING Maximum




Maximum AI Aircraft


1, 5 180 UAL A319, A320, B737, B738, B739, B752,

B753, B763 130 RAMP

4 200 UAL

A319, A320, B737, B738, B739, B752, B753, B763, B772,

B788

200 RAMP

2, 3, 6, 7 130 UAL A319, A320, B737, B738, B739, B752,

B753 130 RAMP

8, 9 120 UAL A319, A320, B737,

B738, B739 120 RAMP


Airline Codes

AAL American Airlines

ACA Air Canada

ASA Alaska Airlines

ASQ ExpressJet

AWE US Airways

BAW British Airways

DAL Delta Airlines

DLH Lufthansa

EGF American Eagle

FDX FedEx

FFT Frontier Airlines

FLG Endeavor Air

GJS GoJet

GLA Great Lakes Airlines

ICE Icelandair

JBU JetBlue Airlines

NKS Spirit Airlines

RPA Republic Airlines

SKW Skywest Airlines

SWA Southwest Airlines

TCF Shuttle America

TSR AirTran Airways

UAL United Airlines

UPS UPS


Aircraft Types

A306 Airbus Industrie A300-600 A312 Airbus Industrie A310-200 A313 Airbus Industrie A310-300 A318 Airbus Industrie A318 A319 Airbus Industrie A319 A320 Airbus Industrie A320 A321 Airbus Industrie A321 A332 Airbus Industrie A330-200 A333 Airbus Industrie A330-300 A342 Airbus Industrie A340-200 A343 Airbus Industrie A340-300 A345 Airbus Industrie A340-500 A346 Airbus Industrie A340-600 A388 Airbus Industrie A380-800 B717 Boeing 717-200 B732 Boeing 737-200 B733 Boeing 737-300 B734 Boeing 737-400 B735 Boeing 737-500 B736 Boeing 737-600 B73G Boeing 737-700 B738 Boeing 737-800 B739 Boeing 737-900 B744 Boeing 747-400 B748 Boeing 747-800 B752 Boeing 757-200 B753 Boeing 757-300 B762 Boeing 767-200/200ER B763 Boeing 767-300/300ER B764 Boeing 767-400 B772 Boeing 777-200/200ER B773 Boeing 777-300 B77L Boeing 777-200LR B77W Boeing 777-300ER B788 Boeing 787-800 CRJ Canadair Regional Jet 100 CRJ2 Canadair Regional Jet 200 CRJ7 Canadair Regional Jet 700 CRJ9 Canadair Regional Jet 900 DH8D De Havilland Canada Dash 8-400 E120 Embraer EMB-120 Brasilia E135 Embraer ERJ-135 Regional Jet E140 Embraer ERJ-140 Regional Jet E145 Embraer ERJ-145 Regional Jet E45X Embraer ERJ-145XR Regional Jet E170 Embraer ERJ-170 E175 Embraer ERJ-175 E190 Embraer ERJ-190 E195 Embraer ERJ-195 MD11 Boeing/McDonnell Douglas MD-11 MD80 Boeing/McDonnell Douglas MD-80 MD81 Boeing/McDonnell Douglas MD-81 MD82 Boeing/McDonnell Douglas MD-82 MD83 Boeing/McDonnell Douglas MD-83 MD87 Boeing/McDonnell Douglas MD-87 MD88 Boeing/McDonnell Douglas MD-88 MD90 Boeing/McDonnell Douglas MD-90


Scenery Fixes and Upgrades

We are committed to providing the highest quality scenery add-ons for Microsoft Flight Simulator. Consequently, we issue fixes and upgrades for our products from time to time. The fixes and upgrades may include simple corrections and improvements (most thanks to the feedback of our customers) as well as significant changes and improvements resulting from technique evolution and refinement on the part of our designers. As our technique evolves, we update previously released products by issuing interim fixes or upgrades. In order to stay current regarding these free fixes and upgrades please visit the “Downloads” page on our web site: http://www.blueprintsimulations.com/

Technical Support Answers to the most common questions about our sceneries can be found in the FAQ section of our website at http://www.blueprintsimulations.com. Any other technical questions must be submitted via email to [email protected].

Acknowledgements

We would like to acknowledge Lee Swordy for his AFCAD version 2.21 freeware, a CAD-style program used for the modification of facility data as well as some of the visible scenery used in Microsoft Flight Simulator. We would also like to acknowledge Arno Gerretsen and the entire www.FsDeveloper.com team for their effort to provide guidance and advice to all MSFS add-on developers.



http://www.fsdeveloper.com/

Documents

Presents - BluePrint Simulationsthe US such as KIAD and KATL, DIA’s terminal consists of three remote concourses connected to each other and to the main terminal via an underground