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

To plan KJFK to RJTT in a flight simulator, generate a date-specific long-haul route using matching AIRAC navigation data, then select the KJFK SID and RJTT STAR for the forecast runways. Validate the North American, North Pacific and Japanese segments, calculate wind-aware fuel and alternates, and load the route into the aircraft’s FMS.

This general flight-simulation workflow applies to Microsoft Flight Simulator, X-Plane, Prepar3D and FSX. The exact import controls vary by simulator and aircraft, but the planning principles are the same.

How to build a KJFK to RJTT flight plan

1. Confirm the airports. KJFK is New York John F. Kennedy International Airport and RJTT is Tokyo Haneda Airport. Do not confuse Haneda with RJAA, Tokyo Narita—a mistake that can remain unnoticed until the arrival is loaded.
2. Select the exact aircraft variant. Use a long-range aircraft profile matching your simulated model, engines and units. A generic profile can produce incorrect fuel, climb performance, maximum take-off weight and step-climb predictions.
3. Set the intended date and departure time. Winds matter greatly on this westbound sector, and North Pacific organised tracks can change daily. Any track used must be valid when the aircraft reaches the oceanic segment, not merely when it leaves KJFK.
4. Generate the operational flight plan. Enter KJFK and RJTT, the aircraft profile, payload and suitable alternates. Our practical SimBrief planning workflow explains how to generate an OFP and export it in a simulator-compatible format.
5. Inspect the route rather than accepting it blindly. Check that it progresses northwest across North America towards Alaska and the North Pacific before continuing into Japan. Investigate unexplained loops, very long direct legs or a route that heads across the Atlantic.
6. Add runway-specific procedures. Select the KJFK departure and RJTT arrival only after checking forecast winds, expected ATC flow and procedure compatibility. Use the appropriate charts to verify transitions, restrictions and approaches; our guide to reading aviation charts in a simulator covers that cross-check.
7. Calculate fuel and alternates. Include taxi, trip, contingency, alternate, final-reserve and any required extra fuel. For a twin-engine aircraft, use sensible EDTO or ETOPS en-route alternates rather than treating the entire Pacific as an unrestricted direct leg.
8. Load and verify the FMS. Import the plan if your aircraft supports it, or enter the airways, fixes and coordinates manually. Compare every route page and the LEGS display against the operational flight plan before departure.

What should the KJFK–RJTT route look like?

A realistic route normally follows this broad structure: KJFK – SID – North American airways and fixes – North Pacific segment – Japanese airways and fixes – STAR – RJTT.

The Pacific portion may use a North Pacific ATS route, a PACOTS track or an operator-preferred route assembled from published fixes and coordinates. The shortest great-circle line is not automatically the best route: upper winds, restricted airspace, available alternates and track validity can all move it north or south.

Do not copy an oceanic track or complete route string from an unrelated date. A filed route is useful only when its procedures, track message and navigation cycle still match; see our advice on recreating real-world airline routes without inheriting outdated fixes.

How much fuel and flight time should you plan?

KJFK to RJTT is roughly 5,870 nautical miles by great-circle distance, while the flown route will normally be longer. A westbound flight commonly takes about 13–15 hours airborne, but winds, routing, aircraft type and payload can move the result outside that range.

Fuel must come from the aircraft’s performance profile and forecast winds, not a simple distance calculation. Check these items before accepting the plan:

• planned zero-fuel, take-off and landing weights;
• trip fuel for the actual winds and route;
• contingency, destination-alternate and final-reserve fuel;
• extra fuel for expected holding, runway changes or poor weather;
• en-route alternates with adequate runway length and suitable weather;
• an achievable initial cruise level followed by weight-dependent step climbs.

RJAA may be considered as a destination alternate when conditions and aircraft requirements permit, but its proximity means the same weather system can affect both Tokyo airports. A more distant alternate may be appropriate. Our broader long-haul planning checklist covers payload, reserves, alternates and cruise-level decisions in more depth.

The flight also crosses the International Date Line. KJFK departures usually arrive in Tokyo on the next local calendar day, so keep UTC, simulator time and local arrival time separate when configuring weather or scheduled operations.

How should the route be entered in the FMS?

Enter the en-route section first, then attach procedures and inspect the resulting legs in sequence.

1. Check the navigation cycle. The planning tool, simulator and aircraft database should use matching AIRAC data wherever possible.
2. Enter or import the core route. Verify every airway exit and oceanic waypoint against the OFP.
3. Select the departure. Add the KJFK runway, SID and transition expected for the route.
4. Select the arrival. Add the RJTT STAR, transition and approach appropriate to the expected landing runway.
5. Review discontinuities. Remove an accidental break between connected legs, but retain a deliberate vector discontinuity when the chart expects ATC vectors.
6. Inspect route geometry. Use the navigation display at a wide range to find loops, doubled procedures and points placed in the wrong hemisphere.
7. Complete performance data. Enter the aircraft’s actual weights, reserves, cruise level and winds rather than relying on placeholder values.

Why does the FMS reject or distort the route?

Most KJFK–RJTT route failures come from mismatched navigation data, duplicated procedures or incorrectly formatted oceanic coordinates.

After correcting an import problem, recheck the full route rather than only the rejected fix. A single missing Pacific waypoint can cause the FMS to connect two distant points directly while still displaying a technically valid route.