I have been puzzling over this for a couple of days now and searched the forum, but still haven't figured out where I'm going wrong on this. It's a simple FMS programming situation that I have checked out on the Toliss A319, but simply can't perform on the impressive FBW A320.

Starting at KBOS with the latest stable version installed and nothing else in the Community folder. I am trying to program the following flight plan to KEWR

PATSS5 PATSS  NELIE FLOSI4  

I download the relevant OFP data from Simbrief, which only gives me the PATSS and NELIE waypoints (as expected), and then enter the departure runway and SID from the FLIGHT PLAN page. No problem. That gets me to NELIE.

Where I run into a problem is the STAR at KEWR. I can enter the the approach (either ILS 4R or ILS 22L) by first selecting the LSK6 key on KEWR. I then enter the FLOSI4 STAR with the NELIE transition. All that does is enter the waypoints on the ILS. The STAR waypoints are completely missing.

Thanks in advance for any thoughts.

If your using navigraph data turn it off and use msfs data only

Edited February 21, 20215 yr by Denwagg

It's still using the default MSFS flight planner which has these quirks like missing nav data even though it's probably in the database.

They are moving to a custom flight planner which is going to take time but I imagine once it's there it will eliminate problems like these.

As a test you should try the same approach on the WT CJ4 it probably won't have that problem as they use a custom flight planner.

I have tried this with Navigraph installed and not installed. Same result.

Thanks for the tip regarding the flight planner. I have tried various other airport pairs and see similar results. I wonder if the problem is that the STAR does not connect with the IAF for the ILS approach. This requires a VECTOR flight plan segment and an unavoidable discontinuity that may not yet be supported. 

6 hours ago, highflyer2020 said:

As a test you should try the same approach on the WT CJ4 it probably won't have that problem as they use a custom flight planner.

Great call!

This works fine on the CJ4, including the insertion of a (VECT) leg between the end of the STAR and the ILS final approach course. I'm sure the team running the FBW project will get there in due time.

BTW, the WT CJ4 is very impressive. Now I know where I'll be spending a lot of time in the coming weeks. 

As an aside, the current sim has a plethora of issues with regards to the STAR. Once inserted, you can't clear any of the waypoints from the FMGS or ND. The LNAV has problems tracking after the IAF and if you have a go around you might as well just call up the tower and give them fuel remaining and souls onboard. 😄

6 hours ago, jrw4 said:

I have tried this with Navigraph installed and not installed. Same result.

Thanks for the tip regarding the flight planner. I have tried various other airport pairs and see similar results. I wonder if the problem is that the STAR does not connect with the IAF for the ILS approach. This requires a VECTOR flight plan segment and an unavoidable discontinuity that may not yet be supported. 

The issues you are describing happen with Navigraph and default data, and I have had similar issues. For now, I think it is pretty hopeless. One of my favorites is when I'm watching the sequence of waypoints in the MCDU and the aircraft just skips a chunk of wayponts and goes directly to the runway. I had one a couple days ago where the sim wanted to turn back to the first waypoint in the flightplan rather than flying the approach. The path in the ND was perfect - nothing funky looking.

the FBW team is creating a custom MCDU to get around this apparently. its not a navigraph issue. its a MSFS issue. You cant delete SIDS/STAR waypoints either. We get all these excuses on what Airbus would approve or not approve from Asobo but we are expected to believe they approved this flight computer that came with the base game that cant even fly a basic STAR without skipping waypoints and turning directly to the airport

When this happens to me, I simply hit "V" to view the VFR map so I can see al the waypoints of the STAR there, even though they're "missing" on the FBWa320 nav display. At some destinations (mostly 3rd party airports), the STAR remains ( I use the MSFS planner) , but other places, they either disappear after hitting "activate approach phase" or disappear if I do nothing. I then simply follow the LNAV using the VFR map and fly the STAR legs using heading mode. If ATC is on the ball, I do what they say with regard to altitude. Having already tuned the ILS freq for the runway I'm going to land on, I then switch the NAV display knob to ILS. Obviously, I hit "APPR" at the "right time" (approach speed, below GS, and on a good intercept Localizer angle).  Can't wait until the FBW team do their magic so auto land works - now and again it would be nice to take screenshots over a wing without having to sit in the cockpit though all the landings. 🙂 Like most auto-land equipped planes, I'd imagine that auto-landing the 320neo requires both Autopilot buttons to be on and both the Captain and FO runway courses need to be set correctly and in synch with each-other.  

Edited June 18, 20214 yr by phantomflyer81
typos fixed