Presents http://www.blueprintsimulations.com/ OnDuty Support Systems LLC. 2007-2013 All rights reserved. 1
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 BluePrint Simulations KMSP version 2 scenery depicts the Minneapolis-Saint Paul International airport as it exists in the summer of 2013. The scenery features highly detailed, full-3d models of KMSP s two terminals, the ATC tower, the midfield cargo ramp, the National Guard and USAF ramps and most maintenance and general aviation facilities within the airport boundaries. All 3D models feature custom-made, high-resolution (32 px/meter) textures and the highest level of three-dimensional detail possible (BluePrint s True3D). All aircraft maintenance and storage hangars are fully three-dimensional and most are usable. The Lindbergh terminal includes 7 concourses (A-G), the main passenger arrival and departure complex and the extensive parking facilities that dominate the field of view during ground operations near the terminal. Altogether, the Lindbergh terminal includes over 120 jetwayequipped gates, each one painstakingly adjusted and customized to match the actual aircraftparking layout and airline usage. Concourse E is used by most major US airlines and their regional partners. All other concourses are one of Delta Airlines largest hubs (next to ATL and DTW), featuring one of the largest all-indoors regional airline terminals in the country (concourses A, B and most of C). The Humphrey terminal includes concourse H with 11 jetwayequipped gates plus the main passenger arrival and departure halls and parking facilities. The scenery also includes KMSP s four runways and its extensive taxiway network featuring realistic ramp and taxiway markings and signs. All field components including navigation aids are positioned as accurately as possible according to current official navigation publications and permit realistic taxi, departure, approach and landing operations under all weather conditions. Terrain elevation and texturing in the vicinity of the field are customized according to current and accurate satellite data and matched to the surrounding environment within the limitation imposed by the simulator s terrain elevation and texturing accuracy. The replacement terrain textures are customized to match seasonal changes and blended with the surrounding environment to provide a realistic experience during approach to all eight runways. BluePrint s KMSP version 2 also includes a highly-detailed rendition of the Mall of America, the world s largest indoors shopping and entertainment complex which is clearly visible during final approach to runways 35 and 4 as well as from numerous locations in the western portion of the field. It also includes detailed models of the three highway bridges spanning the ravine along the southeastern boundary of the airport that are clearly visible during approach to runways 30L/R and 35. OnDuty Support Systems LLC. 2007-2013 All rights reserved. 2
Scenery Features Custom-made, optimized and fully three-dimensional Gmax models of the entire facility including: o Two terminals and 9 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 terminals 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. http://www.blueprintsimulations.com/ OnDuty Support Systems LLC. 2007-2013 All rights reserved. 3
Suggested 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 IMPORTANT NOTICE: You MUST complete the following steps before installing KMSP version 2 if you own a license for BluePrint Simulations KMSP, Minneapolis St. Paul Intl airport version 1 scenery for FS2004 and it is active in your simulator. (If you already removed the version 1 scenery or you do not own BluePrint Simulations KMSP version 1 for FS2004 please skip to step 7 below.) Uninstall BluePrint s KMSP version 1 by either running the original installer and selecting Remove when prompted or by using the Uninstall a program feature in the Windows Control Panel Check and if necessary manually delete the KMSP scenery folder created during the original installation of KMSP version 1 to avoid interferences with the new scenery. In a default installation, the KMSP scenery folder is located at: o o C:\Program Files\Microsoft Games\Flight Simulator X\BluePrint Simulations in a 32-bit version of windows or C:\Program Files (x86)\microsoft Games\Flight Simulator X\BluePrint Simulations in a 64-bit version of Windows. Note: By default, the new scenery will be installed in a folder labeled KMSPv2 to avoid mixing the two sceneries. You may, of course, choose to install the new version 2 scenery in a different folder so please be aware that the new version 2 scenery files will not replace the old version 1 scenery files and the old files will interfere with the new scenery if they remain in an active scenery folder. Remove KMSP version 1 from the scenery library following the procedure below. To remove KMSP version 1 from the scenery library: 1. Run the Flight Simulator 2. Upon starting the flight simulator the following window should open: OnDuty Support Systems LLC. 2007-2013 All rights reserved. 4
3. 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: OnDuty Support Systems LLC. 2007-2013 All rights reserved. 5
4. Select Scenery Library The following window should open: OnDuty Support Systems LLC. 2007-2013 All rights reserved. 6
5. Select BluePrint Simulations KMSP in the Areas list by clicking on it. 6. Click on Delete Area and confirm the deletion when prompted. Please contact BluePrint Simulation s tech support at support@blueprintsimulations.com if you need assistance with this procedure. To install the new scenery: 7. Download the installer and save it in any folder of your choice. The installer is a file labeled KMSPv2.1.1.exe. 8. Double click on the file labeled KMSPv2.1.1.exe to run the scenery installer. 9. Please read carefully and make sure that you understand all the terms of the End User License Agreement (EULA) before continuing with the installation. 10. Select the folder where the scenery will be located. The installer will search your computer hard drives 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. If it cannot find 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 suggested default path was used during the simulator s installation. 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. 11. Complete the installation by following the onscreen instructions. 12. Run the Flight Simulator and add the new scenery to the scenery library as follows: 13. Upon starting the flight simulator the following window should open: 14. If you have setup your simulator to skip this window at start up, you can reach it as follows: OnDuty Support Systems LLC. 2007-2013 All rights reserved. 7
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: 15. Select Scenery Library The following window should open: OnDuty Support Systems LLC. 2007-2013 All rights reserved. 8
16. Select Add Area 17. Navigate to the FS9_root_directory \BluePrint Simulations\ directory.. In a default installation, the KMSP scenery folder is located at: o C:\Program Files\Microsoft Games\Flight Simulator 9\BluePrint Simulations in a o 32-bit version of windows or 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. 18. Select the KMSP folder (Select only, do not double click ) 19. Press OK 20. The KMSP 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. KMSP should appear at the top instead). OnDuty Support Systems LLC. 2007-2013 All rights reserved. 9
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 KMSP s location or its immediate vicinity (This includes regional or global terrain add-ons). 21. 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 FSX 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 scenery activation may also be found in the FS2004 help menu. OnDuty Support Systems LLC. 2007-2013 All rights reserved. 10
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. OnDuty Support Systems LLC. 2007-2013 All rights reserved. 11
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 OnDuty Support Systems LLC. 2007-2013 All rights reserved. 12
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 OnDuty Support Systems LLC. 2007-2013 All rights reserved. 13
Lindbergh Terminal Maximum Airline Gate Maximum AI AI Aircraft Gate Aircraft Wingspan (ft) Assignment (ICAO Codes) Typical Aircraft Aircraft Wingspan (ft) Parking Type A1 N/A N/A N/A N/A N/A A2 N/A N/A N/A N/A N/A A3 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE A4 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE A5 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE A6 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE A7 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE A8 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE A9 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE A10 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE A11 70 ASQ CPZ FLG SKW CR2 ER3 ER4 70 GATE A12 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE A13 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE A14 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE B1 70 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 70 GATE B2 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE B3 70 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 70 GATE B4 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE B5 70 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 70 GATE B6 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE B7 70 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 70 GATE B8 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE B9 70 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 70 GATE B10 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE B11 70 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 70 GATE B12 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE B13 70 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 70 GATE B14 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE B15 70 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 70 GATE B16 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE C1 120 DAL C2 120 DAL C3 120 DAL OnDuty Support Systems LLC. 2007-2013 All rights reserved. 14
C4 120 DAL C5 120 DAL C6 120 DAL C7 120 DAL C8 120 DAL C9 130 DAL 319 320 738 752 DC9 M80 C10 130 DAL 319 320 738 752 DC9 M80 C11 130 DAL 319 320 738 752 DC9 M80 C12 130 DAL 319 320 738 752 DC9 M80 C13 130 DAL 319 320 738 752 DC9 M80 C14 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE C15 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE C16 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE C17 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE C18 N/A ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 N/A GATE C19 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE C20 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE C21 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE C22 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE C23 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE C24 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE C25 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE C26 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE C27 80 ASQ CPZ FLG SKW CR2 CR7 ER3 ER4 80 GATE D1 120 DAL D2 120 DAL D3 120 DAL D4 120 DAL D5 120 DAL D6 120 DAL OnDuty Support Systems LLC. 2007-2013 All rights reserved. 15
E1 120 N/A N/A E2 120 AWE RPA 319 E70 E3 100 N/A N/A 100 GATE E4 120 AWE RPA 319 E70 E5 120 FTT 318 319 E6 120 UAL ASQ SKW TCF CR7 ER4 E70 319 320 73G 738 739 E7 120 UAL ASQ SKW TCF CR7 ER4 E70 319 320 73G 738 739 E8 120 JZA UAL ASQ SKW CR7 ER4 E70 319 320 TCF 73G 738 739 E9 120 N/A N/A E10 80 UAL ASQ SKW TCF CR7 ER4 E70 319 320 73G 738 739 80 GATE E11 120 N/A N/A E12 120 EGF AAL ER4 M80 738 80 GATE E13 120 N/A N/A E14 120 AAL M80 738 E15 80 GLA 80 GATE E16 120 AAL M80 738 F1 120 DAL F2 120 DAL N/A N/A F3 120 ASA 738 739 F4 130 DAL DC9 M80 F5 130 DAL F6 130 DAL F7 130 DAL F8 130 DAL F9 130 DAL F10 180 DAL F11 130 DAL F12 180 DAL DC9 M80 DC9 M80 DC9 M80 DC9 M80 DC9 M80 763 764 DC9 M80 DC9 M80 763 764 DC9 M80 180 GATE 180 GATE OnDuty Support Systems LLC. 2007-2013 All rights reserved. 16
F13 120 DAL F14 120 DAL F15 120 DAL F16 120 DAL G1 120 DAL G2 220 DAL G3* 120 DAL G4 120 DAL G5* 120 DAL G6/G7 200 DAL G8 200 DAL G9 130 DAL G10 130 DAL G11 130 DAL G12 130 DAL G13 130 DAL G14 130 DAL G15 130 DAL G16 130 DAL G17 130 DAL G18 130 DAL G19 130 DAL G20 120 DAL 319 320 332 333 738 752 753 763 764 772 744 DC9 M80 319 320 332 333 738 752 753 763 764 772 DC9 M80 319 320 332 333 738 752 753 763 764 772 DC9 M80 DC9 M80 DC9 M80 DC9 M80 DC9 M80 DC9 M80 DC9 M80 DC9 M80 DC9 M80 DC9 M80 DC9 M80 DC9 M80 220 GATE N/A N/A N/A N/A 200 GATE 200 GATE OnDuty Support Systems LLC. 2007-2013 All rights reserved. 17
G21 120 DAL G22 120 DAL G23 120 DAL G24 120 DAL R1** 130 DAL R2** 200 DAL R3** 130 DAL R4** 200 DAL R5** 130 DAL R6** 200 DAL R7** 130 DAL R8** 200 DAL DC9 M80 319 320 332 333 738 752 753 763 764 772 DC9 M80 DC9 M80 319 320 332 333 738 752 753 763 764 772 DC9 M80 DC9 M80 319 320 332 333 738 752 753 763 764 772 DC9 M80 DC9 M80 319 320 332 333 738 752 753 763 764 772 DC9 M80 200 GATE 200 GATE 200 GATE 200 GATE * Gates blocked when adjacent gate is occupied by heavy. Not included in AFCAD file. ** Remote stands OnDuty Support Systems LLC. 2007-2013 All rights reserved. 18
Humphrey Terminal Gate Maximum Aircraft Wingspan (ft) Airline Gate Assignment (ICAO Codes) Typical Aircraft Maximum AI Aircraft Wingspan (ft) AI Aircraft Parking Type H1 120 N/A H2 120 N/A H3 120 SCX 738 H4 120 SCX 738 H5 120 SCX 738 H6 120 NKS ICE 319 H7 120 SWA TSR H8 120 SWA TSR H9 120 SWA TSR 717 733 73G 738 717 733 73G 738 717 733 73G 738 H10 120 N/A OnDuty Support Systems LLC. 2007-2013 All rights reserved. 19
Midfield Cargo Ramp PARKING Maximum Aircraft Formatted Typical Aircraft Wingspan (ft) for AI Airline Codes Parking Type 1, 3, 5 180 757 310 N/A FDX RAMP CARGO 2, 4, 6 200 757 310 M11 772 N/A FDX RAMP CARGO 10-15 180 752 763 300 N/A UPS RAMP CARGO 20-31 60 N/A N/A RAMP CARGO General Aviation Ramp S PARKING Maximum Aircraft Wingspan (ft) Airline Gate Assignment (ICAO Codes) Typical Aircraft Maximum AI Aircraft Wingspan (ft) 1-7, 16-24 64 64 8-15 80 80 25-27 50 50 AI Aircraft Parking Type RAMP GA MEDIUM RAMP GA MEDIUM RAMP GA SMALL SW Cargo Ramp SW PARKING Maximum Aircraft Wingspan (ft) Airline Gate Assignment (ICAO Codes) Typical Aircraft Maximum AI Aircraft Wingspan (ft) AI Aircraft Parking Type 1 180 180 RAMP CARGO 2 135 135 RAMP CARGO Delta Maintenance Ramp SW PARKING Maximum Aircraft Wingspan (ft) Airline Gate Assignment (ICAO Codes) Typical Aircraft Maximum AI Aircraft Wingspan (ft) 3 200 DAL 200 4, 5 130 DAL 130 6-10 120 DAL 120 11 220 DAL 220 AI Aircraft Parking Type RAMP GA LARGE RAMP GA LARGE RAMP GA LARGE RAMP GA LARGE OnDuty Support Systems LLC. 2007-2013 All rights reserved. 20
USAF Ramp N PARKING Maximum Aircraft Wingspan (ft) Airline Gate Assignment (ICAO Codes) Typical Aircraft Maximum AI Aircraft Wingspan (ft) 1-12 140 140 AI Aircraft Parking Type RAMP MIL CARGO ANG Ramp NE PARKING Maximum Aircraft Wingspan (ft) Airline Gate Assignment (ICAO Codes) Typical Aircraft Maximum AI Aircraft Wingspan (ft) 1-5 140 140 AI Aircraft Parking Type RAMP MIL CARGO W Cargo Ramp W PARKING Maximum Aircraft Wingspan (ft) Airline Gate Assignment (ICAO Codes) Typical Aircraft Maximum AI Aircraft Wingspan (ft) 1 120 120 3-8 130 130 AI Aircraft Parking Type RAMP CARGO RAMP CARGO W Maintenance Ramp W PARKING Maximum Aircraft Wingspan (ft) Airline Gate Assignment (ICAO Codes) Typical Aircraft Maximum AI Aircraft Wingspan (ft) 10-13 120 SCX 738 120 14 120 N/A N/A 120 AI Aircraft Parking Type RAMP GA LARGE RAMP GA LARGE OnDuty Support Systems LLC. 2007-2013 All rights reserved. 21
Airline Codes AAL ACA ASQ AWE AWI CHQ CPZ DAL EGF FLG FTT ICE JZA RPA SCX SKW SWA TCF TSR UAL American Airlines Air Canada Atlantic Southeast Airlines US Airways Air Wisconsin Chautauqua Airlines Compass Airlines Delta Airlines American Eagle Pinnacle Airlines Frontier Airlines Icelandair Air Canada Jazz Republic Airlines Sun Country Airlines Skywest Airlines Southwest Airlines Shuttle America AirTran Airways United Airlines Aircraft Types 100 Fokker 100 141 British Aerospace BAe 146-100 142 British Aerospace BAe 146-200 143 British Aerospace BAe 146-300 312 Airbus Industrie A310-200 313 Airbus Industrie A310-300 318 Airbus Industrie A318 319 Airbus Industrie A319 320 Airbus Industrie A320 321 Airbus Industrie A321 332 Airbus Industrie A330-200 333 Airbus Industrie A330-300 342 Airbus Industrie A340-200 343 Airbus Industrie A340-300 345 Airbus Industrie A340-500 346 Airbus Industrie A340-600 OnDuty Support Systems LLC. 2007-2013 All rights reserved. 22
388 Airbus Industrie A380-800 717 Boeing 717-200 732 Boeing 737-200 733 Boeing 737-300 734 Boeing 737-400 735 Boeing 737-500 736 Boeing 737-600 738 Boeing 737-800 739 Boeing 737-900 73G Boeing 737-700 744 Boeing 747-400 748 Boeing 747-800 752 Boeing 757-200 753 Boeing 757-300 762 Boeing 767-200 763 Boeing 767-300 764 Boeing 767-400 772 Boeing 777-200/200ER 773 Boeing 777-300 77L Boeing 777-200LR 77W Boeing 777-300ER AR1 Avro RJ100 Avroliner AR7 Avro RJ70 Avroliner AR8 Avro RJ85 Avroliner AT4 Aerospatiale/Alenia ATR 42-300/320 AT5 Aerospatiale/Alenia ATR 42-500 AT7 Aerospatiale/Alenia ATR 72 CR1 Canadair Regional Jet 100 CR2 Canadair Regional Jet 200 CR7 Canadair Regional Jet 700 CR9 Canadair Regional Jet 900 CRA Canadair Regional Jet 705 D93 Boeing/McDonnell Douglas DC-9-30 D95 Boeing/McDonnell Douglas DC-9-50 DH1 De Havilland Canada DHC-8-100 Dash 8/8Q DH2 De Havilland Canada DHC-8-200 Dash 8/8Q DH3 De Havilland Canada DHC-8-300 Dash 8/8Q DH4 De Havilland Canada DHC-8-400 Dash 8/8Q E70 Embraer ERJ-170 E75 Embraer ERJ-175 E90 Embraer ERJ-190 E95 Embraer ERJ-195 EM2 Embraer EMB-120 Brasilia OnDuty Support Systems LLC. 2007-2013 All rights reserved. 23
ER3 ER4 ERD M11 M80 M81 M82 M83 M87 M88 Embraer ERJ-135 Regional Jet Embraer ERJ-145 Regional Jet Embraer ERJ-140 Regional Jet Boeing/McDonnell Douglas MD-11 Boeing/McDonnell Douglas MD-80 Boeing/McDonnell Douglas MD-81 Boeing/McDonnell Douglas MD-82 Boeing/McDonnell Douglas MD-83 Boeing/McDonnell Douglas MD-87 Boeing/McDonnell Douglas MD-88 Boeing/McDonnell Douglas MD-90 OnDuty Support Systems LLC. 2007-2013 All rights reserved. 24
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 support@blueprintsimulations.com. 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. OnDuty Support Systems LLC. 2007-2013 All rights reserved. 25