Skip to content
Prepar3D 6 min read 140 views

What KMCO scenery add-ons are available for Prepar3D?

Adam McEnroe
In short

Compare two freeware KMCO scenery add-ons for Prepar3D, including Orlando airport visuals, AFCAD parking, P3D v4-v6 status and conflict fixes.

For Prepar3D, use Orlando International Airport Scenery for FSX & P3D for a general KMCO visual and layout makeover, or AFCAD File for KMCO for airline-coded parking, extra stands, service roads, airport objects and terrain files. Activate only one Orlando International airport definition at a time.

Downloads at a glance: KMCO and Orlando International

Orlando International Airport Scenery for FSX & P3D is the better starting point when you want a broader improvement to the default airport. AFCAD File for KMCO is aimed more squarely at AI parking, ramp capacity and airport operations.

AFCAD is the established community term for an airport-definition BGL. It can control runways, taxiways, parking positions and AI routing, but an AFCAD is not automatically a complete custom terminal or photoreal scenery package.

Exact packageAuthor/release informationIncluded scenery componentsStated compatibility
Orlando International Airport Scenery for FSX & P3DLegacy freeware release issued as one FSX/Prepar3D package; no separate P3D v4, v5 or v6 edition is stated.Updated airport layout, taxiways, parking and roads, plus fuel-truck details and a helipad.The package listing explicitly names FSX and Prepar3D, but does not document confirmation for an individual P3D generation.
AFCAD File for KMCOLegacy freeware AFCAD release; no version-specific Prepar3D build is documented.Airline-coded parking, expanded ramp capacity, revised service roads, airport objects and separate terrain components.Prepar3D v4, v5 and v6 support is not explicitly confirmed. Treat it as a manual compatibility test rather than a native P3D package.

Which Orlando scenery should I choose?

Choose the general scenery package for a wider default-airport makeover; choose the AFCAD when parking allocation and AI ground operations are your priority.

  • For visual flying and routine operations: use Orlando International Airport Scenery for FSX & P3D. It changes more of the airport than a parking-only definition, although it should not be mistaken for a modern photoreal or fully custom-modelled KMCO.
  • For airline AI traffic: use AFCAD File for KMCO. Its airline codes and added stands are the more useful features when building realistic carrier parking.
  • For an existing Florida scenery setup: choose the package that produces the fewest conflicts with regional scenery, terrain mesh and other airport collections.

Parking codes do not create AI traffic. The installed aircraft and flight plans must use matching airline codes, and each parking position needs a radius large enough for the assigned aircraft.

Will these KMCO add-ons work in Prepar3D v4, v5 and v6?

Neither download has documented, version-specific confirmation across P3D v4, v5 and v6, although the broader scenery package is explicitly listed for the Prepar3D family.

PackageP3D v4P3D v5P3D v6
Orlando International Airport Scenery for FSX & P3DPrepar3D support is stated, but a v4-specific test is not documented.Prepar3D support is stated, but v5-specific confirmation is not documented.Prepar3D support is stated, but v6-specific confirmation is not documented.
AFCAD File for KMCOUntested or unconfirmed for v4 in the available documentation.Untested or unconfirmed for v5 in the available documentation.Untested or unconfirmed for v6 in the available documentation.

A simple airport-layout BGL has a better chance of transferring between simulator generations than scenery dependent on old object models, effects or installers. That does not guarantee that every component will work: the layout may load while objects, textures or terrain corrections fail.

Test KMCO in a clean scenario before adding complex weather or AI traffic. Inspect runway elevation, taxiway surfaces, terminal objects, night lighting and parking positions. If anything is wrong, disable the add-on entry rather than deleting Prepar3D's stock airport files.

Can I install both KMCO packages together?

No, not with both airport-definition BGLs active. Competing KMCO definitions can produce duplicate objects, overlapping parking positions, broken AI routing, incorrect runway starts and elevation artefacts.

Advanced users can sometimes retain independent object or terrain components while disabling one conflicting airport definition, but only when the package documentation clearly identifies those files. Do not guess from a BGL name or combine components from different releases without testing each change separately.

How do I install KMCO scenery in Prepar3D?

Install the chosen package in its own directory, preserve its folder structure and register it with Prepar3D instead of scattering BGL files through the simulator's global scenery folders.

  1. Extract the download outside Prepar3D. Check for a read-me and make sure an extra nested archive or folder has not been overlooked.
  2. Preserve the supplied structure. Keep Scenery and Texture directories together. Do not flatten or rename them unless the package instructions require it.
  3. Disable competing KMCO scenery. Temporarily deactivate every other Orlando airport package, including airport definitions bundled with larger regional products.
  4. Register the package. Use the method specified in its documentation. Our guide to registering legacy and add-on.xml scenery in Prepar3D explains folder selection, scenery priority and missing-entry checks.
  5. Set the airport above broad regional scenery. A KMCO-specific package normally needs higher priority than base, mesh or regional layers unless its read-me gives different instructions.
  6. Restart and inspect the airport. Test during daylight and at night, then introduce AI traffic only after the scenery itself displays correctly.

Why is KMCO missing or displaying incorrectly?

Most KMCO problems come from an incorrect library path, a second airport definition or an incompatible terrain component.

  • No visible change: confirm that Prepar3D is registered to the package folder containing Scenery, not an extra parent directory or the BGL folder itself.
  • Duplicate terminals, jetways or parking: disable other KMCO packages one at a time. A second airport file may be hidden inside a regional scenery collection.
  • Sunken runways or an airport plateau: look for another KMCO elevation correction, terrain BGL or regional mesh. Test the AFCAD package's terrain component separately if its documentation permits that.
  • Layout present but objects missing: restore the complete folder structure and textures. A working airport BGL does not prove that every legacy object format is supported by that Prepar3D version.
  • AI aircraft use the wrong stands: verify matching airline parking codes and adequate stand radii. Also confirm that only one airport definition is controlling the parking layout.
  • Runway, ILS or taxiway data disagree with navigation data: the scenery and navigation database may represent different revisions of Orlando International. Changing layer priority cannot reconcile two different airport layouts.
AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members