G3000 planning goes well - having difficulty adding (pre-flight) the selected approach. Issue is - the approach waypoint sequence is starting with (typically) a VOR - or some other “close to airfield” waypoint - then sequence routes back out to the IAF or further to do a 180 turn to finally enter the correct ILS or RNAV waypoint sequence. I have tried KSAN using the Shamu arrival, and also KMLB using the Bithlo arrival. After a dozen tries - everything looks perfect with flightplan / airway enroute, arrival transition selection, but, when I add the approach - it directs the sequence to start with the erroneous VOR or “interior” waypoint before sequencing me back out to the IAF ? What am I missing - ??
One other way to alleviate this is to plan an approach in advance and ensure there is a waypoint as close to the transition (or in the case of a direct, the IAF), so the U turn occupies as little time and distance as possible. This won’t get fixed until WT refreshes the G3000 to NXi standards.
They may have filed the Arrival and Approach in advance? Not sure. Or there’s a different workaround where you switch to HDG and set a course for the Transition, then switch to APR once there.
Many of the arrivals in the US terminate at a waypoint not on any approach. The arrival states something like “Radar vectors to approach/runway”. Basically, the “radar vectors” are a gap between the arrival and the approach. The MSFS default flight planning cannot have these gaps so it puts in “fake” vectors causing strange things to happen like flying out and back to the IAF.
Before takeoff, I check the flight plan in the FMS for duplicate waypoints. I then delete the 1st duplicate waypoint and all the waypoints up to the 2nd duplicate. This should prevent the “flyback” you are seeing.
There are other anomalies with certain SIDs, STARs, and approaches that cause weird flying of flight paths. Always check the FMS flight plan with your SIDs, STARs, and approaches. Also, if entering an approach into the FMS while enroute, make sure you haven’t flown past the IAF…
Understood. I tried deleting the “unwanted” inserted waypoints, to have the approach sequence match my arrival / approach transition. On my system - ha - it deleted the entire approach - poof ! Tried it several times. Understand also - option for now - fly the arrival, switch to HDG before the last arrival waypoint, then use D > to the correct IAF to start the approach - being careful to select the “right” IAF - not the preceding duplicate that places you in the U-Turn procedure.
Flying a relaxed flight now - just eliminated the “arrival” and entered the arrival waypoints in the flight plan. Upon loading the approach - all looks good - no U-turn or duplicates in the flight plan.
I assume with D> you mean a “direct to”? If you do this it (usually) deletes the approach or flight plan as active source, maybe leaves it stored in the background. If you want to fly a direct to and then continue with the planned route/approach you need to set the DTO function to plan or FPL or whatever it’s called in the G3000 before you confirm it.
Note that this is the way how a Garmin usually works, it’s not necessarily how the G3000 in the SIM works I have never really used the G3000.
I have never really used the G3000.