Fsbuild-2 Flight Planner

I have a question regarding the Navigraph AIRAC updates for v1.7. Are they supposed to come with complete arrival procedures, or are we to expect to find some that are not in the database correctly? As an example, I flew an approach to Leipzig-Halle (EDDP) the other night, with LUKOP as the last fix on my route. The airport was landing to the west, so I selected the LUKOP 1W arrival. The chart I was using (which may be out of date) shows a simple arrival path from LUKOP direct to GOBAX, which is an IAF for the west approaches. However, when I looked at the Legs page on the FMC after selecting the arrival, it showed LUKOP, followed by a route discontinuity, followed by what I assume was the final approach fix for the ILS approach I had also selected. I had to manually enter the GOBAX intersection and clear the discontinuity.

In my case, it was a simple matter of adding in a single fix. I am just wondering if I should expect to find more arrival (and departure) procedures like this that are missing some or all of the fixes on the route, or if this is just an anomaly in the navdata supplied by Navigraph.

I have seen this and was going to wait and test more before posting, however, as you have started the discussion, here is what I have seen:

> Adding an approach in the Smiths will load that approach but will not change the list of STAR approaches to reflect the runway chosen.
> Adding the correct STAR subsequently will have the effect you have seen, where some waypoints are lost.
> Selecting the runway only in the Smiths gives the right STAR list so you can select the correct one. After that, if you go to LEGS as activate that then you can go back to the APPR page and now select the approach phase (ILS VOR whatever) and it will load correctly without discontinuities... This method seems to work for me...

As an aside:
> Manually removing the 'MAP' tags from the missed approach procedures in the data will cause the ISG1 gauges to also show the missed approach waypoints - however, beware using VNAV beyond the FAP as the altitudes may be somewhat messed up!

Geoff

You have to select the runway.

In the previous Navdata when the entire Star was listed as belonging to a runway each waypoint was not given a runway, as it was superflous , so if you selected a STAR it you got all the waypoints.

In the the new Navdata from Navigraph it often does redundantly specify what runway each waypoint belongs to even when the entire STAR is assigned to a certain runway. So if you select a STAR from the menu with no runway selected any waypoint specified to belonging to a runway in the Navdata is not selected by the FMS.

So just go back, select the arrival runway then select the same STAR again.

Regards.
Ernie.

Ah, that does sort of make sense. Kind of tricky with some arrivals though. Some arrivals start 200+ miles from the airport and you may not know what runway to expect by the time you begin the arrival route.

I'll just have to remember to scroll all the way through to select the runway first, then do my usual selection of STAR and Approach procedures.

Ernie,

I noticed that the AIRAC data for STARs into KLAX has (the correct) additional data on crossing altitudes. However, this data is not being picked up by the FMS. It would be valuable if this could be read by the FMS and automatically fed into the flight plan waypoint data.

Regards

Shez