How do you plan a KJFK to KATL flight route?

To plan a KJFK-to-KATL flight in a simulator, generate an IFR route using the same navdata cycle as the aircraft, choose the JFK departure and Atlanta arrival from forecast winds and runway flow, then verify airway joins, altitude constraints, fuel, discontinuities and the approach in the FMC before take-off.

For general flight simulation—including Microsoft Flight Simulator, X-Plane, Prepar3D and FSX—the planning logic is the same. Avoid relying on a permanently fixed route string: preferred routings, procedures and waypoint data can change between AIRAC cycles.

A practical KJFK to KATL flight-planning workflow

The most reliable method is to build the en-route portion first, then add procedures that connect cleanly to its first and last fixes.

1. Select the exact aircraft profile. Choose the aeroplane and engine variant you will fly, because climb performance, optimum altitude, speed and fuel burn differ. Our step-by-step SimBrief planning workflow covers generating and exporting an IFR plan.
2. Match the navigation data. Set the planner to the AIRAC cycle installed in the aircraft or simulator. If they differ, a valid planner route may produce NOT IN DATABASE, missing airway or unavailable-procedure errors in the FMC.
3. Check departure and arrival weather. Use JFK's wind and active runway configuration for the SID. Use the forecast weather near the expected arrival time for Atlanta. Keep the JFK airport diagram and departure charts and the Atlanta arrival and approach plates beside the flight plan.
4. Generate and inspect the en-route path. A sensible KJFK–KATL routing normally runs south-west through or near Pennsylvania, Virginia and Tennessee before approaching Atlanta from the north. Airway-based plans may use fixes in the PSB–MOL–VXV corridor, but these are examples rather than mandatory waypoints. Reject a route containing loops, a return towards New York or a large unexplained coastal detour.
5. Add a compatible SID and STAR. The SID's final fix must connect to the first en-route leg, while the STAR's entry fix must join the route from the correct direction. Our guide to loading SIDs, STARs and transitions explains how to select and verify them in an FMC.
6. Choose cruise altitude and fuel. For an A320- or 737-class jet, a level around FL320–FL360 is often practical on this sector, subject to mass, winds and aircraft limits. As the overall course is south-westbound, US IFR direction rules normally favour an even flight level. Let the aircraft profile calculate trip, taxi, contingency, alternate and reserve fuel rather than copying a fixed fuel quantity.
7. Load and verify the route. Compare every FMC leg with the generated operational flight plan. Check the origin, destination, runway, procedure transitions, route distance, altitude constraints, approach and missed approach before activating it.

Which KJFK SID and KATL STAR should you choose?

Choose procedures from the expected runway flow and their connection to the en-route route, not simply because their names appeared in somebody else's flight plan.

At JFK, select a departure approved for the take-off runway and leading towards the first south-westbound route fix. At Atlanta, choose an arrival entered from the north or north-east if that is where the final en-route leg leaves you. The arrival transition must match the last route fix; otherwise the FMC may draw a sharp turn, a long dogleg or a route discontinuity.

KATL has five parallel runways and normally operates in an eastward or westward flow, so the landing runway may change while you are airborne. It is reasonable to plan the likely runway family initially, then revise the arrival or approach if weather or ATC changes the assignment. After any change, recheck altitude and speed constraints from the first affected leg onwards.

How long does a JFK to Atlanta simulator flight take?

A typical jet flight takes about 1 hour 50 minutes to 2 hours 20 minutes airborne, with roughly 2 hours 20 minutes to 2 hours 50 minutes of gate-to-gate time.

JFK taxi queues, Atlanta sequencing, headwinds and a longer runway transition can move the result outside those ranges. Do not shorten the fuel plan merely because the simulator's route preview shows a favourable estimated time.

Why will the KJFK to KATL route not load correctly?

A KJFK–KATL route usually fails because of mismatched navdata, an invalid airway entry, duplicated procedure fixes or conflicting plans in the simulator and aircraft FMC.

• Waypoint or airway missing: regenerate the plan for the aircraft's AIRAC cycle. When entering an airway manually, first enter its valid joining fix; an airway name cannot be inserted from an unrelated waypoint.
• Route doubles back: the selected SID exit or STAR entry does not match the en-route segment. Change the transition rather than forcing a direct leg across the procedure.
• Duplicate waypoint: the final route fix may already be part of the STAR. Remove the duplicate en-route occurrence only after confirming the intended sequence on the chart.
• Route discontinuity: close it only when the surrounding legs should connect directly. A discontinuity after a vectors leg can be intentional; deleting it blindly may create an unsafe shortcut towards the runway.
• World map and FMC disagree: some import formats omit procedures or encode them differently. If using built-in ATC, make sure the simulator and FMC contain matching routes rather than allowing each to follow a different plan.

What should you check before take-off?

Before take-off, confirm that the displayed route is continuous, correctly constrained and consistent with the charts and fuel plan.

• The FMC identifies KJFK as the origin and KATL as the destination.
• The SID, transition and first airway fix join without a loop or unexplained gap.
• The last en-route fix connects to the selected STAR transition.
• Altitude and speed constraints agree with the procedure charts.
• The landing runway, approach transition, final course and minimums have been briefed.
• Fuel includes taxi, trip, contingency, alternate when required and final reserve allowances.
• The legs page contains no unintended manual entries, duplicate fixes or direct shortcuts.