RJOO SID ASUKA4 errors at PMDG 777

[DLP084 5]

Hi, 

 

there is no other solution as to live with those intercepts with turns over 180 degrees. 

At the moment the limited PMDG syntax doesn´t allow CF (course to fix) or CI (course to intercept) legs with turn directions.  

 

The only realistic way to get them flown in proper way is as follows:

 

1. Use HDG select and turn manually with the mandated turn direction onto the INTC heading (left 071).

 

2. When established on INTC heading (071) select DCT to FIX (ASUKA) and use INTC CRS function to enter the course (101) to the fix (ASUKA)

 

2.1. If the intercept is going into between two waypoints. A PBD fix along this line could be created to avoid long course to fix legs. 

 

comment to Mystery 2:

 

that is against the intention of the ARINC 424 source, as the A/C arrives at ASUKA and does a left turn back to ASKUKA again. 

 

Translated to ARINC 424 Path Terminators this would read as follows:

 

CA 332°  +500ft - VI (L) 071 - CF 101° (ASUKA) - DF (L) ASUKA + 5000

 

But PMDG is actually doing the following when flying that coding:

 

It skips HDG 071 INTERCEPT RADIAL 101 TO FIX ASUKA and does TURN LEFT FIX ASUKA

 

So thats nothing else than:

 

RNW 32L TRK 322 UNTIL 500 TURN LEFT DIRECT FIX ASUKA AT OR ABOVE 5000

 

which in fact ignores the 101 Radial

 

 

The only way to solve such issues permanently without pilot intervention is, if PMDG develops a new format that handles all the details that are incorporated in the ARINC 424 Path Terminator language. 

 

For more reading about path terminators have a look here:

 

http://www.keilir.net/static/files/Flugakademian/PDF/rnavmanual-kka.pdf

[xpdevs 1]

As this is a conventional procedure, I would just fly the initial climbout on raw data and let the FMS take over once the discrepancy no longer exists.

[NAVData 24]

As this is a conventional procedure, I would just fly the initial climbout on raw data and let the FMS take over once the discrepancy no longer exists.

 

But honestly, the developer tries to make the a/c so realistic as possible - power-settings, aerodynamic, systems, ... but you can´t rely on that the a/c flies the path correctly which is shown on the ND? We know (an Jan-Paul had explain it excellent - thank you), that this is a "design-issue" in the procedure files and/or a "design-issue" in the navigation part of the PMDG addons - as an example: Aivlasoft use the same file format as PMDG, but the procedures there shown correctly (left turn and without any additional circles):

 

RJOO - 32L / ASUKA4

 

Cheers,

Richard

[jango 0]

Hi all,
 

Thanks for all your reply and Advice.
 

I have received a message directly from PMDG that they will discuss these different results between NGX and T7 with their programmer.
 

I hope that I can tell a new positive message next time.
Or maybe get a results directly from PMDG here ?

 

Thank you, PMDG
 

regards
 

Kazuo