NavDataPro Transition

[Qowy 0]

Hi, is there something wrong with the transitions in Nav data pro. Had the problem with EDDH and now checked it at EDDF:

Nav Data pro PSA25S RNAV transition:

With Navigraph (after clearing duplicate entries...):

[hud635jk 102]

I can confirm this.

And it is not a NavDataPro issue. It also happens with Navigraph.

Did 2 flights yesterday:

EGGD -> EGPH

ILS06

Transition: TLA

LGIR -> LGAV

ILS03L-Z

Transition: KEA

Attempted the same approach-transition today (LCLK -> LGAV). I got the same thing (a semi-circle) on the ND (flightplan mode). And I know from yesterday, that this is not just a cosmetic glitch on the ND. The aircraft does indeed fly this weird path, unless NAV mode is disengaged.

This seems to happen always when all the following conditions are met:

- the route does not pass directly, but very closeby, to the previous waypoint from the FAF (final approach fix)

- the turn very close (but not above) this previous waypoint has to start when a certain radial-heading from the FAF (or some other fix) is intercepted

The aircraft, instead of starting the turn towards the FAF when the radial-heading is intercepted, it continues straight ahead, passes over the previous waypoint, and then executes a semi-circle whose diameter is defined by the previous waypoint and the FAF

So it seems, that there is a very serious problems with interception waypoints.

This is very serious. It is critical.

I am surprised how they missed that with so many hundreds of manhours of testing, during all these months.

Here are the pictures:

In each case (first EGPH then LGAV), what the aircraft should do, and what it does instead:

[cbd80 258]

Hi Guys.

Just to let you know that these issues are being looked into by the developers.

[Jean Marc 0]

Got one Question:

I've got NavData Pro, I got AEX and downloaded the ACARS file for it thru Aerosoft Servers, but I only have appearing choice in FMC SID and STARS, no TRANSITIONS, so how do you manage to get them ?

[PeterW 23]

so how do you manage to get them ?

Just click on "VIA" when you select the SID.

[Jean Marc 0]

Thank you for this light, PetreW

[hud635jk 102]

I can confirm this.

And it is not a NavDataPro issue. It also happens with Navigraph.

Did 2 flights yesterday:

EGGD -> EGPH

ILS06

Transition: TLA

LGIR -> LGAV

ILS03L-Z

Transition: KEA

Attempted the same approach-transition today (LCLK -> LGAV). I got the same thing (a semi-circle) on the ND (flightplan mode). And I know from yesterday, that this is not just a cosmetic glitch on the ND. The aircraft does indeed fly this weird path, unless NAV mode is disengaged.

This seems to happen always when all the following conditions are met:

- the route does not pass directly, but very closeby, to the previous waypoint from the FAF (final approach fix)

- the turn very close (but not above) this previous waypoint has to start when a certain radial-heading from the FAF (or some other fix) is intercepted

The aircraft, instead of starting the turn towards the FAF when the radial-heading is intercepted, it continues straight ahead, passes over the previous waypoint, and then executes a semi-circle whose diameter is defined by the previous waypoint and the FAF

So it seems, that there is a very serious problems with interception waypoints.

This is very serious. It is critical.

I am surprised how they missed that with so many hundreds of manhours of testing, during all these months.

Here are the pictures:

In each case (first EGPH then LGAV), what the aircraft should do, and what it does instead:

An update on this with v1.03:

Behavior is better, but still not the correct one:

1. The user is still not presented with the approach transitions (in this case KEA, EGN, PELAG etc.) to choose from. (however, perhaps it is selected automatically based on the final fix of the selected STAR - here it was KEA and it was properly selected)

2. This is what the aircraft does in v1.03: (in 2 different zoom levels for clarity):

Instead of setting a course of 265 from KEA, and then having to do two successive turns based on different radial interception each:

it ignores all this completely and flies directly to the CI03L fix (it is the D11 SAT fix on the Navigraph chart).