Category: Flight Simulator 2004 - Miscellaneous Files
Active ILS - KIAH (G Bush Intercontinental/Houston Airport)

File Description:
As most know initiating the ILS at certain airports for AI Traffic is not a function at this time when using AFCAD2. If you add a new ILS runway to an airport such as KIAH (G Bush Intercontinental/Houston Airport 8L/26R) only the user aircraft can use this runway when visibility falls below 3 miles. ATC will no longer use this runway for AI Traffic because FS9 sees it as a visual runway and will now vector your AI Traffic back to 8R/26L which is also a Terminal departure runway. This file adds all NAVAIDS for making 8L/26R a Precision Instrument Runway by adding all the radar fixes for both the ILS approach portion and the proper missed approach procedures, altitudes and intersections as per current published plates. All AI Aircraft will now continue to use 8L/26R when Airport conditions are less than 3 miles.

Category: Flight Simulator 2004 - Miscellaneous Files
Active APProach - EHAM (Amsterdam - Schiphol Airport)

File Description:
This file is for any 3rd party payware or freeware scenery that renumbered the runways at EHAM. The EHAM_APP_3rd bgl file list all ILS runways correctly (no blanks) within the ATC menu. Included are all the Waypoints for making 18R/36L a Precision Instrument Runway both VMC and IMC. The file also renames runways 01 Left and Right, 19 Left and Right to the current 18L/36R, 18C/36C so ATC and ATIS will use the right voice verbage for these runways. Each STAR is represented (ARTIP, RIVER, SUGOL) and can be flown with or without the default ATC. See the readme for all the details.

Category: Flight Simulator 2004 - Miscellaneous Files
Active Approach - LOWI (Innsbruck, Austria)

File Description:
As most know the Approach and Final (VMC) for AI Traffic in FS9 is a straight in type landing and does not always consider high terrain at airports. This is do to the way that the coding is written in FS9 and it puts limits on IFR arriving aircraft. If you open runways at certain airports the AI Traffic will fly directly through a mountain once it is established on Final for a runway. What you will see with my file is a different type approach used for the way I control AI Traffic in FS9. No longer do the AI Planes use a straight in approach when landing at LOWI. My new AI Aircraft Approach coding for FS9 now uses a base leg approach so AI Traffic does not fly through the mountains. The Innsbruck Control Tower will clear all AI Traffic (IFR FP) landing either on 08 and 26 as a straight in landing even though the offset to final is 30 degrees from the runway center line. My testing shows excellent behavior of the FS9 default models, PAI models and the Aardvark planes of all sizes to execute this new type of visual approach. Read the text file for all the default enhancements added to LOWI along with a full understanding of how the new Approaches work *** Full set of Approach Charts included plus a FS2004 Default Scenery AFCAD ***

Category: Flight Simulator 2004 - Miscellaneous Files
Active Approach - PHNL (Honolulu Intl Honolulu, Hawaii)

File Description:
As most know the Approach and Final (VMC) for AI Traffic in FS9 is a straight in type landing and does not always consider high terrain at airports. This is do to the way that the coding is written in FS9 and it puts limits on IFR arriving aircraft. If you open runways at certain airports the AI Traffic will fly directly through a mountain once it is established on Final for a runway. What you will see with my file is a different type approach used for the way I control AI Traffic in FS9. No longer do the AI Planes use a straight in approach when landing to the west at PHNL. My new AI Aircraft Approach coding for FS9 now uses a base leg approach so AI Traffic does not fly through the mountains. The Honolulu Control Tower will clear all AI Traffic (IFR FP) landing either on 26L and 26R as a straight in landing even though the offset to final is 30 degrees from the runway center line. The Control Tower will instruct the AI Planes landing on either 22L or 22R to fly a left base leg which is greater then a 45 degree offset and then the AI Planes will turn on a short 1.5 mile final. The left base approach to 22L and 22R runways is a 65 degree offset from the runway center line. My testing shows excellent behavior of the FS9 default models, PAI models and the Aardvark planes of all sizes to execute this new type of visual approach that I am now writting code for which supersedes the FS9 default straight in ATC hard code approach. Read the text file for all the default scenery enhancements (plus Jetways) added to PHNL along with a full understanding of how the new Approaches work *** 3rd Party Scenery Designers Special APProach bgl and a FS2004 Default Scenery AFCAD included ***

