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

In a general flight simulator, KBOS to KJFK is about 160 NM direct and usually longer once procedures are included. In a Boeing 737, expect roughly 45–70 minutes airborne or 1:05–1:30 gate-to-gate. Weather, winds, ATC vectors and New York traffic can move either figure substantially.

How long is a KBOS to KJFK flight for Flight Sim?

For Flight Sim planning, allow 45–70 minutes in the air and about 1:05–1:30 from gate to gate in a Boeing 737.

The shorter estimate assumes an efficient departure, little holding and a reasonably direct JFK arrival. Runway queues, coastal routing, strong winds, vectoring and spacing into New York can add significant time. A turboprop or piston aircraft will need a different estimate.

Which route should I use for a B737?

Use a route generated for the flight with the AIRAC cycle installed in the B737 FMS, rather than copying a static route string from an old flight plan.

A common coastal route family connects a SSOXS departure from Boston with BUZRD, SEY and a PARCH arrival into JFK, broadly represented as SSOXS … BUZRD … SEY … PARCH. The ellipses show that intermediate fixes or airway segments may be present; they are not entries to type into the FMS. Procedure suffixes and versions change, so use only those offered by the matched database.

To obtain a planner-generated route that fits the flight:

1. Select the exact aircraft profile. Choose the appropriate Boeing 737 variant and engine or performance profile. This affects climb, cruise, descent and fuel calculations.
2. Enter the airports. Set KBOS as the origin and KJFK as the destination, then request an IFR airliner route in SimBrief or another flight-sim planner.
3. Match the AIRAC cycle. Select planner navdata matching the cycle shown by the aircraft FMS. An add-on aircraft can use different navdata from the simulator's world map, and the FMS database determines what can actually be loaded.
4. Review weather and likely runways. Use winds, ceilings and approach availability to choose provisional runways. Keep them replaceable if flying with live ATC.
5. Generate and inspect the route. Accept the SSOXS–BUZRD–SEY–PARCH family only if the planner offers compatible procedures and a sensible, continuous track. Another planner-generated route can be equally valid.
6. Select compatible procedures and transitions. The SID must lead towards the first en-route fix, while the STAR must accept the final en-route fix and support the expected runway. Our guide to matching SIDs and STARs to runways and route fixes explains this decision in more detail.
7. Verify the procedures in the FMS before loading the completed plan. Check the DEP/ARR pages for the SID, STAR and transition names. If they are absent, regenerate the route against the aircraft's cycle or choose procedures present in both databases.
8. Load and compare the legs. Check every waypoint, constraint and discontinuity against the operational flight plan. Some import formats deliberately omit procedures, while selecting an imported procedure a second time can create loops and duplicate fixes. Our FMC procedure-loading checks cover the practical sequence.

The route, departure runway and JFK arrival remain provisional until cleared. Live ATC, winds, traffic flow and available navdata determine the final clearance—not a route string printed on a webpage.

KBOS to KJFK in a Boeing 737: route, altitude and fuel planning

For a B737, this is a short sector where a moderate cruise level and early arrival preparation usually work better than a maximum-altitude climb.

What cruise altitude should I use?

FL200–FL260 is a useful initial planning range, with the planner and ATC making the final choice. The south-westerly course generally favours an even flight level for planning, but airway restrictions, traffic and ATC instructions take precedence.

Climbing above about FL300 is often inefficient on this sector. The aircraft can spend much of the flight climbing, reach cruise briefly and then need to descend, losing the fuel and time benefits that a high level provides on a longer route. A lower level may also be necessary when traffic flow or arrival restrictions compress the available descent distance.

When should I prepare for descent into JFK?

Set up the JFK arrival early because top of descent may follow shortly after top of climb.

A useful mental estimate is about three nautical miles for every 1,000 feet of altitude to lose, plus distance for slowing. From FL240, that is roughly 70 NM for altitude alone before allowing for deceleration and STAR restrictions. Review the arrival, approach, minima and expected runway before departure where practical, then monitor the first constrained fix rather than relying only on the simulator's generic top-of-descent marker.

How much fuel does a KBOS to KJFK B737 need?

Obtain fuel from the performance profile for the specific 737 variant, payload, cruise level and weather; there is no reliable generic B737 fuel figure for this flight.

The dispatch calculation should include taxi, trip, contingency, alternate, final reserve and any extra fuel for JFK vectors, holding or runway changes. Check whether the output and aircraft use kilograms or pounds before entering the value. Copying fuel from a different 737 variant—or from another simulator aircraft with a similar name—is a common cause of unrealistic take-off weight or excessive reserves.

Choose an alternate with suitable weather, runway length and instrument approaches, not simply the closest airport. Airports near JFK can share the same low cloud, wind or traffic disruption.

What does TRANS mean?

TRANS means transition: the branch connecting a SID, STAR or approach to another part of the route. On an FMS procedure page, it does not mean transition altitude.

A mistake we see constantly is choosing a transition because its name looks familiar. Instead, select the transition that joins your en-route fix to the assigned runway and arrival without a gap, reversal or implausible direct leg. If no transition makes a sensible connection, the chosen route and procedure probably do not belong together, or ATC intends to provide vectors.

The STAR and instrument approach are separate procedures. A STAR can end at a vector leg or feed several approaches, so selecting the arrival does not automatically complete the route to the runway. Use the published chart to verify fixes, altitude restrictions and speed limits; our guide to checking SID and STAR charts in a simulator explains what to inspect.

Why does the KBOS to KJFK route break in the FMS?

Most route failures are caused by mismatched navdata, duplicated procedures, an incompatible transition or an intentional vector discontinuity.

• NOT IN DATABASE appears: the planner and aircraft probably use different AIRAC cycles, or the procedure has been renamed. Use the aircraft cycle and generate the route again.
• The route doubles back: check whether the imported plan already contained a SID or STAR before selecting it manually. Remove the duplicate procedure rather than deleting isolated fixes at random.
• A discontinuity follows VECTORS or MANUAL: this may be intentional. Do not close it unless the assigned approach or ATC instruction provides a valid next leg.
• The route jumps directly from departure to arrival: the import format may have omitted the en-route segment or failed to recognise an airway. Compare the LEGS page with the planner output and enter the missing fixes in order.
• ATC changes the JFK runway: replace the approach and, where necessary, the STAR or runway transition. Recheck every downstream altitude, speed and discontinuity before executing the change.
• The B737 cannot meet arrival constraints: descend earlier, plan a lower cruise level or reduce speed sooner. On this short route, waiting for a late geometric descent point can leave too little distance to slow and descend.

If the planner output and aircraft disagree, the aircraft database controls what can be loaded, while the ATC clearance controls what should be flown.