Plan a KJFK to EGLL flight route with valid North Atlantic tracks, realistic fuel and alternates, and checks that prevent FMS errors.
Plan KJFK to EGLL with a dispatch tool using the exact aircraft, planned departure time and forecast weather. Select a valid eastbound North Atlantic track or random oceanic route, then verify the SID, oceanic entry and exit, EGLL STAR, alternates, fuel and every FMS waypoint before departure.
This method applies to general flight simulation, including Microsoft Flight Simulator, X-Plane, Prepar3D and FSX. There is no permanent KJFK–EGLL route: winds, runways, North Atlantic tracks and navigation data change, so an airway string copied from an old flight may be invalid.
How should you build a KJFK to EGLL flight plan?
Build the flight plan in dispatch order, starting with the aircraft and schedule rather than choosing waypoints by hand.
- Select the exact aircraft profile. Use the correct variant, engines, weights and performance profile. A Boeing 777, 787 and Airbus A330 may receive different initial cruise levels, speeds and fuel figures for the same city pair.
- Enter KJFK, EGLL and the planned UTC time. Use forecast winds for the period when the aircraft will cross the Atlantic. Track validity is determined by the estimated oceanic entry time, not merely the KJFK departure time.
- Choose suitable alternates. The destination alternate must accept the aircraft and have adequate weather, runway length and fuel coverage. EGKK or EGSS may work for some flights, while a more distant airport such as EGBB can provide better weather separation; do not assume the nearest London airport is automatically suitable.
- Generate the en-route section. A dispatch planner can calculate winds, track availability, step climbs and fuel. Our step-by-step SimBrief planning guide explains the aircraft profile, route-generation and operational flight-plan fields.
- Check the route structure. It should follow the pattern
KJFK → SID → domestic airways → oceanic entry → oceanic waypoints → oceanic exit → European airways → EGLL STAR. Our North Atlantic planning notes cover oceanic procedures, alternates and crossing preparation in more depth. - Add procedures for the expected runways. Select a KJFK SID and EGLL STAR that connect cleanly with the en-route fixes, but be prepared to change them when the wind or ATC runway changes. Verify altitude restrictions and transitions against charts; our simulator chart-reading guide shows what to check.
- Import or enter the plan and inspect every leg. Confirm waypoint order, coordinates, airway joins, discontinuities, total distance and destination. An imported route is not ready merely because a magenta line appears.
Should you use a NAT track or a random oceanic route?
Use a published North Atlantic track only when its direction, validity period and available levels fit your estimated crossing; otherwise, a valid random route may be the better choice.
| Option | Choose it when | Main check |
|---|---|---|
| Published NAT track | The track is valid at oceanic entry and suits the aircraft’s direction and flight level | Use that day’s actual coordinates and validity window, not an old track letter |
| Random route | The flight is outside the organised track period or winds favour another crossing | Validate every coordinate, oceanic boundary fix and airway connection |
Eastbound organised tracks generally serve the overnight flow towards Europe, but that does not make a track compulsory for every simulator flight. A planner may legitimately produce a random route, especially outside the track window. If flying with online ATC, file the routing and levels required by that service rather than assuming the generated plan will be cleared unchanged.
How much fuel and what cruise altitude should you use?
Fuel and cruise altitude must come from the selected aircraft’s performance calculation, not a fixed KJFK–EGLL figure.
The routed distance is normally around 3,000–3,300 nautical miles, and a modern airliner often spends roughly six to eight hours airborne. Jet-stream strength, routing, departure delays and Heathrow holding can shift both figures substantially.
- Fuel: Include taxi, trip, contingency, destination-alternate, final-reserve and any extra holding fuel. Add ETOPS or en-route alternate planning if the aircraft simulation and intended realism call for it.
- Initial altitude: A heavy wide-body may begin around the low-to-mid thirty-thousand-foot range, but the aircraft’s weight and track level govern the actual choice.
- Step climbs: Enter planned climbs only where performance permits. Treat them as requests when using ATC rather than guaranteed clearances.
- Arrival margin: EGLL congestion and runway changes make extra holding or rerouting fuel sensible when the forecast or traffic warrants it.
Why does the FMS reject or alter the imported route?
The FMS usually rejects a KJFK to EGLL route because its navigation database differs from the planner’s data, its coordinate format is unsupported, or procedures have been inserted twice.
- Waypoint not in database: Align the planner and aircraft navigation-data cycles, then regenerate the route. Do not replace an unknown fix with a similarly named one unless charts confirm it.
- Oceanic coordinates rejected: Different avionics accept different latitude-and-longitude formats. Re-enter the coordinates in the format required by that FMS and verify each point on the map.
- Duplicated SID or STAR: This happens when the imported plan already contains a procedure and the same procedure is selected again in the cockpit. Remove one copy and check the resulting airway join.
- Route discontinuity: Clear a discontinuity only when the fixes genuinely connect. A charted vectors segment may be intentional and should be handled with ATC vectors or an appropriate direct-to clearance.
- Unexpected simulator routing: Some simulator planners recalculate imported routes or load only the en-route portion. Compare the cockpit legs page with the operational flight plan before departure.
If automatic import produces a confused route, use our method for entering and checking a route manually in the FMS. Regardless of the loading method, confirm the first SID fix, oceanic coordinates, exit fix, STAR transition, destination runway and total distance before take-off.