How do you plan a KJFK to KMIA flight route in a simulator?

To plan KJFK to KMIA in a flight simulator, build an IFR high-altitude route using matching navigation data and forecast winds, then choose a Kennedy SID, cruise level, Miami STAR and approach for the active runways. Check every airway and waypoint before loading the plan into the aircraft’s FMC or GPS.

This general-simulator workflow applies to Microsoft Flight Simulator (MSFS), X-Plane, Prepar3D and FSX. The controls differ, but the route-planning decisions are the same.

What should a KJFK–KMIA flight plan look like?

For a Boeing 737- or Airbus A320-class jet, expect approximately 949 nautical miles direct and roughly 1,050–1,200 nautical miles after airways and procedures. Airborne time is commonly around 2 hours 40 minutes to 3 hours 15 minutes, depending on winds, traffic routing and runway configuration.

There is no single permanent route between Kennedy and Miami. US traffic flows, winds, runway use and AIRAC revisions can all change the preferred clearance.

How do you build the route step by step?

1. Check weather and runway use. Review the departure wind at KJFK, arrival conditions at KMIA, en-route winds and the weather at potential alternate aerodromes. If using preset simulator weather, plan against that rather than unrelated live conditions.
2. Select the exact aircraft profile. Aircraft variant, engine type, passenger and cargo load, cost index and planned cruise speed all affect fuel and altitude. Do not calculate an A320 plan and load its fuel figures into a 737 simply because their route is identical.
3. Generate an IFR route. Enter KJFK and KMIA in a flight planner, choose an appropriate high-altitude routing and calculate the operational flight plan. Our step-by-step SimBrief workflow for the JFK–Miami city pair covers the required entries and OFP checks.
4. Inspect the route rather than accepting it blindly. Confirm that every airway joins at the stated waypoint and that the route does not double back. If recreating a scheduled service, use our method for finding and validating a real airline routing.
5. Add runway-compatible procedures. Choose a KJFK SID whose transition joins the first en-route fix, followed by a KMIA STAR that connects from the final airway. Select the approach separately because the landing runway may change during the flight.
6. Review altitude, fuel and alternate. Check the aircraft can reach the planned cruise level at its departure weight, then review taxi, trip, contingency, alternate, reserve and any extra fuel. Block fuel is not the same as trip fuel.
7. Validate the loaded plan. Step through every FMC or GPS leg, looking for route discontinuities, duplicate fixes, sharp turns and unexpected altitude constraints before departure.

Can you use an example airway route?

A conventional airway spine seen in older and compatible navigation datasets is:

CANDR J60 DRAIK J60 PSB J61 HUBBS J193 PXT J191 BARTL J121 CHS J79 OMN

Treat this as an illustrative en-route section, not a guaranteed clearance. It deliberately excludes a SID, STAR and approach. A newer AIRAC may offer different RNAV or Q-route options, and some databases may no longer recognise every segment. Prefer the route generated against the same navigation cycle used by your aircraft.

How should you choose the JFK SID and Miami STAR?

Choose the runway first, then select procedures whose transitions connect cleanly to the en-route plan. Copying an old SID or STAR name is one of the most common causes of missing waypoints and broken flight plans.

At KJFK, check that the departure procedure supports the runway in use and leads towards the route’s first airway fix. At KMIA, select an arrival from the north or north-east that is compatible with the expected landing flow. The STAR normally feeds the terminal area; it is not itself the ILS, RNAV or visual approach.

If flying without online or simulator ATC, choose the most likely procedures before departure and revise the arrival when the destination weather becomes clearer. After any runway change, recheck the STAR transition, approach, missed approach and every altitude or speed constraint.

What cruise altitude and fuel should you use?

For most jet plans on this south-westerly track, an even RVSM level such as FL340, FL360 or FL380 is a sensible starting point. The planner may choose lower if the aircraft is heavy or higher if the wind and weight make it worthwhile; an ATC clearance takes precedence when one is being followed.

Use aircraft-specific fuel calculations rather than a fixed KJFK–KMIA quantity. Review the fuel remaining at Miami, the alternate requirement and final reserve as separate values. A nearby alternate such as Fort Lauderdale may be convenient, but it can share Miami’s thunderstorms or low cloud, so a more distant aerodrome can be the better planning choice.

How do you load the route into the simulator?

Use one route-loading method and then verify the result in the aircraft. Importing through both the simulator’s flight-planning screen and the aircraft’s own integration can create duplicate waypoints or conflicting procedures.

• Supported airliner integration: import the route through the aircraft’s FMC or EFB, then check whether procedures and performance data must be entered separately.
• Microsoft Flight Simulator: choose the import path supported by the specific aircraft rather than assuming every cockpit synchronises with the World Map. Our guide explains the MSFS 2020 and 2024 import methods for SimBrief plans.
• Generic GPS or older simulators: export a format recognised by that simulator or aircraft, then compare the imported fixes with the original plan.

For an Airbus or Boeing, follow the complete airliner FMC loading and leg-check procedure rather than activating LNAV immediately after import.

Why will the KJFK–KMIA route not load correctly?

Most loading failures come from mismatched navigation data, incompatible procedures or importing the same plan twice.

• NOT IN DATABASE: the planner knows a waypoint or procedure that the aircraft’s AIRAC does not. Match the navigation cycles or regenerate the route using fixes available in the aircraft.
• Invalid airway segment: the entry or exit fix is not on that airway in the installed database. Check both endpoint fixes rather than forcing a direct connection.
• Route discontinuity: inspect the legs on either side before clearing it. A gap between an airway and procedure may indicate the wrong transition, while a vectors segment may be intentional.
• Duplicate or looping legs: remove one source of flight-plan synchronisation and reload the route. This often happens when the simulator plan and aircraft FMC both insert procedures.
• Different runway from simulator ATC: replace the arrival and approach, then review all downstream constraints. Built-in ATC may not reproduce the runway or route selected by an external planner.

Can you fly direct from KJFK to KMIA?

Yes, a direct GPS route is acceptable for a quick simulator flight, but it does not reproduce normal airline routing or terminal procedures. For realistic airliner operations, use an IFR airway or RNAV route with a connected SID and STAR, while retaining direct-to as a tool for an ATC shortcut or recovery from a route problem.

What should you check before take-off?

Before take-off, confirm the route begins on the selected runway and SID, reaches the first en-route fix without a gap, and ends through the intended STAR and approach.

• The FMC route matches the operational flight plan.
• The displayed track has no loops, unexplained gaps or extreme turns.
• The initial cleared altitude is not confused with the final cruise level.
• Take-off performance uses the actual runway, weight and weather.
• Fuel on board matches block fuel rather than trip fuel alone.
• The Miami arrival and alternate remain suitable for the simulated weather.