How do you plan KDEN to KJAC in a flight simulator?

Plan KDEN to KJAC as a short, high-terrain IFR flight: use matching AIRAC data, select a Denver departure and Jackson Hole arrival for the active runways, connect them with validated airways or RNAV fixes, then check weather, terrain, fuel and the missed approach before loading the plan into both the simulator and aircraft FMS.

This is a general flight-simulator plan rather than a product-specific menu sequence. The same decisions apply in MSFS, X-Plane, Prepar3D and FSX, although procedure availability and simulator ATC behaviour vary with the installed navigation data.

A practical KDEN–KJAC route structure

A usable route should be built around the active runways and matching procedure transitions, not copied as a permanent string. The direct distance is roughly 350 nautical miles, but the filed distance will increase when departures, arrivals and terrain-compatible routing are included.

Use this structure:

KDEN [SID/transition] [validated airway or RNAV fixes] [STAR or approach transition] KJAC

Choose a Denver transition that sends the aircraft north-west without a large turn back towards the airport. At the Jackson Hole end, the final en-route fix must connect cleanly to the selected arrival or approach transition. Our guide to adapting real-world routes to simulator navdata explains why a route should be checked rather than copied blindly.

How do you build the route step by step?

Build the route only after setting the aircraft, weather and expected runways.

1. Match the navigation data. Check that the planner, simulator and aircraft FMS use the same AIRAC cycle where possible. A cycle mismatch commonly produces NOT IN DATABASE, missing airways or procedure transitions that do not join.
2. Set the airport conditions. Review winds, visibility, cloud, runway condition and instrument approach availability at both airports. KJAC has one runway, 01/19, so a wind or approach change can reverse the whole arrival.
3. Generate the en-route backbone. Use a route planner to obtain validated RNAV fixes or airways rather than drawing an unchecked direct line across the Rockies. We cover suitable tools, export formats and navdata checks in our summary of free flight-planning and route-export options.
4. Add the SID and arrival separately. Select transitions that connect to the first and last en-route fixes. Do not force a STAR if none joins sensibly; a published approach transition or expected radar vectors may be the better representation.
5. Inspect the vertical profile. Compare the cruise altitude with charted minimum en-route altitudes and the planner’s terrain display. Check every descent constraint and brief the missed approach before departure.
6. Calculate performance and fuel. Include taxi, climb, trip, contingency, approach, missed approach, alternate and reserve fuel. KDEN and KJAC are both high-elevation airports, so temperature and density altitude affect take-off, landing and go-around performance.
7. Cross-check the loaded plan. Compare the simulator flight plan, FMS legs page and map waypoint by waypoint. Confirm there are no duplicate procedures, gaps, unexpected course reversals or direct legs through unsafe terrain.

For the wider clearance, departure, en-route, descent and missed-approach sequence, use our complete simulator IFR workflow.

Which runway and approach should you choose at KJAC?

Choose runway 01 or 19 from the wind, reported conditions, approach minima and aircraft performance rather than from the shortest map track.

Jackson Hole sits at about 6,451 feet above sea level and its single runway is approximately 6,300 feet long. That combination leaves less performance margin than a long, low-elevation runway, especially with heat, contamination, a tailwind or a heavy aircraft.

• Load only an approach that exists in both the chart set and aircraft database.
• Do not assume an ILS is available for both runway directions.
• Keep the published minimum altitudes until established on the correct approach segment.
• Enter the missed-approach altitude and verify every missed-approach fix before starting down.
• If the simulator expects vectors, retain the discontinuity until cleared or established; do not close it with an arbitrary direct leg across terrain.

A visual approach is suitable only when the valley, runway environment and surrounding terrain are clearly visible. Low cloud or mountain obscuration removes the margin that makes an improvised visual arrival acceptable.

What cruise altitude and fuel should you plan?

Select the cruise level from terrain clearance, winds, aircraft performance and route length; there is no universal altitude or fuel quantity for KDEN to KJAC.

The north-westbound magnetic course normally favours an even IFR flight level under the US semicircular system, although the cleared route and ATC assignment take precedence. For descent planning, use roughly 3 nautical miles per 1,000 feet to lose, then add distance for speed reduction, procedure constraints and wind.

Do not choose an alternate merely because it is the nearest airport on the map. It needs usable weather, a suitable approach and runway, acceptable terrain access and enough fuel for the missed approach followed by the diversion.

Why does a KDEN to KJAC plan fail in the simulator?

Most failures come from mismatched navdata, disconnected procedures or loading the route into only one navigation system.

• Missing fixes or procedures: rebuild the route using the cycle installed in the aircraft rather than replacing unknown fixes with arbitrary direct legs.
• A discontinuity before the approach: determine whether it represents expected vectors or a genuinely broken transition. Preserve it for vectors; otherwise select the correct published transition.
• Simulator ATC ignores the FMS: file or import the route into the simulator’s flight-planning system as well. Our explanation of how simulator ATC receives a flight plan covers the difference between an ATC plan and an FMS-only route.
• Duplicate waypoints: some aircraft import the simulator plan automatically. Check before entering the same SID, STAR or approach manually.
• Arrival starts too late: calculate descent from altitude above KJAC’s field elevation, not sea level, and allow extra distance for slowing before the approach.
• Landing or go-around performance is marginal: reduce weight, wait for better conditions or use a more suitable aircraft rather than assuming the simulator will compensate for density altitude.