Category: Flight Simulator 2004 - Miscellaneous Files
Active ILS - KLAS (McCarran Intl - Las Vegas, Nevada)

File Description:
As most know initiating the ILS at certain airports for AI Aircraft or User Planes is not a function at this time when using AFCAD2 if visibilty falls below 3 miles. This is do to the somewhat complex XML code that has to be written for NAVAIDS and then the compiling into a bgl file. If you add a new ILS runway to an airport such as KLAS (rwy 01L) only the user aircraft can use this runway when visibility falls below 3 miles. ATC will no longer use 01L ILS runway for AI Traffic or User Aircraft (by default) because FS9 sees it as a visual runway and will now vector your Planes back to rwy 7/25LR ILS which is also being used as a Terminal Departure Runway. The KLAS_ILS_jv.bgl file adds all NAVAIDS for making 01L a Precision Instrument Runway by adding all the radar fixes for both the ILS/DME approach portion and the proper missed approach procedures as per current published plates for runway 01L. See the readme for what's new at the KLAS airport. **** AFCAD2 included for FS9 default scenery. ****

Category: Flight Simulator X - AFCAD Files
Active ILS - Aspen-Pitkin Co Sardy (KASE)

File Description:
AFCAD style 100 percent compliant FSX airport. AI/User Planes can now fly the I-ASE LOC Approach to RWY 15. KASE is coded for both VMC and IMC Airport conditions with proper vectors from ATC. See the readme for all the details and what has been added to the Aspen-Pitkin Airport. AFCAD style airport and Approach code written with SDE.

Category: Flight Simulator X - AFCAD Files
Active ILS - Comox BC Canada 'CYQQ'

File Description:
This bgl file fixes the ILS Localizer and Glideslope Transmitters for CYQQ. FSX inadvertently misplaced the Localizer to the rightside of the runway. CYQQ is not a offset ILS type Approach. No other changes have been made to the airport.

Category: Flight Simulator 2004 - Miscellaneous Files
Active ILS - EFHK (Helsinki - Vantaa Aerodrome)

File Description:
As most know initiating the ILS at certain airports for AI Traffic is not a function at this time when using AFCAD2. If you add a new ILS runway to an airport such as EFHK (Helsinki - Vantaa 4L/22R) only the user aircraft can use this runway when visibility falls below 3 miles. ATC will no longer use this runway for AI Traffic because FS9 sees it as a visual runway. This will cause ATC to vector all your AI Traffic back to 4R/22L which is also a Terminal departure runway. This bgl file adds all NAVAIDS for making 4L/22R a Precision Instrument Runway by adding all the radar fixes for both the ILS approach portion and the missed approach procedures, altitudes and intersections as per current published plates. All AI Aircraft will now continue to use 4L/22R when Airport weather conditions are less than 3 miles. *** FISD Finnish Scenery Designers and FS2004 Default Scenery AFCAD's included ***

Category: Flight Simulator 2004 - Miscellaneous Files
Active ILS - EHAM (Amsterdam - Schiphol Airport)

File Description:
As most know initiating the ILS at certain airports for AI Traffic is not a function at this time when using AFCAD2. If you add a new ILS runway to an airport such as EHAM (Schiphol 18R/36L) only the user aircraft can use this runway when visibility falls below 3 miles. ATC will no longer use this runway for AI Traffic because FS9 sees it as a visual runway. This will cause ATC to vector all your AI Traffic back to (01L/19R old numbers) 18C/36C (new numbers) which is also a Terminal departure runway. This bgl file adds all NAVAIDS for making 18R/36L a Precision Instrument Runway. All AI Aircraft will now continue to use 18R when Airport weather conditions are less than 3 miles. Read the text file for all the enhancements added to EHAM *** 3rd Party Scenery Designers Special ILS bgl and FS2004 Default Scenery AFCAD included ***

Category: Flight Simulator X - AFCAD Files
Active ILS - Jacksonville International Airport, Jacksonville, Florida (KJAX)

File Description:
This AFCAD style airport for Jacksonville, FL is 100 percent FSX compliant. All Jetways and Parking Spots have been changed to their proper Airline/Cargo Codes and reordered for proper parking of 3rd party AI Flightplans. Both Runways (7/25, 13/31) are operating simultaneously as per my crosswind runway technique. Additional Fuel Trucks, Airport Vehicle roads, new Fire Station/Trucks plus other features have been added. XML source code also included.