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

In a general-purpose flight simulator, a realistic KJFK-to-OMDB route should be generated for the aircraft, weather and matching AIRAC cycle, then checked as four parts: KJFK departure, North Atlantic crossing, European/Middle Eastern airways and OMDB arrival. Calculate fuel from that complete route and verify every FMC leg before departure.

The method is the same in Microsoft Flight Simulator, X-Plane, FSX and Prepar3D. What changes is the route importer, available navigation database and depth of the aircraft’s flight-management system.

A realistic KJFK–OMDB route structure

There is no single permanent waypoint string for New York JFK to Dubai International. Winds, Atlantic track availability, active runways, airway changes and airspace restrictions can all alter the filed route.

A typical plan follows this structure:

KJFK [SID] [north-eastern en-route fixes] [oceanic entry] [oceanic waypoints] [oceanic exit] [European and Middle Eastern airways] [STAR] OMDB

The flight normally heads through north-eastern North America, crosses the North Atlantic, continues across Europe and then approaches the Arabian Gulf through a valid eastern corridor. An organised North Atlantic track may be used when its direction and validity period suit the flight, but a random oceanic route is also normal. Do not force a NAT track simply because another KJFK departure used it.

A copied real-world route can become unsuitable when an airway closes or the simulator’s navigation database cannot recognise its fixes. Airspace availability around Eastern Europe and the Middle East also needs checking if the aim is operational realism rather than an unrestricted offline flight.

Building the KJFK to OMDB flight plan

Build the route with a long-haul planning tool, then inspect it instead of importing it blindly.

1. Select the exact aircraft profile. A generic Boeing 777 profile may calculate different fuel, climb and cruise results from the specific 777 variant installed in the simulator. Match engines and weight options where the planner supports them.
2. Generate the operational flight plan. Enter KJFK and OMDB, departure time, payload, forecast winds and a suitable destination alternate. Our walkthrough of the route, aircraft-profile and fuel fields in SimBrief covers the complete setup without duplicating it here.
3. Match the AIRAC cycle. The planner and aircraft FMC should use the same navigation-data cycle. If they differ, an airway may appear broken or the FMC may report NOT IN DATABASE. Regenerate against the aircraft’s cycle or replace unavailable fixes using one consistent database.
4. Inspect the route on a map. Look for loops, sudden reversals, implausibly long direct legs and airways that do not meet at a common fix. Pay particular attention to the oceanic entry and exit points.
5. Validate the Atlantic crossing. Oceanic latitude-and-longitude formats vary between FMCs and importers. Our oceanic route-planning guidance explains track timing, waypoint formats, diversion planning and common crossing errors.
6. Add runway procedures last. Choose the KJFK SID and OMDB STAR from the expected weather or ATC flow, making sure their transitions connect to the en-route plan.
7. Load and verify the FMC. Step through every waypoint on the flight-plan or LEGS pages, using plan mode where available. Check distances, tracks, altitude constraints, discontinuities and duplicate fixes before activating the route. Our airliner FMC setup guide explains this verification process in more detail.

Which aircraft should you use?

Use a long-range widebody with a profile that accurately models payload, reserves and cruise performance. The KJFK–OMDB sector is unsuitable for an ordinary short-haul configuration without unrealistic fuel or range changes.

A mistake we see constantly is using fuel figures from one aircraft variant with another. Even closely related variants can have different empty weights, tank capacities and cruise performance.

How much fuel and flight time should you plan?

Calculate fuel from the generated route rather than entering a fixed quantity copied from another flight. The great-circle distance is about 5,950 nautical miles, while an operational plan may be roughly 6,000–6,500 nautical miles depending on winds and routing.

Eastbound airborne time is commonly around 12–14 hours, but the aircraft, season, wind field and chosen route can move it outside that range. The fuel plan should include:

• taxi fuel at KJFK;
• trip fuel for the complete route;
• contingency fuel;
• destination-alternate fuel;
• final reserve fuel;
• extra fuel for weather, holding or expected delays.

A heavily loaded widebody may be unable to reach its optimum cruise altitude immediately after departure. Use the lower initial level from the operational flight plan and programme step climbs as fuel burns off. For airline-style realism, also check oceanic diversion airports and any ETOPS or EDTO calculations supported by the planner and aircraft.

OMDW, Dubai World Central, and OMAA, Abu Dhabi, are geographically plausible alternate candidates, but proximity alone is not enough. Confirm weather, runway suitability, approach availability and the fuel needed to reach the selected alternate.

How do you choose the KJFK SID and OMDB STAR?

Choose the SID and STAR from the active or expected runways, then verify that their transitions connect cleanly to the en-route fixes. Do not select a procedure merely because it produces the shortest line on the map.

At KJFK, the departure runway and traffic flow determine which procedures are practical. The SID must support the runway, aircraft navigation capability and first en-route fix. At OMDB, match the arrival transition to the final airway and the expected runway configuration.

Some arrivals end in a vector segment rather than a continuous path to the runway. A VECTOR or related discontinuity may therefore be intentional; deleting it can create an incorrect direct leg across the terminal area. If the runway changes during the flight, replace the arrival and recheck every constraint. Our procedure-loading checklist for SIDs, STARs and transitions covers the correct sequence.

Fixing rejected or broken imported routes

Most broken KJFK-to-OMDB imports come from mismatched navigation data, incorrectly decoded oceanic coordinates or incompatible procedure transitions.

Before pushback, confirm the route distance, first and last en-route fixes, departure runway, destination runway, alternate, initial cruise altitude, planned step climbs, loaded fuel and FMC performance data. That final check catches most errors before they become difficult to repair over the Atlantic.