Compare KJFK scenery add-ons for Prepar3D, from airport makeovers to Canarsie approach lights, AFCAD parking and runway-operation updates.
For Prepar3D, freeware John F. Kennedy International Airport (KJFK) options include two airport scenery packages, an AFX correction for the Parkway Visual/Canarsie lead-in lights, and an AFCAD-style airport layout update. Choose one main KJFK package; do not stack competing airport files, because duplicate layouts commonly cause overlapping buildings, parking conflicts and runway problems.
Which Prepar3D KJFK scenery add-on should I choose?
Choose an airport scenery package for visual improvements, or an AFX/AFCAD file when your priority is approach lighting, parking or runway operations.
| Option | Choose it when | Main changes |
|---|---|---|
| General KJFK airport enhancement | You want a straightforward improvement over the stock Prepar3D airport. | Adds dedicated KJFK scenery files and improved airport detail. |
| Terminal 5 and Terminal 8 KJFK makeover | You want a more substantial rebuild with revised parking. | Rebuilds Terminal 5, adds the Terminal 8 concourse and provides an option for crosswind runway operations. |
| Canarsie lead-in-light AFX correction | You mainly want the Parkway Visual, or Canarsie, lighting corrected. | Adjusts lead-in lighting associated with the procedure on the Runway 13L/31R alignment. |
| Revised KJFK AFCAD airport file | You want updated parking and different runway-operation options without a complete terminal makeover. | Revises airport layout and operational data, with optional crosswind runway activation. |
The terminal makeover and the general enhancement overlap in purpose, so treat them as alternatives. The AFX and AFCAD downloads are operational corrections rather than substitutes for detailed terminal models, although they may still replace the airport-definition file controlling runways, taxiways and parking.
These packages represent the airport data and buildings included by their authors; they are not guarantees of a present-day KJFK layout. Check the download description and included documentation if exact gate numbering, terminal construction or present-day airline parking matters to your flight.
Can I combine multiple KJFK scenery packages?
Usually not: the safest Prepar3D configuration has one active KJFK airport definition and one matching set of visual scenery files.
- A full airport package may already contain its own AFCAD-style file, even when that file is not prominently named.
- Crosswind and standard runway-operation variants are normally alternatives. Do not activate every optional BGL at once.
- An AFX correction should only be placed over another KJFK package when its documentation says the combination is supported.
- Scenery-layer priority cannot reliably cure contradictory aprons, exclusions, parking positions or elevation data.
Before changing packages, disable the old KJFK scenery layer and remove any optional airport file left active elsewhere. A mistake we see constantly is deleting the visible scenery folder while leaving a second KJFK airport BGL in another add-on directory.
Will these KJFK downloads work in Prepar3D v4, v5 and v6?
A Prepar3D compatibility label does not guarantee that a legacy FSX/P3D scenery package has been validated in every later Prepar3D generation.
Plain scenery BGLs and textures are generally more portable than executable modules, but differences in default scenery, elevation handling, materials and installers can still matter. Check which simulator generation the download page or readme names rather than assuming that all Prepar3D versions behave identically.
If an installer recognises only FSX or an older Prepar3D installation, do not point it blindly at the simulator's root folder. Inspect the archive and follow its manual or external-scenery instructions where supplied. This also makes the package easier to disable during troubleshooting.
Why are KJFK buildings doubled or aircraft misplaced?
Doubled terminals, buried aircraft and incorrect AI parking usually indicate a second KJFK airport file or an elevation correction conflicting with the selected scenery.
| Symptom | Likely cause | What to check |
|---|---|---|
| Overlapping buildings, aprons or taxiway signs | Two visual packages or airport-definition BGLs are active. | Disable KJFK layers one at a time and retain one main package. |
| Aircraft float above or sit below the runway | An old elevation file, terrain add-on or mismatched airport definition is active. | Remove earlier KJFK elevation corrections and use the file supplied for the chosen package, if provided. |
| AI traffic parks inside buildings or follows the wrong taxiways | The active AFCAD does not match the visible airport. | Use the airport file bundled with the scenery instead of an unrelated standalone AFCAD. |
| Missing or black terminal objects | Textures, required objects or compatible material support are missing. | Reinstall the complete package, check listed dependencies and confirm that your Prepar3D generation is supported. |
| Canarsie lead-in lights remain unchanged | The AFX correction is inactive or overridden by another KJFK definition. | Check its scenery priority and remove the competing airport file before retesting. |