Plan a realistic KJFK to KDTW flight plan with route, SID/STAR, cruise altitude, fuel, FMC checks and fixes for common navdata errors.
To plan KJFK to KDTW in any flight simulator, generate an IFR route using the same AIRAC cycle as the aircraft, then select the JFK departure and Detroit arrival for the expected runways. Verify airway continuity, cruise altitude, fuel, alternate and FMC discontinuities; never copy a fixed SID or STAR from an old route.
A reliable KJFK–KDTW planning workflow
Build this sector from the en-route core outward, adding procedures only after checking the weather and likely runway flow. The method works in Microsoft Flight Simulator, X-Plane, Prepar3D and FSX, although route importing and stock ATC behaviour differ.
- Set the exact aircraft and payload. Select the correct aircraft variant and engine where the planner supports them. Weight changes the fuel burn, climb performance and sensible cruise level on this relatively short sector.
- Match the navigation data. Ideally, the planner, simulator and aircraft FMC should use the same AIRAC cycle. If an older aircraft database cannot be updated, build the route with fixes and airways available in that database rather than forcing newer procedures into it.
- Check weather and runway availability. Review winds, visibility, pressure and relevant runway closures at both airports. JFK departures and Detroit arrivals depend heavily on runway flow; do not select a SID merely because its line initially points west.
- Generate the en-route route. Enter
KJFKandKDTW, the aircraft, dispatch time, payload and an initial altitude. Our detailed SimBrief setup and export workflow covers route generation, fuel planning and simulator export without relying on a saved route from another AIRAC cycle. - Add compatible procedures. Choose a JFK SID whose runway and transition connect legally to the first en-route fix. At Detroit, choose a STAR from the direction of arrival, followed by the correct runway transition and approach. Use our procedure and airport-chart checks to confirm altitude restrictions, vector legs and approach joins.
- Select a practical cruise level. This is a westbound flight, so an even IFR flight level is normally appropriate in US airspace. Test the aircraft's predicted fuel and climb profile rather than automatically selecting its maximum cruising altitude.
- Plan fuel and an alternate. Include taxi fuel for JFK, trip fuel, contingency, a possible missed approach, alternate fuel and the applicable reserve. Choose the alternate for weather, runway suitability and available services, not simply because it is the nearest airport to KDTW.
- Load and compare every route. Compare the planner route, simulator flight plan and FMC legs page fix by fix. An add-on aircraft may maintain an independent flight plan, while stock ATC may continue following the route loaded through the simulator's planner.
What route should I use from KJFK to KDTW?
There is no permanent KJFK–KDTW route that remains correct across every AIRAC cycle, runway configuration and ATC flow. The great-circle distance is about 440 nautical miles, but procedures and airway routing make the planned distance longer.
Use this structure rather than treating an old route string as fixed:
KJFK – SID/transition – en-route fixes and airways – STAR/transition – KDTW
The SID must finish at, or have a valid connection to, the first en-route segment. The STAR must accept the final en-route fix through a published transition. Load the instrument approach separately once the landing runway is known; an approach is not normally part of the filed en-route route.
A recently used real-world routing can be a starting point, but it still needs validating against the installed navigation data. If an airway no longer contains the entered fix, replace that segment with a planner-validated route rather than deleting fixes until the FMC accepts it.
Choosing a flight-planning tool
The best planner depends on whether you need airline dispatch data, visual route inspection or simple integration with a stock aircraft. Our comparison of simulator flight-planning tools explains the broader differences.
| Planner | Choose it when | Main check |
|---|---|---|
| SimBrief | You want airline-style routing, fuel, payload and export formats. | Confirm its AIRAC data matches the FMC. |
| Little Navmap | You want to inspect airways, terrain, procedures and route geometry visually. | Select the same navigation-data source used by the simulator. |
| Simulator planner | You are flying a stock aircraft and want straightforward native ATC integration. | Check that the aircraft avionics actually received the same route. |
What cruise altitude is best for KJFK to KDTW?
For an airliner, begin by testing an even flight level between roughly FL280 and FL340, then let aircraft weight, winds and performance decide. The sector is short enough that climbing higher can save little or even increase total fuel if the aircraft reaches top of descent soon after levelling off.
| Aircraft type | Planning starting point | Decision factor |
|---|---|---|
| Airliner jet | FL280–FL340 | Use the operational flight plan's optimum and maximum levels. |
| Turboprop | FL200–FL260 | Balance cruise efficiency against a long climb and descent. |
| General aviation | Aircraft-dependent | Respect ceiling, oxygen or pressurisation limits and published minimum en-route altitudes. |
These are planning ranges, not clearances. Online ATC may assign another level for traffic, routing or direction-of-flight requirements.
How do I fix FMC errors on this route?
Most KJFK–KDTW FMC errors come from mismatched navigation cycles, incompatible procedure transitions or duplicate fixes introduced during import. Diagnose the message before editing the route.
| Symptom | Likely cause | Fix |
|---|---|---|
NOT IN DATABASE | The waypoint or procedure is absent from the FMC's AIRAC cycle. | Check the spelling and cycle; use routing available in the aircraft database. |
AWY/WPT MISMATCH | The chosen waypoint is not on that airway in the installed data. | Inspect the airway endpoints and enter a validated segment or an authorised direct leg. |
| Discontinuity after the SID or STAR | The transition does not connect, or the chart contains an expected vector leg. | Compare the chart before clearing it. Preserve a vector discontinuity when ATC is expected to provide headings. |
| Loop or doubled waypoint | The import duplicated a common fix at a procedure boundary. | Remove only the duplicate and recheck nearby altitude and speed constraints. |
| Simulator ATC follows another route | The world-map plan and aircraft FMC are separate. | Load or enter the same route in both systems before departure, then keep them aligned after amendments. |
What if the departure or arrival runway changes?
Keep the en-route core when possible, but replace any SID, STAR, runway transition or approach that is no longer compatible. After making the change, inspect every FMC leg for loops, gaps, incorrect intercepts and lost altitude constraints.
At JFK, a new departure runway may require a different SID or initial climb instruction. At KDTW, verify the complete runway identifier because its parallel runways are easy to confuse, then reload the approach and landing data for that exact runway.
Do not activate a replacement procedure blindly while airborne: some FMCs insert duplicate transition fixes or create a direct leg that bypasses a restriction. Under online ATC, the controller's clearance takes precedence over the generated plan; our JFK online-ATC departure guidance covers clearance copying, runway changes and the airport's complex taxi operation.