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

To plan KJFK to ZSPD in any general flight simulator, generate an AIRAC-matched long-haul route for the exact aircraft, then choose runway-dependent SIDs and STARs, calculate wind-aware fuel and alternates, and verify every airway and waypoint in the FMC. Do not rely on a fixed route: winds, airspace restrictions and procedures change.

What route should you use from KJFK to ZSPD?

Use an AIRAC-valid, wind-optimised route generated for the intended flight date rather than a permanent waypoint string. An old route copied from a previous flight may contain retired fixes, unavailable airways or airspace that the operator could not legally use.

The route should have this structure: KJFK – SID – departure transition – en-route airways and fixes – arrival transition – STAR – approach – ZSPD. A shortest-path result commonly follows a northern, high-latitude corridor, but airspace avoidance may move the flight towards a longer North Pacific or other permitted routing.

Our aircraft-to-OFP SimBrief workflow covers entering the airports, selecting the correct airframe profile and generating an operational flight plan. Treat the generated route as a dispatch proposal that still needs checking, not text to paste blindly into the FMC.

KJFK–ZSPD planning baseline

Kennedy to Shanghai Pudong is an ultra-long-haul sector of approximately 6,400 NM by great-circle distance, with the planned distance normally higher.

Do not confuse ZSPD, Pudong, with ZSSS, Hongqiao. That error can survive route generation and only become obvious when the arrival procedures or runway layout fail to match.

How do you build the KJFK to ZSPD flight plan?

Build the route from matching navigation data, a suitable aircraft profile and the weather expected along the whole sector.

1. Match the AIRAC cycles. The planner and aircraft FMC should use the same navigation-data cycle. If they differ, valid planner waypoints may produce NOT IN DATABASE, missing airways or unavailable procedures in the aircraft.
2. Set the exact aircraft and payload. Select the correct variant and engine profile where available, then enter passengers, cargo and departure time. A generic widebody profile can produce misleading fuel and climb figures.
3. Generate and inspect the en-route path. Compare suggested routes by distance, winds and any avoidance settings. Inspect the map for loops, sharp reversals and implausible direct segments rather than accepting the first result.
4. Decide which operational rules to reproduce. A fictional offline flight can use the shortest simulator-valid route. To recreate an airline operation, use our method for reconstructing and validating real airline routings, including the operator and period being simulated.
5. Add terminal procedures after checking runways. Select the expected KJFK departure runway and a SID whose transition joins the first en-route fix. At ZSPD, choose a STAR and transition that connect cleanly to the expected approach. Our procedure-loading and discontinuity checks explain how to join these sections without creating duplicate legs.
6. Calculate fuel and alternates. Include taxi, trip, contingency, alternate and final-reserve fuel, plus any extra required by weather or remote routing. The wider decisions are covered in our long-haul fuel, payload and alternate planning guidance.
7. Load and verify the route. Export in the format intended for the simulator or aircraft, then compare the FMC legs with the operational flight plan. Check every discontinuity, coordinate, airway exit, altitude constraint and total distance before departure.

Choose one route source as the authority. Loading procedures in the simulator’s flight planner and then adding them again in an add-on aircraft FMC commonly creates duplicated SIDs, STARs and approaches.

Should the route cross Russian airspace?

Only if that matches the operator, date and ruleset being simulated. Airspace permission varies by nationality, operator and geopolitical period, while the simulator itself may impose no restriction at all.

• Fictional or unrestricted offline flight: use the most efficient AIRAC-valid route if operational restrictions are not part of the scenario.
• Real airline recreation: apply the relevant avoided FIRs and compare the result with the aircraft’s range and payload capability.
• Online ATC flight: follow the routing and restrictions issued for that network or event, even when they differ from the simulator’s automatic suggestion.

If an avoidance route pushes the aircraft beyond its limits, reduce payload, select a more capable variant or plan a technical stop. Adding fuel beyond maximum take-off weight is not a valid fix.

Aircraft, fuel and alternate planning

A long-range widebody must remain within take-off, landing and fuel limits for the actual route rather than merely having a published range above 6,400 NM. Winds, payload, reserves and airspace avoidance can consume much of the apparent margin.

For twin-engine operational realism, include EDTO or ETOPS considerations and suitable en-route diversion airports. High-latitude routes can leave long gaps between practical alternates, and a geographically nearby airport is not automatically suitable for the aircraft, weather or runway state.

ZSSS may appear attractive as a destination alternate because it is close to Pudong, but it can share the same regional weather and disruption. Select an alternate using forecast conditions, runway suitability, fuel requirement and the operation being simulated.

How should cruise altitude and step climbs be planned?

Use the performance-calculated initial cruise level and step climbs from the aircraft profile, then revise them for ATC and weather. Starting too high at maximum weight can cause poor climb performance or an altitude the aircraft cannot maintain.

Chinese operations may present assigned levels in metres or as converted flight levels, depending on the charts and ATC service being used. Keep the units consistent and follow the controlling service rather than substituting a familiar round flight level.

Why does the FMC reject a generated route?

Most KJFK–ZSPD route failures come from mismatched navdata, malformed coordinates or duplicated terminal procedures.

Preflight checks before leaving KJFK

A valid-looking route is ready only after its geometry, performance and terminal procedures agree across the planner and aircraft.

• Confirm the origin is KJFK and the destination is ZSPD.
• Compare the FMC route distance and waypoint count with the operational flight plan.
• Inspect the legs display for loops, route reversals and unexamined discontinuities.
• Verify that the KJFK SID transition joins the first en-route segment.
• Confirm the ZSPD STAR, runway and approach form one continuous arrival.
• Check take-off weight, predicted landing weight, reserve fuel and alternate fuel.
• Review planned step climbs, altitude units and remote diversion airports.
• Recheck ZSPD weather and the arrival runway before descent, then update the STAR or approach if required.