How do you plan KJFK to KPHX in a flight simulator?

To plan KJFK to KPHX in a general flight simulator, generate an IFR route for the exact aircraft and selected weather, then choose runway-compatible JFK departure and Phoenix arrival procedures. Verify every waypoint against matching navdata, calculate wind-aware fuel and an alternate, and load—not blindly accept—the route into the FMS.

This is a simulator-independent planning task applicable to MSFS, X-Plane, FSX and Prepar3D. The great-circle distance between John F. Kennedy International and Phoenix Sky Harbor is roughly 1,865 NM, with the filed route normally longer because of airways, weather and airspace constraints.

KJFK to KPHX flight-planning workflow

The best KJFK to KPHX flight plan is generated for the aircraft, departure time, weather and installed navigation database rather than copied as a permanent route string.

1. Select the exact aircraft profile. Enter the correct variant, engines, payload and reserves. A 737-800 profile is not interchangeable with a 737 MAX or A321, even if all can cover the sector. Many piston aircraft and shorter-range turboprops will require a fuel stop.
2. Set the operating conditions. Use the weather selected in the simulator, including winds aloft, convective weather and expected runway configurations. If the flight uses historical or preset weather, plan against that rather than real-world conditions.
3. Generate a high-altitude IFR route. A realistic route should follow the structure KJFK → departure transition → airways/Q-routes and directs → Phoenix arrival transition → KPHX. The middle portion changes with winds, restricted airspace and available procedures. For a dispatch-style result, our aircraft, fuel and export setup for SimBrief explains the full process.
4. Keep the SID and STAR provisional. Select procedures compatible with the expected runways, but be prepared to change them after receiving simulator ATIS or an ATC clearance.
5. Choose a performance-valid cruise level. This is a westbound flight, so an even RVSM level will normally fit US IFR direction rules. Aircraft weight, winds and maximum altitude still take priority over convention.
6. Calculate complete block fuel. Include taxi, trip, contingency, alternate, final reserve and any justified extra fuel. JFK ground delays and long taxi routes deserve consideration, but arbitrary excess fuel increases take-off weight and burn.
7. Import and audit the plan. Compare the FMS legs with the generated route from beginning to end. Confirm the first fix, airway joins, arrival transition, route distance, altitude restrictions and destination before departure.

Which SID, STAR and runway should you choose?

Choose procedures from the runway configuration and route transition, not simply from the direction of Phoenix on the map.

At KJFK, a westbound flight may initially be routed north or south to fit New York traffic flows. Select a SID authorised for the departure runway whose transition joins the first en-route fix cleanly. JFK also has complicated runway crossings and lengthy taxi possibilities, covered in our JFK runway, procedure and taxi-planning notes.

At KPHX, the arrival should connect from the east or north-east and serve the expected flow towards Runways 7L, 7R and 8, or Runways 25L, 25R and 26. The STAR and instrument approach are separate choices: an arrival can be valid while the selected approach transition is not.

Procedure names, revisions and transitions change between navigation-data cycles, so we do not recommend one permanent SID or STAR. Use the charts matching the installed database and check fixes, restrictions and runway applicability with our practical guide to reading simulator aviation charts.

What cruise altitude and fuel should you use?

For an A320- or 737-class aircraft, FL340 or FL360 may be sensible initial candidates, but the correct level comes from weight, winds, temperature and aircraft performance.

• Cruise level: Use an even westbound level unless ATC assigns otherwise. A heavily loaded aircraft may need to start lower and step-climb after burning fuel; do not enter an altitude above the FMS maximum or close to buffet limits.
• Trip and reserve fuel: Calculate fuel from the exact aircraft profile and forecast winds. A block-fuel figure copied from another variant or weather situation is unreliable.
• Alternate: Choose an airport with suitable weather, runway length and services. KIWA is close but may share the same regional weather; KTUS can provide more geographical separation at the cost of additional diversion fuel.
• Arrival performance: Phoenix heat can produce high density altitude and longer landing distances. Check predicted landing weight, approach speed, braking and runway suitability rather than assuming KPHX's long runways remove every limitation.

Why will the KJFK–KPHX route not load correctly?

Most loading failures come from mismatched navdata, duplicated procedures or an import format the selected aircraft does not fully support.

• Waypoint not found: The planner and FMS probably use different navigation-data cycles. Regenerate the route against the installed data or replace the unavailable airway segment with valid fixes from that database.
• Duplicate fixes or loops: A mistake we see constantly is importing a plan containing procedures and then selecting the SID and STAR again in the FMS. Retain one copy and verify the resulting leg sequence.
• Route ends before the runway: Some imports contain only the en-route section. Add the SID, STAR and approach manually using the aircraft's own navigation database.
• Unexpected discontinuity: Join ordinary route discontinuities only after confirming the tracks make sense. Do not automatically remove a MANUAL or vectors leg because it may represent an intentional ATC-vector segment.
• Route line jumps elsewhere: Identical waypoint identifiers can exist in different regions. Check the fix position, adjacent bearings and leg distance before accepting it.

After any runway or procedure change, inspect the entire arrival again. Look for duplicate transitions, impossible turns, deleted altitude restrictions and a top-of-descent point that no longer fits the revised route.

Can the same plan work in every simulator?

The en-route waypoint sequence can usually be reused, but each simulator and aircraft may require a different file format or manual procedure entry.

Microsoft-family simulators commonly use .pln files, while X-Plane commonly uses .fms; advanced airliners may instead rely on their own company-route format. Older FSX or Prepar3D databases may not recognise newer RNAV procedures or Q-routes even when a planner accepts them.

If using built-in ATC, load an equivalent route into both the simulator and the aircraft avionics. Otherwise, ATC may issue instructions for one plan while the FMS follows another. The FMS remains the final check: never assume a successful file import means every leg, altitude and procedure is valid.