Plan a realistic KBOS to KJFK simulator flight with route structure, SID/STAR choices, cruise altitude, fuel, navdata and FMS checks.
In a general flight simulator, plan KBOS to KJFK as a short IFR flight: match the planner and aircraft navdata, use weather to choose runways, connect a suitable Boston SID to a JFK STAR, then check altitude, fuel, constraints and route discontinuities. Avoid fixing the procedures before winds or ATC are known.
What KBOS to KJFK route should I use?
The best KBOS–KJFK route is the one generated for your aircraft, weather and matching AIRAC cycle, not a frozen route string copied from an old flight.
Boston Logan to New York JFK is roughly 160 nautical miles direct, although procedures and traffic routing make the flown distance longer. For jet planning, one representative coastal route family is SSOXS … BUZRD … SEY … PARCH, using the active SSOXS departure and PARCH arrival versions available in the navdata.
Treat that as a route shape rather than a guaranteed clearance. Procedure numbers change, runway assignments matter, and a planner may produce another valid route. If those fixes or procedures are absent from matched navdata, do not force them into the FMS; generate a fresh route or use our guidance on finding and assessing real-world simulator routes.
The STAR and instrument approach are separate parts of the plan. A JFK arrival may end at vectors or an approach transition, after which you still need the assigned ILS or RNAV approach and runway.
How do I build and load the flight plan?
Build the en-route core first and keep the departure, arrival and approach replaceable until the weather or ATC assignment is known.
- Select the aircraft and IFR planning level. Use a high-altitude profile for an airliner, a lower airway profile for a turboprop or piston aircraft, and the correct performance model for fuel calculations.
- Match the navdata. The planner, simulator and aircraft FMS should use the same AIRAC cycle where possible. A cycle mismatch is the main reason a valid-looking SID, STAR or waypoint produces
NOT IN DATABASE. - Check airport weather. Review KBOS departure winds, KJFK arrival winds, visibility, ceilings and forecasts before choosing runways. Our weather-chart planning guide explains how these affect routing, altitude and alternate selection.
- Generate the IFR route. Enter
KBOSas the origin andKJFKas the destination, then calculate the route with the correct aircraft profile. Our step-by-step SimBrief workflow covers route generation, fuel and operational flight-plan output. - Add anticipated procedures. Select a runway-compatible Boston SID and a JFK STAR that connects naturally to the en-route fixes. If flying with live ATC, regard these as provisional until cleared.
- Inspect the route map and vertical profile. Look for sharp reversals, duplicated fixes, impossible altitude constraints and a STAR that fails to connect to the selected approach.
- Transfer the plan once. Import it through the simulator or aircraft integration, or use our GPS and FMS entry procedure. Importing procedures and then selecting the same procedures again manually often creates loops and duplicate waypoints.
- Brief the short sector. Confirm the first altitude, initial lateral mode, expected arrival, approach frequencies or minima, and the point at which descent preparation must begin.
What cruise altitude works for KBOS to KJFK?
A moderate cruise altitude usually works better than climbing as high as the aircraft can go because this route provides little time at level flight.
| Aircraft type | Useful planning range | Main consideration |
|---|---|---|
| Airliner jet | FL200–FL260 | Higher levels may leave almost no cruise segment before descent. |
| Turboprop | 12,000–18,000 ft | Balance airway minimums, winds and pressurisation. |
| IFR piston | 6,000–10,000 ft | Check airway minimums, icing, cloud and aircraft equipment. |
These are planning ranges, not clearances. The south-westerly magnetic course normally favours an even-thousand IFR altitude under US direction rules, but published minimum altitudes, airspace and ATC instructions take precedence.
When should I start the descent into JFK?
Prepare for descent soon after levelling because a jet at FL240 may need around 70 nautical miles just to lose altitude on a three-degree path.
A useful estimate is three nautical miles per 1,000 feet to descend, plus extra distance for slowing and meeting STAR restrictions. Do not wait for the geometric descent point if the arrival imposes an early speed or altitude constraint.
How much fuel and which alternate should I plan?
Fuel should come from the selected aircraft’s performance profile and include taxi, trip, contingency, alternate, final reserve and any extra allowance for vectors or holding.
Do not copy a fuel quantity from another aircraft, even if it flies the same route. The difference between a regional jet, narrow-body airliner and turboprop is too large for a generic figure to be useful.
Choose an alternate with suitable weather, runway length, approach capability and fuel distance. Nearby New York airports may share JFK’s weather and traffic disruption, so the closest airport is not automatically the best alternate.
Why does the route break in the GPS or FMS?
Most KBOS to KJFK route failures come from mismatched navdata, duplicated procedures or an arrival transition that does not connect to the selected approach.
- A procedure is missing: regenerate the plan using the aircraft’s AIRAC cycle or substitute a procedure that exists in both databases.
- The route doubles back: check whether the SID or STAR was imported and then selected a second time. Remove the duplicate procedure rather than deleting individual fixes at random.
- A discontinuity follows
VECTORSorMANUAL: this can be intentional. Close it only when the planned or assigned approach provides a valid connection. - ATC changes the JFK runway: revise the STAR transition and approach, then recheck every altitude and speed constraint downstream of the change.
- The aircraft misses descent constraints: reduce the planned cruise altitude, begin down earlier or use the FMS descent forecast rather than relying solely on the simulator’s generic top-of-descent marker.